Boblekobold

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 75 total)
  • Author
    Posts
  • in reply to: Bioshock 2 (Fixed crash) #219854
    Boblekobold
    Participant

    I have changed the TextureStreamingMemoryLimit to 128.000000 but sadly, I still get crashes every 15 minutes or so, specially when I access machines (upgrades, ammo, health packs, etc.) and also when manually saving; from Windows 10 and 11 too.

    I use both :
    TextureStreamingMemoryLimit=128.000000
    TextureStreamingDistanceLimit=30000.000000

    You can try other values. Maybe 64 or 32, or 1. If 0 worked for you, you can still use it. It doesn’t seems to lower the graphics too much and too often (and you play on Quest 2, so do you really notice the difference ?)

    You said “Did you try the virtual monitor tip”; Can you please tell me how to do it in a more detailed way and which resolutions should I try ? I don’t know what is it or where to find it and nor how to set it…

    Check my post above : May 26, 2024 at 2:52am
    There should be a shortcut on your desktop to launch VorpX Desktop Viewer.
    I would try 3840×2880 or if it’s too much 2880×2160 (but it shouldn’t be too much on this game). Once again, maybe it doesn’t change too much on a Quest 2, I don’t know. On a Reverb G2 I can tell the difference.

    I also was unable to find where that Tesselation setting is set.

    In Bioshock2SP.ini, there is two lines named TesselationFactor.
    There are a lot of other things you can change here, but it’s not always better. It depends.

    in reply to: Cyberpunk 2077 Path Tracing #219847
    Boblekobold
    Participant

    When I try path tracing, vorpX keeps crashing. Are there some settings or something I’m missing, or does path tracing just not work with it?

    Thanks in advance.

    Path tracing worked for me (with ultra settings 4k and DLAA), with an RTX4090, but I got 15fps (30 with AMDFidelityFX -max quality- instead of DLAA). It’s playable, but I would recommand to play any other game with current graphic cards and wait a little…
    Every other games I tried were smooth and most of them were more impressive in VR currently.

    in reply to: Bioshock 2 (Fixed crash) #219792
    Boblekobold
    Participant

    Tesselation up to 15 in .ini files (two separate lines) is great. I hesitated a lot with Low, but for now, I play with ClarityFX to full and sharpness/texture enhancement to 2.0. Walls with corals are very detailed and sharp in Dyonisus Park. It gives volume to rust/coral.
    This game is very impressive in VR. You don’t need to play recent games to get stunning graphics with VorpX. Even with an RTX4090, it’s better overall than Cyberpunk 2077 in VR.

    in reply to: Bioshock 2 (Fixed crash) #219775
    Boblekobold
    Participant

    Using TextureStreamingMemoryLimit=0.000000 and TextureStreamingDistanceLimit=800000.000000 is perfect for me. I don’t seem to have crashes anymore ! THANK YOU THANK YOU THANK YOU XD

    TextureStreamingMemoryLimit=0.000000 seems to prevents some textures from loading, like detailed version of pink coral (or make it extremely slow), so I recommand to use a >0 value (128.000000 works well for me).

    I am curious about how did you get to test that specific change ? Had you some documentation about Bioshock 2 or was it just trial and error ?

    I’ve found some intel on the internet (Helixmod comment about G3D, Steam forum about Bioshock 2 even without 3D), and I tried several values/combinations. I asked myself the same question about the original intel ;)

    I’ve found the DynamicShadowDetail upgrade alone (it was obvious in the ini file).

    I think you can raise tesselation too (I tried 2.0 by myself and it seemed to me it was different but I wasn’t sure it was a good idea so I reverted, but I just read it can reach 15.0, so I’ll try).

    – It works only in Windows 10, not in Windows 11 where I still get crashes (Dual boot saves the day)…

    I play on Windows 11 without much problems so there must be a combination of factors. I have an RTX4090 with 31.0.15.5168 pilot. I use a Reverb G2 with OpenXR runtime.

    Did you try the virtual monitor tip ? You should if you have a good headset (displayport). High resolution is very important in every Bioshock (important textures can be very detailed, and a very high resolution is a way to negate aliasing in these games).

    in reply to: Bioshock 2 (Fixed crash) #219772
    Boblekobold
    Participant

    Erratum : ClarityFX to Low seems to be enough for me with last VorpX Beta version.

    in reply to: Bioshock 2 (Fixed crash) #219771
    Boblekobold
    Participant

    Because not everyone seems to know : you can use 3840×2880 resolution even if your monitor doesn’t allow it.

    Only once :
    – Install VorpX Beta.
    – Add Predefined resolutions above 4k in VorpX config (“Virtual Monitor” tab)

    Every time :
    1) Launch VorpX Desktop Viewer
    If you play Bioshock 1 or infinite, unzip/replace your edited ini files before or after ( no need with Bioshock 2 )
    2) launch the game (make sure you hook, you can create a direct VorpX Desktop Shortcut, you can exclude Launchers, etc.)
    3) If needed (each time you load a new level in Bioshock 1 for example), change the resolution to 3840×2880

    in reply to: Bioshock original CRASHES only with vorpx #219770
    Boblekobold
    Participant

    Hello, thanks for your answer.

    You said “Don’t Optimize game settings”… Do you mean to turn off “change game settings” in vorpx ?

    There is a checkbox “Don’t Optimize game settings” in VorpX configuration.

    And yes, VorpX change Bioshock 1 and Infinite settings each time you launch it. So my solution was to configure ini files, zip them, and unzip them before each launch.

    You need to configure ini files to change resolution and at least FOV.

    IT’S VERY IMPORTANT TO CHANGE FOV if you want the right zoom/scale. I explain how here :

    Bioshock 2 (Fixed crash)


    in my post “May 26, 2024 at 1:08am”
    It’s the same thing for Bioshock 1&2. It’s easier with Infinite ini files.

    You said “I play with 3840×2880″… I suppose it depends on your monitor right ?, mine is up to 1920×1200

    It doesn’t depend on your monitor.

    Only once :
    – Install VorpX Beta.
    – Add Predefined resolutions above 4k in VorpX config (“Virtual Monitor” tab)

    Every time :
    1) Launch VorpX Desktop Viewer
    and (you can switch order)
    1) Unzip or replace your Bioshock ini files
    2) launch the game (make sure you hook, you can create a direct VorpX Desktop Shortcut, you can exclude Launchers, etc.)
    3) If needed (each time you load a new level for example), change the resolution to 3840×2880

    This way, the game won’t be blurry at all (at least on a displayport headset, without compression).

    After that, you unzoom to the border of your view, and you choose a FOV you’ll keep in your ini files (105-110 is great in Reverb G2).

    This way, you get a native-like experience, like if you really were in the game.

    in reply to: Vorpx Minimal Windows version #219769
    Boblekobold
    Participant

    Never had a crash on Win10 with Bioshock 1 original (and Infinite) with VorpX. I played with a reverb G2 and it was perfect (OpenXR runtime).

    I didn’t crash on Win11 but I only played a few minutes.

    With Varjo Aero, I was forced to use SteamVR runtime, and It freeze for a second sometimes (but maybe it’s just me), so I use a G2 again.

    I have only a few crashes on Bioshock 2 on Win11 (1 per 5 hours I would say), but I had to do this :

    Bioshock 2 (Fixed crash)

    You should switch between two savegames, because if it crashes during the save process, you may have to remove the last savegame from directory (or the game will crash at launch).

    in reply to: Bioshock 2 (Fixed crash) #219768
    Boblekobold
    Participant

    (If you don’t know Bioshock at all, you should start by Bioshock 1, then 2, then Infinite, then Burial at Sea Ep1&2 to avoid spoilers…but if you know them, it’s better in the order I indicated).

    in reply to: Bioshock 2 (Fixed crash) #219766
    Boblekobold
    Participant

    I would recommand to play :
    1) Bioshock infinite
    2) Then Burial at Sea Ep1&2
    3) Then Bioshock
    4) Then Bioshock 2
    5) (Then Minerva’s Den)

    This way you :
    – respect the story chronology
    – graphics gets better over time (because Bioshock 2 is the best, and Infinite the worse, except Burial at Sea Ep2 wich is really stunning).
    – gameplay gets better and more complex (Bioshock 2 > Bioshock 1 > Bioshock Infinite)
    – it gets harder to configure ‘^^

    These 3 games are some of the best VR games you can do, in my opinion. It worth it even if you already know them (you can use Silvermod for Bioshock 1 original, custom ini mods for Bioshock 2 to raise or change difficulty). I can explain how to edit Bioshock 2 ini files if you need to.

    Don’t forget to use a very high 4:3 resolution like 3840×2880, to unzoom to the border of your view and to raise FOV until you get a perfect native-like experience.

    in reply to: Bioshock 2 (Fixed crash) #219765
    Boblekobold
    Participant

    I’m playing the original one (lightings are better and I use mods to increase difficulty).

    I had no crash at all with Bioshock 1 (with Silvermod).

    With Bioshock 2, the game crash 1 time per 5 hours I would say. I would recommand swithing between too savegames because it can get corrupted and you may need to remove it from directory (it’s very rare).

    Finally, I use :
    TextureStreamingMemoryLimit=128.000000

    It’s impossible to reach max graphics using game menu. You must edit Bioshock2SP.ini :
    DynamicShadowDetail=High
    It seems to improve graphics significantly.

    I also replaced texture details options by UltraHigh in .ini files :
    TextureDetailInterface=UltraHigh
    TextureDetailTerrain=UltraHigh
    TextureDetailWeaponSkin=UltraHigh
    TextureDetailPlayerSkin=UltraHigh
    TextureDetailWorld=UltraHigh
    TextureDetailRenderMap=UltraHigh
    TextureDetailLightmap=UltraHigh

    I don’t know if it does anything.

    To answer my own question, the best VorpX shadow parameter is :
    G3D shadow : auto (it’s perfect this way)

    110 FOV with +0.1 camera high seems great to me on Reverb G2.
    To change FOV, use something like that in User.ini :
    Up=MoveForward|setFov 110
    Down=MoveBackward|setFov 110

    This way you change FOV when you move. It can be useful because FOV change each time you aim. You can do a sniper mod by doing something like this :
    MouseWheelDown=setFov 90
    MouseWheelUp=setFov 50

    The same solution works for Bioshock 1.

    It’s not necessary in infinite (but with this game you should raise font size with .ini).

    I use “HT positional tracking : on” to have 6dof in Bioshock 2 (even if I play with keyboard&mouse). Beware Delta’s helmet (you may need to recenter sometimes).

    I didn’t find the way to move HUD in Bioshock 2 (but it doesn’t bother me too much because I can see most important informations without edgepeek).

    in reply to: Bioshock 2 (Fixed crash) #219701
    Boblekobold
    Participant

    Is it normal I can’t change HUD scale and position in Bioshock 2 ?
    It works in Bioshock 1 and Infinite.

    in reply to: Bioshock 2 (Fixed crash) #219695
    Boblekobold
    Participant

    To answer one of my questions :
    “TextureStreamingMemoryLimit=256.000000” is better. And it doesn’t crash.

    in reply to: Bioshock original CRASHES only with vorpx #219677
    Boblekobold
    Participant

    I just tried it and I have no problem with Bioshock 1.
    Win11 RTX4090 VorpX V24.1

    I use “Don’t Optimize game settings” and textures on ultra in VorpX.

    I play with 3840×2880 resolution. G3D (Shadow no S3D) with clarityFX to full, sharpness to 2.0 on reverb G2.
    I use the setFov option on keymap in ini files in order to have a FOV of 105 (so scaling is perfect in Full VR, unzoomed to the border of my view).

    If you don’t know how to do it, configure in User.ini :
    Up=MoveForward | SetFOV 105
    Down=MoveBackward | SetFOV 105
    (Of course you can choose another key or FOV value)

    The game is stunning this way.

    No crash, but I just tried the beginning. I tried quicksave a few times (save and load).

    I use OpenXR runtime, but I suppose you can’t with your Quest 2.

    Did you try Oculus Runtime ?

    Are you sure it’s the original version ?

    in reply to: system shock #219671
    Boblekobold
    Participant

    (I use virtual monitor to get 3840×2880 or 3200×2400 resolutions)

Viewing 15 posts - 1 through 15 (of 75 total)

Spread the word. Share this post!