Consistent Launch Crash

Avatar
Icey
  • updated
  • Completed - Resolved

Hello Support Team,


I am experiencing a consistent crash upon launching the game: The game's logo displays and then the error occurs.

As per a suggestion I read elsewhere on the bugtracker, I have attempted running the game without having my USB-attached sound device connected. It has made no difference.


Specs:

  • OS: Windows 7 Home Premium 64-bit (6.1, Build 7601)
  • Memory: 4096MB RAM
  • CPU: Intel Core i5 CPU, M 430 @ 2.27GHz (4 CPUs), ~2.3GHz
  • GPU: ATI Mobility Radeon HD 5650

I'm sadly unable to provide my game's exact build as its stated in the game's main menu and the crash occurs before that, but I can at least say that its whatever Steam has available for download as per 25 December 2015. :)


Please find the log included here: error.log

Thanks for any assistance or commentary you can provide.

Game Version:
Steam Public
Platform:
Windows
Replies 37
Avatar
0
Stefan Furcht Programmer

This sounds strange, then the option should be there indeed.
Can you try to create a desktop shortcut for the game (by right clicking on WftO in your games library).
Can you right click on the shortcut and use option "Run on ATI Mobility Radeon HD 5650" if any.
Otherwise can you right click on your desktop and select "Configure Switchable Graphics".
Find "WFTOGame.exe" in the "Recent Applications" list and click on "Power Saving" on the right side to toggle it to "High Performance".
Do any of those work either?
Otherwise I need to wonder why you don't have options to assign GPU on your system.

Avatar
0
Icey

For the record, am I correct in my statement that I am using the generic AMD drivers when I download them from http://support.amd.com/en-us/download? Just making sure I'm not messing up here.


In response to your suggestions:
When I create a shortcut and then right click it, there is no "Run on ATI Mobility Radeon HD 5650" option or anything similar.

Right clicking on my desktop does not show me the option "Configure Switchable Graphics"


I took the liberty of browsing to the Power Options in the Control Panel, which are set to "High Performance" as the default option. Not sure if the settings there would matter.


Thanks for your continued support!

Avatar
0
Stefan Furcht Programmer

You're welcome! But I admit the issue seems harder to resolve than expected :)

Well it is important to note that the Switchable Graphics Driver is not the Catalyst Control Center and is a part ofthe normal ATI Radeon HD Display Driver.
So installing newest Catalyst Software Suite is not enough, you need to install the newest ATI Beta Driver (Radeon Software Crimson Edition Beta).
http://support.amd.com/en-us/download/desktop/legacy?product=legacy3&os=Windows+7+-+64
It's also recommend to remove the old acer driver first. However checking "Remove anything AMD" during installation should do.
There is a FAQ for Mobile Drivers:
http://support.amd.com/en-us/kb-articles/Pages/LaptopsFAQ.aspx

And after doing bit of research I see Acer is not very nice when you try to install it.
So the custom installation fails on a regular basis, but it can be by-passed by changing a BIOS option (yikes)
http://acer.custhelp.com/app/answers/detail/a_id/26985/~/can%E2%80%99t-update-graphics-driver-for-switchable-graphics

So I wonder how it simply worked when you installed it already?

However the above BIOS option should force the dedicated GPU for all applications, so if you are willing to touch it, then maybe try this first without installing anything, to check if forcing your ATI GPU fixes the issue for you at all.
If it does then it's up to you if you wanna change this just for playing the game or if you want to get the flexible assignment options by using the generic beta driver.

Switchable Graphics it self is a mess and Acer does add its own hurdles unfortunately :/
Quite some people had issues because the driver assigns wrong GPU to WftO, but if you not even have an option to assign the dedicated GPU manually with Acers driver it becomes way more cumbersome to fix.

I'm sorry for your inconvenience.

Avatar
0
Icey

My apologies for not immediately jumping to install the Radeon Software Crimson Edition Beta, but it seemed like it could take some time and I needed my notebook at the time.


With all that said, I have now installed it... something which it automatically did in my native language. This might somewhat complicate communications on the matter. Communications which, of course, will remain necessary as the game continues to crash right after the logo splash for me.


I have checked up on my BIOS' Video Mode settings. These were already set to 'Discrete'. This could explain why there was no option on right clicking: There was nothing to choose other than the ATI GPU. :)

Sadly, this does not explain why no GPU is detected at all so that continues to be a problem.


Kind regards,

Icey

Avatar
0
Scott Richmond Programmer & Producer

Hi Icey,


Our apologies for the continued issues you're having. I have one other quick step you could try:


Before you run the game from Steam, press and hold down left alt, and then click Play. Keep the alt key held down. If a small window doesn't pop up like below - eventually you should see the the WFTO icon flashing down in your taskbar. Click on it and you should see the window.



Try replicating the above settings to your window and hit Play.


Avatar
0
Icey

Hey Scott,


Thank you for your response!

In an attempt to follow your instructions I opened my Steam library, selected War for the Overworld, pressed down the left alt key, clicked play while holding the alt key and then waited. The game displays the Splash Logo as normal (though it appears in the background now) and then crashes like it has been. I cannot access the displayed Configuration window this way.


Kind regards,

Icey

Avatar
0
Stefan Furcht Programmer

I would really like to get a gist why it does not even manage to load any basics before it crashes for you.
Seems it's really an hard to resolve problem which I do not understand yet.

Avatar
0
Stefan Furcht Programmer

It is an access violation in kernelbase.dll, so there is something going wrong deep in the operating system.
Thus the log does not tell us much for what we are looking and I am running out of ideas.
@Scott
Do you have any other idea?

Avatar
0
Scott Richmond Programmer & Producer

Well this at least confirms that the issue isn't with our code nor is it with Icey's graphics drivers or GPU - It never gets that far into initialization.


Icey - Do you have any kind of anti-virus or security software installed at all? If so, could you try disabling it temporarily and trying to play the game?

Avatar
0
Icey

I do not have any active anti-virus software installed.