Nedum

There is a way to calibrate the TQS without Software. Calibration - Viper TQS Mission pack.pdf The second step worked for me, with plugin the USB port and pressing the Center Hat of the communication button at the very same time. Cheers EDIT: @Benco showed it already. I was too late.

Hi, I want to show you all this link: https://www.3dcenter.org/news/news-des-3031-dezember-2023 It's German, but it will give you a good look, how the 4080 and the other GFX compare to each other. I would go with the 4080. The super refresh won't be so far ahead. Cheers

Hi and my Answers: 1. Not a tiny little bit. More System-RAM can help to make the FPS more stable, but won't give you more FPS, and for sure, it won't stop the shimmering. 2. Hand tracking is still off. It's a pita to use it in DCS. Buy a Trackball mouse, that would help you much more. 3. Idn. For what stuff would it be good for? 4. Idn, because I never had an Oculus VR-HS. If you want to raise your FPS, go in order with the following things: 1. GPU with 16+ GB VRAM (by 100 % more FPS) 2. CPU (more fluid FPS) 3. RAM (more fluid FPS) Your system is limited by the GPU. 8 GB VRAM is not enough to have fun in VR. Any "new" GPU with 16 GB VRAM would boost your VR experience a lot. For DCS I would prefer nVidia, but AMD GFX cards are good too. Cheers

Thank you all for the hints. @Hartsblade That looks promising. A really nice guide. Thank you. @Habu_69 thank you too.

Hi, if the game is not starting in VR, it tries to use the wrong environment. It looks like it wants to start in SteamVR, but your shortcut settings lead to OpenXR and with that it will only start in 2D. Check your Steam VR settings, if set disable OpenXR runtime support. Look at this link, second posting:

@speed-of-heat thank you, but that wasn't the problem. The issue was, I was playing with the size of the environment (OpenXR Toolkit). My setting was 120%, went down to 100% again, and now all looks good. The only "issue" is now, the cockpit of the 190 D is so small, if I move my head a little bit my head is outside the cockpit. It feels like my shoulders are the hole time outside the cockpit too. I would never have fit in this little bird. That thing is too small for me, and I am not a big man (180 cm high, chest is 117 cm). The size of this bird is the right one. Seems to be a little bit off for me. But anyway, now most of the planes fit with the height again.

Thank you for the information @speed-of-heat

Hello all, I've tested the AH64 these days, and I am always hovering much too high over the seat (feels like 20 cm too high). I have the same feeling the whole time in the F16, but not that big as in the AH64. I always center the view position, but that doesn't fix the height issue. No mods, nothing else change in any file. Did many slow repairs, but especially in the AH64, the head of the side click (VR) is near my (real) knees. I am sitting much too high in the AH64. Anyone who knows a fix? Is this a known issue with DCS or is it a problem with my VR setup?

Nope, doesn't work for me. I can bug the target with a single TMS right, but the bugged targets staying fulfilled. To bug a track isn't the problem. It's the symbolic that stays the same as an unbugged target, so you don't know anymore, which target is bugged as long you try to switch the target with another short TMS right. BTW: why is the thread still marked with missing a trk. file? Did I miss something?

Please remove all the mods you have installed and do a slow repair. That should fix the problem.

MT and ST are all good.

@Pit versus Cockpit Erst ein provokante Frage stellen, die an Infantilität kaum zu überbieten ist, und sich im Anschluss auch noch gönnerhaft geben? Was soll so ein Verhalten bewirken, außer Stress? Wenn man der Meinung ist, dass es eine Abkürzung nicht gibt, dann sagt man es richtig oder man lässt es bleiben. Entweder macht man das, was @Ganesh gemacht hat, und lässt andere an diesem Wissen teilhaben oder man sollte die Finger still halten und sich auf keinen Fall als Besserwisser produzieren. Ein Kumpel/Gleichgesinnter würde andere darauf verweisen, dass es den Begriff nicht gibt und dann auf den Ursprung des Begriffs verweisen (Teilhabe an Wissen). Ein Klugscheißer will seine (angebliche) Überlegenheit damit hervorheben, indem er über provokante Fragen auf einen (in seinen Augen) Fehler hinweist und die (für ihn offensichtlich) "Dummen" selber darauf kommen müssen, was der angebliche so überlegende überhaupt gemeint hat. Manch Einer würde sich ob dieses Verhaltens schämen.

