 | | Re: LDraw.org MOTM/SOTM voting for March is open
|
|
(...) perhaps it should be moved? It's breaking a lot of the rules for 'Model'. I'm _almost_ sure I entered it for SOTM, not MOTM. AndersI (23 years ago, 1-Mar-02, to lugnet.cad)
|
| |
| | Re: LDraw.org MOTM/SOTM voting for March is open
|
|
(...) Certain messages arriving in my mailbox are copied to my phone through a SMTP to SMS/GSM gateway. The status report from the program that updates the MOTM/SOTM voting pages is one of that kind of messages. Another example is the report the (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev.org.ldraw, lugnet.off-topic.geek)
|
| |
| | Re: LDraw.org MOTM/SOTM voting for March is open
|
|
"Jacob Sparre Andersen" <sparre@nbi.dk> wrote in message news:GsABo8.CwG@lugnet.com... (...) How so? From a script you wrote? Scheduling on the phone? -Tim fut -> lugnet.cad.dev.org.ldraw, though will probably end up in off-topic.fun (23 years ago, 1-Mar-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | LDraw.org MOTM/SOTM voting for March is open
|
|
We have entered a new month, and that means that it is time to take a look at all the nice renderings entered in the competition for the title LDraw.org Model/Scene of the Month for March 2002. Take a look at (URL) make a (hard) decision. Play well, (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev.org.ldraw, lugnet.cad, lugnet.announce)
|
| |
| | Re: Inline POV-Ray code? [DAT]
|
|
I see now that your problem is difficult to solve. Sorry I tried to put it into a nutshell, Steve. My preference would be to design an auxiliary file for each case, and markup the LDRAW part in a very general way, so that future programs could (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) Right! I have always thought of the "0 IFNDEF L3PPOV" as a way to utilize most of the normal LDraw lines (that L3P can convert to equivalent POV code) and only replace a small tricky curvy section by some POV code that would look better. This (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Printable Parts Catalog Updated
|
|
I blame the flu for the delay. For those who haven't found it yet, it has a new home: (URL) is my own domain name, so I don't foresee any address changes ever again. Enjoy. -- Patrick Sayre-Little patrick@nightsolo.net (23 years ago, 28-Feb-02, to lugnet.cad)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) When I wrote this message, I was trying to figure some rational way to mix LDraw and L3P/POV-Ray code. Something like: 0 IFNDEF L3PPOV (ldraw code) 0 ELSE 0 #if (STUDS) 0 LDRAW 0 1 16 0 0 0 1 0 0 0 1 0 0 0 1 stud2.dat 0 LDRAW END 0 #end 0 (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) I'm not following. Are you agreeing with the idea of using embedded POV-Ray code, or having separate file libraries? I *think* you agree with the second, am I right? The one thing we gain by having embedded POV-Ray code is the ability to have (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
In a nutshell, 'namespaces'. Switching among parts libraries to get different versions (or different data) should be an application capability, not the individual part file. (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: No shadow in LDLite 2.3?
|
|
(...) Look here: (URL) think it got changed to -E1 on the command line when some alternate shading methods were added. Have fun, Don (23 years ago, 28-Feb-02, to lugnet.cad)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) Well, if thats how you really feel, then why even bother to "write up a spec/reference page on 0 IFDEF" at all. The instant you put the line: 0 IFDEF <code> in a part file you're blessing a non-ldraw extension. The <code> is by definition a (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: No shadow in LDLite 2.3?
|
|
Can anyone help, please? Jaco (...) (23 years ago, 28-Feb-02, to lugnet.cad)
|
| |
| | Re: Another stupid part-authoring question (Primo?!?)
|
|
(...) Yes, the stud is hollow. The studline substitution would leave a hole 56 (or at least 48) LDU across... big enough to fit a microfig-scale capital ship. -- Tony Hafner www.hafhead.com (23 years ago, 28-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: Inline POV-Ray code?
|
|
In lugnet.cad.dev, Don Heyse writes: [snipped things down a bit] (...) Generally, yeah. But mostly to the extent that I haven't thought it through enough. (...) That could work, but IMO only pushes the issue to the side. To some extent, LDraw.org (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: New tool: LDDesignPad 0.3 for LDraw
|
|
Hello Ryan, i looked at the problem and you are right. I will fix it in the next version because current one is almost bug-free and in want ti implement one or two more features. Thanx for telling Carsten "Ryan Farrington" <ryanjf@ifriendly.com> (...) (23 years ago, 28-Feb-02, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) So it appears as if we agree that L3P-generated objects don't really belong in official LDRAW part files. Once again this brings us back to the 0 INCLUDE suggestion. Imagine that ldraw.org (or someone else) distributes a separate set of part (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Another stupid part-authoring question (Primo?!?)
|
|
(...) Hmm. I don't have any Primo parts handy, so I've got to throw out a basic question. Isn't the inside of the Primo stud actually hollow? If we made a Primo stud that was subject to studline'ing, that would leave a huge hole in the Primo parts, (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) No, I meant the POVRay code referring to L3P-generated objects. By allowing this code in official part files, we'd be endorsing language that hasn't been generally discussed and reviewed. Not that I see any particular problem with the code. (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: *** LDView Version 1.9.2 Released ***
|
|
(...) Hmm, that does seem strange. Do you get the dialog prompting you to select the LDraw directory? If not, do you either have LDraw in C:\LDRAW or have the LDRAWDIR environment variable set? If so, does the selection of a directory work? (Note (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev)
|
