waitFor3D cmd or workaround for LOD artifacts

[mrcurry 496]

Hey!

I was wondering if any of you guys have any ideas on the following scenario.

---

For some reason you want to move the player from point A to point B (player setPos pointB). The points are pretty far apart so on most machines the game will struggle with LOD artifacts as you load in the new area.

If you would want to make sure that the player doesn't have to experience this, how would you go about doing that?

One solution that could work is the dreaded loading screen: fade to black, sleep x seconds, fade back in.

titleText ["Loading...", "BLACK", 0.5];
player setPos pointB;
sleep someNumber;
titleText ["Loading...", "BLACK IN", 0.5];

However this is a really blunt tool. Players with a high-end rig suffer for it and low-end PC users might still experience the artifacts. Could you make it smarter?

Preferably we would have a waitFor3D or finalize3D command that pauses scripts until things are properly loaded to allow for better control. That however might be trickier than it seems. Games have been plagued with LOD issues as long as I can remember, the arma series in particular.

Thoughts?

[kylania 568]

There are camera preload commands maybe try to use those?

[mrcurry 496]

Cheers kylania,

Search-fu fail... I can't believe I missed that.

Disregard topic!