(2024-10-06, 23:34)Travis Cobbs Wrote: There is a critical bug in Mesa 3D (that I reported slightly over 2 years ago) that causes this problem in LDView when running with Mesa 3D as the OpenGL provider. I tried and failed to work around it.
One more thing: If you change the top-level model references to use color 16 instead of another color, it will probably work around the LDView problem. Note that I am not saying that using 14 at that level is wrong; it's not. But due the details of the Mesa bug that shows up in LDView, making that change should make the problem go away.
At least for the Transport-1.ldr subfile, it does not appear that any of the parts are referenced using color 16. This means that the color 14 you use when placing Transport-1.ldr in the model is completely ignored. I suspect that the same is true for Transport-2.ldr, Transport-3.ldr, and Transport-4.ldr. Assuming this is the case, you should be able to modify the following four lines in the file:
Code:
1 14 -40 0 0 1 0 0 0 1 0 0 0 1 Transport-1.ldr
1 14 160 0 250 1 0 0 0 1 0 0 0 1 Transport-2.ldr
1 14 -30 0 350 1 0 0 0 1 0 0 0 1 Transport-3.ldr
1 14 160 0 0 1 0 0 0 1 0 0 0 1 Transport-4.ldr
Update them to instead be:
Code:
1 16 -40 0 0 1 0 0 0 1 0 0 0 1 Transport-1.ldr
1 16 160 0 250 1 0 0 0 1 0 0 0 1 Transport-2.ldr
1 16 -30 0 350 1 0 0 0 1 0 0 0 1 Transport-3.ldr
1 16 160 0 0 1 0 0 0 1 0 0 0 1 Transport-4.ldr
After that, LDView should render the model correctly.