L3DT Users' Community

Hi Dennis,

Following from the above post:

4) Does the latest dev build make any difference (v2.4a build 5, Aug 30)?

I've been digging through the map display code, and whilst I haven't found a 'smoking gun' fault, I have found and fixed a few bits that were written in a way that I would not use now and could be related to the problem at hand.

This appears to be one of the nastier, harder-to-find bugs I've come across, but I shan't rest until it has been squished. Thanks again for your patience.

Regards,
Aaron.

Hi Dennis,

Please disregard the above posts. The problem is, I believe, due to display colour depth. L3DT blindly assumed the screen colour-depth to be 32-bit (in ABGR), and whenever it's not, you get crazy rendering such as you found. I've got a nasty hack going to fix the problem, but it makes the screen refresh really slow. I'll upload a proper (faster) fix tomorrow.

Best regards,
Aaron.

Aaron, the new dev build worked perfectly. Thank you for the fantastic support. Here is the properly imported terrain: