 | | * LDraw Design Pad (LDDP) 1.53 released *
|
|
LDDesignPad (LDDP) is a tool for editing and handling LDraw files in a very comfortable way. Features are: -Fully customizable editor with syntax highlighting -Open multiple files at the same time -Unlimited Undo/Redo -Use/define codesnippets (...) (21 years ago, 26-Jan-04, to lugnet.cad, lugnet.cad.dev, lugnet.announce)
|
| |
| | Interesting BFC finding
|
|
Well, I've finished an initially working implementation of BFC in my next-gen LDView code tree, and discovered that on my particular video card, BFC actually slows the rendering down. A test model renders at about 50 FPS with BFC handling disabled, (...) (21 years ago, 24-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) And now the archive is public (Thanks, Dan!). See the mailing-group list at the bottom of the page at (URL) (Thanks Orion for making the list!) Steve (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I could go for that. Simpler is better! Of course that means the METALLIC (or PEARLY) tag needs an argument to define the color of the embedded bits. If you want it to be the same color as the substrate, just use the same color code. Don (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I've been keeping clear on the dither issue so far, because I didn't have a strong opinion one way or another. However, the more I think about it, the more I think we're not seeing the forest through the trees. Because of this, I vote we (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I would prefer that spaces not be allowed in the color name as well. However, the spec does say that all the keywords are case sensitive (must be all caps), and I believe the original suggestion was that keywords by themselves with spaces (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I realize many current ldraw rendering programs use a stipple pattern to render transparent surfaces. I do it in ldglite because I'm too lazy to do the sorting required to use alpha blending. However, I don't really want the specs to dictate (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) [snippety] (...) [doo-dah] (...) I was thinking no space. So far, we've avoided wrapping literals in quotes in LDraw (with only occasional trouble). I'd like to keep avoiding quotes. [snippety-ay] (...) Good question. We hadn't thought about (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) But what if Lego prints an opaque dithered pattern on a transparent brick? I think the ALPHA is more versatile if only applied to the VALUE color. You can still get an alpha dither color by using a color code for d which points to a color with (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I don't think so. What if CODE is part of the color name? I can't think of a quick example for that, but other key words are easy. AlphaTeamRed, BlueChrome... I'll support color names with no space characters, and I'll consider supporting (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Disregard the NAME suggestion. I'm brain dead today. -Orion (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) How about NAME? (...) I don't see a problem with this. Steve or Jacob? -Orion (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I won't make any guarantees, but there's a reasonably high probability that I won't even try to support the above, even if it's what the spec says in the end. It's too much of a pain. Additionally, it disallows further expansion of the colour (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) HTML uses # (...) The name should be the characters after the !COLOR keyword and before the next keyword. The only contraint I can think of is that is not be one of the other keywords. (...) ALPHA should apply to the VALUE color and the color (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I prefer the currently used 0x prefix, but I guess if you picked # to match other file formats in use by ldraw users then I can live with it. I forget, does POV or HTML use # for the hex prefix? (...) No spaces in the name? Alpha-numeric only? (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) I forgot to mention. I didn't try fly-through mode, but wouldn't expect it to be very usable at 1 frame per second. --Travis (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) My system is a 2.4GHz P4 with 1GB RAM. However, according to the Windows XP task manager, LDView was only using about 125 megs when the model was loaded with normal-res studs. (This compares very favorable with the current LDView release that (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) Wow. That must be amazing in fly-thru mode. I'm also curious. What sort of CPU and how much memory do you have, and how much of that was in use by the LDVIEW? (...) I bet you have to get all your display list(s) and vertex arrays into the (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) I have a copy. Let me know if you still need it and I can email it to you. I still point to the LEDIT portion of this tutorial in the ldglite instructions so I'd like to see this back on the internet somewhere as soon as possible. Don (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) Name: ldrawtutorial.zip Size: ~410K -Orion (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | 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)
|
