Jump to content

[RESOLVED] CTD MP


Neuse

Recommended Posts

I'm thinking it's got to do with ground clutter because my chances of crashing when locking over sea are considerably lower (like 5% of times when locking using PAL or going STT) compared to over land where I crash 50% of the time. Didn't try to lock a targets above, someone if they have time should do extensive testing trying MLC in or MLC off, higher or lower, over land or over sea, this could nail it down.

 

I think it might still have to do with jester and his behavior once you have a target STT locked, whether it be PAL or another method. It seems that is the situation I CTD the most. With a human RIO, I never have crashes even when STT locking.

Modules owned:

 

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

Link to comment
Share on other sites

  • Replies 124
  • Created
  • Last Reply

Top Posters In This Topic

I think it might still have to do with jester and his behavior once you have a target STT locked, whether it be PAL or another method. It seems that is the situation I CTD the most. With a human RIO, I never have crashes even when STT locking.

 

I've had 8 crashes in one night as a human RIO, trust me on this, it definitely still crashes and crashes a lot more often when ground clutter (even if in a Doppler mode) is processed.

Jester accounts for the random crashes probably, the ones unrelated to PAL or STT.

 

This is just a theory, how the returns are processed, how deep the simulation is, I've got no idea but I really don't see why, in my case and for a couple other people and friends I know, locking a bandit lower when he's over sea makes me crash less often then when he's over land other then ground returns being involved. You get a lot less over sea, close to none.


Edited by Rex854Warrior

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Anything new on this? There goes no day without seeing people complain on Blueflag server that there F14 CTD´s all the time...i dont even bother trying anymore thb.....its a pain preparing everything and then just crashing for weeks.

 

 

Yeah sadly I've just realised I haven't opened DCS once this month in favour of 'another' sim due to the crashing.

 

 

It sucks because the F-14 is a masterpiece and online MP play is the only way you can get a decent dynamic experience against good adversaries.

 

 

 

I hope it gets fixed soon but until it is looks like DCS will attract some dust.

F-15E | AH-64 | F/A-18C | F-14B | A-10C | UH-1H | Mi-8MTV2 | Ka-50 | SA342 | Super Carrier | Nevada | Persian Gulf | Syria |

Intel Core i7 11700K - 32GB 3200MHz CL16 DDR4 - MSI GeForce RTX 3060 Gaming X 12GB - Samsung 970 EVO Plus NVMe SSD 1TB

Link to comment
Share on other sites

(As Human RIO) When the F14 was first released, I had no CTD. After first patching CTD all the time, then it was patched again and it seemed ok for a bit.

Since the latest few patches its Back to CTD. My friend is also having identical issues.

 

In Fact I've stopped flying F14 as a Human Rio. I believe this may be the case for many as I'm seeing less and less F14's on the servers.

 

Will submit logs later - but I don't think you will find anything different to what has already been posted.

 

My question is - Can anyone fly this thing with human pilot and human RIO without CTD?

Link to comment
Share on other sites

Same here, is the 14 flyable just with a pilot and no CTD? Is everyone here having crashes with a human RIO as well or are you flying as just a pilot.

 

I too had a period of no crashes but now the module is unusable (certainly as a 2 human seater).

 

When my RIO crahes out I am then unable to use any of the radar modes at all. This happens on every session.

 

If there is anyone that does fly the F14 with 2 humans and has no crashes at all I'd love to hear what is different or what your settings might be.

Link to comment
Share on other sites

I have had multiple crashes in MP with F14. The game just closes and throws me to desktop!

Intel i7-9900K @ 4.9GHz | 32G DDR4-3600 | RTX 2080 ti (11GB) | VKB MGC Pro Gunfighter II + РУД Warthog Throttle + Slaw Device RX Viper Pedals | 34" WQHD 120Hz | Track IR 5.

Link to comment
Share on other sites

I keep crashing on Blue Flag server with no logs provided. Happens pretty much every time I'm being engaged by bandits, low altitude with Jester.

 

 

 

I invest 30-40 minutes into flying and it just crashes, wasting my whole free time. Getting really frustrated here.

Link to comment
Share on other sites

Yeah I've shelved the F-14 and DCS entirely for the time being.

 

 

Any ideas why there's been not response from the Dev team? Are they still trying to find out what is going on?

F-15E | AH-64 | F/A-18C | F-14B | A-10C | UH-1H | Mi-8MTV2 | Ka-50 | SA342 | Super Carrier | Nevada | Persian Gulf | Syria |

Intel Core i7 11700K - 32GB 3200MHz CL16 DDR4 - MSI GeForce RTX 3060 Gaming X 12GB - Samsung 970 EVO Plus NVMe SSD 1TB

Link to comment
Share on other sites

Yeah I've shelved the F-14 and DCS entirely for the time being.

 

 

Any ideas why there's been not response from the Dev team? Are they still trying to find out what is going on?

 

https://forums.eagle.ru/showthread.php?t=241316

 

I'm not sure they know what's going on at the moment based on responses to my post in the link above.

 

I'm not sure how they are trying to testing for it (i.e. how many testers, how long, etc), but they said that they cant reproduce it at all.

 

I'm thinking it might have something to do with large, populated servers and the information overload when stt locking? Maybe they need to focus their testing on an environment where many people are involved. Maybe try playing a couple rounds in the Blue Flag or DDCS servers to reproduce?

Modules owned:

 

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

Link to comment
Share on other sites

