Nedum

I think you're very much mistaken And it wasn't just transferred once, but at least twice. The first time onto the jet's magnetic tape and at least a second time when uploading. Even with the first transfer to the F-16's on-board data tape, subtleties are lost. This effect is squared during the second upload. And this is also clearly visible if you look at the only high-resolution image of an original recording (last row, right image). The sharpness of the overlay almost comes close to that of the sniper pod from DCS, but the details to be recognized are many times higher than in DCS. Just look at how razor-sharp the shadows are. What the video shows us has nothing to do with what the !!analog!! camera system of the original can really do. You can extrapolate all this by comparing the sharp original image with the overlay of the video. If I calculate the ratio in my head, the original should be at least 3 times sharper than what we can see in DCS. Knowing the size and resolution of the MFD of the F16 and you know the PPD of the MFDs. PPD is the magic term. I'm willing to bet that what we can currently see in DCS is nowhere near the PPD of the MFD of the F16. And the analog cameras of the original Sniper have a much higher resolution as the F16 MFDs. https://qasimk.io/screen-ppd/ As I said before, it looks like one have missed some parts badly in his calculations. I hardly doubt, by math, the DCS Sniper Pod show us what the original can do, if I am looking at the original razor sharp image picture.

I think you are showing exactly the opposite with your comparison pictures. 1. the video of the original you are referring to is very heavily compressed. You can see this very clearly if you look at the overlay. It definitely doesn't show the sharpness of a 720p video, and I'd wager not even 320p 2. In the last row, you've put the original on the right-hand side. Here the overlay is almost as sharp as in DCS and you can clearly see how bad the picture of DCS Sniper Pod is in comparison. The aliasing alone should scare anyone. 3. if you look closely at both PIP images, you will notice that everything in the PIP of the original is the same size as everything around it. The image of the DCS Sniper Pod changes the size massively. The buildings there are smaller, but the fine structures are almost twice as thick. It looks to me as if the heavy compression from the original video was not taken into account when developing the DCS Sniper Pod. And something else doesn't seem to have been considered. The cameras in the original Sniper Pod are !!! not!!! digital. They are analog. With the same "resolution", an analog camera will always be able to display a much more detailed image. I hope the sharpness of the image and the details are adapted to this fact. If not, one have really missed the mark.

Several Points to make here! This would never work with the Marianas map! You want to test your GPU and your settings? Go to the Marianas. Fly low and fast and look to the side, down to the trees! If you get more than 30 % extra FPS with Eye Tracking and QV on, you are a lucky pilot. I easily can get high FPS with Eye Tracking on, if I am always looking forward. That what really sucks down the FPS is the side view down to fast moving objects on the ground, like trees. I really would like to see, he is going to the Marianas and circle over the trees and buildings, and looking over them to the horizon. I would bet, with all graphics settings maxed out, he wouldn't even get 50 FPS with Eye Tracking and QV on.

I really can't understand what's so hard to understand the issue. So, you try to explain, that DL on disables Radar functions, like make more than one tracked target with TMS right short to systems targets? It has nothing to do with the Radar building tracked targets, we already see big fulfilled squares, not the small ones. With the DL Mode on, you are unable to: 1. make more than one tracked target with TMS short right to a system target 2. see how many tracked targets are made into system targets 3. white and yellow hollowed squares system targets anymore, like in the actual official guide (page 342 and the following). If you do the exact same mission, and you disable DL, suddenly all the magic happen. Now you are able to make all the tracked targets with one single TMS short right into system targets, and on top of that you can see they all have become system targets because they are all hollowed. And all that under the 100 % exact times and ranges/conditions. So, PLEASE, I really would like to know, how I can get all the fancy symbology like in the official Access Guide and how I can make more than 1 tracked target with DL enabled with a short TMS right to system targets! Right now, I do something wrong, because I can't get even one hollowed yellow symbology with DL on, and I can't make more than 1 tracked target to a system target with TMS short right and bug it as long DL is enabled. If I am doing something wrong, what is it? I am asking this more than a year and all I get is an explanation about things I know, and they all have nothing to do with the issue.

