SOMA v1.02 available on Steam

[ADEdge]

Was having heaps of issues early on, lots of stuttering. Particular places made the game either hang (rarely) or crash completely (most of the time)

Happy to report that I updated today and had a bit of a test-play. BuildID 790226 and everything is running much nicer. Havent noticed any stuttering, and I just played for a good hour without it even threatening to crash. Framerate seems better too, havent noticed it getting low at any point as it was before.

Was holding off playing the game too much until this stuff was patched (doesnt help immersion when the game is crashing!), so feels like Ill be able to play through without issue from now onwards.

Cheers guys! Loving the intriguing story-line going on with SOMA

(Windows 8.1 Pro, 64-bit, i5-3570K, GeForce GTX570 if extra details needed)

[wizardoftristram]

So I personally have no problems running the game, but I thought I'd run a few tests in order to see what might be causing problems with stuttering.
CPU: AMD FX-8320
GPU: NVIDIA GTX 970
Notable NVIDIA Control Panel Changes:
Shader Cache and Threaded Optimization - Off
Maximum Pre-Rendered Frames - 1
AA - FXAA - On
AO - Performance
VSync - Adaptive
Game Settings:
Resolution - 1920x1080
AA, AO, VSync - Off(Because they're turned on through the Control Panel)
Bloom - Off
Other General Settings - Either turned up High/On

I ran through the game four times, from the start of a new game to the first underwater tunnel right after acquiring the Omnitool. I did approximately similar actions each time, and I walk(no running) through each section in order to maximize time spent in each area without stopping progression.

Test 1:
I play up to the previously mentioned area. CPU usage averages around ~20%. FPS was 60 throughout, except when loading new areas or autosaving, at which the FPS dropped a nominal amount for only a second. No problems to note.

Test 2:
I play up to the previously mentioned area while streaming. OBS reported an average CPU strain of ~10-15% on top my base usage, putting my CPU at around ~30-35%. No other differences to note.

Test 3:
I play up to the previously mentioned area while streaming AND recording. OBS reported an average CPU strain of ~30-35% on top of my base usage, putting my CPU at around ~50-55%. Stutter becomes noticeably apparent at this point. Autosaves take a second or two longer to complete. While loading new areas, the game jumps from ~50% straight to 100%, and the FPS drops to less than ~10 for a few seconds. Otherwise, no other problems to note.

Test 4:
I play up to the previously mentioned area while recording. Results are similar to the results of Test 2, where I just streamed. No other differences to note.

GPU was observed using GPU monitoring software provided by NVIDIA. GPU load and VRAM load never go over 50%. Temperatures were normal. CPU observed using Windows Task Manager. FPS observed using Steam's In-Game Overlay. No other unnecessary programs were running.

Sorry if this isn't the right place to put this. I thought maybe this might help give anyone some insight to their problems. Other than the weird CPU jump in test 3, the game works smoothly for me. I've also added my hpl log below through pastebin as it's size was too large to be attached. In addition, I ran the dependency walker on Soma.exe. MSVCR90.dll and MSVCR80.dll couldn't be found, but that never stopped the game from working. I copied the dlls that already existed elsewhere on my drive into the Soma folder to resolve the issue.

http://pastebin.com/1NgRh2iX

Also, the twitch highlight of Tests 2 and 3:
http://www.twitch.tv/wizardoftristram/v/17802948

[AleNes]

I have 789976 bulid. Is it okay?

[wizardoftristram]

I have 789976 bulid. Is it okay?

The most recent build as of now would be 790226. If you aren't having problems, then you should be okay. Otherwise, restart Steam in order to get it to initiate the 1.02 update.

[Filizitas]

My experience with 1.02:

- Texture streaming seems a lot more faster!
- Played 120 minutes and ende the game properly everything ok to me!

[AleNes]

Otherwise, restart Steam in order to get it to initiate the 1.02 update.

It doesn't help. How to get the last build? Verifying game's cache doesn't help either.

[wizardoftristram]

Otherwise, restart Steam in order to get it to initiate the 1.02 update.

It doesn't help. How to get the last build? Verifying game's cache doesn't help either.

If restarting and verifying cache don't work, you could try opting into the beta. It might update, and once it does, you can opt out of it again. If that doesn't work either, you might have to unfortunately re-install the game. Although it is weird that it wouldn't update already from a verify and a restart, unless it is updated, but is showing the wrong build number.

[Googolplex]

Wait for final patch.

[demon0496]

If it helps, whenever I launch SOMA it says SOMA.exe has stopped working. Then Windows looks for a solution, and offers to debug. But after you select debug, the screen locks up, and you can't choose any other window other than closing the debug window. After you do so, the screen unlocks and you can browse freely again.

[raylinth]

Really disappointed this is not on GOG yet... I'm getting the crash at the "Brandon Wan" terminal.

---

Really disappointed this is not on GOG yet... I'm getting the crash at the "Brandon Wan" terminal.

Let me clarify, for the linux version.