 | | Re: Radiosity example (F1 Ferrari) once again
|
|
Mine look purhaps abit 'edgy' since I don't like to use the lgeo library. Too many parts are not available and if I combine them with the standard parts it don't look all that good. (2 URLs) first attempt>> This is my first attempt with Nico's (...) (20 years ago, 26-Sep-04, to lugnet.cad.ray, FTX)
|
| |
| | Adjustable paths for parts
|
|
A while ago there was a discussion about user definable searchpaths for parts. In meanwhile MLCad uses this, but how about other programs like L3P? I am using several unofficial files, but I don't want to mess up the P and PARTS folders. Niels (20 years ago, 25-Sep-04, to lugnet.cad)
|
| |
| | Some issues with the newest version of MLCad
|
|
Michael, I recently noticed a couple of things in the newest version of MLCad, which behave differently from the previous versions. I hope you'll consider changing these back to the way they behaved previously. I was working with a file that had a (...) (20 years ago, 25-Sep-04, to lugnet.cad.mlcad, FTX)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
(...) Yours look good as well but the edges seem a little "jaggy". Are you using anti-aliasing? The good news is that Nico's setting are a snap to implement. -Orion (20 years ago, 25-Sep-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: New Part: 3041p01.dat Brick 45 2 x 4 Double With Headlamp Pattern
|
|
(...) 3041p01 is fine, but I like the existing peeron title "Slope Brick 45 2 x 4 Double with Blue and White Headlight Pattern" Please use your real name in the Author: line (...) Not necessary and IMHO undesirable if there are few patterned (...) (20 years ago, 24-Sep-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
Aaaarrghh! I thought my renderings were the bomb (URL) galery>> but now I've seen Nico's pictures, I guess I'll have to start all over! :) (20 years ago, 24-Sep-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: non-lego rendering using various LDraw tools
|
|
(...) I mostly meant that I knew what their windings had to be (because of the way the edges are constructed), but the code isn't aware of it. However, like you say, it's easy enough to find an extreme point and test the winding. Steve (20 years ago, 24-Sep-04, to lugnet.cad.dat.ideas, FTX)
|
| |
| | Re: non-lego rendering using various LDraw tools
|
|
(...) You lost me there. How could you not know which is which if they already go in the opposite direction? Just take a cross product at the topmost point. If it's negative, then it's clockwise and thus a hole. Don (20 years ago, 23-Sep-04, to lugnet.cad.dat.ideas, FTX)
|
| |
| | Re: non-lego rendering using various LDraw tools
|
|
(...) OK. My edges already were counterclockwise. :) Umm, for inside outlines (inlines?) to be clockwise, that's 'clockwise' from a global view, right? If so, then my inlines are already clockwise. But I don't know which ones are inlines, and which (...) (20 years ago, 23-Sep-04, to lugnet.cad.dat.ideas, FTX)
|
| |
| | Re: non-lego rendering using various LDraw tools
|
|
(...) Err, reverse course. I peeked at the autotrace source and it says in pxl-outline.c "Outside outlines are traced counterclockwise". So if you want to make things easier for me, do it that way. ;^) (...) (20 years ago, 23-Sep-04, to lugnet.cad.dat.ideas, FTX)
|
