rob10

And how many posts have you seen of people missing the DCS.exe from their DCS-MT folder after the update? Can't say I've seen more than yours, which would suggest a problem on your end rather than a widespread ED/DCS problem. Following Rudel_chw's advice in the post above would be a good starting point.

None of the fuzing info has been updated in the manual to reflect the recent changes, so don't bother looking there. Due to limitations with the MC it's not possible to have 2 different fuses on the SAME weapon. So you could have different ones on GBU-12 vs GBU-38 but not 2 different fuses on GBU-12's or 2 different fuses on GBU-38's on the same plane at the same time.

You might as well. Today's newsletter announced that ST will be fully deprecated with the next patch.

You just need to click on the little triangle in the upper left corner of the weapon pylon with the LGB on it and it will give you options to change the laser codes and fuzes on the bomb. In the mission editor of course.

According to your logfile your pagefile is set to: 256 MB which is why Silverdevil mentioned it. Your DxDiag seems to show you have 32 mb pagefile set though . But definitely showing out of memory errors in a few spots in the logs so I'd question whether you have a hardware memory issue.

I completely understand where you're coming from, but not sure how you do that with a keypress or button press. It's either ON or OFF. In theory you could have it ramp up from zero to full, but then if you stop pressing does it immediately go back to zero or ramp down? And where does it start if you press again quickly -- on full or start over at zero and ramp up? Not really sure how you do brakes well without an axis.

Tracks are NOT a recording of what happened. They were originally designed as debugging tool and they record inputs and recreate what happened based on the inputs. This means that due to random changes in conditions you can get wildly different results in the track than what originally happened (and different results with multiple runs of the same track). From the forums they have generally gotten better more recently, but you're not going to consistently get an exact replay of what happened.

Hmmm ... in that case you probably need to contact ED support. I like to rule out the forum vs account thing because it often catches people out.

The actual STORE website should use your DCS account. That is DIFFERENT to login you're using for the forums (unless you happen to use the same ones, they are 2 separate systems)

Are you in A-G master mode? You won't get a reticle in the HMD if you're not (just a cross IIRC). I'm assuming you realize that the HMD will blank when you're looking at the HUD unless you turn off HUD BLANKING in the settings for the HMD.

16 GB RAM is technically the min required, but the latest updates are definitely using more and lots of people with only 16 GB RAM starting to have issues. Increasing your pagefile is a good starting point, but you might as well plan on getting more RAM in the foreseeable future to keep playing.

Was reported long ago. Even aside from that I doubt it's a high priority fix. See this thread for a detailed description of procedure restart if you run out of fuel at an airport. Tried it tonight and it works IF you follow the directions exactly (esp. waiting for before turning the EXT POWER switch to OFF).

Post a log. Might give some clues. My 1st suggestion would be removing whatever MODS you have installed (esp. whatever you might have installed in the Saved Games folder). There have been all kinds of weird interactions that give behaviour that makes no sense (i.e. F-14 fine, F-4 problem) over the years. What you're seeing is pretty extreme and there would be pages of posts if the root problem was the F-4 being that bad. Which suggests something different on your end is causing the issue you're seeing.

Yep, that's what I was thinking of.

There was a change recently in what you have to do to make this show up IIRC. I don't use it so I can't remember exactly what it is or where to find it, but I'd start by reading through the Mission Editor subforum because it was likely there.

At this point you should try uninstalling the A-4E mod and see if that helps. There is a massively repeating what appears to be a graphics error.

Do some digging around in this forum. I seem to remember someone else having this issue sometime earlier this year and there was a simple cause (can't remember what the cause was right now). Here's the thread that has some solutions (farther down in the thread). Others were running into this issue back in Jan of this year and this seemed to help them.

For starters, your system is getting pretty weak for current versions of DCS. At a minimum try bumping your pagefile to get a total of 64 GB between pagefile and physical RAM. There are a lot of recent crash issues where the user has 16 GB or less of RAM. While that may technically meet minimum requirements, it's not really realistic anymore. Also a RX570 video card with 4 GB is going to make this worse (and it doesn't meet min 6 GB requirement). DCS is very memory hungry.

Reported issue. Use MT and it will work. May or may not be fixed in ST going forward since ST will be depreciated (removed) likely in the fairly near future since these types of bugs are starting to pile up in ST. It was announced last year sometime that ST was on it's way out.

That was what I figured had happened.

Here's the Tacview. Looks like Matrix hit one and I must have fired high both runs. Tacview-20240825-132004-DCS-SYRIA M4 NIGHT MOVES.zip.acmi

Near right side of the row of buttons at the bottom of the controller bindings screen.

Random thought: have you tried disabling HOT PLUG in DCS? Power management/sleeping USB hubs would have been my other thought but you've looked after that.

I'd be pretty sure that if Vulcan was added it would have been mentioned in the change log. Pretty sure ED talked about Vulcan being required more for deck crew stuff than the Airboss.

Pretty sure ChillNG will fix it for you (and DRM will prevent you from doing much with it anyway). The "easy fix" comment is since a lot of the time changes in DCS mean fixes aren't easy but apparently this one is something obvious and simple to fix. But you'll have to wait for the next update.