 | | Re: [LSC] Colour Definition meta-statement
|
|
(...) Color codes will be defined in decimal notation and the 24-bit RGB will be in Hex. -Orion (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) RGB is actually 3 numbers - I'd suggest something like RGB(r,g,b) where r g & b can be decimal or hex as per other numbers. ROSCO (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) What would the name of the file be and how big is it approx.? Then I can browse through my 6 year old collection of "Download CD's..." :-) Jaco (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | 81 million points
|
|
I normally don't make posts like this, but I thought the numbers involved deserved a post. Just out of curiosity, I stuck a counter in my development LDView code to count the number of points being drawn. I loaded up the copy I have of town.dat (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
I'll bite. (Note that none of my comments are meant as criticism.) In lugnet.cad.dev, Steve Bliss wrote: <SNIP> (...) I personally think the # for hex numbers is a mildly bad idea. The currently accepted way to specify hexidecimal values is to (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | [LSC] Colour Definition meta-statement
|
|
Here's the initial write up for a color definition meta-statement, to be used in ldconfig.ldr and in any model file. The LSC has a couple of outstanding issues with this spec, let's discuss those in follow-up messages. Please respond with any (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Matrix mirroring question
|
|
This question is mostly directed a developers that have had to deal with mirroring while processing LDraw files, but I welcome comments from anyone. It seems to me that any model specified with a mirror matrix will be mirrored relative to its parent (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Save that code! Once an LDraw/POV-Ray library is a going thing (and it looks like that won't take so long), those parts can be submitted there. Steve (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) True, but the 'embedded code' is still code we are effectively certifying as being good, whether it works strictly within LDraw, or in other GDL/SDL's. (...) Sorry, we never got around to making the list public. I'll work on that. Steve (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Bram's LDraw and LEdit Tutorial
|
|
Attention all, Thinkquest, the site that hosted Bram's LDraw & LEdit Tutorial, recently deleted this tutorial from their archive. Neither Tim nor I had a hard copy of the webpages. While I've contacted Bram asking him if he still has a copy, I'd (...) (21 years ago, 21-Jan-04, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Kevin L. Clague wrote: [much snippage] (...) The above example parallel directory structure is just an example. I see that there are many possible alternate solutions... POV directory as sigbling of LDRAW subdirectory, where the (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) One thing the project clearly needs right now is a small homepage to tell what it's all about, and outline what people can do to help. That might help pull in more active participants than a lone CVS archive. I've seen your pages, Larry. I bet (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Larry Pieniazek wrote: <much snippage> (...) As Orion described, we'd rather put the ability of using POV or whatever other renderer you choose outside the LDraw file format, and outside the LDraw format parts library. If we (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) The relatively easy solution on how to make the wrench tool and, even more obvious, the (unofficial) patterned maxifig heads - that solution has become undone. (...) The only thing that ever has frustrated me about LGEO is that I never ever (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) What's entailed? Do you want participants who can test but not do much else? (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Actually, the only Official Library parts that have embedded P-R SDL are some of Paul Easter torus primitives. Since nothing was ever done in the first place, nothing is being undone now. If you're like me and frustrated that LGEO is (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Only until 3rd party libraries (like LGEO) become available. ROSCO (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Too sad. If I got that complicated language correcly, this means that the problem presented at (URL) and was solved by embedded POV-code has now regressed to be un-solved again. /Tore (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Yes, and if you want to join the project team let me know (this goes for anyone else as well). (...) -Orion (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) OK, but whether or not the P-R SDL code was out of whack would not affect the usability of parts as parts within LDraw format programs themselves, right? (0)Only affect the accuracy or completeness or error state of transformation (by tools (...) (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
