Hi Andy,

Can you send us an output log from this attempt? If your last time launching the game was under these drives the output log in the folder currently or in the appropriate crash folder should be perfect.

It'd be interesting to see if it's made any changes. Once you've done that maybe try the following:

1. https://support.brightrockgames.com/knowledge-bases/2/articles/4404-how-to-force-dedicated-gpu
2. If that fails then try launching the game with the following launch parameter "-force-d3d9" without the quotation marks. I'm not sure exactly how this works with Galaxy but you should be able to click the "Add command line arguments under more > settings on the galaxy client
   1. It's unlikely D3D9 will work in the current version of WFTO but given that your previous output log indicated D3D11 was failing to initialise with your graphics drivers this may be a potential solution.

The first option may yield a result however, we think its possible the game is incorrectly loading partially onto the Intel GPU in your system, and forcing the Nvidia GPU to do it all should help.

Let us know how you get on,

Lee

Hi Endymon,

Sorry for the delay in our response, we've been extremely busy recently preparing for a major milestone on our other project.

I'm currently on leave after a very crunchy week. But I wanted to quickly look into some of these reports we've had recently.

We've had a few reports recently from Nvidia users of crashes which is quite odd. However looking into your issue further yours seems different. One factor I've noticed is that your drivers are dated 4/30/2017. It might be worth giving these an upgrade and seeing if it changes the nature of your issue?

Cheers,

Lee

Hi Anddy,

Sorry for the delay in our response, we've been extremely busy recently preparing for a major milestone on our other project.

I'm currently on leave after a very crunchy week. But I wanted to quickly look into some of these reports we've had recently.

One thing I've noticed is that we've had a few crash reports from Nvidia users recently. I can see that you're on the drivers dated 01/03/2019 which if I'm not mistaken are the latest drivers from Nvidia. (419.35).

Can you confirm for me that you are indeed on the latest drivers? If so perhaps we could try rolling back your drivers to an earlier version. You should be able to locate drivers from an earlier time this year or late last year. If you can install these in the place of your current drivers it might be worth seeing if that resolves your issue.

Cheers,

Lee

Hi Sims_doc,

Sorry to hear that you're experiencing crashes after installing the game. Can you please provide us with a log, system specs and dxdiag output as outlined in this article: How to: Submit a Bug Ticket

Can you also ensure that your Windows install is completely up to date and your graphics drivers are on the latest version.

Lee

Hi Squibert,

Thanks for your report and sorry for taking such a long time to respond to you, we've been extremely busy lately preparing for a major milestone on our next project.

I'm sorry to hear you've experienced the too many threads crash in the game recently. Typically this error occurs due to some underlying issue in the Unity Engine on specific rigs. This can make it incredibly hard to pin down. It's frustrating when we see it as there's usually very little we can do about it.

I'll push this topic into our review queue for our upcoming triage pass for when we can return some programmer attention to WFTO. In the meantime can I suggest a few things to try:

1. Update your graphics drivers and OS to the latest versions
2. Ensure all the dependencies are installed for WFTO. You can usually find the installers for these bundled in the WFTO directory.
3. See if there's a newer version of your BIOS (The firmware which runs your motherboard) and if you can update it then do so. (Be aware this can cause any overclock to be removed and that if you interrupt the process it can cause serious issues with your PC)

Let us know how you get on.

Lee

Hi YourShadowDani,

This is a fair shout. I'll drop this into our triage queue for when we do a pass through all the WFTO tickets. I imagine it should be a fairly easy fix.

Cheers,

Lee

Hi Anddy,

Unfortunately our team is heads down on a major milestone for our next project at the moment but we'll try to get back to you as soon as we can.

In the meantime can you confirm for me:

• Is this your first time running the game or have you successfully run the game in the past?
• Can you provide a DXDiag output for your computer? How To: Generate a DXDiag Report.

Hope we can get you into the game soon,

Lee

Hi Oneday Host,

Unfortunately I'm not sure what you mean by the text description. Can you provide a step-by-step on how you achieved this state?

Cheers,

Lee

Hi Alexander,

Sorry to hear you're experiencing a crash. Have you played War for the Overworld before, if so are these crashes a recent development?

I wonder if you'd be able to upload to us a DXDiag of your system How To: Generate a DXDiag Report.

In addition, I assume you're playing Level 3 of the main campaign. Can you describe when the crash is happening, is it happening at random intervals and always on this level. Does the crash happen in Skirmish mode?

Unfortunately, our team is currently very busy working towards a major milestone on our next project. But crashes are important to us and we'll try to get back to you as soon as we can.

Hope we can get you into the game,

Lee

Hi Endymon,

Thanks for your ticket, this is certainly behaviour that deserves further investigation. There are some known issues with this UI element already so I suspect they might be related.

As our team are currently very busy on Project: Aftercare we don't currently have the resources available to investigate but we are planning to do a pass on WFTO tickets in the near future.

In the meantime Can you confirm for me the resolution you play at?

I'll drop this into our Triage queue.

Cheers,

Lee