 | | Re: DirectX and .dat
|
|
Thanks all, I am going to concetrate on them normals then. I even got some ideas on how to determn the correct direction for them by examening base lego parts. But first things first, back to math class for me :) Roland (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | 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: 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: 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)
|