What I can say 100% is that what the DCS pilot can map right now when looking to the side is just looking down. The important thing here is !down and not back!. You should watch the video below.The RL pilot you see there moves his body and head to the left to look over his right shoulder, and at the same time he moves his left shoulder forward and his chin up.The DCS pilot cannot move his hips, shoulders, upper body or chin as an RL pilot could.The DCS pilot's upper body is glued to the seat, and he can only move his shoulders to the left or right. What he can “simulate” is looking to the side down, not back! As the DCS pilot's body cannot simulate the body movements of a real pilot, the more the player looks backwards, the more the head position and body position no longer match. The VR player moves his body, and therefore also his head, much more naturally than the DCS pilot can currently simulate. Or quite simply: the DCS pilot's helmet is only in the way because it cannot simulate the natural movement patterns, the pilot always “sticks” to the seat with his back and that is 100% wrong. We're playing a combat simulator, and pilots move just like in the video I linked. And this is not represented in any way in DCS, which is why the helmet is very often in the players way. The only RL position if he looks to the sides that would fit this kind of body movement of the DCS pilot is if he were looking sideways and !down! In the video, it's a fighter pilot strapped to his seat, and yet he's clearly moving more and differently than the DCS pilot. A helicopter pilot has much more room to move his body more extreme. Everyone can test this, even if you are strapped to a seat. Sit in your car and try to look over your shoulder behind you with only moving one shoulder down and the other one up, both shoulders must always touch the seat, like the Pilot does in DCS. And what you get is, that you only can look to the side and down, not behind you. If you try to look over your right shoulder behind you, you have to move your upper body to the left and your left shoulder moves forward. And the more you try to look behind you and up, the more this movement will extract. So, please ED free the upper body of our Pilot, or give us the possibility to disable only the pilot head.

I'd never used a Quest Pro for long. Could test it 3 Times. Not long enough to compare it with others. With DFR enabled I can hold 72 FPS. The trick was, I'd run my Crystal OG with the Companion App from Tally Mouse. My Resolution was 240 %. So running the Crystal Super @165 % resolution with my current settings isn't a big difference. At first I was a little bit disappointed looking around inside the Cockpit. I couldn't see any difference. That changed completely as soon I was looking outside of the Cockpit. I can read all the traffic signs of the Airport from the triple distance, and they are razor sharp. You don't have to guess anymore from the distance, you can read it like in RL (300 feet). The sharpness in the distance, this is the real thing where the Crystal Super shines. This sharpness in the distance is awesome. But, I have to say there are limits with a 4090. To get all of the Super, you have to go with a 5090. 30-40 % more performance in VR is a huge number of Frames you can invest in your settings. At the end it's all about money... again.

There is one thing in this guide that's not necessary and will trigger a bug with XRNeckSafer. In the VR-Options there is no need to enable Eye Tracking. Does nothing for me. The Pimax Eye Tracking will work without it. What it does if enabled is, it will disable the Eye Tracking at the point XRNeckSafer starts to work. So, if you want to use XRNeckSafer you better never enable the DCS Eye Tracking! Till today I am not knowing for what this option is good for. Is there any VR-Headset that needs this special option?

There are some "issues" with the Pimax Light. 1. You have no Eye Tracking 2. The Image Smoothing from Pimax doesn't work very well. Because of those 2 points you have to lower your settings a lot. If not done already you can use the option Lock to Half Frames in the Pimax Software. Use 90 Hz, lock to Half Frames, lock your max Frames within the NVidia-Driver Software to 45 and you should get a smoother experience. Even people with a 4090 have to lower their settings with a Crystal Light, coming from a Crystal OG. Eye Tracking is the most important part for any kind of VR Headset. Without Eye Tracking, you have to lower your settings. The guy below has made a good video of how to setup you Crystal Light. But he is using a 4090. If you look at your settings and the ones he is using, you will notice your settings are too high. A 4090 is 75 % faster as the 3090Ti you are using. Please read this Thread if not already done. It's about micro stutters but gives a good help for your problem too.

Hi, last Saturday. Preordered November last Year.

To fix that issue, you have to make the room setting directly at your flight seat position. The important part is, that the Headset is in the middle of your seat. If done, start DCS only if you have placed the Headset at your seat. At that point, it doesn't matter if you are too low or too high, or if you're a looking left or right. The only thing that's important, that the Headset is in line with the middle of your seat. I have set up the room setting in a way, that my flight chair is the middle for all room setting. Works perfect with XRNeckSafer. Edit: And you have to disable the DCS Eye Tracking, if you want to use Eye Tracking with the XRNeckSafer. I don't know for what the DCS Eye Tracking slider is good for, but for sure not for Eye Tracking with a Pimax Headset.

