Francois Levy Posted March 11, 2007 Share Posted March 11, 2007 I can't seem to control the relative size of my model with respect to the overall window size when exporting a QuickTime VR object movie. No matter what I select or what page size I designate, I get a relatively small model with a lot of white space. As a result even if I zoom whilst in the QT player, the model is fairly low-res, but the QTVR movie is still pretty large. I'm paying a lot of file size overhead just for white pixels. Any ideas how I can control this? Quote Link to comment
islandmon Posted March 12, 2007 Share Posted March 12, 2007 You need to create an invisible 3d polygon ( a circle with radius within the model iso-dimensions works best ) and make sure that it is selected. Create VMRL-Poly & VRML-Lites Layers...then Layer Link them with the VRML-Poly layer linked last and therefore shown as selected ... the radius of the 3dPoly controls the dimensional extent of the VRML export and therefore the final resolution based on 72dpi. Quote Link to comment
Dave_Donley Posted March 12, 2007 Share Posted March 12, 2007 Hello Francois: Islandmon is right, or just set both the fill and line styles to None so it is invisible in the rendering. Quote Link to comment
Francois Levy Posted March 12, 2007 Author Share Posted March 12, 2007 Great, thanks Islandmon very much for the help. I'll give it a shot. Not sure I follow the logic of using layer links in this case, but I'll play around with it. BTW, Dave, is the 3D poly a documented tip? I don't notice it in the manual... Quote Link to comment
islandmon Posted March 12, 2007 Share Posted March 12, 2007 The logic of the Layer Link is basically a protocol: Do not corrupt a model with extraneous elements which are not part of the model Layer space. And set-up project parts to be re-useable whenever possible. _____ Also, the over all size of the VRML depends on the size of the display window. So shrink the display to a reasonable size and re-center the image in the window. Quote Link to comment
Francois Levy Posted March 12, 2007 Author Share Posted March 12, 2007 I understand the logic of layer links in general; was wondering whether layers of the specific names you provided and layer links were required in this particular application. I also tried the 3D poly and it seems to have made no difference. It may be that my model elevation (about 450' above z=0) may be contributing to the problem. Quote Link to comment
Francois Levy Posted March 14, 2007 Author Share Posted March 14, 2007 I've tried adjusting the model to be centered (0,0,0) on the page, selected a circular 3D poly, changed the active layer scale, changed page size. None of these measures make any difference whatsoever; all QTVRs (not VRMLs BTW) come out the same: small model, lots of white space. Any other suggestions? Quote Link to comment
islandmon Posted March 14, 2007 Share Posted March 14, 2007 Um ... interesting problem... http://www.fractalnet.org/CAD/CAD_LevyCube.mov Quote Link to comment
islandmon Posted March 14, 2007 Share Posted March 14, 2007 Here's a sample .mcd file and mov ( 350k ) showing the process: http://www.fractalnet.org/CAD/CAD_VRML_Levy.zip Quote Link to comment
Francois Levy Posted March 14, 2007 Author Share Posted March 14, 2007 Thanks for the effort! I do feel a little dizzy spinning around in that cube. Can yo let me out now? The extruded circle you use does in effect define the boundaries of the model, but that cuts both ways. In the sample file you included, removing the 3d circle enlarges the model. I thought my particular problem might have been in having objects (both 2D and 3D) in invisible classes, but even after removing everything the model still renders with heaps of white space. Dave, if you are monitoring this, may I send you the file? Quote Link to comment
Francois Levy Posted March 14, 2007 Author Share Posted March 14, 2007 Ah I think I go it. By making the 3d circle somewhat SMALLER than the model, and selecting the 3d circle ONLY (two important details), I've managed to export a view of the model with little white space. My guess is that as with static exports, VW adds white space automatically. Thanks Islandmon for leading me to this. Dave, may I request better documentation on this procedure in future manuals? Shall I cross-post to Wish List? Quote Link to comment
Dave_Donley Posted March 14, 2007 Share Posted March 14, 2007 Hi Francois: I'll forward this info so it goes into the manuals. Sorry for the trouble. Quote Link to comment
Francois Levy Posted March 14, 2007 Author Share Posted March 14, 2007 No trouble at all--it's fun to figure things out. It's little tricks like this (and 2d polygon clipping in DTMs, to name another) that make the program sing in the right hands; if these functions are documented then everybody benefits. And thanks for monitoring! Quote Link to comment
islandmon Posted March 14, 2007 Share Posted March 14, 2007 Glad you got it worked out ... Did you notice any differences between the 2 LevyCube examples posted ? Quote Link to comment
Francois Levy Posted March 14, 2007 Author Share Posted March 14, 2007 Well sure. I like the blue background and slow spin on the first one. Quote Link to comment
islandmon Posted March 14, 2007 Share Posted March 14, 2007 Example #1 was created in less than 30 sec. with the new Quartz Composer which utilizes the graphics card processor... the file is only 16k. Whereas, #2 @ 176k and 25% smaller image was created using the main processor by VW export . Quartz Composer is free with Tiger. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.