 | | Re: Animation using Datsville
|
|
Also, it would be nice if LDBoxer could replace bricks that have only their bottoms or only their tops covered, as opposed to replacing only those bricks that have both their bottoms and their tops covered. This, however, would necessitate the (...) (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: Animation using Datsville
|
|
There was some discussion a while back about a technique whereby one culls all objects that are not within the field of view. I don't know if this technique was ever created. I don't know if it's possible to get the bounding box of every object, but (...) (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: More Transparency issues (was: "Illusions")
|
|
(...) Not at 6:30am though. :) I think I found my problem. I am rendering at Q1, where filter and transparency values don't seem to make much difference. Taking out all the #if QUAL checks seems to solve the problem, though it's going to make it a (...) (21 years ago, 4-Mar-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: More Transparency issues (was: "Illusions")
|
|
This file renders fine on my machine. I'd say a) Get a clean copy of the Ldraw radisioty file (and, BTW, try rendering without radiosity to see if there is any difference - I doubt it, but hey) or b) Provide your specific color settings (including (...) (21 years ago, 4-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: More Transparency issues (was: "Illusions")
|
|
(...) Just one? I would fill up a few *lines* with question marks if I wasn't worried about leaving some for the rest of you. I tried it again, thinking maybe it was just last night or something. Same problem. So I tried something different: I (...) (21 years ago, 4-Mar-04, to lugnet.cad.ray, FTX)
|