Hi, my VR-Headsets in order: G2 -> Crystal OG + Quest III -> Crystal Super 50 PPD Visual differences Crystal OG too Crystal Super: 1. the Crystal Super is much brighter = flying during the F16 Night Free Flight (full Moon), you now can see the trees and the shadows (couldn't see them before) and the Blacks are still black. Looks much more natural. In my Crystal OG I have always some kind of gray in the visuals during Night Flight. Like some smear. That's completely gone with the Super. 2. wider FoV = with my Crystal OG I couldn't see the Wings, if I was looking left or right without moving my whole body. Now I can see the Wings (not fully) and the 3 outer stations with only moving my head. And I see a bit more in the vertical. So much, that I notice it without to measure it. 3. the clarity in the distance is much better. 4. the eye tracking works better, is more precise. I always have some trouble with my Crystal OG. I need several tries for the calibration with the Crystal OG, and after the calibration I have always problems on the left side with the precision during the test with the dots you have to look at. With the Crystal Super, I calibrate, and the precision is rock solid. 5. The Crystal Super has the better/bigger Sweet Spot. All other VR-Headsets are not playing in the same league as the Crystals (OG and Super). The Quest III is too dark and not sharp enough, overall clarity is better than with the G2. You can look around only with moving your eyeballs. The G2 has the smallest Sweet Spot but is sharper than the Quest III in that Sweet Spot, but you have to focus on the Sweet Spot and to move always your head to look around. Both Crystal beat those VR-Headset with ease. The Quest III will beat the Crystal OG if we would talk about a bigger Sweet Spot and edge to edge clarity at the end of the lenses (the last 10 %), but it's never enough to go for a Quest III. With the Crystal Super, the Quest III has nothing it can fight with, if we let Hand Tracking and AR outside. At the end the Crystal Super is right now out of the box more comfortable as the Quest III, has 1000 times better visuals and is the best VR-Headset for DCS.

Hi, every system from Pimax will be better, as long as it has local dimming and Eye Tracking. You can lower the resolution of the HS if needed, and you will always get a much better image the Q3 can handle too you. And with the 72 FPS mode and Eye Tracking, it will always run as smooth as the Quest 3. The question is more like: "How much are you willing to pay for it?" I'm waiting for my Crystal Super 50 PPD. Nearly 130° horizontal FoV. Can't wait for it. Better local dimming than my current Crystal, much brighter, better colors, smaller, less weight, without any battery, I am so excited.

@NineLine As far as I can see, there was no fix for the F16's problem with the pitch behavior during the landing, which you yourself confirmed. My Question is: does the internal fix actually make it into the patch? If so, why wasn't it written into the notes? DCS: F-16C Viper by Eagle Dynamics Added AIM-9 seekers tracking flares prior to the missile being launched. Added Throttle OFF/IDLE Mouse Click on the throttle (key command/binding no longer required). Fixed: PDLT cycle with EXP causes freeze/crash. Fixed: Using GMT causes a game crash. Fixed: Special key bind for parking brake / antiskid not working. Fixed: Damage model - Pilot cannot survive any explosive hit. Fixed: Dogfight mode gets stuck in NO RAD. If not, why is a new track needed for a known issue that has not yet been solved? What exactly would change with a new track?

But it isn't! Can one explain, how ED is simulating >>not<< to align with the first viewed right target after the hand off? The interesting part is, at first the Mav tries to align and picks the right target after the auto hand off, but the Mav cross never closes. And as soon I try to get a lock with TMS up (Mav cross should be closed) the Mav tries to lock another target! Auto hand off -> Mav picks the right target, but one didn't get a good lock (no closed cross) TMS up short -> Mav switches to another target, even so hast the right target in the center of the open cross, and one gets instant a closed cross. TMS down and TMS Up again -> Mav switches back to the right target, but the Mav cross stays open. Repeating procedure till 4-3 miles., and then the "Magic" happens: right target, closed cross. I am really interested in to know how is that the right way to "simulate" how a Mav would behave with an auto hand off? And what I can't understand, why is the Mav switching to another target with TMS up even so, it is looking at the right target after an auto hand off, but only hasn't locked it. And if it auto-switches to the wrong target with TMS up, why do I get instant a closed Mav cross now? So, no, I don't believe, even If I am drunk, that the current behavior of the Mavs is any near a RL behavior! Not a tiny little bit!

Is there only a guessing of how often, and when, the pilot has to start to "fix" the GPS/INS drift? Is there no documentation about this procedure? Like: After a flight time of yy minutes, you will get a shift of xx to xx feet. To minimize the drift, you have to start the "fix" every yy minutes of the current flight time. Till now, I have the feeling, even ED doesn't know the answer! Would be nice to have something more than guessing! For me, it's hard to believe that CCIP bombing (if it would work ;)) is the most accurate and less dangerous way to drop bombs with the F16.

