Jump to content

[RESOLVED] DCS Crashing While Flying F14

TexasBread

By TexasBread
in Bugs and Problems

 Share

Recommended Posts

TexasBread

TexasBread

Posted
Posted (edited)

So this is a new problem that I have encountered while flying the F14. I have not had this issue prior to the last update.

 

 

While flying in MULTIPLAYER I experience a crash to desktop with no warning about every half hour or so when flying the F14.

 

 

Current system is a 9700k @ 5ghz, 2080ti, 64gb ram, and ssd.

 

 

I do apologize for pasting the raw text from the dump file but I cant upload it for some reason.

 

 

 

2019-03-16 23:41:10.043 ERROR WORLDGENERAL: waParts f-14b_damageparts_stabilizer (//models/f-14b_damageparts_stabilizer.edm): box is invalid, skip render

2019-03-16 23:42:05.499 ERROR SOUND: invalid source_params(woLA-17934376:aircrafts\engines\f110afterburnerrearclose): gain

2019-03-16 23:42:09.413 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-16 23:42:09.413 ERROR WORLDGENERAL: waParts f-14b_damageparts_stabilizer (//models/f-14b_damageparts_stabilizer.edm): box is invalid, skip render

2019-03-16 23:42:55.054 ERROR SOUND: invalid source_params(woLA-16794632:aircrafts\engines\f110afterburnerrearclose): gain

2019-03-16 23:44:08.663 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-16 23:44:08.663 ERROR SOUND: invalid source_params(woLA-16781584:aircrafts\engines\f110afterburnerrearclose): gain

2019-03-16 23:45:02.141 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-16 23:45:02.141 ERROR SOUND: invalid source_params(woLA-19464481:aircrafts\engines\f110afterburnerrearclose): gain

2019-03-16 23:45:03.276 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-16 23:45:03.276 ERROR SOUND: invalid source_params(woLA-16923437:aircrafts\engines\f110afterburnerrearclose): gain

2019-03-16 23:45:20.099 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-16 23:45:20.099 ERROR EDCORE: Cant open file: /textures/liveries/fa-18c_hornet/104th_vmfa/description.lua.

Edited by IronMike
Gracey

Gracey

Posted
Posted

Did you run the DCS Repair?

Also you can delete the fxo and metashaders2 folders in your Saved Games/DCS.openbeta folder.

 

That might help you out with that.

It will just rebuild them when you run the game again.

Failing that, delete DCS and re-install.

Gracey's Village Always be yourself ~ Unless your can be a Unicorn, then be a Unicorn

❤️🦄❤️

TexasBread

TexasBread

Posted
  • Author
Posted
Did you run the DCS Repair?

Also you can delete the fxo and metashaders2 folders in your Saved Games/DCS.openbeta folder.

 

That might help you out with that.

It will just rebuild them when you run the game again.

Failing that, delete DCS and re-install.

 

 

 

 

Yes, already tried both. I can not re-create this crash while doing single player. Just in multiplayer and it usually crashes when someone gets blown up while in visual range of it.

Gracey

Gracey

Posted
Posted

I would assume your computer cannot keep up with the large amount of calculations it needs to do when something blows up.

Either that or you run out of memory when it happens.

Since a texture would load when you see that explosion, maybe your GFX card or cpu or both can't keep up.

Gracey's Village Always be yourself ~ Unless your can be a Unicorn, then be a Unicorn

❤️🦄❤️

TexasBread

TexasBread

Posted
  • Author
Posted
I would assume your computer cannot keep up with the large amount of calculations it needs to do when something blows up.

Either that or you run out of memory when it happens.

Since a texture would load when you see that explosion, maybe your GFX card or cpu or both can't keep up.

 

 

 

 

Lol you did see my specs right? In the original post. RAM and video memory usage are well below being maxed out however. CPU usage is around 20 percent when playing. Nothing so far indicates a memory leak

Gracey

Gracey

Posted
Posted
Lol you did see my specs right? In the original post. RAM and video memory usage are well below being maxed out however. CPU usage is around 20 percent when playing. Nothing so far indicates a memory leak

 

I mean I have 2 2080Ti's and 512GB of ram... LOL

 

Anyways,

 

2019-03-16 23:45:20.099 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-16 23:45:20.099 ERROR EDCORE: Cant open file: /textures/liveries/fa-18c_hornet/104th_vmfa/description.lua.

 

So, could it be that the crash is because of that part of the log? The missing texture.

 

Also I do not have that f110 file. Or any of those for that matter... Oddly enough.

 

The other option is to delete the F-14 Module, and then run repair, Then install it again. Also delete any non official mods.... DCS is already finicky.

 

By the way, you have an RTX card, which is not officially supported by basically anything...

Gracey's Village Always be yourself ~ Unless your can be a Unicorn, then be a Unicorn

❤️🦄❤️

TexasBread

TexasBread

Posted
  • Author
Posted
I mean I have 2 2080Ti's and 512GB of ram... LOL

 

Anyways,

 

2019-03-16 23:45:20.099 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-16 23:45:20.099 ERROR EDCORE: Cant open file: /textures/liveries/fa-18c_hornet/104th_vmfa/description.lua.

 

So, could it be that the crash is because of that part of the log? The missing texture.

 

Also I do not have that f110 file. Or any of those for that matter... Oddly enough.

 

The other option is to delete the F-14 Module, and then run repair, Then install it again. Also delete any non official mods.... DCS is already finicky.

 

 

Currently not running any mods but I went ahead and downloaded the 104th skin to see if that'll fix that part of the crash log

Clem Fandango

Clem Fandango

Posted
Posted
Did you run the DCS Repair?

Also you can delete the fxo and metashaders2 folders in your Saved Games/DCS.openbeta folder.

 

That might help you out with that.

It will just rebuild them when you run the game again.

Failing that, delete DCS and re-install.

 

 

Delete the entire folder, or just the contents of?

Ramsay

Ramsay

Posted
Posted
Delete the entire folder, or just the contents of?

 

Either, DCS will create the folders if missing.

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

TexasBread

TexasBread

Posted
  • Author
Posted

Still receiving crashes unfortunately.

 

 

 

2019-03-17 04:30:52.806 ERROR DX11BACKEND: Texture /textures/f-18c_damage_main.dds is 3d but has depth == 1.

2019-03-17 04:32:20.845 ERROR SOUND: invalid source_params(woLA-17572884:aircrafts\engines\f110afterburnerrearclose): gain

2019-03-17 04:32:32.614 WARNING LOG: 1 duplicate message(s) skipped.

2019-03-17 04:32:32.614 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 351 squares

2019-03-17 04:32:32.625 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 578 squares

2019-03-17 04:32:32.625 INFO EDTERRAINGRAPHICS41: surface5 gc() 28.065200 ms

2019-03-17 04:32:34.694 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 28 squares

2019-03-17 04:32:34.696 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 48 squares

2019-03-17 04:32:34.696 INFO EDTERRAINGRAPHICS41: surface5 gc() 3.095300 ms

2019-03-17 04:32:34.720 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 0 squares

2019-03-17 04:32:34.720 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 0 squares

2019-03-17 04:32:34.720 INFO EDTERRAINGRAPHICS41: surface5 gc() 0.092500 ms

2019-03-17 04:32:34.749 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 0 squares

2019-03-17 04:32:34.749 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 0 squares

2019-03-17 04:32:34.749 INFO EDTERRAINGRAPHICS41: surface5 gc() 0.093500 ms

2019-03-17 04:32:51.191 ERROR WORLDGENERAL: waParts f-14b_damageparts_stabilizer (//models/f-14b_damageparts_stabilizer.edm): box is invalid, skip render

2019-03-17 04:34:37.459 ERROR SOUND: invalid source_params(woLA-16871978:aircrafts\engines\f110afterburnerrearclose): gain

Gracey

Gracey

Posted
Posted

I mean, getting into the model itself at this point.

Hopefully Cobra or one of the guys will see this post.

 

Sorry man.

Gracey's Village Always be yourself ~ Unless your can be a Unicorn, then be a Unicorn

❤️🦄❤️

J3ST3R

J3ST3R

Posted
Posted

I'm also having this issue. All other aircraft are fine. No crashing to desktop. But I get in a tomcat on and within a minute or so, the game crashes with no warning.

INTEL i9 9900k @ 5Ghz, Asus Z390 strix ROG, 32gb 3200mhz Ram, Nvidia GTX 1080Ti, Corsair RM850i, Corsair H110i,, HP REVERB, Win 10 64bit.

[sIGPIC][/sIGPIC]

J3ST3R

J3ST3R

Posted
Posted (edited)
We are monitoring this issue and hunting this CTD. Shortly we'll go through all the bugreports here and tag them appropriately. Fear not- we're listening- just a bit too busy to reply :)

 

Thats good to know. I for one, certainly appreciate the hard work you guys are putting in!

Edited by J3ST3R

INTEL i9 9900k @ 5Ghz, Asus Z390 strix ROG, 32gb 3200mhz Ram, Nvidia GTX 1080Ti, Corsair RM850i, Corsair H110i,, HP REVERB, Win 10 64bit.

[sIGPIC][/sIGPIC]

Farlander

Farlander

Posted
Posted
Did you run the DCS Repair?

Also you can delete the fxo and metashaders2 folders in your Saved Games/DCS.openbeta folder.

 

That might help you out with that.

It will just rebuild them when you run the game again.

Failing that, delete DCS and re-install.

 

Please, don't go through that stuff (re-install) anyone.. Sure delete your fxo and metashaders if you want, but none of that will be fixing this issue.

 

There is also no way dcs is maxing out 64gb of ram, and too heavy for RTX2080's (paired with a high end cpu), so don't start buying supercomputers. This issue will also happen on very simple missions, which should not require more than 16gb ram. It's likely not an RTX issue either (as i've not seen really any issues with that?) and the fact it's happening to people across the board. Instead, give the heatblur guys some time to get on top of all these bug reports and wait for a fix :)

NastyFruit

NastyFruit

Posted
Posted

Yeah, same here. Seems to be combat related, not sure if its when it locks something or when something dies, but every time for me, its when I am busy engaging something. (Most of the time I am shooting at TU-22's, feels like it happens more often if I come up from behind at high speed and shoot at them, every time close range , 1 - 10nm

 

Well, that is for me at least.

Neuse

Neuse

Posted
Posted

Had it again today. Discover a target and while going in a steep decent it crashed. Others on BF discord reported the same behavior.

luza

luza

Posted
Posted

Having CTD non stop today. All using F14 on the Dogfight server. Crashed 3 times within about 10 minutes. All had targets within visual range, and could be triggered when something explodid

[sIGPIC][/sIGPIC]

Nero.ger

Nero.ger

Posted
Posted

as a RIO(multiplay) i often crash to desktop right after pilot uses CloseComabt modes or i use any STT modes. haven nailed it down any further sadly (not using Pilots CCmodes or STT, i can fly around lobbing missles for 1h+)

'controlling' the Ka50 feels like a discussion with the Autopilot and trim system about the flight direction.

-741- Vapor

-741- Vapor

Posted
Posted

Sometimes the sim chrashes to desktop seconds after takeoff with the F-14, but most of the time after 10 minutes or more. It happens in SP and MP.

i7 4770k - 24GB RAM - GTX 1070Ti

 

DCS - NTTR - Persian Golf - M2000C - MiG-21Bis - AV8B - F/A-18C - Spitfire Lf Mk IX - Bf-109 K-4 - F-15C - F-5E - F-14B

Krag6

Krag6

Posted
Posted

Here's the mission i use to crash it and 2 logs from 2 crashes. I cant get you any tracks as the game literally exits.

 

Sometimes it took a minute to do it, sometimes it crashes instantly.

 

I managed to crash it on purpose by selecting F14B Intercept slot, then using F10 menu to spawn Mig31.

 

Dcs2.log i managed to not crash thru one missile.

dcs.log insta crash basically a second after mig31 spawns

 

If you need any more testing ill be happy to help.

PUCKER TIME.miz

Logs.zip

 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...