[BUG] F-14B Tomctd? (10th April Update CTD ) - ED Forums
 


Notices

Reply
 
Thread Tools Display Modes
Old 04-10-2019, 06:51 PM   #1
ebabil
Senior Member
 
ebabil's Avatar
 
Join Date: May 2009
Location: Turkiye/Istanbul
Posts: 2,827
Default [BUG] F-14B Tomctd? (10th April Update CTD )

Just for the heads up, first flight online and CTDs' again
__________________
FC3 | UH-1H | Mi-8MTV2 | A-10C | F/A-18C | Ka-50 | F-14A/B | F-4E | F-16C
Nevada | Syria
NS-430 | Carriers
Ultimate Argument | Oilfield | Argo | Border

Youtube

Last edited by IronMike; 04-14-2019 at 05:41 AM.
ebabil is offline   Reply With Quote
Old 04-10-2019, 07:05 PM   #2
Strikeeagle345
Senior Member
 
Strikeeagle345's Avatar
 
Join Date: Jun 2016
Location: Illinois, USA
Posts: 1,189
Default

Quote:
Originally Posted by ebabil View Post
Just for the heads up, first flight online and CTDs' again
upload logs...

say "i ctd when I fly the tomcat" doesnt really help much.
__________________

Strike
VF-41
vCVW-11
www.vcvw-11.com

i7-9700K OC 5GHz| MSI MPG Z390 GAMING PRO CARBON | 32GB DDR4 3200 | GTX 1070 | Samsung SSD | Samsung Odyssey+ VR | HOTAS Warthog
Strikeeagle345 is offline   Reply With Quote
Old 04-10-2019, 10:06 PM   #3
chrisofsweden
Member
 
chrisofsweden's Avatar
 
Join Date: Jan 2014
Posts: 566
Default

I had one too. Originally posted in DCS World Bugs Game Crash section
chrisofsweden is offline   Reply With Quote
Old 04-10-2019, 10:16 PM   #4
Eldur
Senior Member
 
Eldur's Avatar
 
Join Date: Dec 2009
Location: On a fluffy cloud above Ponyville
Posts: 2,060
Default

Quote:
Originally Posted by Strikeeagle345 View Post
upload logs...

say "i ctd when I fly the tomcat" doesnt really help much.
Well, on a CTD DCS doesn't even create a log. See the issue?

I can count the crash logs DCS made in over a decade on a single hand... but I had way more of instant crashes on the contrary to that.

Probably depends on what you see as CTD though. For me CTD is just the sim (or any game or program) instantly vanishing so I just stare at my desktop a fraction of a second after I still was in the sim with no warning, crash messages or alike.

At least it's possible to up the regular logfiles, though they hardly ever contain valuable information on a crash.
__________________
Eldur is offline   Reply With Quote
Old 04-10-2019, 10:23 PM   #5
statrekmike
Member
 
Join Date: Dec 2011
Location: Providence RI
Posts: 452
Default

When posting about these crashes, Heatblur is going to need more than "It crashed again". While it is true that these CTD's seldom (if ever) produce logs, it is useful for us to provide them with the circumstances of the crash. What we you doing? Were you on a big multiplayer server? Were you playing single player? If so, was it a custom mission or one of the pre-made ones?

Going into as much detail as possible will help them duplicate the crash and thus solve it.
statrekmike is offline   Reply With Quote
Old 04-11-2019, 12:23 AM   #6
Strikeeagle345
Senior Member
 
Strikeeagle345's Avatar
 
Join Date: Jun 2016
Location: Illinois, USA
Posts: 1,189
Default

Quote:
Originally Posted by Eldur View Post
Well, on a CTD DCS doesn't even create a log. See the issue?

I can count the crash logs DCS made in over a decade on a single hand... but I had way more of instant crashes on the contrary to that.

Probably depends on what you see as CTD though. For me CTD is just the sim (or any game or program) instantly vanishing so I just stare at my desktop a fraction of a second after I still was in the sim with no warning, crash messages or alike.

