[NO BUG] f-14 crashes on loading.

[agentdarnell]

So the f-14 has started crashing every time I try and load into the game. The other modules work fine and its just the f-14. Say I load free flight it loads almost all the way then crashes. Same thing with custom scenarios. It worked till this week.

Edited August 14, 2019 by IronMike

[RaisedByWolves]

Did you try doing a repair?

[agentdarnell]

Did you try doing a repair?

 

I have uninstalled the f-14 and reinstalled. Its not the dcs as its only the f-14 doing it. Can I just repair the f-14 or delete all files for the f-14 when uninstall it and redownload them?

 

Edit I just did a repair and it is still crashing with just the f-14.

Edited August 11, 2019 by agentdarnell

[draconus]

Please attach dcs.log and try with clean profile.

[agentdarnell]

Please attach dcs.log and try with clean profile.

 

What do you mean by clean profile?

 

Here is the log

dcs log.txt

[draconus]

What do you mean by clean profile?

Just temporarily rename the folder:

C:\Users\<User Name>\Saved Games\DCS OpenBeta

Run the game, it will start with new config. If it works ok with new profile then it was something in your configs (added or modified files). If not I suggest to contact support.

https://www.digitalcombatsimulator.com/en/support/faq/710/

https://www.digitalcombatsimulator.com/en/support/faq/556/

 

After clean/repair - did you run the updater? (you should)

[agentdarnell]

Just temporarily rename the folder:

C:\Users\<User Name>\Saved Games\DCS OpenBeta

Run the game, it will start with new config. If it works ok with new profile then it was something in your configs (added or modified files). If not I suggest to contact support.

https://www.digitalcombatsimulator.com/en/support/faq/710/

https://www.digitalcombatsimulator.com/en/support/faq/556/

 

After clean/repair - did you run the updater? (you should)

Yes ran the updater. I also switched back to the stable version and it still crashed when loading the f-14. I played every other module without an issue. I am switching back to open beta now and will try to do a clean profile.

 

Edit. I tried what you suggested and still crashes just with the f-14 module. I have most of the modules and only the f-14 has problems with crashing.

Edited August 13, 2019 by agentdarnell

[draconus]

How do you test? Is it specific mission you try to run all the time?

System specs?

[agentdarnell]

How do you test? Is it specific mission you try to run all the time?

System specs?

 

So far its any quick mission I try to load or any custom I try to load. Say I try free flight in the Persian Gulf or in Caucasus, takeoff from anywhere, even creating my own. I can pull up any other module and it works but always crashes with the f-14.

[draconus]

I asked for system specifications as my last idea is to make sure you have big enough swap file, ex. 32GB and also try low graphics settings. Please contact support team.

[IronMike]

Hi, sorry I did not answer you earlier.

 

Yes, could you please share more information. Since this is a single, isolated issue, it strongly suggests that something on your side might not be coping with the F-14 well or that you suffer from a corrupt install in which case it is best to remove all F-14 related folders (also inputs), and run a repair.

 

But it is very hard to tell on that little info.

[agentdarnell]

Hi, sorry I did not answer you earlier.

 

Yes, could you please share more information. Since this is a single, isolated issue, it strongly suggests that something on your side might not be coping with the F-14 well or that you suffer from a corrupt install in which case it is best to remove all F-14 related folders (also inputs), and run a repair.

 

But it is very hard to tell on that little info.

I had attached my log. I will try and do an uninstall and find the f-14 folder and delete everything. It was working till the last update

[IronMike]

I had attached my log. I will try and do an uninstall and find the f-14 folder and delete everything. It was working till the last update

 

 

Oh, my sincere apologies, I overlooked that reply. I just forwarded your log to our devs, we will take a look if it reveals something. Would you mind sharing your full system specs, too, please? Thanks!

[agentdarnell]

Running an Intel xeon hex core, 24 gigs ram, sli GTX 1070, think I have around 200 gigs free on this hard drive. I might swap it over to my games drive as there is around 2tb of space. Running a 1440p 27" monitor.

[IronMike]

Running an Intel xeon hex core, 24 gigs ram, sli GTX 1070, think I have around 200 gigs free on this hard drive. I might swap it over to my games drive as there is around 2tb of space. Running a 1440p 27" monitor.

 

 

 

 

Thanks, your specs should not be the problem.

[agentdarnell]

OK I have uninstalled it again, deleted the folder for the f-14, ran a clean, and re-downloading the f-14 now and will reinstall it. I will update here and if crashes again include the log.

 

Now that I reinstalled it it says need module for load mission f-14b

Edited August 13, 2019 by agentdarnell

[agentdarnell]

OK after uninstalling, deleting the f-14 folder, reinstalling and running a repair it seems to be working. I was able to pull up free flight in Caucus map.

[draconus]

OK after uninstalling, deleting the f-14 folder, reinstalling and running a repair it seems to be working. I was able to pull up free flight in Caucus map.

:thumbup:

[IronMike]

OK after uninstalling, deleting the f-14 folder, reinstalling and running a repair it seems to be working. I was able to pull up free flight in Caucus map.

 

 

 

 

Awesome that is great news, it spares me to tell you that the log did not indicate anything to what have caused it, in that sense even better that you got it fixed! I wish you lots of fun with it! :)

[draconus]

Awesome that is great news, it spares me to tell you that the log did not indicate anything to what have caused it...

 

What about DCS and module version mismatch? Is it normal?

[IronMike]

What about DCS and module version mismatch? Is it normal?

 

 

yeah, nothing in the log pointed to a reason for a crash.