Jump to content

Recommended Posts

Posted

People, devs know it's crashing. Instead of saying "erp it's crashing" a thousand times try to be helpful and give them snippets of your crash.log so they can work with that.

Posted

It seems to crash generally when i get closer to the enemy. It might be something to do with the jester files in that situation.

Modules owned:

 

FC3, M-2000C, Mig-21bis, F-5E, AJS-37 Viggen, F/A-18C, KA-50, Mi-8, F-14A&B, JF-17

Posted

I was wondering because I didn't have crashes, but I was flying performance tests only and A/G with just some light and totally incapable Anti Air (le me being too fast for them). But now I had three crashes in a row in the PG BVR quick mission. Looks like it's pretty easy to reproduce there. But they're always Windows APPCRASHes, no crashlogs generated at all...

dcsdashie-hb-ed.jpg

 

Posted

CTD in single player for me whilst using the Dynamic Campaign engine, no logs and another in a multiplayer coop server.

 

Was turning on to a couple of MiG-29s in DCE and firing my second phoenix in multiplayer.

Posted

Just had a CTD when i tried launching a sparrow myself.

V/R,

Ohgr

VCVW-11 "Vapor"

 

USN AE 2001-2015

Heatblur Tomcat Tester

Posted

I had that happen to me, actually it didn't even get to the crash. but I am having massive multiplayer issues, in both the "stable" Version, and the beta. I am scared that when the next update for the stable version comes along I wont be able to go pn multiplayer in that version either.

Posted

I forgot that this was talked about even though i experienced two crashes tonight.

 

I did some ground pounding first (aka lawn darts), no issues (game crash wise).

Decided to do some intercepts. Engaged two F-16s, phoenixed both no issues.

Engaged a bear, phoenix missed got close with sidewinder and guns, no issues.

Engaged two MiG-29 (S i think), closed distance to around 25 NM i think and crash.

Logged back in, re-engaged the MiGs, closed distance and crashed.

 

Don't know if the MiGs launched at me, but i think they did lock me (without issue). F-16s definitely got closer than the MiGs, as did the bear, so its not just a distance issue.

Posted
Thank you for testing and letting us know about the issue.

 

We have identified the cause of the crashes, and we are testing a fix now.

 

Thank you. If all goes well, can we expect a hotfix today, or should we just rollback to the previous patch for the moment? (i.e. fix coming later than tomorrow)

Posted
Thank you for testing and letting us know about the issue.

 

We have identified the cause of the crashes, and we are testing a fix now.

 

Good to hear. I have had only performance related crashes before this last patch. This last patch has since fixed most performance issues, however it has caused crash issues related to BVR AIM7 combat it seems.

Current specs: Windows 10 Home 64bit, i5-9600K @ 3.7 Ghz, 32GB DDR4 RAM, 1TB Samsung EVO 860 M.2 SSD, GAINWARD RTX2060 6GB, Oculus Rift S, MS FFB2 Sidewinder + Warthog Throttle Quadrant, Saitek Pro rudder pedals.

Posted

my observations:

as long as i stay out of STT and the pilots doesnt use any of his modes i am fine for longer

If in STT/Pilots modes, dont manouver hard or CTD

 

of course this is all VERY subjective but its how it feels to cause the issue

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

Posted (edited)

I created this little mission here (f14 vs f5), I would say DCS crashes 50% of the time while playing this mission. I don't get any crash logs

 

> After trying a couple more times, it seems to crash when jester identifies the target as an F5 around 9.7nm. It seems to happen when I have locked the target up. You don't even need to have any weapons selected. I locked the target up with the horizontal scan mode.

training.miz

Edited by dikkeduif
Posted (edited)

Looking forward to the fix. I can't complete the Trench Run Reactor Strike Mission without a CTD. After four attempts, DCS always crashes after bombing the reactor and getting away from the pissed off MiG-23's.

 

(Heatblur F-14)

Edited by syncs

Heatblur F-14 Tomcat | DCS F/A-18C Hornet | DCS A-10C II Warthog | BelSimTek UH-1H







 

 

RTX 2080 Super, i7 8700K @ 4.9Ghz, 16gb 2400Mhz DDR4, Asus Z370F, Corsair H115i Pro

Posted

I hadn't enough time to play with the Tomcat after release, so i don't know if this CTD's are from the last patch....

 

I had 3 CTD's only in the F14 and everytime under the same conditions:

- Singleplayer with 1 Tanker or some trucks(6) for training, nothing more

- evreytime i was quite low and pulled some +G's and DCS crashed without error message or the usual crash report logs

 

First i was flying the F-18 and doing some AAR, switched from the F-18 to the F-14 in the ME and tryed the same, did some low level flying afterwards and got the CTD. I looked in the last tmp log from DCS, these are the last lines, file attached.

2019-03-23 14:12:09.787 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\windrushing): gain

2019-03-23 14:13:36.726 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:damage\structuralgroan): gain

2019-03-23 14:13:36.841 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_impact): gain

2019-03-23 14:13:36.842 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_missileimpact): gain

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Posted

CTD

 

2019-03-23 15:22:17.759 ERROR EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH

2019-03-23 15:22:17.762 ERROR EDOBJECTS: Object HB_F14_EXT_PHX_ALU with id=292 already declared in table MissileTable

Posted
We don't need more logs gents :)

 

This is fixed internally. For now; unfortunately, you'll have to disable Jester by using A->A->8->1 to avoid any crashes.

 

So RIO required for MP until a patch is released?

Posted
Crash direct to desktop

 

Mission: Beyond Visual Range - Persian Gulf

Situation: Crash After TWS Launch of 2x AIM-54 at two Mig-29 from 25nm

 

PC:

 

I7 2700K @ 5ghz

16 DDR3 1866Mhz

GTX1080TI

RAID0 2XSSD 480GB SATA III

Windows 10 PRO 64 Bits 1809

 

log below

 

+1

I was about to describe the same situation. Well, I'll play some tennis I think, see the world outside.:music_whistling:

Intel 8700K@4.7ghz(all cores) / 32Gb DDR4 /WD Black SN750 Heatsink 500gb (DCS Only) / MSI GeForce RTX 2070 GAMING Z 8G / Windows 10 PRO / VPC WarBRD Base + Warthog Stick + Foxx Mount / Thrustmaster TPR pedals / Thustmaster MFD / Thrustmaster Warthog throttle + Monstertech chair mount

Posted (edited)
We don't need more logs gents :)

 

This is fixed internally. For now; unfortunately, you'll have to disable Jester by using A->A->8->1 to avoid any crashes.

 

what does that mean for Multiplayer human RIOs? or was jester active even when a human climbed into the back?

my Pilot rarely crashes, its just me as a RIO

Edited by Nero.ger

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

  • Recently Browsing   0 members

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