You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's seems a vanilla problem, it's explain why the Render depth control reset to minimum when you load that map in vanilla versions of descent 3.
May Interplay devs noticed this but they don't have time to resolve it, only with this ugly trick reseting the render depth control to 40.
I've tested every piccuengine and the FPS drops happens in all cases, and may be caused because the render depth allow to set to 100 in this map.
For other hand, with vanilla versions the FPS works fine, because, again, the render depth are set to 40 automatically by the game when you enter to PTMC Research Bunker
Another test that I've done is trough piccuengine set render depth to 40, and the FPS works fine, but the map look bad, with those violent clipping in the near distance.
It's seems a vanilla problem, it's explain why the Render depth control reset to minimum when you load that map in vanilla versions of descent 3.
May Interplay devs noticed this but they don't have time to resolve it, only with this ugly trick reseting the render depth control to 40.
I've tested every piccuengine and the FPS drops happens in all cases, and may be caused because the render depth allow to set to 100 in this map.
For other hand, with vanilla versions the FPS works fine, because, again, the render depth are set to 40 automatically by the game when you enter to PTMC Research Bunker
Another test that I've done is trough piccuengine set render depth to 40, and the FPS works fine, but the map look bad, with those violent clipping in the near distance.
Here's a video showing pe 1.2.2 in PTMC Research Bunker
https://youtu.be/a1uvTCBDGGA
Even with Render depth set to 40 my graphic card (rtx 4070 ti sup) drops to 110~120fps.
So the problem seems be a performance vanilla engine code.
The text was updated successfully, but these errors were encountered: