 | | Re: Loader
|
|
(...) Hmm. What are those hexadecimal values doing in the DAT lines? --Todd (25 years ago, 19-Dec-99, to lugnet.cad.dat.models)
|
| |
| | Re: Loader
|
|
(...) the hex values are for mlcad 1.6 custom color. ldlite as far as I know doesnt support it, and ldraw crashes when hex is encountered. some alternatives for colors are : 42 = lime green transparent / neon green 44 = orange transparent (25 years ago, 19-Dec-99, to lugnet.cad.dat.models)
|
| |
| | hex values (was: Re: Loader)
|
|
(...) Wonderful. So why does MLCad insert nonstandard data into LDraw DAT files? --Todd (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
I thought LDLite is able to display this colors! If this is realy a problem I can change this to use comment lines defining these custom colors! Todd Lehman wrote in message ... (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Loader)
|
|
(...) I suggest defining the custom colors the way LDLite does, ie: 0 COLOR ... That way, you can still use the color numbers in the .dat lines so that the file will still work in LDraw and LEdit, except that the colors will be off. --Bram Bram (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
Michael, I can understand the need to use hex to define custom (non-TLC produced) colors, and I'm sure that you'll find a way to fix this. What I'd like to know is why the transparent versions of the standard colors are now saved in this manner. Now (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
This seems to be a bug, I will look at it, beside this I will take over the strategy suggested by Bram with using COLOR meta commands ... Michael Will Hess wrote in message ... (...) in (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
