Wizard_03

I appreciate that, I wouldn't them to just take anyone's word for it, certainly but it just frustrating sometimes when the correct implementation is so obvious and it seems like it's just out of reach. It makes sense based on the whole idea of MSI (early form of Sensor fusion) that trackfiles are just that, files and the MCs doesn't care what display that contact is on. It's even color coded with the other tactical displays. They clearly wanted the pilot to be able to see the battle space as one cohesive picture rather then discreet sensor displays as it is in older jets.

I really find it hard to believe that the SA page cursor is only used for TUC data and can't interact with trackfiles. Like you can Designate on a track file with the cursors on AZ/EL and Attack Radar pages, but the designers just omitted it for the aircrafts main DL display page. Everything on those three pages works the same except the ability to designate. Doesn't sound reasonable. The cursor on the SA page is almost completely superfluous with the current implementation. But we know for a fact the SA page has a captain's bar cursor. It just doesn't do anything except change display settings and show TUC stuff. Which, by the way, indicates that the data is in fact corrolated in space. Makes no sense. This is one of those cases where I would have hoped ED could just make a good guess about how it works. Because It's pretty obvious. I appreciate EDs commitment to realism but we like 99 percent there already. As for restricted information The advanced functionality cat is also already out of the bag, L&S on offboard tracks. The cursor working the same way across tactical pages is very much a convenience thing. And for the record I really really doubt that the government would have an issue with the cursor functionality but not the network warfare capability. Lol Publicly available documents already acknowledge the SA page has a cursor and in the absence of direct evidence that it works differently then the other tactical pages surly common sense and deductive reasoning should be enough. In otherwords what evidence is there that it doesn't work that way?

Should we have this ability in DCS hornet? Considering we Already have TUC data on the SA page and can now Designate offboard track files, and we can designate from both the Radar Attack page and the AZ/EL page. Shouldn't we be able to also designate directly from the SA Page. It would seem to me the computer should treat all track files the same regardless of which display they are on? I.E. if it has the yellow cursor, and the tracks are all corrolated across multiple displays (the whole point of MSI) we can make the track an L&S or DT2 contact from whichever display. Otherwise what's the point of having a cursor for the SA page at all?

Native imperial user here, I'm all for a metric option for the F-15C, make it as inclusive as possible. I've been enjoying the MiG-29A and I'm glad they included imperial system for that module as well. Personally, I use the native Cyrillic cockpit with metric system when I fly it. As I took the time to learn the appropriate characters and spoken Russian, Also I already knew how to use the metric system but I didn't mind learning some of the language nessary to operate the jet EKRAN warnings, caution lights etc. Because that's representative of real MiGs, and I prefer maximum realism in as can be achieved in a commercial entertainment product. That said I think having custom language or measurement system options is only good for the sim because it opens the door to more casual players, or players who may not have as much time in their sessions to learn an entirely new system of measurement just to fly a digital airplane around. However I wouldn't expect ED to just accommodate everyone at the expense of development resources. But I would totally welcome a metric cockpit option if its possible and reasonable within the limits of their resources.

Totally agree.

It's not an air superiority by anyone's standards. An air superiority fighter is meant to go to the enemies airspace and take control of the sky from them. For that role it needs robust independent search and track cabilities, lots of range and lots of weapons. It has to be able to see, fight, and survive in contested air space outnumbered and often behind enemy lines. The Flanker filled that role for the Soviet Union. The Fulcrum is very much optimized for defensive counter air. As such It lacks the range, payload and most importantly the sensor suite to go establish air superiority somewhere else. It's a point defense asset and meant to be intergated into a comprehensive layered air Defense system. It was designed to be cheap and easy to mass produce, and it relies on things like GCI to provide situational awareness. Outside that environment, isolated and independent the MiG is not very survivable.

What a welcome surprise!! Such an Iconic warbird!

Also WW2 AI is yet to receive the newer dogfighting AI fast jets now have. So in addition to over performing the AI just makes silly decisions and does not know how to actually fight the planes according to RL period tactics. But this is ED's responsibility not mag3's, and supposedly is in the works.

