megalodon opened this issue on Jun 22, 2000 ยท 8 posts
megalodon posted Thu, 22 June 2000 at 9:23 PM
I hope that this is a simple (not simple-minded) question that has a (relatively) easy answer. We've downloaded the beta for Vue3 and think it's very good. We've tried World Construction set and World Builder and Vue3 (aside from being cheaper) is extremely intuitive and provides great renders. My question is this: When importing LightWave objects with boolean cuts - the boolean cuts don't appear in Vue3. Is this a problem with Vue3 and LightWave or is there something we are missing? Any help would be (more than) greatly appreciated! Thanks!
tesign posted Fri, 23 June 2000 at 8:18 AM
Can't help much here butI am not sure about using Lightwave objects with boolean cut. Earlier version of Vue does has limitation with terrain being boolean. When you have two terrain boolean to create a cave, you get weird result but doing it with primitive is okay. Talking about it, have yet to try with the newer beta version. As you have only the demo version, may be writing to e-on would get you a more definite answer. Bill
silverbranch posted Fri, 23 June 2000 at 9:45 AM
Megalodon, If there are any objects like that on the web you can point me to, Id be happy to try it with 3.1 and see if it works. Gail
Fyg posted Fri, 23 June 2000 at 12:10 PM
I import booleaned lightwave objects into Vue with no problem. Sometimes when you boolean, say, X object minus Y object, Y's surface might end up on X where it sliced into X. This might cause the booleaned area to not show up. Whatever the case, if you resurface the object after the boolean, that should care of whatever the problem is.
bloodsong posted Fri, 23 June 2000 at 12:14 PM
heyas; i'm not sure how lightwave works; if it makes true booleans or 'proceedural' booleans. vue makes proceedural booleans. that is, you still see both objects fully in your scene in vue, they are only subtracted/cut when you render. if you put two objects together in lightwave, and the 'boolean-ed' version of that object still has both objects' mesh, then it would not import into vue as the cut mesh. you would have to perform a vue boolean operation on the two objects. ya know? it sounds like fyg knows, and you have to do something in lightwave before you export a booleaned object, to get it to be one new object.
megalodon posted Fri, 23 June 2000 at 4:07 PM
My THANKS(!) to everyone for responding. One of the guys I work with (and is also interested in buying Vue3) was testing a few different methods and found out that by simply subdividing the pologons in Lightwave before importing them into Vue 3 solves the problem. The initial problem must lie with how Lightwave creates polygons. I do have one more question. When importing several different objects separately that make up a whole (such as a house; door, roof, walls, etc.) Vue3 won't place them as they were situated in Lightwave - I think it puts them at a center point. Aside from moving them around in Vue3 or making one large object in LW, can anyone think of a workaround? Thanks Again!!!
silverbranch posted Fri, 23 June 2000 at 4:29 PM
Hi there, While I don't know this for sure, there is an option (under File...Options...) to "resize and center imported objects". I would try unchecking that and see what happens. Gail
megalodon posted Fri, 23 June 2000 at 10:49 PM
Thanks Gail - and everyone else! I think we're going to buy Vue3 and give it a try. Fortunately it's not nearly as pricey as World Builder or World Construction Set so we can (somewhat) afford to buy and really test it. I (and we) really do appreciate the responses. It's good to know alot of people "out there" work with this program and are open to giving advice and help. Thanks!!!