Keep getting dumped out of the sim
 

With an error like this:

AppName: sh4.exe AppVer: 1.0.0.0 ModName: d3d9.dll
ModVer: 5.3.2600.2180 Offset: 0008834b


I haven't even made it further into the game than the museum. I consistently get errors after viewing ships for a bit.

Oh, and I don't know quite what to say about the aircraft featured in the museum. Yikes!

Did you opt to install DirectX with the game?

I unchecked "install DirectX 9" since I thought I had the latest, but when I tried to start the game, it gave me a similar error. After exploring the DVD and installing DirectX off of it, it worked just fine.

I installed DirectX during the game installation.

Here's another error report:

AppName: sh4.exe AppVer: 1.0.0.0 ModName: sh4.exe
ModVer: 1.0.0.0 Offset: 00220805


This really sucks. I can't play the game for more than few minutes without being dumped out with one of these errors. Happens even if I just walk away from the game and don't touch a thing.

These types of errors can be caused by your Anti-Virus software affecting the dll files when being extracted and the correct registering of them. You might try un-installing the game, disabling AV, then re-installing.

Knowing Akdavis, he won't be running any AV for sure.

Nah, I did have AV running. I uninstalled and reinstalled with AV disabled. Same problem. I've never had an issue like this before. Incredibly frustrating.

it *could* be a hardware issue, i was getting CTD's like that in Medieval 2 Total War because of a bad stick of RAM.

I don't believe it is a hardware issue. Certainly, I'm not having any issues with other games (including MTWII, ;) ).

FYI, ubi support page does not work right now. You can't ask a question. No way to seek resolution at all. I've been loyal to Ubi for many years, buying most of their sim products and always giving them the benefit of the doubt, but the state of this product is just beyond the pale.

Is there any additional information about the error in the system logs?
Let us know if you don't know how to find them.

Next step after your re-install didn't fix it is to check what programs are running and shut down everything possible. There's something running that's got a lock on the memory that the game needs to run. (my guess)
Do a fresh boot, bring up task manager and make a note of the amount of memory in use. On a fairly clean system it should be no more than about 125mb. Under 100 meg is great.
Go to Sysinternals.com, then click on System Information and download PROCESS EXPLORER. This will help you find things that are running that you never knew existed.

I've got a lot more things we can check so don't give up yet. It just may take a little time with having to go back and forth. The best thing you can do is to provide as much information as possible.

I think I isolated the problem to the sound drivers. I was one version behind latest release when I thought I was current.

However, after reinstalling game and video/sound drivers, it sure seems like I'm taking a huge performance hit at "high" graphics, when before I thought it ran pretty smoothly (for the short minutes before a crash). Maybe it is just perception since I was focused on the error issue.

Thanks for the help. I'll probably just add a question about optimization in the technical help thread, see if I've still got an underlying issue here.

I was wrong. Just turns out the error can occur after longer than 5-10 minutes.

I really need some help here. I have no idea how to copy the full report text, as I can't select it with the cursor, but the first file mentioned is usally sh4.exe and then a series of different .dll files.

I downloaded the game from Ubi.

I've installed latest video and sound drivers. I've uninstalled and reinstalled game. I have patched the game.

This is making the game completely unplayable for me. If someone knows a way to contact someone for technical support, please let me know. Ubi support won't even let me post a question.

Thanks.

Take a screenshot of it, and post here.

If you downloaded the game, might be a corrupted DL. Did it come with a chksum that you can compare?

I believe this problem has now been solved by forcing v-sync. I thought I had already tried that, but I had been changing the v-sync variable in the SH4 program file directory main.cfg rather than the my documents/SH4 file. Around 3 hours total without another crash and also rid me of some stuttering. We'll see if it holds.