The 4090 alone will give you an 80% boost with lower temps over your current 3090. The CPU switch would be something around a 5% - 10% FPS boost. The 14900 is overrated. Stay as long as you can with your 5800X and if you want to switch, go for the 7800X3D. This CPU will beat the 14900 in most games, is a way less expensive and does need only a half of the power. If you mostly play and mostly Sims, do not go for Intel.

Thank you for bringing this up again. Yes, there was a thread months ago with the same hint for something is off with TWS as long using DL. And (as one mentioned) it has nothing to do with any kind of modding. The F16 TWS behaves "strange" since months, and we never got any report from one of the forum Mods. Every F16 owner can show this "bug" flying the F16 Free Flight Instant Action Mission. The new thing you found out is, you can bug targets with slow pressing 2 times TMS right. I have to test this. Another part for me was, as soon I have tracked one target in TWS and activate AA mode after that, TWS has to be activated again, and with that you are not able to track any other target as the first one you tracked before you switched to the AA mode. F16 TWS is off with DL on. Doesn't work in kind of what is showing in any known document we have.

That sounds strange. You got the crossed eyed effect only if you try to play games or did this happen even if you have the start screen? Have you deinstalled all the WMR stuff before installing the Pimax SW? You have to use 2 different accounts for Pimax. One is for the support, the other one for the shop. Strange, but that's how it works for me.

I think, not enough infos. Plz guys, there is a Sticky about all the stuff needed to start some guessing. What version you are playing? Beta or Stable? Since when did that issue occurs? What're your DCS system settings? What Map? The Module you are using? What about your Oculus settings? Software? Do you use mods? Did you already do a slow repair? Do you have logs and/or a Vid for, to show the trouble you are in? Yes, not enough information, that's for sure. Now, it's your part.

Since a while I have seen so many MIG 29 videos or videos where the MIG 29 had a highlighted place, I have to ask, is the MIG 29 fully "functional" (clickable Cockpit) ready for rumble? Or is it all about a story that pasts me? Last Video I saw:

He told about maneuvering, not only combat. That's a difference. And with the same weapons, I would guess the more advanced (if so) radar wasn't such a big advantage for the SU 27. MiG 29, fast and nimble, like the F16. I think, that was what he had in mind.

No bug. That's how DLSS works. DLSS will always blur the picture. To some degree, you can try to use the sharpening inside the DCS settings, but you will always stay with blur, no matter how much you raise the sharpening slider. It's a part of the nature of DLSS.

Better image quality with DLSS, even so 3.5? Clearer and sharper? I would bet 1 million $ without a doubt, that's pure "personal Magic". The naming of DLSS 3.5 is a brain fart from nVidia. It's there to make the money mountain even a little bigger. It's a commercial "lie". And It works. Sad but true. DLSS 3.5 has >>nothing<< to do with DLSS. N O T H I N G! DLSS 3.5 is a pure RayTraycing technic. It can only work as long as RayTraycing is enabled. Without RT, there will be no DLSS 3.5, that's for sure. Please guys, open your mind. There is the internet, the search machines, go get use them. It doesn't hurt, and it will not bite you... I swear.

DLAA uses the same technic for AA as DLSS, so it would be a nice trick if DLAA wouldn't add blur. It's adding pixels by guessing the position and color, and that's good and bad at the same time. Guessing will always not as good as knowing. Guessing is faster, knowing is slower but much more precise. I can see the text blur coming from DLAA. And that's not all, the whole picture gets a slight blur touch. Not much, but I clearly can see it as soon there are color borders. They are not as sharp as without DLAA. It's not as blurry as the DLSS blur, but it's still there. Even the colors itself are not as crisp as without DLAA. And I would wonder if not, if one knows how DLAA is working. DLAA is working on the complete picture (all pixels). AA is only working on the pixel borders. @DLSS DLSS isn't made for adding quality, it's made for a performance gain, for the cost of quality. If people try to explain, the quality gets better with DLSS switching on and doing XY things, they are 100% wrong. It's impossible by the nature of how DLSS works. DLSS takes the picture with fewer pixels and adds some pixels by guessing to get the same count of pixel as the native resolution was before. Now most of the pixels get nearly the same color, but beforehand there were some pixels between them with a completely different color, to make the picture looking sharp and giving the feel of depth. With DLSS the different colors for those effects are gone and the part of the picture becomes blurry. It's the same effect as with a camouflage suite. That's the nature of DLSS and >>nothing<< can undo that. There will never be any AI that could be right by 100 % with pure guessing. It's impossible. To reach that scenario, the AI would have to know how the future would look like. To give a picture sharpness, you need many pixels with different colors. If the pixel colors are looking nearly the same (DLSS) the picture will become blurry, and you will lose depth information, which will add the loss of the 3D effect. That's how DLSS works. At the end, DLSS has >> always<< to add a loss of the picture quality to gain performance. There will be >>never<< any kind of better image quality. If people tell the picture with DLSS is looking better, it's a kind of personal "magic".

