Nedum

Here is a track.Datalink-issue.trk The difference: hollowed squares versus none hollowed squares after bugging the tracks in TWS Datalink off: 1. TMS right long = RWS to TWS 2. TMS right short = white hollowed squares Datalink on: 1. TMS right long = RWS to TWS 2. TMS right short = still fulfilled yellow squares With Datalink on, you can't see anymore which tracks you have bugged because the yellow squares stay fulfilled, no hollowed squares anymore. Edit: I don't know if this is right or wrong, but I am interested in the answer too, so I thought I might could help out.

I watched the video. It looks to me as if the new FM is slower. The circle is completed in the same time. With the new FM there is less speed left and the blackout comes faster and takes longer. The video shows exactly what I thought after the first few tests. I lose more speed and the blackout comes quicker and lasts longer. And I feel like the rolling axe is very itchy. I need to test it again, but I also feel like I black out before I even get to the 9G. Am I the only one who thinks this is the opposite of better? I don't see anything there that is better.

Coming from a G2 and going to a Quest 3 would be a little step back, if we talk about the image quality (sweet spot). @GPU The 40XX series is the best for DCS. If money isn't a big problem, go for the 4090. DCS eats VRAM like there is nothing else. The 30XX series is too power hungry. Too much heat for what it can give you in comparison to a 40XX series. With less power, the 40XX series will give you round about 80 % more FPS. My 4090 needs 150 Watts less and is 80% faster as my old 3090. If you have not enough bucks, try to get a 4080 or 4070Ti.

How so? DLSS 3.5 != DLSS -3.xx DLSS is a word game by nVidia. It has nothing new until you use Raytracing. DLSS 3.5 without Raytraycing is DLSS 2-3. Nothing more. So without Raytraycing, and DCS has none, how is DCS using DLSS 3.5? DLSS 3.5 isn't DLSS. Period!

That would be a downgrade coming from a G2. The edge to edge clarity might be better, but you will go some steps down with the picture quality. As a former G2 owner, I would never go for a Quest 3. The Quest 3 is by far not as good as the G2 if we are talking about picture quality. I could test the Quest 3. It's not bad, but not as good as the old G2. The only benefit is the edge to edge "clarity", that's it (if we are talking about Sims). No good sound, no long playtime. Do not buy the Quest 3 for DCS, if you want a real upgrade from a G2. The next big thing in VR is eye tracking. I wouldn't buy any VR HS without eye tracking anymore. There is actually nothing that can beat a Pimax Crystal if you are playing Sims. But if you can wait, wait for the Somnium VR1.

Sorry, but something with your system must be wrong, if extreme visibility adds more "smoothness" to your system. How could it, if it adds more CPU and more GPU stress? I tested all your settings and nothing did things better, most of it did the opposite. What I've found out on my system and the systems of my friends: if possible, disable all system tracking tools. Do not use any overlay (like Afterburner) and disable Process Lasso if present. There is no setting in the nVidia control panel and no "magic" setting in DCS, that will remove problems with DCS or add some hidden superpower. I tested all the "magic" stuff I and others could imagine until my eyes starts bleeding, and there is no hidden magic or superpower. If there are stutters or other issues with DCS, it's DCS itself (bugs) or the system on which DCS is running. "A good and stable running system will fix most of the DCS issues."