At least it's possible to up the regular logfiles, though they hardly ever contain valuable information on a crash.
more often than not, these Tomcat CTD's are producing a log.
__________________

Strike
VF-41
vCVW-11
www.vcvw-11.com

i7-9700K OC 5GHz| MSI MPG Z390 GAMING PRO CARBON | 32GB DDR4 3200 | GTX 1070 | Samsung SSD | Samsung Odyssey+ VR | HOTAS Warthog
Strikeeagle345 is offline   Reply With Quote
Old 04-11-2019, 02:00 AM   #7
F900EX
Member
 
Join Date: Jan 2018
Posts: 254
Default

Same here, updated DCS, went to instant action>Persian Gulf and play the SP Southern Watch 1998 mission and within 5 mins of been in the air, I paused to look at briefing after locking a target ahead and it froze>CTD went I tried to unpause it...


Last logs below ...


2019-04-11 01:43:58.103 WARNING DX11BACKEND: Texture './Mods/aircraft/F14/Cockpit/Resources/IndicationTextures/HB_VDI_Broken.dds' has unknown format: 95
2019-04-11 01:45:10.436 INFO EDCORE: (wcTanker)enterToState_:0
2019-04-11 01:45:10.436 INFO DCS: wcTanker::onEvent:4
2019-04-11 01:45:10.436 INFO EDCORE: (wcTanker)enterToState_:1
2019-04-11 01:45:10.436 INFO EDCORE: (wcTanker::Channel)enterToState_:0
2019-04-11 01:45:10.436 INFO EDCORE: (wcTanker::Channel)enterToState_:1
2019-04-11 01:45:10.461 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\touchdown): gain
2019-04-11 01:45:23.830 WARNING LOG: 2 duplicate message(s) skipped.
2019-04-11 01:45:23.830 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\engines\f110engineint01): gain
2019-04-11 01:45:23.830 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\engines\f110engineint02): gain
2019-04-11 01:45:27.178 ERROR SOUND: invalid source_params(woLA-16783104:aircrafts\engines\f110afterburnerrearclose): gain
2019-04-11 01:45:29.102 WARNING LOG: 1 duplicate message(s) skipped.
2019-04-11 01:45:29.102 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\groundroll): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110rearclose): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110reardistant): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110_front_flyby): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110_side_flyby): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110_rear_flyby): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110rearclose): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110reardistant): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110_front_flyby): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110_side_flyby): gain
2019-04-11 01:45:39.842 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110_rear_flyby): gain
2019-04-11 01:45:40.405 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110enginesidel): gain
2019-04-11 01:45:40.405 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110enginesider): gain
2019-04-11 01:45:40.405 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110enginesidel): gain
2019-04-11 01:45:40.405 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110enginesider): gain
2019-04-11 01:45:42.480 ERROR SOUND: invalid source_params(woLA-16783360:aircrafts\engines\f110afterburnerrearclose): gain
2019-04-11 01:46:21.541 WARNING LOG: 1 duplicate message(s) skipped.
2019-04-11 01:46:21.541 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 28 squares
2019-04-11 01:46:21.541 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 28 squares
2019-04-11 01:46:21.541 INFO EDTERRAINGRAPHICS41: surface5 gc() 0.892321 ms
2019-04-11 01:46:27.664 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 7 squares
2019-04-11 01:46:27.665 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 37 squares
2019-04-11 01:46:27.665 INFO EDTERRAINGRAPHICS41: surface5 gc() 1.241598 ms
2019-04-11 01:47:05.215 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 32 squares
2019-04-11 01:47:05.215 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 32 squares
2019-04-11 01:47:05.215 INFO EDTERRAINGRAPHICS41: surface5 gc() 1.403329 ms
2019-04-11 01:47:09.762 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 44 squares
2019-04-11 01:47:09.762 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 44 squares
2019-04-11 01:47:09.762 INFO EDTERRAINGRAPHICS41: surface5 gc() 0.987182 ms
2019-04-11 01:48:21.961 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 42 squares
2019-04-11 01:48:21.961 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 42 squares
2019-04-11 01:48:21.961 INFO EDTERRAINGRAPHICS41: surface5 gc() 1.813256 ms
2019-04-11 01:48:24.568 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 33 squares
2019-04-11 01:48:24.569 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 33 squares
2019-04-11 01:48:24.569 INFO EDTERRAINGRAPHICS41: surface5 gc() 0.884856 ms
2019-04-11 01:53:16.027 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 39 squares
2019-04-11 01:53:16.027 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 39 squares
2019-04-11 01:53:16.027 INFO EDTERRAINGRAPHICS41: surface5 gc() 2.126144 ms
2019-04-11 01:53:21.318 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 9 squares
2019-04-11 01:53:21.318 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 9 squares
2019-04-11 01:53:21.318 INFO EDTERRAINGRAPHICS41: surface5 gc() 0.923734 ms
2019-04-11 01:54:39.661 INFO Lua: Lua CPU usage: metric: average mission execution: 0.6178 %
F900EX is offline   Reply With Quote
Old 04-11-2019, 03:27 AM   #8
CYLON
Senior Member
 
