 | | Updated 30399.dat [DAT]
|
|
I have fixed the duplicated lines according to L3P. Is this the correct name? Also, do I need to submit this to the tracker? If so, how do I get an account? I hope this one is correct, I don't think any of the parts that I have made have been OK'd. (...) (22 years ago, 24-Jul-02, to lugnet.cad.dat.parts)
|
| |
| | Updated 30400.dat [DAT]
|
|
I fixed this one's duplicated lines as well. 0 Brick 4 x 18 0 Name: 30400.dat 0 Author: Ronald Scott Moody <RonaldScottMoody@netscape.net> 0 Unofficial Element 0 1 16 120 4 20 1 0 0 0 -5 0 0 0 1 stud4.dat 1 16 160 4 20 1 0 0 0 -5 0 0 0 1 stud4.dat 1 (...) (22 years ago, 24-Jul-02, to lugnet.cad.dat.parts)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) I have found 3.5 to be almost twice as fast as 3.1 with the same files - tested on a PII, P3 and P4. Most incompatabilities can be removed with the version directive. (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
<snip> (...) Try this link: (URL) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: ASSOCIATE (was: Re: Renaming of 2916.dat)
|
|
(...) WAY better than using naming to overload. 2916 and 2917 get at best a very weak association if they have train in their name. With the ASSOCIATE keyword extension it becomes quite explicit what their connection is. (and parts can also have (...) (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: ASSOCIATE (was: Re: Renaming of 2916.dat)
|
|
(...) Yes. Play well, Jacob (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) Can't help it, I'm an upgrade junkie. Been that way for years :) Anyway, is there a good tutorial on MegaPOV? I have not used that yet, still using L3P. (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | ASSOCIATE (was: Re: Renaming of 2916.dat)
|
|
(...) Hmm. Interesting idea. So part 3937 (URL) might have an entry like: 0 ASSOCIATE 3938 6134 and part 3938 (URL) might have: 0 ASSOCIATE 3937 2440 (of course, these examples capture information that otherwise might be captured by a connectivity (...) (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New Part in progress - Baseplate 32 x 32 with Craters
|
|
(...) Wow! I think you've definitely got sufficient detail there. (...) If you include a comment in the part file, indicating that the bottom is modeled as a flat surface to reduce the size/complexity of the part, I think that would be alright. (...) (22 years ago, 24-Jul-02, to lugnet.cad.dat.parts)
|
| |
| | Re: CMDLINE Meta-statement
|
|
(...) The purpose is to specify viewing characteristics for a part that should be the default, but we don't want to hard-code into the part itself. Generally, it's used to specify the 'correct' color for patterned parts. So a patterned minifig head (...) (22 years ago, 24-Jul-02, to lugnet.cad)
|
| |
| | Re: Trouble with POV 3.5
|
|
"Sproaticus" <jsproat@io.com> wrote in message news:GzrFGw.AJx@lugnet.com... [ ... snipped ... ] (...) that (...) I too had problems with 3.5 so went back and installed 3.1. WRT MegaPOV - where is the best place to download the current version of (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) I was also having the same problems and I spotted this: (URL) he suggests adding a #version 3.5; line at the top of the file. This worked from me but I am still having other issues with the orthagonal view. I guess I'll just have to go back to (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) I loaded POVRAY 3.5 and started using it to render my LDraw designs and noticed right away that it is slower on my machine and it leaves areas of the render with an odd color and fuzzyness to the image. in some areas it is almost transparent. (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) Unfortunately, the POV dev team has a history of breaking backwards compatability in their revisions. Think back to how they mutilated the halo feature of 3.0 when they introduced media in 3.1. Their goal is to force everyone to use the latest (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Part Fix 3959 Space Gun
|
|
(...) I'm not sure if this needs realy torii. I can live with cones because the details are so fine that it's not neccassary to use torii. For the name I suggest "Minifig Torch". It's a understandable name. Space gun is to one-sided. 0 Minifig Torch (...) (22 years ago, 24-Jul-02, to lugnet.cad.dat.parts)
|
| |
| | Re: Trouble with POV 3.5
|
|
<snip> (...) Why are we trying to use Pov 3.5? What is computer user's *NEED* to have the latest and greatest? Does Pov 3.5 provide the LDraw rendering community anything NEW that 3.1 did not? Why go thru all the headaches of learning 3.5 when 3.1 (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: So what *IS* a Building Instruction anyway?
|
|
(...) If you get around to fixing it, then I would appreciate it, if you could seperate the code in operating system specific and non-operating system specific parts. Where is the syntax for the "SUB" meta-statements documented? Play well, Jacob (22 years ago, 24-Jul-02, to lugnet.cad)
|
| |
| | Re: Renaming of 2916.dat
|
|
(...) It might. (...) I can see your point. And I must admit that the first category I would search for this part under would be "Train". - Which certainly implies that "train" at least should be a keyword for the part. (...) Sort of. In principle (...) (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) Yeah, it has something to do with POV-Ray switching "versions" before loading colors.inc. I tried to delete the lines but didn't help much. Think Lars has to change the code in L3P a bit. I also expierenced errors in MegaPOV after installing (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Trouble with POV 3.5
|
|
Is anyone else having trouble getting POV-Ray 3.5 to work? I got some sort of error about macros in the colors.inc file. What does that mean and is there something I can do to fix it. In the meantime, I have just gone back to 3.1. (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
