 | | Re: New LDConfig.ldr color file
|
|
(...) It may be able to display a billion polygons, but it certainly can't keep a billion unique polygons in video memory. Each unique point requires a bare minimum of 12 bytes, and usually requires more than that (for color/texture info). The (...) (15 years ago, 13-Aug-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) Thanks for the explanation. Since my computer at work (which I am using) is a high end CAD workstation with enough VRAM to display a billion polygons, I guess I should just leave it on HIGH! On my home machine, I will probably slow it down. (...) (15 years ago, 13-Aug-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) The main effect that this setting has is its control over the amount of display list compilation used. Display lists are a feature in OpenGL (the graphics library used by LDView) for drawing static objects. They convert (compile) the data into (...) (15 years ago, 12-Aug-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) This makes me curious as to how this Memory Usage feature works. Why would I set the memory usage to "Low" if I have plenty of RAM? What does this do for me? Eric (15 years ago, 12-Aug-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) Well, what we are actually trying with the new LDConfig.ldr file is getting more colors into LDraw, colors people find in today’s set but not LDraw and IMHO it lowers the bar for users if the colors are consistent throughout the system. Since (...) (15 years ago, 12-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) I have a few comments here. First of all, if you're going to load a huge model in LDView, it's usually best to set its "Memory Usage" setting to Low (especially on old hardware). Secondly, as has been pointed out, LDView takes a lot longer to (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) Did you have any suggestions for him? I did not, other than that he does not have his paths set up correctly (which was already mentioned). I do not even have LPub 2 installed anywhere anymore. Do you? If so, maybe you could help him. I'd (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) That is not correct. The 1.8 sec are the drawing time. If you will have a look into 'statistics' you will see that most of the time the loading will take and then 1.8 sec. for the drawing is used. So this comparison is not correct, but you are (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) That is just so not true. (...) Well then, welcome to my reality. Viewing just a small portion of Datsville on my AMD1100, for example TOWN-10.ldr, takes 1.8 seconds in L3Lab. But several minutes in LDView - if it doesn't crash. I am (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) So far we have much more TLC color numbers than in LDraw (Bricklink) with TLC apparently not going further than 300. Therefore a numbering starting with 3000 would be fine. w. (15 years ago, 7-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) In order to add new colors to the list easily and with some officiality, it makes good sense to follow a system like using the colors provided from the Lego company. This is what I agreed to when creating this list of colors; as I knew that I (...) (15 years ago, 3-Aug-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) I used this calculator: (URL) get darker shades for the trans edges. Could you try to get a ratio that works for the trans colors? w. (15 years ago, 3-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) So is it possible to save a version of LDView's lighting parameters so that it defaults to colors that look right when using this ldconfig.ldr file? If so, then I'd like to suggest putting some comments at the top of the file mentioning this, (...) (15 years ago, 31-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | (canceled)
|
|
|
| |
| | Re: New LDConfig.ldr color file
|
|
Has any thought been given to anyone on how patterned parts/stickered parts are to be handled? Because there are more colors used in printed and stickered parts then there will ever be in the plastic colors that this defines. I'm not trilled with (...) (15 years ago, 30-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | (canceled)
|
|
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) It is the webmaster's policy that the authors submit and maintain the links to their tools and we only remove broken links. Obviously nothing hinders us to update the link for L3P at Ldraw.org but since nothing on the official page (URL) (...) (15 years ago, 30-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) I think he means the semi reserved ranges 32..63 (transparent version of 0..31) and 256..511 (dithered version of two encoded 0..15 colors). But as far I know these can be overridden by a 'normal' definition and should only be treaded as (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) Indeed, basically it doesn't matter what range you use. I just wanted to point out that 'other' ranges are rounded upon hexadecimal notation (due to math advantages). So I suggested also using that for these new ldc numbers for consistency (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) That's very good news! Very recently I visited (URL) and there it reads: "Version: 1.3 | File size: 78.00 Kb" and links to (URL) where it reads: "NEW Read about the v1.3 20010120 release NEW". Maybe time to update some pages? I haven't checked (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) As far as I remember LDView does a more than decent job converting to PovRay as well as viewer so there is actually no need for L3P or L3Lab - not counting in that accordingly the L3P page (URL) supports the LDConfig.ldr file: "Colors from (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) Well, actually there are two forbidden zones; the small at colors 29 through 31 and the large at 48 to 255. Color numbers within those ranges generate errors if used in L3P and L3Lab. In original LDraw and other really old programs, colors (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) This can be done with the caveat that we start with something like say 2001 or 3001 in order to preserve the original LEGO numbering starting from 1 to 300. for 2001 the TLG color number would be "#7D1". Correct? w. (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) Could you be a bit more precise. What is the "Forbidden zone"? w. (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) renamed to "ldcfgalt.ldr" (...) Hmmm this would be best solved with an additional command in the file - say CATEGORY or CLASTER or whatever. Anyway, modifications to the synthax can only be applied by the LSC. (...) Good point. I'll modify the (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) for MLCAD use: (URL) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) <snip a lot of info> Seems like quite an undertaking. (...) My vote would go to keeping the old ldraw colors, like said else were most monitors aren't calibrated. (...) I don't know about other software but my LD4DStudio uses the config file (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) All new color codes except 313 Maersk Blue generate errors in L3Lab and L3P because the numbers just had to be picked from the forbidden zone... :( :( :( /Tore (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) I don't really know what I'm talking about here, but I think there might be a big difference between the representation of RGB values in a dye based color system for bricks, another one for printing on paper, and a color system for computer (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) SNIP (...) So it'd be goodbye for Stone Gray? :-( Well, I can live with that.. (...) Nice! :-) SNIP (...) Hmm... looking at the new colours I'd be otherwise fine sans the new Black... looks too bluish for me. (...) Well that's going to be (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | New LDConfig.ldr color file
|
|
Hi folks, working on and off for almost a year with Scott Wardlaw, Alex Taylor and with the help from Joshua Delahunty we put together a new LDConfig file which hopefully fills in where the old version failed: (URL) file has the following (...) (15 years ago, 28-Jul-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.announce) !
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) Partly correct. I used an open source version of pascal to compile this program. Since it's not win specific, it's probably not as optimized to the win platform as Delphi is. -Orion (15 years ago, 20-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) This is for Mac OS and windows OS at the same time. I think LDDP is only for WinOS. (15 years ago, 18-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) I wonder why this windows execute is soooo large (12,6 MB!) and LDDP is only 1,9 MB?. cu mikeheide (15 years ago, 17-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) Current version of DATHeader checks this. (...) Please see the document what DATHeader is testing for at (URL) the POV code test I think it is a complete list of things that got a hold vote or at least not certified on the PT during the last (...) (15 years ago, 17-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) That's only true if the polygons are the same color. If they're different colors, it's an error. I've seen official parts with overlapping polygons that are different colors. --Travis (15 years ago, 16-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) I'll look into this. The !LICENCE check is case sensitive so unless you have exactly what's in the spec, it will complain. (...) The Lib Spec says that 3 decimal places is enough in most cases (4 for scalable primitives). This would be a (...) (15 years ago, 16-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) It complains with invalid !license on files that seem ok to me. (...) What do you mean? (...) I think it could be done. But is it really necessary? Thresholds would need to be defined too... Philo (15 years ago, 16-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) Try out LDraw Validator: (URL) zip file contains both a Windows and OS X binary. I'll post the source once the program is complete. What it checks: - Compliance with header spec (mostly, see below) - Compliance with !CATEGORY and !KEYWORDS (...) (15 years ago, 15-Jul-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: L3P -check Messages and hold votes
|
|
(...) I suggest to use LDDP or Datheader instead. Both of them include the correct code to check for non-coplanar quads and are more convenient to use. Planarcheck should only be used by parts authors to automatically split non-flat quads. (...) (...) (15 years ago, 12-Jul-09, to lugnet.cad.dev.org.ldraw)
|