They didn't call it the ensign eliminator for no reason. Flight model feels great.

I found the mirrors in the Corsair cause a big time performance hit. More so then other aircraft in game.

As the springs in the stick start to wear out it can drift off center introducing unwanted control input. No one prefers using deadzones but it is a way to correct for worn out joysticks without having to buy a new one or change the springs out.

Performance is horrible, breathtaking visual slideshow at 15 fps here.

So i recently updated to windows 11 and the issue went away for several weeks but it just came back, I had my game freeze my whole system in the mission editor again today. This is with track IR running however, I will try replicate the issue without trackIR but in the past I have been able to get it to freeze without running trackIR I just didn't save the logs at that time as I was trying all sorts of potential fixes, and pulling my hair out. I will try and post it again if it happens without trackIR just to rule it out. DxDiag.txt dcs.log

2025-04-17 21:27:04.445 INFO DXGUI_WIN_ADAPTER (Main): ChangeDisplaySettings failed! Result is -1 This seems to be the culprit.

Game is still freezing as of update 2.9.15.9408 logs attached. Can someone from ED please weigh in on this issue Multiple threads have been started, across both Russian and English language forums, several people on discord have encountered this same issue. I have been through the ENTIRE Crash trouble shooting guide, with no success. This issue is completely sapping my enjoyment of the game. dcs.log

Me too

I'm experiencing full PC freeze when DCS starts. A solution that has been working for me is to, before opening the game, delete metashaders2 and FXO files in saved games folder, perform a short repair of DCS and finally perform a cleanup from the launcher, and then DCS runs great for me. I Its only a workaround though, the last major update (the one that introduced save functionality) clearly borked something, that or its some kind of driver issue or both, the new NVIDIA driver has lots of issues with multiple games. My latest log is attached which is from a session where the game froze shortly after starting, shows no errors. The log analyzer in DCS discord recommends rolling back GPU drivers. dcs.log

No effect on the freeze for me, with or without park control. The logs also don't show any cores being parked. It freezes with and without trackir for me as well.

Very interesting, so I used to use the task manager to uncheck and recheck affinity for all cores in the DCS process, and that would instantly net me 20 - 30 FPS. So you might be on to something. This was before when I could get passed the main menu though. So I will give this a try however the problem I see is that, once the freeze happens my entire computer locks up, all im able to do is restart. But I might be able to do this before the game completly loads and freezes.

First thing I tried. Before renaming my entire saved games folder. No effect in both cases.

So this solution is now working for me as well, however I must also restart my computer between sessions, then I can do a repair and cleanup, and finally it will run. This is problematic however since I will have to rebuild shaders literally every game session, and DCS lags quite a bit during that process. Seems like a corrupted file path is created each time the game is started, which then causes it to hang the next time it is run without doing a cleanup and repair.

No effect, this isn't a stutter or FPS problem btw. I get around 80 FPS in game, when DCS is running like it had been prior to 2.9.14.8222. Instead this a full system freeze. My whole computer stops responding, Mouse keyboard, screen, controllers everything. I have to do a hard restart of my PC when it happens, and it happens now everytime I start the game, and only with DCS. Several other resource intensive programs on my PC have no issues. So I don't think its a hardware problem either, otherwise it would be happening with other major programs too.

Neither of these worked to fix the freeze on startup. Latest log attached. dcs.log

Interesting does it ever freeze mid mission for you? I was able to get past the main menu by doing a slow repair and check for excess files. Only to have it freeze again mid mission and then subsequent restarts result in it freezing on startup again. I'll try that, but many of my freeze logs have no hot plug issues so I'm not sure that's it's related. Also I have hot plug disabled in the controls section. So if it's still on then that is a separate bug.

Just updated BIOS did not fix the issue for me. DCS is not being run as admin. Latest log attached. The game worked for a second and i was able to hit the settings button and load the settings menu before it completely locked up on me. Haven't had any major performance/Crash issues in DCS for several years now. Definitely something to do with the last major update. dcs.log