Error with OSMesa version of LDView


RE: Error with OSMesa version of LDView
#5
(2023-09-23, 1:58)Orion Pobursky Wrote: I wonder why I haven't run into this error with the part image generation?

Also, moving all the official parts out of the mpd didn't work. I guess I'm misunderstanding the nature of the bug.

I misread your file when I looked at it the first time. It's not doing what I thought it was doing. I thought it was using color 16 to refer to the tyre (2997.dat) in step16.dat, but I now see that it is not doing that. However, I still feel that the problem is triggered by the Mesa bug that is related to nested colors. Try changing all 4 of the references to step36.dat from color 0 to color 16 to see if that helps.

In other words, update the following:

Code:
1 0 251 -54 -180 0 0 -1 -1 0 0 0 1 0 8880 - step36.ldr
1 0 251 -54 500 0 0 -1 -1 0 0 0 1 0 8880 - step36.ldr
1 0 -251 -54 500 0 0 1 -1 0 0 0 -1 0 8880 - step36.ldr
1 0 -251 -54 -180 0 0 1 -1 0 0 0 -1 0 8880 - step36.ldr

Change it to the following:

Code:
1 16 251 -54 -180 0 0 -1 -1 0 0 0 1 0 8880 - step36.ldr
1 16 251 -54 500 0 0 -1 -1 0 0 0 1 0 8880 - step36.ldr
1 16 -251 -54 500 0 0 1 -1 0 0 0 -1 0 8880 - step36.ldr
1 16 -251 -54 -180 0 0 1 -1 0 0 0 -1 0 8880 - step36.ldr

The reason this doesn't affect the parts tracker is because LDView flattens all of the geometry in each part before drawing it. Since the parts tracker only renders one part at a time, it cannot trigger this bug. Flattening all of the geometry from all the parts in the model would in theory avoid the bug, but LDView does not allow you to do this due to the huge amount of memory it would require.
Reply
« Next Oldest | Next Newest »



Messages In This Thread
RE: Error with OSMesa version of LDView - by Travis Cobbs - 2023-09-23, 2:14

Forum Jump:


Users browsing this thread: 1 Guest(s)