Join Date: Jul 2014
Posts: 1,136
Default

Oh no, not again. Is it very frequent and bad?
__________________
Intel Core i7-6800K/64GB DDR4/GeForce 1080/Windows 10/2TB HDD/1TB SSD
CYLON is offline   Reply With Quote
Old 04-11-2019, 05:08 AM   #9
overalien
Junior Member
 
Join Date: Feb 2006
Posts: 87
Default F-14B Tomctd? (10th April Update CTD )

Hello Heatblur Devs,
Perhaps this helps: I have a 100% repeatable CTD flying the single mission called 'Eclipse' from DCS user files. The crash always happens somewhere around waypoint 2 with the master arm set to on and all weapons set up for an air to ground assault just after take off. The mission requires radio silence so there is no communication on route.

The trigger for the crash appearsto simply be the time into the mission since there is no specific action that precedes the crash other than approaching waypoint 2 or waypoint 3.

I tried a suggested workaround that involves turning off TacView recording in the special options screen. This made a difference by significantly delaying the onset of the crash. The CTD still came but only one I reached the carrier.

Windows logs show application errors for dcs.exe and ntdll.dll. Nothing else in the dcs log.

I hope this helps you to reproduce the crash. If it helps, I reproduced this crash with a vanilla install, no mods other than exporting displays and no export script running either.




Sent from my iPhone using Tapatalk
__________________
__________________
overalien
Hog Driver starting to really like the Tomcat

System specs:
Intel i7-8700k - OC to 5.0 GHz
| 32 GB RAM 3600 MHz | Nvidia 1080ti SLi | Mixed Storage - Win 10 and DCS on Samsung SSD 970 Pro


Flightgear:
7 Displays (3 x 1440p, 1 X 1080p, 3 X Lilliput Touch) | 3 x Cougar MFDs
| Warthog HOTAS | Thrustmaster TPR Pedals | Jetseat + Simshaker for Aviators | Helios | VAICOM Pro + AIRIO | TrackIR 5
overalien is offline   Reply With Quote
Old 04-11-2019, 07:52 AM   #10
Super Grover
Member
 
Super Grover's Avatar
 
Join Date: Nov 2010
Posts: 114
Default

Thanks for the reports.

I tried Eclipse twice using a debug build so I could get more info should it have crashed. But it didn't. Hard to tell what caused the crashes for you and if it was the F-14. However, we will keep testing, and of course, crash logs that you will send us may help.
__________________
Krzysztof Sobczak

Heatblur Simulations
https://www.facebook.com/heatblur/
Super Grover is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT. The time now is 01:11 AM. vBulletin Skin by ForumMonkeys. Powered by vBulletin®.
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.