diego999

It doesn't make any difference. What you see in your monitor is just a copy of the frame being sent to your VR headset. The workload to render that image has already been done. No extra GPU load.

With DLSS in Performance mode your graphics will be horrible no matter the other settings. Use DLSS in Quality Mode with the sharpness slider all the way to the max (1.0). Worst FPS killers are shadows, clouds, MSAA, SSAO, SSLR. Lower Textures to medium and check if you notice the difference. In VR with a Quest 3, I can't. Terrain textures, on the other hand, look horrible on low. Try these as a baseline and work you way up. In the Quest software, set max res (1.3, slider all the way to the right). Leave it at 72hz with ASW on.

Just tested. The bug is fixed.

It has potential but it's almost abandonware at this point. We're approaching a year since it was launched, and it has received the amazing amount of zero updates. It lacks basic stuff like correct frequencies and bridges. Avoid for now.

I think it was in April's patch, I'm not sure, when people started to report their AV flagging the M2000 module as malware. There was nothing in the patch notes for the Mirage but some files were updated and this bug appeared. Very strange.

Not at home right now so I can't check, but I'm reading today's patch is released and the Mirage bug wasn't fixed.

This is a new bug introduced by the latest patch. And with the RAZBAM debacle, expect it not to be fixed for the time being (if ever).

It is absolutely different to every other plane within DCS. The swedish phylosophy and doctrine is nowhere near the other NATO or soviet planes we have. There is an english cockpit mode, so don't worry about the language. Compared to the M2000 it's almost the exact opposite. The Mirage is an interceptor with limited secondary A-G capabilities. The Viggen is a pure A-G platform. It can carry Sidewinders and it has a pretty rudimentary air gunnery mode in the radar, but that's it. About turning and dogfighting, it doesn't turn. And it doesn't dogfight. But if you like doing Mach 1 at ground level, shooting cruise missiles or GPS guided cluster munitions, then landing in a backroad, then go for it. As I read in an old Viggen tutorial: 'if you're not dodging trees, you're not going low enough'.

Right click spamming the 'set compass mode' knob fow a few seconds fixes it for me.

Left click on the ignition and keep holding while you right click the idle detent pad.

Set a trigger -> do script -> copy the code in the text box. Change desired weight and edit the unit's name you want to add the load to. That's it.

It's not mandatory, but if you copy them to the same folder they're easier to find. I did it that way.

Didn't know about this option, just tried and it works great. Thank you.

From what I read in an old discussion, rBAR needs to be coded into the game itself to be able to function. Forcing it will make no difference. Doesn't hurt to try tho. Will test tonight and report if there's any improvements.

I use GPU Temp and Core Temp, very simple programs that show GPU and CPU usage, temps, voltages, etc., with the very elegant method of peeking below the VR googles to look at the monitor while I'm playing DCS. Open XR Toolkit has an overlay that shows CPU and GPU frametimes inside the game while you're flying. That's important information too that migh help you pinpoint the source of the problem.

Long shot, but have you tried to disable power service in windows and test if the problem persists?

Have you tried lowering the simulation rate in the special options? It doesn't make any difference for me, but it's worth a shot.

Keybinds are stored in Saved Games\DCS\Config\Input. Every folder in there stores the keybinds for that particular module. There's one file for every device you used (joystick, keyboard, mouse, trackIR, etc.). The extension is '.diff.lua'. They're just a plain text file really. Inside your new pc, open DCS, go to controls, there's a Load Profile option on the top right, click there and navigate to that old keybind file you saved on the old PC. Then you have your old config back again. Here are the files, for example, for the A-4 Skyhawk mod.

Interesting perspective. It matches my experience so far.

Great tip. I forgot to mention that.

I feel the same as when I fly the F1 and I shoot 530s at the enemy: the limited radar and missile capabilities only allow to shoot once and I'm already at the merge. BVR is a distant dream. More practice is needed as this is probably due to operator error, but I'm getting exactly the same vibes.

It's explained on the picture from the manual. It looks 8° degrees to each side and it overlaps 1°. From what I understand it's like a primitive vertical scan mode that searches in a fixed line in front and above your nose. So if you're turning it still scans above your nose, whichever direction it is pointed at, not above the horizon. It's not stabilized.

As others suggest, use lens inserts. They're very good and cheap enough. From what I read the focal point of most VR headsets is around 1-1.5m, so your reading glasses won't help while playing.

I suffer this too. Even when exiting the mission, still have stutters and low fps on the main menu. GPU usage shows 100% but the temps are low, near idle. It happened twice last night flying the Phantom over Cyprus on Syria map in a very simple training mission.

Yes. On HEAT the radar is looking at the center. With RADAR is looking to the right, with GUN is looking to the left.