rob10

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.

That really sounds like a hardware issue, likely a hard drive issue (logs are full of access denied errors when trying to write). Blue screen of death and buzzing noise like that is unlikely to be caused by DCS. The update might have increased the load on the hardware just enough cause it to show up now or it might be coincidence that it happened now.

It all worked correctly -- told me to do a 2nd pass which I did and failed to kill them again, then mutterred choice words to himself and was going to do a 3rd pass before the wing called that dam had been blown. That's all working correctly. It was after the dam was blown and mission fail screen came up that it then carried on with the mission success messages behind that. Not sure if I actually killed them and it failed to register that, but I assumed I hadn't. Don't have track but likely still have Tacview if that helps.

My guess is that it probably hasn't been set up for those modules. I have never used the profiles, but I didn't think you could download from DCS to the SimAppPro profile -- I thought you had to set it up in the profile and download that to DCS. I know you don't want the "don't use it" answer, but I suspect that the profiles within SimAppPro aren't used by many so it likely doesn't get a lot of attention from WinWing. I use the software for controlling lighting on my devices, but I've never used the profiles. If you want a backup you're likely better to just bind it in game in DCS then make a copy of the inputs folders. Worst case you can rename the device ID's and get everything back if you had to move to a new computer and it's pretty simple to do.

Not sure what the actual specs are, but I have a full F-18 MIP setup with 3 screens plugged into a 7 port powered hub and haven't had any issues with it. And I have a cheap powered hub with just a button box (some lights), wireless + wired mice and wired keyboard that has issues some times so YMMV .

Pretty minor, but if you don't manage to take out the terrorists on the dam, you get the message from yourself cursing at your own incompetence (nice touch!), then message from wing that they've blown the dam. Not too long after that the "mission fail" screen comes up, but in the background, since the people on the dam are washed away and killed presumably, you get a "way to go" message from your wingman and then the mission success/RTB message from strike. This occurs during the timeout for the mission fail screen which functions properly and ends the mission after the 10 second or so delay. Just needs a trigger to stop mission success from firing if dam blown condition occurs.

That's the "ghost" VV so you have an indication of where it actually is pointing. Caging allows you to keep the HUD ladder in your view when it otherwise might be skewed off the side and hard to see due to wind etc. The ghost VV is so you can still see where your actual VV is pointed (which is important since that's where you aircraft is actually going) AND be able to see your HUD ladder under those conditions. So, yes this is normal.

Do you have any mods installed? That doesn't look right at all which implies something interfering and mods are the 1st suspect.