Phantom711

„Kein support mehr“ heisst de fact wohl nur, dass es nicht mehr gepflegt/geupdated wird. Man kann es immer noch nutzen. Einige haben inzwischen berichtet, dass es bei ihnen zu Problemen führt. Netterweise kann man aber das Toolkit auch per Tickmark zeiteeise deaktivieren und/oder auf Default Werte zurücksetzen, wenn man testen möchte.

@DST To be honest, I have no idea how the Steam version of DCS behaves exactly. In any case use I recommend you use the „start with OpenXR“ option. As for the openxr toolkit. You can start the exe and change the keybinds to operate it. Instead of the F1-F4 keys I changed it to the arrows. Just for convenience. Once you are in the game, just press CTRL+down and the toolkit window appears and you can change settings. Some might need you to restart the game though.

@DST Wait…what? Are you running via SteamVR the whole time? Cut the crap! Just use QuestLink, set this as your OpenXR runtime and start DCS.

@Sr. Also your graphic setting being at „Godlike“ is a bit too bold with a 4080, I would argue. Even on this screenshot your FPS is at 70, hence doesn‘t meet the 72Hz refresh rate…and you are only parked at the ramp.

The controllers are really not required for DCS. I never used them when I had the G2.

To me it sounds like you have not selected SteamVR as your OpenXR runtime. You can do that in the SteamVR options. You can also get rid of SteamVR all together and install „OpenXR tools for windows mixed reality“ from the Microsoft store. Now you select this one as your OpenXR runtime and you‘re good to go.

Don‘t worry about the CPU. I am running the same one for about a year now without problems. As someone already mentioned, it‘s not a problem specific to DCS but make sure to update your BIOS to prevent any possible damage if you want to be on the safe side.

ACLS würde ich erstmal aussen vor lassen. Auch wenn der Flieger dann von allein fliegt, bringt es bzgl Bedienung noch einmal zusätzliche Komplexität. Es ist aber keine Schande den ein oder anderen Auropilot mode zu nutzen. Im Holding hauptsächlich BALT, auf dem Final Bearing dann HSEL. Wenn ich Konfiguriert habe, nutze ich gern Autothrottle und dann den Stick um auf dem Glideslope zu bleiben und den heading bug mit HSEL um schöne kleine Korrekturen zu machen. Wenn ich das Deck sehe, deaktiviere ich alle AP Funktionen und auch Autothrottle. Man kann und darf die F/A-18 aber auch mit Autothrottle landen.

I think for some reason turning it on and off like that doesn‘t work very reliable anymore. Personally I don‘t mind because I prefer if it actually kicks in when I drop below native refresh. In OTT you can assign hotkeys to cycle through the different ASW methods (including. OFF). Maybe try if that works.

My personal observation is, that MP replays work for me if I leave a multiplayer session directly via „Quit to desktop“ as opposed to „softer“ methods like „Quit“ or „Leave server“. Sounds counterintuitive but works for me. Note: I do use some mods, but no actual module mods.

@Sr. My google search came up with that it can run at 120Hz on QuestLink since around March. Doesn‘t have much relevance for DCS though I guess, since the hardware to run DCS at 120FPS in VR doesn‘t exist yet.

Why? What for? If your headset runs at 72Hz you won‘t effectively see more that 72FPS anyways…

@CF104 If you are using that Markpoint method because you want to ripple multiple JDAMs, then that‘s so 2022…

@RandomPilot Understood. I also read through another thread here, that elaborates a bit further on how the JDAM interacts with the jet‘s INS.

Hi… Coming from the Hornet side, I just read this here out of curiosity. Question: If you want to do a preplanned attack with a JDAM, why don‘t you program the target coordinate into the JDAM instead of using a steerpoint for it? (In the Hornet this wouldn’t even be considered pre-planned but TOO). Even if the jet‘s position is slightly off, the JDAMs GPS guidance shouldn‘t be effected…it should not inherit that error from the jet.

@wikz No, you should not need the controllers for DCS.

If doesn‘t have it already, he needs to “OpenXR tools for Windows Mixed Reality“ from the Microsoft store. In that tool he needs to set WMR as his OpenXR runtime…and then that‘s it. You can alternatively also still go via SteamVR.

@DerekSpeare I have to ask this, since it‘s not 100% clear from your posts: Have you tried running DCS just via WindowsMixedReality (with WMR as your OpenXR runtime)? So without using SteamVR at all?

@DerekSpeare I would suggest an alternative approach here: There is a program called „OpenXR picker“ which lets you quickly choose, which runtime uses OpenXR. So with that you can select SteamVR to be your OpenXR runtime and also unselect it. What kind of headset are you using?

@Rufuz64 @Harker Alright...it all starts to make sense now. I didn´t read rufuz´post as providing an example of the problem at hand but rather another unrelated problem. And my thought process was more like, if the system saves 33ft to be 33m, then the MK point would be above the previous designation. But as I said, it makes sense now.... My bad for causing more confusion. (Even though I believe, nothing I said is actually wrong, it just isn´t the cause of this particular problem).

@Rufuz64 If you are actually doing this in relatively quick succession, I think the error should not be as big as it apparently is. Which would then probably make this a bug. Well, yes, it can be inaccurate. Google "DTED (Digital Terrain Elevation Data)". This is now talking real life...don´t know how that is reflected in DCS.

This could be a bug. But it could also be „correct as is“ if it is meant to portray some inaccuracies in target location if looking at it from an angle and also slight inaccuracies in terrain elevation data.

You mean the external lights on your Hornet? You probably forgot to turn on the „External lights master switch“. It is a pinky switch on the throttle. As for your Air Refueling: Sorry, that‘s a skill issue. I fly in a virtual squadron and we do this almost every mission…there is really not witchcraft involved… But please, let‘s not start the umpteenth „How to AAR“ thread. Use the search function here in the forum.

I can‘t help you with the main issue here. As for the other question: I don‘t know if it‘s documented, but if you want to use QVFR with DCS you now need to tick the respective box. For whatever reason the eye-tracking works without the box ticked.

Kind of… There is a mod called DCS-DTC. It basically actually starts pressing the respective buttons, so it is advisable to keep your hands clear as long as it‘s doing it‘s thing. Google it, it‘s on github and discord. Unfortunately JDAM PP programming is currently bugged and the developer is taking sone time off at the moment. EDIT: There is an unofficial fix to that JDAM PP programming now.