Ich glaube, ich hätte den Sarkasmus besser herausstellen sollen.

Das mit der F35 ist doch mal gut! Dann steht ja auch nichts mehr einer SU27SM Su35 oder MiG29 ++++, MiG 35 im Wege! Wenn ich es noch richtig in Erinnerung habe, war der Hauptgrund, weshalb keine modernen Varianten dieser Muster entwickelt wurde, dass man einen extrem hohen Anspruch für die Technik (RADAR, Störsender, etc.) hatte. Man wollte nicht raten und spekulieren. Mit der Entwicklung der F35 ist das wohl eindeutig hinfällig. Dass für das RADAR oder das IFF-System oder gar dem Helm der F35 genauere Daten vorliegen als bei der SU27, SU35 oder MiG29, glaubt doch wohl kaum ein Mensch. Es wird Zeit, dass endlich "Rote" Kampfjets in diese SIM Einzug erhalten, die die Kämpfe endlich wieder auf Augenhöhe ermöglichen! Warum sollte das beste geratene Ergebnis, was bei der F35 möglich sein wird, nicht auch bei den russischen Jets funktionieren? Hoffentlich wird sich eine Firma finden, die das umsetzen möchte und kann!

Du achtest ja gar nicht auf die Signale und ignorierst sogar die Richtungsanweisungen. Was ist deine Erwartungshaltung, an die Crew, wenn du diese ignorierst? 1. rollst du viel zu schnell 2. bewegst du dich weiter in eine Richtung, obwohl die Signale aufgehört haben (Minute 2:58) 3. ignorierst du die Signale der Crew (Minute 3+) Mein Vorschlag: 1. nur so schnell rollen, dass du jederzeit die Bewegung des Jets stoppen kannst 2. wenn du keine Signale bekommst, immer stehen bleiben. Das ist sicherer als weiterzurollen. 3. Erst wieder bewegen, wenn du den Signalgeber und seine Signale klar identifiziert hast. Die KI hatte in dem Beispiel, was du gezeigt hast, überhaupt keine Schuld. Wäre ich KI-Crewmitglied an Bord des Trägers gewesen, hätte ich dich zur Sicherheit der anderen Crewmitglieder vermutlich aus dem Jet geschossen. ;)

As a VR user, the Helmet alignment fail will now happen if the lines are not overlapping or the angle of the two crosses is too big. With one of the older patches, you have not to be as good as possible to overlap the crosses in the middle, the lines of the crosses have to be as parallel as possible. I can always align, but I have to move my had in such a position that the lines are in the best way parallel to each other. A little angle doesn't matter (as you can see in your screenshot where you can see the Align ok text), but if the cross of the Helmet and the HUD cross have a too big angle, the alignment will always fail, no matter if you have centered the crosses or not. Try to move your Head so the Helmet cross lines and the HUD cross lines are as much parallel as you can get, and your alignment will always be ok. Edit: but I don't know if this is the same as in RL. That's the way it works for me by 100 %!

If the DMS AFT long Button Press doesn't work, look for the visor toggle and/or up and down Button. Perhaps you have bound one of them without knowing. In RL you would see that, because the world would become brighter if you would raise the tinted visor, but not in DCS (so sad). So this can have the same effect as the DMS long after press. And you don't have to wait. Go into the controls section and search for visor. Then you will see, if there is an active binding for your controls, or what key bind is activating it.

The Kola Map is by far the worst Map if it's about FPS! I can play all other maps with 72 FPS at ground, and here and there a few short FPS drops lower than 72. But the Kola Map gives me steady 60 FPS low flying and on the ground 50-40 FPS at the lower end. I will stop playing this Map, after I have finished the F16 Campaign. I thought about buying the F18 Campaign for the Kola Map too, but no, that would be a pita. The funny part is, the Buildings' or models of other Planes or Helis are not the FPS eaters, and it doesn't matter how many of them I can see. It's all about the trees! So, RIP Kola for me and >>any<< Campaign or server with this Map!