Hi, thank you for your answer. DGFT and MRM are well known and how they work, but thank you. And I can understand that AA and AG have their own preset modes. Nothing to discuss. But it's hard to understand why AA, NAV and MRM are staying in their default mode (RWS) and they can't switch automatically If the pilot changed the tracking mode in one of these 3 modes. I am able to set the TWS for AA, NAV and also MRM, and they will stay in this manual mode even if I am switching the modes all to TWS or RWS. If it's possible to manually chose TWS and RWS for all RADAR Air modes, why is there no automation to enable TWS or RWS in any mode if the Pilot has set one of those modes in NAV or AA before? If I have set TWS in NAV, MRM and AA mode, the workload done in one of those modes, will be captured for all of them. If the NAV mode is set to TWS, AA to RWS and MRM to TWS, the workload done in the NAV mode will be captured for the MRM mode, but not for the AA mode. Why not stay automatically in the Radar mode (TWS or RWS) I have picked before? Why do I have to repeat all the workload again, if I am switching between AA, NAV or MRM and forgotten to set them to the same mode as the one I was working with before the switch? Makes absolutely no sense to me. If I want to change it manually (for what reason whatever) to another tracking mode, I can do, and I know I will lose all my work I've done before. There is no (for me known) logic to force the pilot to do that unnecessary workload. For me, it feels wrong. So my question again, why are the tracking modes (RWS/TWS) are not switching automatically if I have chosen one of them in one of the 3 modes (AA, NAV or MRM) and switching to another mode (like AA mode = TWS -> switch to NAV mode = TWS too)?

Hi, I'm using the F16-C Instant Action "Free Flight" (Caucasus map) mission. 1. Activating TWS with TMS right long 2. Activate AA 3. TWS is switching too RWS 4. Deactivating AA 5. RWS is switching too TWS For what reason for? Is this right? If yes, why has the system to act like this? What's the reason for this? For me, it's a "stupid" extra workload for nothing. I am on a patrol. I am tracking air targets, but no engagement necessary. Rule of engagement changed. The targets are now free for attack. I have the order to attack the targets. I would be happy If I had only the following workload: 1. Master Arm = on 2. AA Mode = on 3. select the nearest enemy target in TWS mode 4. fire Missile Right now, I have to add the following workload: After step 1. and 2. 3a. switch to TWS again 3aa. try to find and track the enemy targets again 3aaa. FFO check again 3aaaa. select the enemy target 4. continue with the rest of the needed steps to fire the Missile. Can someone explain, why we have to lose the tracking if we switch from the Navi mode to the AA mode if TWS was selected before?

Hi, my previous Headset was the HP-G2. I switched to the Pimax Crystal because of 4 major important points. 1. Resolution, the resolution should be at last as good/high as the one from the G2 2. Lenses with a sharpness of most of the view field 3. Colors and black 4. Eye tracking The only current headset that could fix all of those points, is the Pimax Crystal The only competitor, the Bigscreen, has no eye tracking, so a No-No for me. If you can wait, wait for the Somnium VR1. It's sound s like the best VR headset each user can take the best from. https://somniumspace.com/

Same as with the HUD. If you fly against a nearly white background, the HMCS and the HUD markings become invisible. That's a big issue in DCS, not only for the F16. I can't believe there isn't an option to change the color contrast or something else. Would be nice to get something to "fix" that problem.