captain_dalan

Hmm, i'll do some more test runs then. Maybe even tonight if i get that extra free time. Same server, just to try and replicate the circmustances.

Thanks mate. Sorry for the late reply, i was just away from DCS for the holidays. I found the solution, and it turned out to be the size of my virtual memory page file. I had it set under 32 gigs. And it looks like that wasn't enough! I will clear out the temp folder though, as it seems like a good practice! Thanks again and happy holidays!

This is a strange bug that is either rare, new or it's just me first time encountering it. I was on Through the Inferno Syria this evening, grabbed an F-14A slot just as the carrier started turning. After some bumping around the carrier settled in on a new course, but my plane was leaning to one side. Never the less i still tried the starting procedure. The right engine started OK, but the left never spooled up at all. I assumed it might be plane damage, so i spawned in a new slot. The Left engine again, wouldn't start. I asked in the chat and someone mentioned it's a bug and i should start from land. I don't have a track as this was in MP, but i was wondering, has anyone experienced this issue before?

Thanks mate, your input seems to have fixed the issue!

Hi @Flappie these crashes may not be related, but i didn't want to clog the forums with new threads without a good reason, so i'll write here first. These crashes are fairly new, only started in December, which coincides with both Changes in the missions that cause them (Through the Inferno Syria and to some extent TTI Caucasus), the new DCS patch, me buying a new GPU and PSU. The interesting thing is i don't get crashes on any other MP servers, nor in SP. My rig is: CPU: i5 9600KF RAM: 32GB DDR4 GPU: NVIDEA GF RTX 3060 with 12GB of VRAM SSDs both for the system drive and the game drive I wrote to the guys of TTI on their forum page/post as well. And here is my latest log file, from last night - this morning, which is the last time i had the crash. Thanks in advance and Marry Christmas! dcs.log dcs.20221225-040325.crash

What about the RWR in other manned planes?

Ever since the start of December, i just can't get a break with the Syria server, and i get random crashes to desktop. Sometimes while still starting up on the deck of the Super Carrier, and sometime after flying around for a bit, but a crash is a certainty. Sometimes the crashes happen on the Caucasus server as well, but not as often and not as regular. I run no mods, except for a few custom made skins, the A-4 and the T-45. My setup: CPU: i5 9600KF RAM: 32GB DDR4 GPU: NVIDEA GF RTX 3060 with 12GB VRAM SSD for a hard drives, both the system drive and game drive. The only thing different i noticed from before is that the ping went up from the usual 160-170, to 180-190. However, the ping on the Caucasus is usually higher, and that results in less crashes. Anyone has any ideas what the crashes may be caused by? I don't get them on any other servers, nor in SP. Thanks in advance! EDIT: here is my latest DCS log file, from last night (this morning) if it's of any help: dcs.log

Hi devs, a short question on the new flight model (yet to come) Question: Will the new FM refinements include changes in fuel consumption as well?

@IronMike?

High pitch as in manually lofting the missile?

Nice! Didn't know that.

You can change seats in MP now?

Did the same this week (got new GPU and PSU) so i'll see how things work out in time.

What about in MP?

For a time i've been suspecting this, so tonight i finally kicked two of my training missions, one against a SARH equipped Flanker and the other against the ARH equipped Eagle. External inspection confirmed, though i didn't record a video. Jester launches chaff at certain point when faced with a semi-active threat, but never against an active one, not even after the missile has gone active and the RWR is screaming. Attached Tacviews bellow: Tacview-20221211-041509-DCS-BVR F-14A duels VS F-15C.zip.acmi Tacview-20221211-041125-DCS-BVR F-14A duels FOX 1 Su-33.zip.acmi

In my case, i may need a new power supply

The final challenge, swapped the vanilla Viper for the ED version, picked the USN adversary skin, remove pylons, matched the fuel of the vanilla bandit, and tried to shoot it down before it ran out of fuel. Took 5 tries

I don't think this to be case, as i have recording of the same thing happening with selected Sparrows or Phoenixes, but i fear that if i upload any more DCS content, Youtube will ban me for spamming! It must be that then. And a few fast experiments i performed tonight, showed that if i count slowly to 10 or so before turning away, the tracking never drops. So there's a new good common practice to have in mind i guess.

Hmm, it seems that the best workaround would be to keep the nose still for about 8-12 seconds from the moment the radar transitions from RWS to TWS. That should be enough for tracks to properly build, right? As for it being a bug or a feature.... @IronMike? Might try that as well if i have the time this evening.

Yeah, i always keep 'em on as part of the challenge.

Not an impossibility, but it would happen more randomly if it was so, and there seems to be a method to this. Also, PAL and PLM are mapped to my throttle buttons. And once i punch in blower i leave it alone. My Jester shortcuts are mapped to my keyboard, and they only involve TID orders. It's my own modification of that mission to include Charlie Phoenixes, but the mission isn't an issue, i can recreate it on any mission, including vanilla instant actions. Here's some from the Persian Gulf BVR mission. In the first 2 cases, the radar reacquires and continues tracking, but in the third one it doesn't: It appears the issue is more likely to appear near the edge of the radar cone. Also, not sure, but switching TID to 50 mile scale may play a part? I also include two tracks as short as possible, for all those are worth these days: track lost and recovered.trk track lost and not recovered.trk

No mods, except for custom skins (some made by me) and A-4 and T-45. That's actually a very good idea!

Yep, 0:43-0:46. I didn't give any commands, either PAL, PLM, or shortcut for a Jester command. i was just trying to build some offset, like i usually do when i accelerate before launching. The targets were too far away for any such attempt anyways. Though, now that you mentioned it, could it be that some weird part of the Jester logic kicked in, and he changed the radar mode on his own? This is fairly easy to reproduce really, just wait for the tracks to build, and then gently turn away from them. It also appears to happen only the first time around. Later on, if you pick them up again and let Jester/AWG-9 sort them out and build track, they won't drop if you turn away.

Thanks mate! Nah, no intent on my part, i had so little time for DCS i just forgot to turn on the high gun rate mode . Given the chance, i even take snapshots with high gun rate.

Hey guys, this is a question and potential bug report (if the behavior isn't intended). A short video follows. When looking away from the bandits after Jester sorted them out and the radar built tracks for them, especially if banking away slightly but still apparently inside radar gimbals, AWG-9 would sometimes drop the tracks, just like long ago it would drop STT locks. Is this a bug or a feature of the radar? And if the latter, how do we counter it except for running straight for the bandits? The video: The tackview: Tacview-20221204-175352-DCS-F-14A_IA_Marianas_BVR_JA11 Mk60C.zip.acmi