All Activity

With all maps and most of DCS aircrafts installed my DCS installation requires approx. 1.45TB SSD space, Saved Games included. A 2TB SSD will be ok I guess, but as I have other games too I decided for a 8TB SSD. Unfortunately I do not have access to any faster web connection than 50MBit/s. DCS updates often requires a few hours. The last DCS update was 110GB for me.

+1

Same stack trace as your other logs. Yeah as I mentioned earlier, given this is 100% reproducible with the 1st mission and always when switching from hellfires to rockets I'm not convinced that these settings and other system changes will resolve this. Let's see how you go anyway though. I'd recommend going back to Stone Sky to let them know the exact circumstances, i.e. only occurs in the first mission, always occurs when switching from hellfires to rockets, and see if they can reproduce that. Do those same steps work in other missions, i.e. switching from hellfires to rockets only causes this problem in the 1st mission, switching to those in other missions is fine? Does it matter when you do switch to rockets, i.e. if you switch immediately after flying for a bit it crashes, or only after a certain point in the mission? Curious as to whether or not there are other trigger actions in that mission which expose this problem. The stack trace is a little similar to an apache crash from a few patches ago where a certain set of steps would trigger it, unrelated steps though to what you're describing. Depending on the above testing, and reproduction of this crash in the 1st mission by Stone Sky using those steps, we can ping the ED dev team to see if they can replicate anything as well.

Or multiple installs, which I don't think is that unreasonable in the case of DCS. This would also double (or more) the savings of being able to remove unwanted data.

In your esoteric attempt to derail this well-documented Heatblur USS Forrestal Bug. Did you bother to check the Launch Speeds of those S-3B? For your, and Heatblur's information, on this now even more well-documented Bug: Heatblur's USS Forrestal - 18 kts Way/15 kts Wind at 350°R/32 kts WOD. - DCS S-3B/fully fueled Data Point: Weight coming off the main wheels Cat #1: 126 kts Cat #3: 116 kts Cat #2: 126 kts Cat #4: 126 kts Again, #3 Cat shoots slow. This is a Heatblur USS Forrestal bug, that manifests itself w/ non-augmented thrust A/C, namely the A-4E-C. And you are? @IronMike Bowie Not asking them to fix anything but their Own Product, namely the USS Forrestal's slow #3 Cat. The Point of this entire Thread. And you are? Bowie

Yes, I use VoiceAttack with VAICOM which circumvent the radio menu. I suggest the OP starts using a hat for browsing the radio menu. That special feature has its own "module" like general in the controls settings. Sent from my SM-A536B using Tapatalk

With great humility and excitement, may I present the showcase of bandit648's Weather Mod 2.00: https://www.youtube.com/watch?v=r8tC6O3LrsY (edit: upload a second cut)

Yeah, I know of course. But that's still a racing seat.

Then the A-4E is placed in the wrong folder. You did unzip it of course. [emoji4] Cheers! Sent from my SM-A536B using Tapatalk

That's very strange. Probably something got corrupted. Did you do a repair after uninstalling the maps? Should have worked. They revoked your licenses? Or was it maps on trial. Then it makes more sense. A repair after uninstalling should have fixed that. Correct. This was mentioned in a newsletter, I guess you didn't see that during your time away. I pray it won't. Support should be able to help you with your old account. Just tell them your old username on this forum. Cheers!

I know I'm a bit late for the party, but I didn't get the chance to play DCS in more then a month. Here's some of my own tests, under different scenarios. Tactical use in medium and high altitudes, mostly subsonic and transonic launches, as well as some "idealized" shots in different scenarios. Top Mach achieved in a very high to very high firing scenario, from a Mach 1.8 platform was Mach 4.1+, against slightly lower target. Using the Mk60 variant should ramp that up to 4.2+. For a higher target with an even bigger RCS, and thus a longer range shot, I could see the numbers going even higher. Here's the vid:

Yeah, but not for a week! [emoji1] To be honest, the last time I had any issues with any of my banks was in 2016. Of course, if NETS is down, we all have problems, but I can't remember when that last happened. Sent from my SM-A536B using Tapatalk

I don't understand your answer. Did you even bother to read what I wrote? ED nor HB support unofficial mods.

Adding to the advice above, which I agree with (Intel for gaming makes absolutely no sense right now) I'd say a PD of 1.5 is way too optimistic and well into placebo land. In my experience, and others of this forum, when going above 1.2 or 1.3 you rapidly start to see diminishing returns. Your mileage may vary. And absolutely, get 64GB of RAM.

We added this to the to-do list. Thanks for the idea. I will keep you updated.

Hi mate. It was the V1.7 that the Black Owls shared. I've got it now...and it works with the latest version of DCS. Now I need to setup the radar correctly...it doesn't show aircraft targets.

"They are augmented thrust, Afterburning A/C. This enables them to tail-stand and accelerate to flying speed even w/ the #3 Cat's low-speed shoot. The A-4E-C is not." Did you bother to shoot an A-4E-C off the #3 Cat...? That is the Documented Issue and Bug. And you are? @IronMike Bowie

Thanks SERP International for recording our Sunday event and to everyone else that participated in both Friday and Sunday Events! Hope to see everyone at the next public event! https://www.youtube.com/live/2KVsK3jg9IQ Please note that this group is led by a group of flight enthusiasts, and none of us claim to be experts!

I would like cage/uncage for the gyros to be a toggle—so I can bind them to the same button.

Stick auto firing-safeties are also affected by this in the BE

Is it UH-1B?

Thanks! It’s the ‘map’ layer of the in game F10 map

I’ve done some testing, I can see from your photos you have Easy Communications On and are pressing the / key to open up the ‘Auto’ menu for communications in both cases. The problems I was having was using the hardbound COM1 and COM2 with easy coms off. I’m not sure if this still is an issue but I’m happy to use Easy Comms just for this campaign if it solves the problem, thanks.

Just an update. I reset the DCS settings as you advised and while my graphics look crisper (especially at 24K in the viper) the apache crashed again when I switched to rockets. I'll try the other suggestions and keep you posted! Thanks for the help. I've attached the new crash file as well. dcs.log-20250907-215416.zip