rob10

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.

What are you getting when you hit F10? It will often start zoomed way in so you might just get blue or whatever colour the ground is under wherever it's looking until you zoom back out.

I agree with this. I've landed overweight with excess descent rate and not had any issues and well within parameters and broke things enough times that to me the biggest factor seems to be being level (no bank) at time of impact. Which makes sense since if only one wheel is making contact it's going to get a lot more of the force (at least initially).

Practice, practice and practice. With a big sideorder of practice . AAR seems impossible until you manage to get some fuel the 1st time but it really does get easier. Carrier landings I'm still hit and miss.

I don't use Steam so I can't help you on that side. I know people using Steam seem to run into this semi-regularly. Check the Steam Support section on here and maybe it'll give you some ideas.

Almost for sure your authorization errors are anti-virus related. I'd start looking there. McAfee has likely decided another file is suspicious and quarantined it. McAfee has caused issues with DCS for many, many years now.

No, you don't need to delete from the old. You can reinstall from scratch without issues. It's possible (and allowed) to have DCS installed on multiple computers, you just can't use more than one copy at a time.

Check that you are actually ending up in MT. On the bottom right corner of the main screen is it showing MULTI-THREAD PREVIEW before the installed version number? If it's not, you're not launching MT for some reason. If it showing that, post your DCS logs because there's something different going on with your problem.

I've had that before. Check that the screenshot isn't actually there. IIRC it said that but it had actually saved it anyway.

It would have been useful to know you were using easy comms, but either way you really need to post a track of this occurring or we are literally blindly guessing what your problem is. You can save a track from the debrief window when you end the mission.

The map issue is a known issue with ST (and sounds like it may not be fixed). Is the GUI issue you seeing ST only as well or is a MT problem?