Die 5090 wurde in China zum erste Mal mit 2600 USD als Preis genannt. https://www.guru3d.com/story/rumor-nvidia-rtx-5090-and-rtx-5080-pricing-details-unveiled-for-chinese-market/

Das Log zeigt mir an, dass du neben einer Pimax Crystal auch ein Varjo XR am Start hast? Sind die beide aktiv? Hast du wirklich eine langsame Reparatur durchgeführt und den Haken aktiviert bei der Suche nach extra Files nach der Reparatur? Es ist schon seltsam, dass erst die kompletten Treiber und Settings für die Varjo geladen werden, und am Schluss dann die Pimax Crystal als Open XR Renderer. Edit: hat damit nichts zu tun. Es gibt keinen besonderen Fehler im Log File, was mich vermuten lässt, dass der Fehler eher von der Hardware kommt, als vom Spiel. Kann es sein, dass du deine 4090 irgendwie verändert, übertaktet hast oder mit geringerer Spannung laufen lässt? Am häufigsten tritt so ein Fehler auf, wenn die CPU oder GPU nicht vernünftig, bzw. außerhalb der vorgegebenen Spezifikationen laufen. Falls das der Fall ist, mal diese Änderungen rückgängig machen und es wieder probieren.

Und obendrauf kommt noch das inside outside tracking der PIMAX Air. Das ist ein gewaltiger Kostenvorteil. Mit Micro QLED und dafür größerem FoV wäre mir das HS lieber gewesen und ich hätte das gekauft, aber dann wäre der Formfaktor wohl nicht mehr möglich gewesen. So wird es die PIMAX Crystal Super mit QLED. 57 PPD, wir brauchen dringend eine 6090+. :)

How you try to compare the big sweet spot and so a nice sharp image of the Q3 with the more limited sweet spot of the Pimax Crystal Light leads to wrong assumptions! It sounds like, because of the smaller sweet spot of the Pimax Crystal Light, the image quality and sharpness of the CL is limited to the smaller sweet spot. That is wrong, and we should say that. The Pimax Crystal Light, once in the sweet spot, will always give you over 95 % of the whole lenses a way sharper picture as the Q3 can ever do! There is no question about that! There is a big difference if we talk about edge to edge clarity of the lenses (here is the Q3 the big winner), the sharpness (here hits the CL the Q3 like a bus) or the sweet spot. What's right is, the Q3 has the bigger sweet spot, so you don't need to struggle with the headset to find it, but the Pimax has a much bigger sweet spot than the G2. And If the player has found this sweet spot, the overall sharpness of nearly the entire lenses of the Crystal Light, is much, much, much better as the one of the Q3! The Quest 3 can and will never compare with the Pimax Crystal if we talk about sharpness, colors, and brightness! Not a tiny little bit! I own the Quest 3, the G2 and the Pimax Crystal (not Light), and I can compare all of them. And one should know, the new panels and lenses of the Crystal Light are now better as the ones of the old Crystal. I could test the Crystal Light, and I was impressed how good they are. And if my old Crystal is so much better than the Q3, how could one try to compare the Light and the Q3 if we talk about sharpness? No way! I think people try to compare apples with oranges, if they try to compare a Quest 3 and a Crystal light if we talk about visuals and sharpness. If we are talking about features, then the Q3 starts to shine! Leaving aside the thing about the sharpness, the rest of your posting is spot on. At the end: If I had to choose between a Q3 and the Light, and it's only about Sims, the Light would be my favorite. Would I also like to play other VR-Games, like Beatsaber, or do some social gaming, or AR, I would go with the Q3. The Q3 has the better features and the controller tracking is much more precise. Are visuals the main thing, then again the Crystal Light. The tracking of the controllers is good enough for most of the games. Even Beatsaber is very playable if you play only hard mode. Personally, I would never buy any new VR-Headset without eye tracking anymore. If one has the money, one should go for a VR-Headset with eye tracking. It's unbelievable how much more GPU power one can use for better image quality. But it's expensive if you want to buy a new VR-Headset like the Pimax Crystal Super.