For those having random setting or game crashes

[Kelius]

Could you email your Profile.bin file to support@seamlessent.com? I'm trying to track down what the root cause might be for these issues, and one common source seems to be corruption in the profile data. I want this fixed and I want it fixed in a way that isn't going to destroy everybody's campaign progress. Symptoms can be sliders not showing up on slide bars in the options screen, random numbers or letters showing up on any options text, or a crashrelated to a Mesh's index buffer. You can find Profile.bin here:

<PATH_TO_STEAM>\Steam\steamapps\common\sol exodus\SOLExodusGame\SaveData

Thanks!

[SeamlessStocks]

Yes, please guys. We want to lick this nasty, smelly bug as soon as possible!

[SeamlessStocks]

Update to crash bug:

We thing we found it and are gonna push out an update today that should address it.

[MetalDestroyer]

The latest patch has fixed the profil corruption. But now, the game just crash at launch. I was playing Day 6 mission, I had a game over and then, the first crash occured. Then, whenever I wanted to play SOL: Exodus, I got this message:
http://tof.canardpc.com/view/b354db4f-3ab4-4436-a5ac-947ba739dca6.jpg

I redownload the game just in case, but still crashing.

[FlyingWok]

Hey MetalDestroyer, I ran into the same problem. I renamed my "profile.bin" file to "profile.bin__" and now the game boots up again.

Here's how I think I hit this bug originally (the repro-steps may be a little off since this was yesterday and I'm doing this from memory)

1. Start SOL Exodus for first time
2. Set resolution to 1680 x 1050 Full Screen
3. Start Campaign
4. Go to Display options and check-on Use VSync, Use MSAA, turn Texture Detail to High
5. Hit Apply
6. Game goes into windowed mode and squished to half the width of my display. The settings menu now shows a blank Resolution field. I can't remember if Windowed Mode was checked or not at that point.
7. I open the Resolution drop down menu and set 1680 x 1050 and hit Apply
8. Game crashes
9. Try to reboot game, hit the error that MetalDestroyer hit.

I still have the original Profile.bin if you guys at Seamless want it.

[Kelius]

In the next patch, 1.9, Profile.bin gets separated out into three files: Profile.bin (contains story/upgrades/scores), VideoAudioSettings.bin (video and audio settings), and ControlSettings.bin (keymapping and other control settings).

Existing Profile.bin files should have no problem loading up and performing the split and working seamlessly, even if the existing one is corrupted. Any corruption, which is very rare, has never directly impacted campaign information, so if any corruption is found, it gets repaired and leaves the campaign information intact.

I'm sorry to everybody that had trouble with this. Having to delete your game progress just to compensate for an error in some other aspect of the game isn't acceptable. Let's hope for simpler and less painful bugs going forward. :)

[Kelius]

It may be possible that some profiles were corrupted in a way that could not be repaired. If you crash on startup of the latest patch, try deleting your VideoAudioSettings.bin and ControlSettings.bin (KEEP your Profile.bin to preserve campaign progress). If you get a crash, and this fixes it, let me know. If you start up without issue, as most users have, great!

[will3265]

The latest patch has fixed the profil corruption. But now, the game just crash at launch. I was playing Day 6 mission, I had a game over and then, the first crash occured. Then, whenever I wanted to play SOL: Exodus, I got this message:
http://tof.canardpc.com/view/b354db4f-3ab4-4436-a5ac-947ba739dca6.jpg

I redownload the game just in case, but still crashing.

I get a very similar message when i load exodus. the game has never run for me, EVER. I have installed and re-installed and had no change, still crashing at load up splash screen.

Steam won't give me a refund on my dud purchase so please fix.

[Kelius]

I get a very similar message when i load exodus. the game has never run for me, EVER. I have installed and re-installed and had no change, still crashing at load up splash screen.

Steam won't give me a refund on my dud purchase so please fix.

Please email me at support@seamlessent.com and include a screenshot of the error as well as your DxDiag.txt. If you've never run the game, this cannot be profile corruption from the prior patches. To create a DxDiag.txt, go to the Windows Start menu, and at the bottom, type 'dxdiag'. In the next window, select the button near the bottom that says 'Save All Information...' and save that file somewhere and attach it to your email.

[MrToad]

Hello,

I have the exact same error that MetalDestroyer, FlyingWok, and Will3265 are getting. I can't get past the Unreal engine screen before it freezes. As I have never been able to get this game to play, I deleted the controlSettings.bin, the VisualAudiosettings.bin, and my Profile.bin and then relaunched, that didn't help. The game will still not start even after this lattest patch.

Here is the error:

Rendering thread exception:
Fatal error!
Address=0x1097c4c0(filename not found) [in C:\Windows\system32\igdumd32.dll]
Address=0x10981d50(filename not found) [in C:\Windows\system32\igdumd32.dll]
Address=0x1097b014(filename not found) [in C:\Windows\system32\igdumd32.dll]
Address=0x10981a85(filename not found) [in C:\Windows\system32\igdumd32.dll]

If I browse to that path that dll is not there, but the 64 bit version of it is. That dll is resident on my machine, just not in that path. My laptop appears to have two video cards an integrated Intel card and a GeForce GT540M.

I contacted support and they said you need to figure out how to tell the game to use the Geforce card, ummm What? I have no idea how to bind an application to a specfic video card. And I Tried disabeling cards and that really hosed my machine.

So, if 4 people in this one forum are having the exact same issue, I think there is something on your end that needs to be fixed. I really want to play this game, but not being able to get the game to even launch is really frustrating. I can send you my profile.bin before the 1.9 patch and my profile.bin after the 1.9 patch if that will help. Please lets figure this out!!!!

[Kelius]

Use the NVidia control panel to modify which applications use the card. I am looking into why either Unreal, the installation, or Windows would have a problem doing this automatically.

The direct path to the SOLExodus.exe is here:

<PATH_TO_STEAM>\Steam\steamapps\common\sol exodus\Binaries\Win32

That is how the majority of users that had this problem were able to resolve it.

The problems in this thread are not all this same error, in fact most are related to some profile corruption that could occur in prior versions of the game, and contacting me through the support email is preferred as I am able to check and respond to email far faster than I can here.

[Crippledeye]

My game will not even start up past the unreal engine 3 logo, I am also having the same Rendering Thread Exception. Here is the error.

Rendering thread exception:
Fatal error!

Address = 0xc4fc540 (filename not found) [in C:\Windows\system32\igdumd32.dll]
Address = 0xc501dd0 (filename not found) [in C:\Windows\system32\igdumd32.dll]
Address = 0xc4fb094 (filename not found) [in C:\Windows\system32\igdumd32.dll]
Address = 0xc501b05 (filename not found) [in C:\Windows\system32\igdumd32.dll]

I am running a 64-bit PC, DX 10 system (i5 integrated graphics) with 8 gigs of ram, yet it always runs the DX9, 32-bit version.

[Kelius]

There is no 64-bit version of the game, as Steam integration does not support 64-bit applications. It may be possible to force DX10 or DX11 in the configuration files, but this game has been created and tested for DX9.

As far as that error goes, it is the same as the one just above your post. It seems some NVidia drivers or installs do not correctly detect the game. This is not isolated to our game, and does not occur with every NVidia system that runs the game, but the solution is the same as I just posted. So far I have not found any information on why a program would not be set as expected, but the bug is somewhere on their end.

[Crippledeye]

Thanks very much for the reply, but I do not have an nVidia card. I am using an intel HD 3000.

[Kelius]

Closing thread as profile related corruption and crashes are gone as of patch 1.11.