|
|
 | | 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)
| | | | | Re: L3PLiTE?
|
| Tore Eriksson <tore.eriksson@mbox3...wipnet.se> wrote in message news:38DE84F4.380C9D...pnet.se... (...) only those standard bricks, plates, and tiles (...) could be a way to free up some resources for (...) somehow, and I don't know exactly how (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) colour < 47) ), interior can be skipped. Of course you mean above the lower edge relative to the parts current orientation. That would require taking the transformation matrix into account. -Chuck (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) For basic bricks, slopes, plates and tiles, one could simply remove the studs and then make the simplified part as the bounding box of what remains. This could probably be automated. If one want more details, the studs could be added again (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Problem with primitives?
|
| I've been screwing around with some part authoring, and I give a big Thank You to Lars Hassing for L3Lab and L3P, both of which have made proofing much easier than rendering and rerendering and rererendering in LDraw. However, I notice that on one (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray)
| | | | | Re: L3PLiTE? [DAT]
|
| (...) You mean something like: 0 Brick 2 x 4 0 Name: 3001.dat 0 INTERIOR BEGIN 1 16 20 4 0 1 0 0 0 -5 0 0 0 1 stud4.dat 1 16 0 4 0 1 0 0 0 -5 0 0 0 1 stud4.dat 1 16 -20 4 0 1 0 0 0 -5 0 0 0 1 stud4.dat 1 16 0 24 0 36 0 0 0 -20 0 0 0 16 box5.dat 4 (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Tore Eriksson suggested... (...) IMHO this should not be limited to POV. If the simple parts were made in LDraw syntax, you could speed up Datsville in L3Lab (and others viewer) too! See also (URL) about finding those parts suitable for replacment, (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | L3PLiTE?
|
| How about making a library of very simplified standard pieces and replace only those standard bricks, plates, and tiles that are not clear and have no studs or bottom visible? I know there are some difficulties yet to be overcome, but I think this (...) (25 years ago, 26-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: LDRAW models and pictures
|
| (...) Sounds similar to the box I made for set 6888[1]. I created three sides, and added a fourth side that wasn't visible so the shadows would look right. (...) Could you post a code sample? (only to cad.ray, please) --Bram 1) (URL) Lambrecht / o o (...) (25 years ago, 26-Mar-00, to lugnet.cad, lugnet.cad.ray)
| | | | | Re: "Glowing" Lights in POV-RAY (2nd attempt)
|
| (...) Thank you, thank you, thank you!!! How I have looked for that. (...) Once again, thank you! /Tore (25 years ago, 24-Mar-00, to lugnet.cad.ray)
| | | | | Re: "Glowing" Lights in POV-RAY (2nd attempt)
|
| (...) Hello, 1. To make a light stronger you can use a multiplier. For example: color rgb 2*<1,1,1> (double the light of the light source) or color rgb 0.5*<1,1,1> (half the light of the light source) or any other multiplier you like. 2. You can use (...) (25 years ago, 24-Mar-00, to lugnet.cad.ray)
|
|
