- This topic has 18 replies, 5 voices, and was last updated Feb 9, 2025 11:46pm by
.
-
Posts
-
Concerning TextureDetail, I said I wasn’t sure, but my current file has :
TextureDetailInterface=Normal
TextureDetailTerrain=Normal
TextureDetailWeaponSkin=Normal
TextureDetailPlayerSkin=Normal
TextureDetailWorld=Normal
TextureDetailRenderMap=Normal
TextureDetailLightmap=Normalin [WinDrv.WindowsClient] section, and UltraHigh in the [XeDrv.XenonClient] section.
I don’t know if it was intended.
Be careful with these parameters, because it may be worse if you go too high (if I remember well, I tested them in Dionysus park with tesselation and UltraHigh wasn’t the best). I’m not sure if normal or high is the best parameter, but if I used normal in the end, it may be “normal”.
Bioshock 2 original is on GOG (with Remastered) :
https://www.gog.com/en/game/bioshock_2_remastered
I didn’t try it (I personally used my old version V1.0 from 2010).I don’t know if there is Minerva’s Den original DLC. I had to do it with Remastered (and broken physics / spear gun). If anyone knows where to find it, I’m interrested ;)
Thanks!
One additional hint: After years of (on and off) searching for some mysterious vorpX bug that only materializes in the original Bioshock 2 and a handful of other 32bit DX9 games, I’m pretty sure I recently found the actual issue while I did some general memory optimizations: too much memory used with vorpX.
For the GOG (not Steam unfortunately) version that can be fixed by making the game ‘large address aware’, which raises the 2GB RAM limit 32bit applications usually have to 3GB. The same fix also works for Dragon Age Origins btw., which has similar random crash issues without being large address aware.
A simple patcher can be found here for example:
https://www.techpowerup.com/forums/threads/large-address-aware.112556/Note that trying this fix only ever makes sense for old 32bit games, newer (64bit) games will never need this.
- You must be logged in to reply to this topic.