Frictional Games Forum (read-only)

Full Version: Game issue: Frozen desktop image, only audio!
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Evening All! I'm currently having an issue trying to run SOMA - I've gone through the troubleshooting guide (drivers, beta version, admin. rights etc. etc.). Whenever I start the game it attempts to go into fullscreen and then just shows a frozen image of the dektop with the audio playing. I can't alt>enter or anything.

I'm attempting to run it in Windows 10 on a 1080ti.

I have attached a copy of the hpl log in case anyone can spot something in there. Amy help on this would be great Smile
According to this log, it seems like the window does get created, but perhaps your Desktop window isn't focusing on it. Or maybe there is something wrong with the resolution.

Right click on SOMA in your Steam Library and run the Settings Launcher (or run Launcher.exe from SOMA's local installation folder), and from there, switch it to Windowed Mode. Let the game boot up, and then try changing settings from SOMA's main menu.
(07-19-2017, 03:10 AM)Romulator Wrote: [ -> ]According to this log, it seems like the window does get created, but perhaps your Desktop window isn't focusing on it. Or maybe there is something wrong with the resolution.

Right click on SOMA in your Steam Library and run the Settings Launcher (or run Launcher.exe from SOMA's local installation folder), and from there, switch it to Windowed Mode. Let the game boot up, and then try changing settings from SOMA's main menu.

Thanks for that - hmm, I've tried using -sw & -windowed via the Settings Launcher in Steam and it still ran full screen. What is also odd is that there is no Launcher.exe in the SOMA local installation folder (I've launched the verifier which claims that everything is fine).
You're right - It doesn't look like SOMA has one. Looks like you'll have to do it the old-fashioned way.

Go to Documents\My games\Soma\Main and open the file that looks like <your_steam_name>_<some_id>_user_settings.cfg using something like Notepad. Find the entry
Code:
FullScreen="true"
and set it to false. Save and try starting now.
(07-19-2017, 10:04 AM)Mudbill Wrote: [ -> ]You're right - It doesn't look like SOMA has one. Looks like you'll have to do it the old-fashioned way.

Go to Documents\My games\Soma\Main and open the file that looks like <your_steam_name>_<some_id>_user_settings.cfg using something like Notepad. Find the entry
Code:
FullScreen="true"
and set it to false. Save and try starting now.

Cheers, now that's odd - there's no config file either!

Right, I've managed to get it to creat a config file however there is no fullscreen option in there:

<Game />
<Debug ShowFPS="false" ShowSoundPlaying="false" ShowPlayerInfo="false" ShowEntityInfo="false" SaveCheckPointOnMapLoad="false" ShowDebugMessages="false" UseProgLog="false" />
<Input InvertMouse="false" SmoothMouse="true" />
<Map File="" Folder="" StartPos="" />
<Graphics TextureQuality="0" TextureFilter="2" TextureAnisotropy="4.000000" SSAOActive="true" SSAOQuality="0" DepthOfFieldQuality="2" BloomActive="true" WorldReflection="true" Refraction="true" ShadowsActive="true" ShadowQuality="2" ShadowResolution="2" ParallaxQuality="0" ParallaxEnabled="true" />
<Sound Device="-1" Volume="1.000000" MaxSoftwareChannels="64" MaxVirtualChannels="1000" ForceShowSubtitleCharacterName="false" ShowSubtitles="false" SpeakerType="HomeCinema" />
<Screen Width="1707" Height="960" />
<Main FirstGameStart="false" />
Right, I have updated the config so that it runs in windowed mode unfortunately now it just crashes on startup. Log attached.
The game crashes because it couldn't find a video driver. Try updating / reinstalling your graphics drivers.
Thanks for the reply Mudbill - unfortunately I have already tried updating the drivers as well as uninstalling and reinstalling to see if that was the issue.
Hang on a minute - I think I may have been an idiot. Just realised I'm on the insider builds for windows 10. Looks like 16241 has borked a lot of games.
Well either way the log claims that the only "driver" available is the Microsoft Generic GDI.

Code:
Vendor: Microsoft Corporation
  Renderer: GDI Generic
  Version: 1.1.0
  ...
  GLSL Version: (null)

I'm not sure what would cause this in this particular case though.

Edit: Ok, you're on a trail then.
Pages: 1 2