The CTDs seem to be very random for me. Lastnight I had no CTDs during a 4 hour mp mission. Same mission a couple of nights ago I CTDed 3 times. I always play on DDCS server. Most CTDs are with PAL lock and launch of a aim54.

 

I would like to test locking an enemy in PAL and then have him turn on jammer. Maybe that is creating my CTD? Or have enemy JAM before I lock in PAL and then try locking him.

 

CTD has happened when I lock F18s and F15s I know. Both A/C have a jammer.

 

Everyone on TS and Discord that has F14 CTDs in mp. I find it hard that the internal testers are not. Just have them play on a BF or DDCS server.


Edited by mia389
Link to comment
Share on other sites

Locked an AI helicopter with PAL. CTD. So I do not think it's jammer related.

 

EDIT:

Happened to me again just now. This has happened multiple times on the same SP mission.

 

Flying SP mission. Just started up. Took off from carrier, flew to AO.

Have Gun selected

Press PAL lock with an enemy helicopter in sights.

Instant CTD, no errors.

 

Latest DCS.

No mods.

No programs running except TrackIR.

nVidia GTX 980, driver 430.53


Edited by chrisofsweden

GPU: PALIT NVIDIA RTX 3080 10GB | CPU: Intel Core i7-9700K 4,9GHz | RAM: 64GB DDR4 3000MHz
VR: HP Reverb G2 | HOTAS: TM Warthog Throttle and Stick
OS: Windows 10 22H2

Link to comment
Share on other sites

After a while of a F14 break today first flight on blue flag...crash when getting locked up by an F18.

 

2019-05-27 17:55:43.701 INFO Dispatcher: //=== END OF INIT ======================================//

2019-05-27 17:55:43.701 INFO EDCORE: (dDispatcher)enterToState_:2

2019-05-27 17:55:43.777 INFO EDCORE: (dDispatcher)enterToState_:3

2019-05-27 17:55:43.777 INFO Lua: Lua CPU usage: metric: average game loading: 37.8750 %

2019-05-27 17:55:46.290 INFO NET: client has started

2019-05-27 17:56:12.343 INFO NET: client has stopped

2019-05-27 17:56:16.055 INFO EDCORE: (dDispatcher)enterToState_:5

2019-05-27 17:56:16.087 INFO DCS: application shutdown

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\terrains\nevada\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\uh-1h\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\tf-51d\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\sa342\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\mi-8mtv2\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\mig-21bis\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\m-2000c\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\l-39c\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\ka-50\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\flaming cliffs\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\fa-18c\sounds\sdef"

2019-05-27 17:56:16.160 INFO SOUND: detaching sdef path ".\mods\aircraft\f14\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\mods\aircraft\f-5e\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\mods\aircraft\c-101\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\mods\aircraft\av8bna\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\mods\aircraft\ajs37\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\mods\aircraft\a-10c\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\mods\tech\combinedarms\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\sa342\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\mig-21bis\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\m-2000c\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\i-16\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\f14\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\christen eagle ii\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\chinaassetpack\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\c-101\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\aircraft\av8bna\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\tech\uss john c stennis\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path ".\coremods\tech\techweaponpack\sounds\sdef"

2019-05-27 17:56:16.161 INFO SOUND: detaching sdef path "sounds\sdef"

2019-05-27 17:56:16.182 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 0

2019-05-27 17:56:16.183 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 1

2019-05-27 17:56:16.183 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 2

2019-05-27 17:56:16.249 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 3

2019-05-27 17:56:16.301 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 4

2019-05-27 17:56:16.304 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 5

2019-05-27 17:56:16.305 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 6

2019-05-27 17:56:16.305 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 7

2019-05-27 17:56:16.305 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 8

2019-05-27 17:56:16.306 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 9

2019-05-27 17:56:16.306 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 10

2019-05-27 17:56:16.306 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 11

2019-05-27 17:56:16.306 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 12

2019-05-27 17:56:16.527 INFO VISUALIZER: SceneManager_Implement::~SceneManager_Implement()

2019-05-27 17:56:16.527 INFO VISUALIZER: TerrainRenderer::release

2019-05-27 17:56:16.529 WARNING LOG: 1 duplicate message(s) skipped.

2019-05-27 17:56:16.529 INFO TERRAIN: lSystem::exit()

2019-05-27 17:56:16.529 INFO TERRAIN: lSystem::CleanScenes()

2019-05-27 17:56:16.531 INFO DX11BACKEND: DX11Renderer::shutdown()

2019-05-27 17:56:16.571 INFO DX11BACKEND: NVIDIA API exit OK

=== Log closed.

Link to comment
Share on other sites

Happened to me also. CTD in MP.

ASUS N552VX | i7-6700HQ @ 2.59GHz | 16 GB DDR3 | NVIDIA GF GTX 950M 4 Gb | 250 Gb SSD | 1 Tb HD SATA II Backup | TIR4 | Microsoft S. FF 2+X52 Throttle+Saitek Pedals | Win 10 64 bits

Link to comment
Share on other sites

Really hope this can be identified and fixed soon so we can start enjoying this birds combat aspects. So far, all CTD's I've had have all been when locking something up with PAL. Both in SP and MP.

HB, you seem to struggle with this bug(s). Is there anything more in depth error reporting we can do as a community to help identify the issue?

GPU: PALIT NVIDIA RTX 3080 10GB | CPU: Intel Core i7-9700K 4,9GHz | RAM: 64GB DDR4 3000MHz
VR: HP Reverb G2 | HOTAS: TM Warthog Throttle and Stick
OS: Windows 10 22H2

Link to comment
Share on other sites

  • Recently Browsing   0 members

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