I’m in the process of setting up a qcad template with the same colors lightburn uses.
I did this by exporting an object in each of the colors one by one to a svg. (When exporting to dxf the rgb values turned out differently, with C05 and T1 actually having the same color.)
When importing a test file back from qcad I noticed that 29 imports as C23, and T1 imports as C05.
I found on the forum that T1 and T2 are not supposed to be mapped (anymore), so I’m guessing there’s an off-by-one error happening here.
Personally I would like to see this T1 and T2 not mapping “feature” to be reconsidered. I would find it tremendously useful when designing dxf files, as I often have a “guide” layer with objects that don’t need to be cut.
The way it now works, with it mapping to a different non-related color, is actually really unhelpful, as this just throws it together with stuff which does need to be cut, making it even harder to differentiate and change back to the correct T1 layer.
As it is now (with the off-by-one bug) it would actually be workable, I could use T2 for my guides and pretend nothing is wrong. But when this bug gets fixed I’d really be in it…
So I guess there’s just something going wrong with my C29 and T1 imports, for whatever reason.
The link you’ve shared only talks about C0-29, it doesn’t mention the colors for T1/2.
C29 on that link is the same as I have it.
Both #0c90d1 and #0c96d9 work fine for my T2 mapping. (Not sure why you have a different value for this, I just did a svg export and looked in the generated file to get the color code.)
If you also have #f36926 for T1 I guess something’s up with the qcad dxf export.
In any case, if it’s just qcad messing up those C29/T1 colors, I can live with that. I’ll happily use T2 for my guidelines and forget C29 and T1 exist