|
|
 | | Re: More LDRAW renderings
|
| (...) I am using two fill lights on both sides of the castle with values 0.5*<1,1,1> and the front light has a value of 2*<1,1,1>. That's why the shadows are so hard. Next time i'll try area lights... (...) I am using the tomtree.inc. You can find (...) (24 years ago, 2-Apr-00, to lugnet.cad.ray)
| | | | | Re: More LDRAW renderings
|
| (...) the shadows are a bit hard. Perhaps you could use area lights to make them softer. This will seriously increase the rendering time, though. You could also try to add a few fill lights, but this will also increase the rendering time, I'm (...) (24 years ago, 2-Apr-00, to lugnet.cad.ray)
| | | | | More LDRAW renderings
|
| Castle Siege at: (URL) Time: 11 hours 52 mins on my PIII/450 with 256MB Ram. I'll post more pictures of the castle as soon as rendering finishes ;) Enjoy! George (24 years ago, 2-Apr-00, to lugnet.cad.ray) !
| | | | | Re: '59 Caddy Hovercar Raytraces
|
| (...) What kind of texture did you use for the chrome pieces, BTW? In my opinion, it has a tad bit too much reflection. I can't see that the parts are silver, I only see the reflection of the environment in them. Also, did you try to add a (low key) (...) (24 years ago, 2-Apr-00, to lugnet.space, lugnet.build, lugnet.town, lugnet.cad.ray)
| | | | | Re: '59 Caddy Hovercar Raytraces
|
| (...) Thanks! (...) I wish...(well, not really. The only thing I could build with pink bricks is Cadillacs :) They really can't be any other color...) You'll notice that the MPD file is in the colors I actually built the model--white. --Bram (24 years ago, 2-Apr-00, to lugnet.space, lugnet.build, lugnet.town, lugnet.cad.ray)
| | | | | Re: '59 Caddy Hovercar Raytraces
|
| (...) Wow, a blast from the Future that Never Was. Very cool. Where's the robot Elvis, though? Oh, and how do you get your models to float? <grins, ducks and runs> ++Lar (24 years ago, 2-Apr-00, to lugnet.space, lugnet.build, lugnet.town, lugnet.cad.ray)
| | | | | Re: '59 Caddy Hovercar Raytraces
|
| (...) front down to the huge trunk. Now, where can get that many pink bricks? ;-) Cheers, - jsproat (24 years ago, 2-Apr-00, to lugnet.space, lugnet.build, lugnet.town, lugnet.cad.ray)
| | | | | '59 Caddy Hovercar Raytraces
|
| Here are some pics of my hovercar: (URL) LMKWYT! --Bram (24 years ago, 2-Apr-00, to lugnet.space, lugnet.build, lugnet.town, lugnet.cad.ray)
| | | | | Re: L3PLiTE?
|
| (...) I think this is a little too much for the task, you don't need to try to remove the interior too, it won't make a big difference. Think of a 2x2 plate, if you can remove the stud4, you're saving 48 quads, 64 lines and 32 optional lines while (...) (24 years ago, 30-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) In this case you could leave out the interior of the 2x2, but you must use the entire top of the 4x4. In the case of solid wall like structures, however, it could reduce 90% of the blocks to no interiour, and no studs. -Chuck (24 years ago, 30-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Tore Eriksson wrote... (...) Uh, maybe. However, if you have a 2x2 brick on top of the 2x4, how do you leave out only half the TOP section? Or you wouldn't? Maybe parts should be broken into subparts for analysis? I think the main problem is, that (...) (24 years ago, 30-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| John VanZwieten wrote... (...) A general analyzer may be a good idea. As you say, the optimized .dat file can be viewed in any rendering engine, and also, you can run L3P on it. Of course, the analyzer could be compiled into L3P, L3Lab, LDLite etc. (...) (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Leonardo Zide wrote... (...) I assume you have manually added extra info to all parts into your pieces.bin. Is there any chance you could export that info into some META commands to be inserted into each part in the LDraw PARTS base, so LDraw (...) (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) It does take some extra time to load a big file but the speed increase later is well worth it. After doing the initial calculations, you only need to check the studs for the bricks you move so it's very fast. Leonardo (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Leonardo: (...) So in "every" part you have put a "stud-slot-point" in all the places where a stud from another part can connect with this part. So if a stud on a non-transparent part is at the stud-slot of another non-transparent part, it is (...) (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) Basically it checks if a stud primitive is close to a "inverted stud" (the cylinders under a plate for example) or to some predefined points added by me and remove them. The original idea was to make the bricks really connect when they get (...) (25 years ago, 28-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Leonardo Zide <leonardo@centroin.com.br> wrote in message news:38DFDCB4.594866....com.br... (...) So what test do you run to determine what studs get removed? -John Van (25 years ago, 28-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) I have done something like that for LeoCAD, it removes the studs above and below the bricks and plates for the rendering. I haven't added this option for the POV-Ray export but that's something that I can do if you want. Leonardo (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) Argh! Didn't think of that... :o/ /Tore (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: LDRAW models and pictures
|
| (...) Of course! Here it is: plane { z,0 pigment { image_map { sys "bushes.bmp" } scale <300,300,1> } normal { bump_map { sys "bushes.bmp" bump_size 10} scale <300,300,1> } finish { ambient 0.2 diffuse 0.2 } rotate <90,0,0> translate <0,140,0> } I (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray)
|
|