Hi, which version of DCS do you have? Standalone or Steam? Do you start the DCS from DCS World OpenBeta\bin-mt\DCS.exe? The standalone version needs that blue marked line added to the shortcut (--force_OpenXR isn't necessary anymore). If DCS is a Steam game, you have to start DCS directly from steam (I only read that). And as already said, Pimax isn't a WMR HMD. If you didn't need it anymore, you should delete the whole WMR stuff. @mbucchia has a sticky in this section. Go there and open the link. He explains all you have to know how to get your Pimax ready to go. With SteamVR you'll get a free game you can play (The Lab).

DLAA uses much more information (depth buffer, brightness, etc.) as TAA to eliminate shimmer and flicker, so DLAA hits the performance a little harder as MSAA x 2 and much harder as TAA. My AA-test (before the Hotfix): TAA = ~5 % FPS decrease / much less shimmer / adds ghosting and blur MSAA x 2 = ~10 % FPS decrease / still shimmer / no ghosting, no blur DLAA = ~13 % FPS decrease / no shimmer / adds a kind of ghosting like "Phoenix flames" around fast moving objects and blur (but much less as with TAA)

Hi, es kommt darauf an: welche VR-HS du einsetzt und welche Techniken dieses schon kann (Eye Tracking). Ich könnte einen langen Text dazu verfassen, aber das lasse ich mal lieber. Wenn dein HS von der Auflösung vorher schon unter einer G2 lag, wird man kaum die Verschlimmbesserungen von DLSS bemerken, sondern sich an einem sehr viel flüssigerem Bildaufbau erfreuen. DLAA ist in etwa so rechenintensiv wie 2 x MSAA, vielleicht ein wenig darüber, zumindest der leistungshungrige der neuen AA-Modi. Leider leiden alle neuen Methoden unter teils extremen Ghosting. DLAA schneidet mMn dort am besten ab, hat am wenigsten Ghosting. DLSS kommt auf den 2. Platz und am schlimmsten empfinde ich das Ghosting bei TAA. Kein Ghosting hat MSAA. Auf meinem VR-HMD sind alle von ED angebotenen neuen AA-Methoden oder Upscaler einfach nur grausam (wie ich schon in der "anderen SIM" sehen konnte, allerdings hat dort TAA gar kein Ghosting). DLAA und besonders DLSS erzeugen bei mir ein sehr unscharfes Bild im Cockpit und vor allen Dingen extrem viel Ghosting, sobald sich etwas auf dem Radar bewegt. Wenn man sehr schnelle Richtungswechsel mit dem Flugzeug macht, verschmiert das HUD. Alles in allem genau das, was ich erwartet hatte. 2.9 hat aber sehr viel mehr als nur das zu bieten. Ich würde den Patch auf jeden Fall installieren.

I had to enable the virtual keys in the TM software coming with it to make it plug and play.

Hi, it would be nice if we all would post our DCS settings. Without that, it will be hard to generate a picture of how "well" the new spotting system works for each of us. Personally, I am a Fan of it. I am playing only in VR and with a resolution of 4312x5102 pixel. As YoYo already said, the transition from the Dot to the model seems a bit off. There is a distance at which the Dot disappears, and the object is invisible. And at some view angles (peripheral view) I can see a Dot, which I can't see if I am looking directly in the direction where the object/dot is. Can't say if that is only a VR thing. nullnull DxDiag.txt

Hi, don't know much about Steam VR and DCS, but I have read something about a "bug" from Steam, if you try to start DCS outside Steam (shortcut), steam can't find the dcs.exe anymore. You have to start it from steam. But I am not sure. Try to search for it, there are several threads about it.

Hi, would you like to give us some more details about your DCS and VR setting and the hardware you are using? That would be helpful. Thank you. Do you play with the OpenXR Toolkit? Try to reset or disable it. Or install it and enable Motion Reprojection. 70 FPS are a way too low to get a good result without MR. But that's all only a guessing from me. We need more information.

I like the new spotting system. For me, it's a step in the right direction. What I've seen is the "spotting dots" disappear at some view angles. That should be fixed. I am playing only in VR. My VR resolution is >= 4312*5102 pixels, no AA and no DLSS effect is enabled.

So I repaired DCS (slow), deleted the fxo and metshader2 folders, no mods, reset the OpenXR Toolkit, disabled the Toolkit. Was testing all possible settings, but the visual in VR are extreme blurry. This looks really bad, like DLSS is working all the time, no matter which setting I am using. 2.8 crystal clear, 2.9 it's like I am playing VR with a Quest Pro. The problem is, the resolution, GPU usage and FPS are the same as with 2.8. I need a hint what I have to do to fix it. DxDiag.txt @BIGNEWY could you shift this thread in the VR Bug forum plz? Thank you.

One said that will happen, and it happens, strange. It's the nature of DLSS, that is how it works. DLSS is no good for big wide areas. An Upscaler is an Upscaler is an Upscaler. DLSS takes many different tiny pixels, needed for the detail and sharpness, and will add big pixel areas which will take a lot of sharpness. DLAA can't do wonders with big pixel areas with fewer edges. Many small different pixel + DLAA = sharp 1 big pixel area + DLAA = no magic can be done = blurry That's the reason DLSS will always be less sharp as without. I am happy we've got TAA and FSR 2.

This must be something new. AFAIK till today, it's not possible to use DLAA and DLSS at the same time. Is there new information about that? DLSS has an "AA" effect, but this effect is not the same as DLAA. You can choose DLAA >>or<< DLSS, not both at the same time. I believe the grayed out in DCS stand for = not working, not possible to choose. Is DLAA cheaper as other AA methods? No! DLAA is all or nothing. It's not like MSAA, where you can choose how much GPU power will be used by choosing 2 times of this effect or more. DLAA is more like SSAA, but it's using special nVidia GPU cores. Does it look better; it depends. I would say yes. I would compare it with SSAA and if I compare the used GPU power of both, DLAA needs less GPU power as SSAA. Will DLAA look better in DCS as MSAA x 4 = yes, I think so, but for the same or more GPU power usage. I would wish we would get TAA. That would be a huge improvement for all GPU brands. For what I've seen in the Video (@4k) the picture was not as sharp as the one of the older Vids. Especially the F-16 cockpit was looking very blurry for me.

Didn't you read what ED wrote about the new RADAR tech? This tech is something way above the 3rd party did. Way above. The new tech will simulate the air dense effect in a way !!no!! current RADAR can. This effect alone will have a huge impact on the scan, track and lock on range. Sometimes we can lock an enemy much further away as the other modules can and sometimes, if you fight in dense air, it can and will be the opposite. That's a big change for how the whole RADAR act and the pilots have to work with. On top, we will get false tracking, Ghost locks, false positions, and many more. I like it. Really. But I bet, that will give ED a big headache, especially for PVP (look down and the new clutter effect). The F16/18 pilots will have to fight the new RADAR "stuff" on top of the enemy. The weather in DCS will have a big influence on the new RADAR, but only for the F16 and F18, and that for years month two weeks.

That's strange. I don't have to log in. I can still fill out all fields and request an e-mail confirmation. You have to fill out all fields. Without that, you will not get the buttons highlighted. But since my e-mail is already registered, I've got the information my e-mail is already known. It could be there are no spots left anymore. Try it without login in.

He only said it's not for people thinking for the price of a quest. I think we will see something around $ 1.5k without tax. Will be built in Europe. I've heard the lenses are the same as the ones coming with the Pimax 12K. That might be the reason for the big horizontal FoV (min 120° real FoV).

DLSS = only nVidia GPUs, starting with the 20xx series DLSS 3.5 != DLSS DLSS 3.5 = no FG without 4xxx series GPU DLSS 3.5 = does need Raytracing enabled to make it better as DLSS 2.x DLSS 3.5 = for all RTX GPUs (starting with the 2xxx Series) DLSS 2-3 = no need of Raytracing to benefit from the features DLSS 3 = GPU 4xxx series only and coming with FG FG = is only a good option if you already get high FPS (It's the same with FSR FG) https://www.hwcooling.net/en/nvidia-launches-dlss-3-5-improved-ray-tracing-not-only-for-rtx-4000-ada/ DLSS 3.5 does not imply DLSS 3 According to Nvidia, DLSS 3.5 as we have just described it should work on all GeForce graphics cards with tensor cores, i.e. on GeForce RTX 2000, 3000 and 4000. It doesn’t require the new dedicated special-purpose units from the Ada Lovelace generation GPUs, unlike DLSS 3. Nevertheless, beware that “DLSS 3.5” in this sense doesn’t mean a fully replacement (or superset) of DLSS 3, although the naming convention implies this. The Frame Generation technology (that inserts frames interpolated from the game’s frames that aren’t rendered by the actual game), which until now has been referred to as DLSS 3, will still require the dedicated hardware of GeForce RTX 4000 graphics cards. The announcement of DLSS 3.5 does not mean that you will now get Frame Generation with GeForce RTX 2000 and 3000 generation graphics cards. In that regard, the designation chosen by Nvidia isn’t very fortunate.

If you are interested in the new Somnium-VR1 you can get a spot for your free reservation. No cost. https://somniumspace.com/#reserveYourSpot Read more about this Headset and what you can expect. https://somniumspace.medium.com/somnium-vr1-headset-development-update-️optics-️production-design-materials-fov-4dedf0b80101

The new RADAR technology will bring many disadvantages to the F16/18 alone. The F16/18 RADAR will have a lot more losses with target tracking, that's what I am reading. It might turn out that we can track targets at a greater distance and lock them. But at the same time the tracking, even at close range, will show up with a lot more interruptions and with a loss of already locked targets, in a way we've never seen before. If all Modules had to "fight" with his new RADAR implementation, I would be fine. It can be an issue, if "only" the F16/18 have to "fight" with the new RADAR stuff, it could have a big impact for the multiplayer. Don't get me wrong, I am happy if new good stuff is coming up, but as always, if only some have their hands on them, it can and will get things more complicated. The open Beta is (ED said so) the thing to go for MP. So even I don't want to test the new stuff, I have to. There is no way to not test it, if you play MP. That can make things much more complicated and remove some fun. So I'll take it with a grain of salt. I hope I am wrong, but I don't think so.

I don't see why not? The 72 Hz mode is working well with the other Headsets. Saw a Beta guy with Project Cars 2 and it was looking good. No stutter, no ghosting. But as always, it will be less smooth as with higher refresh rates., but better as with MR enabled, if you can nail the 72 Hz for every situation. And for sure not nearly as bad as with a bouncing refresh rate from 90 to 70 (or less) and back again.

Flaren: Die DCS F-16 ist auch ohne zu Flaren butterweich zu landen, für mich sogar besser als mit zu Flaren. Das ist gar kein Problem. Die Länge der Landebahn ist dann, in Abhängigkeit zum Gewicht, der begrenzende Faktor in dieser Gleichung. In dem letzten hier gezeigten Video war kein richtiges Abfangen zu sehen. Eine Erhöhung des Anstellwinkels um 2° kurz vor der Landung ist kein "Flaren". Man konnte es auch gut an den Geschwindigkeiten sehen, die blieben nahezu unverändert (Sinkrate u. Schub). Beim Flaren wird sowohl der Vorwärtsdrang als auch die Sinkrate massiv reduziert. Das konnte ich bei keiner der Landungen sehen. Zum NWS: Mit aktivierten NWS, bei gut eingestelltem EXPO für die Ruderausschläge, kann ich sogar besser die Spur halten, sobald das Bugrad den Boden berührt, als es erst danach zu aktivieren, weil ich dann nämlich erst einmal das Ruder neutral bekommen muss. Das Bugrad ist scheint nicht in "Spur" mit dem Heckruder zu sein, da der Winkel, je nach (EXPO) Einstellung, unterschiedlich zu sein scheint und das sorgt dann für "funny moments" bei der Landung, sobald das Bugrad den Boden berührt und NWS aktivert wird. Aus meiner Sicht ist es die doch sehr bescheidene "Boden-Reifen-Kontakt-Physik", welche nicht nur der F-16 ein sehr unglaubwürdiges Steuerungsverhalten auf dem Boden beschert. Ich kann mit den Warbirds mehrere hundert Meter seitwärts schlittern, oder mich mit getretener Bremse bei wenig Schub stundenlang im Kreis drehen, was so in der Realität nie abbildbar wäre. Diese Slides kann ich selbst mit der F-16 ohne Probleme erzwingen. Als ob ich auf einem Seifenlaugenteppich lande. Von Grip, wie er im RL vorkommt, nicht ein Ansatz von einer Spur. Und nein, keines der Muster kippt bei diesem Slides um. Aber es ist eben etwas, womit man leben muss. Schön ist es trotzdem nicht.