LDCad 1.6 Alpha 3 (win+linux)

[Philippe Hurbain]

That's the first time that has happened as far I know. It's hard to say what the problem is given such a vague description though. Maybe they just don't like the filesize or something.

The good thing is that it did not complain about 1.6 alpha 3a...

So in the end it's just the 5% boost I guess

Good to know... though LDCad is already quite fast on a machine able to use a 64b exe!

Yes after some larger chunk tests, it tests every vertex of the part until at least one is inside the region's frustum. That method gives the least (zero) false positives.

And it does work very well. If really needed, maybe the shadow library could provide a way to add extra vertices in the handful of parts (mainly axles) that miss them? A 32L axle might be missed quite often