I just took one of our medium size models, and published it with defaults for tile size (200) and image size (256).
The reults were essentially useless. The surface was way dumbed down and image was super resampled.
The help: does not mention the ranges of values possible.
Two things scare me a bit about this publishing:
1) is my surface being converted to a grid of points whose dist between is the tile size (in meters the help says)?
that would be very bad
2) I happen to know the texture size limit, 4096, from experience with visualizations. My models will take hours to publish if this is the case, and AIM uses 100% of my 4 cores. That basically means I can only publish at night.
Seems like something needs to be done to make that practical.\
The online viewing in IE is excellent. Good job on that Autodesk, this is something I've been waiting for ever since the RDV guys started their efforts years ago. Their viewer was skittish, but yours is great first time out.
Do a really small area using the scenario limits (the new polygon limits tool is awesome - it makes things so much easier, you can also import a shapefile with the limits) and then try all different combinations of TIle Size, Texture Size, and LOD for your model and take a look at the resultant folder after you start increasing these. There is a point when the folder size stops growing. I wish I had my data. I created like 20 different scenarios until there is no noticeable difference in the output so that I could find my upper limit. I think my texture size limits was 2250. I had all these in 2012 using the Labs scenario tool and I can't get back to them after I upgraded my model I guess.
I might like to hear from Autodesk on my 4096 upper limit for images. It may be that they detect my orig image resolution, and do not resample above that for their tiles.
I do not get the tile size number at all though. I do not believe they are dumbing down the surface to a grid of points, so that tile size seems arbitrary. Then to throw in LOD, you could go crazy.
I do love the incompatibility with R2, would not matter except for the complete uninstall and reinstall involved.
My high resolution test crashed 30 minutes in, got a CER dialog and a poof its gone experience.
I then ran my "clean temp folders" batch routine as I always do after a crash, and it found a lot of stuff.
That code is useful if anyone wants, put in a clean temp.bat file:
del /Q "C:\Temp\*.ac$" attrib "C:\Temp\*.dwt" -h del /Q "C:\Temp\*.dwt" del /Q/S "%temp%\*.*" del /Q "%userprofile%\CustomCUIs\2009\*.mnr" del /Q "%userprofile%\CustomCUIs\2012\*.mnr" del /Q "%userprofile%\Desktop\*.bak" del /Q "C:\CAD_SUPPORT\A2009\Menus\*.mnr" del /Q "C:\CAD_SUPPORT\A2012\Menus\*.mnr"
I kill mnr's as they can crash acad if mismatched with a menu.
I think I am, my model is local if that's what you mean.
I did put one model on the web, but if I go to work on it, it must download to local anyway.
Must I publish a scenario to the 360 site to view on the web, or is there a way around?
um, wow, I missed that.
The wiki help system sure did not make it clear.
thanks a bunch!
The Texture Size is what any raster/image data is resampled down to.You can use a maximum value of 2048, and it needs to be a power of 2 (i.e., 256, 512, 1024, 2048) otherwise the textures won't show in the iPad app.
By increasing the texture size, you increase the chance of "out-of-memory" issues on the iPad. In this case, reducing the Tile Size should help because then "less 3D" needs to be put into memory at a time.