LDraw.org Discussion Forums

Full Version: ldconfig.ldr chrome colors and parts tracker.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I'm not quite sure how you sneaky guys on the LSC got this one by me. Wink

Apparently while I was sleeping somebody managed to define a few chrome colors in the ldconfig.ldr file in positions 60-63, which have been reserved for almost forever by ldlite as transparent colors in the range 32 to 63. Now, ldglite inherits the colors from the ldlite code so these display as transparent instead of chrome, and will do so on the parts tracker if you're still using ldglite to render the parts. It's not a big deal to change the ldglite code, but if you want to fix these chrome colors on parts tracker you're gonna need a recompile of ldglite, or else switch to ldview. Or you could redefine the chrome colors in ldconfig.ldr to occur above color 63. Chrome_black, gold, and silver are defined above 63, so they're ok already.

Any thoughts on this?
this thread should be relocated to "Parts and Standards" IMHO
http://forums.ldraw.org/list.php?21
apart from the topic you brought up,
can you change ldglite to read and use ldconfig.ldr ?
or does it already?

I remember that Chris had to jump through some hoops on the Parts Tracker
to get ldconfig.ldr converted into something that ldglite understands.
As ldconfig.ldr seem to me now be a standard of LDRAW, every program should move towards the direction of using it IMHO

I should have posted this below
http://forums.ldraw.org/index.php?7
, but found no really suitable group there.
As stated already here http://forums.ldraw.org/showthread.php?t...333#pid333 ,
I feel ldglite not properly represented in this forum currently.
Done!
I think there are already too many forum categories. Any list that goes off the bottom of the screen is too many. I'd much prefer to see some of the wasted vertical space squeezed out of the recent messages view (showing all categories) over creating more subforums.

As for ldconfig.ldr support, I think all the current released ldglite executables look for it in the parts search paths so copying it into the ldraw/models directory should work. The Parts Tracker executable is a custom offscreen rendering only build for BSD made long ago when I had a login account on the ldraw.org server. It predates the ldconfig.ldr code, and uses the older ldliterc.dat file and format instead.

I've recently updated the code to look in the main ldraw directory first, but I'd really like to see that location codified in an official standard before I put in the effort required to create a bunch of executable releases. However, if the account with the parts tracker code still exists, it probably wouldn't require too much effort to recompile it with the latest code.
Wow, this is good news.

Chris, I'll send you a link to this thread, so we can maybe improve the PT rendering.

If I can be of any help, let me know anybody.
I just tried to file a request to LSC to officially document the location of ldconfig.ldr:
http://forums.ldraw.org/showthread.php?t...348#pid348

Well, maybe that's not even necessary, because the recent parts updates
included that file in LDRAW's root folder,
so that's a de-facto standard already now.
Would that be enough reason to modify ldglite accordingly?
Don Heyse Wrote:
-------------------------------------------------------
> I'm not quite sure how you sneaky guys on the LSC
> got this one by me. Wink

The LSC does not control the contents of LDConfig.ldr. This was discussed internally in the LSC at some point in the past, and we did not want control over the file.
Pages: 1 2