Nedum

Nun, es ist eine Spekulation, die sich dem erschließt, der mit offenen Augen durchs Leben geht, und diese nicht vor Dingen verschließt, die oft vorkommen. Es ist kein "Gesetz", dass es so sein muss, aber es wäre eine logische Erklärung dafür, dass gerade bei Aufträgen, die in irgendeiner Weise vorfinanziert werden müssen, es sinnvoll ist die "Gold-Week" mitzunehmen. Es ist nämlich rein statisch erwiesen, dass gerade in den letzten Tagen vor einem Release, die Vorverkäufe noch einmal sprunghaft ansteigen. Ich würde gerne einen Auszug der Bestellung der F4 für die letzten 3 Monate sehen, bis zum Zeitpunkt, an dem die Meldung veröffentlicht wurde. Ich würde darauf wetten, dass es einen nicht unerheblichen Peek für die letzten 14 Tage gegeben hat. Natürlich ist das reine Spekulation, wie das Wort "vermutlich" in meinem Posting, welches diese Debatte auslöste, auch deutlich gemacht hat. Allerdings, wenn man diese Aussagen nicht in die Überlegungen von Spekulationen mit einbeziehen will, dann ist das eines jedermanns gutes Recht. Was mir sich nicht erschließt, ist, wie solche Aussagen: "Oder glaubst du wirklich, daß ALLE potentiellen Kunden die F-4E Phantom II als pre-order kaufen und niemand erst den Release abwartet?" die von mir aufgestellte Mutmaßung in welcher Form auch immer entkräften könnte? Inwiefern steht diese Aussage nun konträr zu meiner getätigten Spekulation? Weder wird meine These damit bestätigt, noch widerlegt. Diese Aussage, ist identisch zu meiner, rein subjektiv, und damit auch nur reine Spekulation. Wie einfach das Leben doch sein kann.

"Ich glaube" leitet in keiner mir bekannten Welt eine faktische Behauptung ein. Im Gegenteil. "Ich glaube" ist immer ein Hinweis darauf, dass es sich um eine subjektive Aussage handelt. Edit: Unter den identischen Punkt fällt auch "vermutlich". Allerdings, wenn Sie diese im ersten Satz spekulative Aussage so erfolgreich erkannt haben, dann machen mich Ihre weiteren Einlassungen schon ein wenig sprachlos zurück. Etwa doch nicht erkannt, dass es sich um eine Spekulation gehandelt hat? Offensichtlich, ansonsten hätten Sie sich den Rest der Satzzeichen besser gespart. Wer hier eine "üble Nachrede" in die Welt gesetzt hat, ist wohl mehr als eindeutig, und ich bin es sicher nicht gewesen. Wenn Sie Anstand haben, dann nehme ich ihre öffentliche Entschuldigung gerne an. Ansonsten sollten Sie sich schämen. Wer eine Diskussion so vergiftet, sollte am besten freiwillig eine Pause einlegen. Und das, mein Herr, ist kein Befehl, sondern ein Vorschlag.

I am using 72 Hz only. And yes, you will notice a kind of flicker (more a kind of noise in the picture), but a 1000 times less as with the 60Hz of the G2. The good thing, after a while you will only notice it, if you play a long time with 90 HZ or more again. Even then, it's not nearly as obvious as with the 60 Hz of the G2. If you want to buy a headset with a good field of view, the best clarity, and you only play Sims, go for the Pimax. It's worth every cent. If you want to play beat saber or games with heavy and fast body movement, look for another HS. For games with a lot of body movement, I use the Quest 3. It's by far not as sharp and clear as the Crystal, but it's enough to play beat saber. In my opinion, the Pimax is the best consumer VR-HS for Sims. The pros outweigh all the cons. There is only one VR-HS which could come near to the Pimax, the Varjo Aero. The problem with the Aero I have is, the tiny vertical FoV. For a Combat Flight Sim, in my eyes, a big No No. It !feels! like you have only the half of the view you got with the Pimax Crystal. Physically it's much more than the half, but I'd always had the feeling I am wearing a medieval helmet, with a tiny slit to see through. Nothing you want to use if you are in a Dogfight, especially in a Warbird.

Wichtig wäre eine rechtzeitige Kommunikation gewesen, und, dass man dabei glaubwürdig bleibt. Bei uns heißt es: "Gebe Antworten, bevor der Kunde fragen kann." Soll heißen, besteht eine große Wahrscheinlichkeit, dass der Kunde mich mit unangenehmen Fragen löchern könnte, werde ich ihm proaktiv die wahrscheinlichen Fragen beantworten, indem ich ihm Auskunft über mögliche Änderungen der Planung rechtzeitig gebe. Das nimmt extrem viel Druck vom Kessel und ist nur fair gegenüber dem Auftraggeber. Alles andere ist unprofessionell. Natürlich wird es auch dann immer noch Personen geben, die sauer werden, die Anzahl tendiert aber fast gegen 0. Wir fahren bei uns sehr gut damit. Offensive Kommunikation ist das A und O für unsere Kunden. Wir sind diejenigen mit dem Wissen über unsere Produktionszeiten und müssen fair mit unseren Kunden umgehen, und ihm Planungssicherheit geben, auch wenn es bedeuten könnte, er geht mal woanders einkaufen. Aber das ist bei uns selten der Fall und bisher sind alle wieder zurückgekommen. Ich glaube nicht, dass HB nicht schon Wochen vor dem Ablauf des angepeilten Liefertermins wusste, dass der Termin nicht zu halten ist. Eine proaktive Kommunikation hätte hier Wunder gewirkt und allen eine stressfreiere Zeit beschert, besonders HB selbst. Vermutlich ging es HB nur darum, noch ein paar Vorbestellungen mitzunehmen, die bei einer rechtzeitigen und ehrlichen Kommunikation der anstehenden Verzögerung so nicht stattgefunden hätten. Und das ist es, was ich den Firmen dann wirklich übel nehme. Es ist eigentlich schade, dass sich Dinge wie "Two Weeks" als Meme etablieren konnten und Verzögerungen und ungenügende Kommunikation keine Ausnahmen, sondern Standard geworden sind. Warum sollte mich im Nachhinein die Begründung für die schon stattgefunden Verzögerung jetzt noch interessieren oder gar verzücken, insbesondere dann, wenn man sieht, dass es sich nicht um nur wenige Tage handelt, sondern, dass es sich bei der Verzögerung um Wochen und sogar Monate handeln könnte?

Thank you for sharing the solution with us. Glad it's working for you now. Have fun.

Since the last Pimax SW-Update you should reboot the HS within the SW after each first start of the SW. You can clearly see that the 120 Hz option is missing. It's a known bug since the last update. Without DFR you will get a hard time with the Crystal and DCS. Why are you using Open Composite? It's not necessary anymore, at least for DCS. If there is no other reason, I would delete it. Would you please show us your DCS Option System settings too? Edit: Did you ever try a reset of the OpenXR Toolkit? If not, please do so. It is a "must do" if you ever used another VR-HS from another brand.

Yes, that's the Software behavior. The setting even resets from 72 Hz to 90 Hz after a fresh PC start and the 120 Hz mode is gone. If I restart the HS within the Pimax Tool, the HS symbol looks different and the 120 Hz mode is again available and the 90 Hz mode is also active. It's Magic.

Please, give us some Screenshots from your DCS Options System settings. Some settings will cause issues with VR and especially with DFR enabled (see below, first screenshot, green marker). My settings for a smooth VR experience are below. Some things are made with the OpenXR Toolkit in game. I have reduced the HS-Resolution to round about 3900 x XXXX (I don't know exactly the numbers). I tested it yesterday with the Caucasus F16 Instant Action Mission "Free Flight". With 120 Hz Mod set in the Pimax Tool, I've got 100+ FPS at the start and 90 FPS near the ground. Normally I am using the 72 Hz mode, because the other Maps are much more demanding for the GPU. Most problems with real bad VR performance are coming from old settings from other VR brands (the last screenshot). Deinstall all drivers and settings, especially in Steam. If you don't know how to reset the setting, deinstall all the SteamVR tools and after that reboot your PC. For more precise help, we need some screenshots from you (see below).

There is no need in TGP Auto mode to switch automatically to the WPN page if I point track a moving target to make sure it's the target I want to hit first. The MAV can't "see" that far as the TGP can do. It's not necessary to switch to the WPN Page 15 miles away from the target. I have to do all the research with the TGP. At this distance the WPN Page is pointless. And even with the Mav Ds the problem stays for a ripple shot. As soon I switch to Point Track, I have to switch back to the TGP page to designate another target. Now again my question, what is the reason and/or the benefit that the WPN page will be automatically become SOI if I activate Point Track? Workload added for what reason? Don't use ever Point Track until you are sure you marked the right target? And if you only use VIS or BORE Mode, why is there a function to designate the target to the mavs, without switching to the WPN page, but as soon you use Point Track, it's switching automatically? I don't get the reason for this behavior, but I want to know what's the trick behind it. "Hey, there is a bridge, use Point Track, because Area Track mostly let the MAV miss the target." Sorry for the "switch back"." If this behavior was bound to a WPN Mode like VIS, I could understand it, but now it's a pain in the A for ripple shots. And yes, I know you can fast shoot in VIS mode, but that is no reason or explanation for this, in my eyes, stupid behavior. You guys never use Point Track to research moving targets? What is the "Magic" behind that feature? What is better now?

You mean something like this: https://pimax.com/wp-content/uploads/2023/10/Crystal-User-Manual.pdf

If you post some pictures from your settings (e.g., Pimax, PimaxXR Control Center, OpenXR Toolkit and DCS), it would help a lot. As always: 1. disable all mods 2. do a slow repair 3. delete the FXO and metashader2 folders in \games\DCS(.openbeta) or whatever your folder therefor is. Deinstall all old drivers if you ever have used any other VR-Headset from another brand. I had those kinds of flickers with an older DCS update, but that was more than 6 months in the past. A slow repair fixed it for me. With the current build there should be no flashes at all.

Ghosting is primarily a problem with the number of images the graphics processor can deliver to the screens in the required time. The faster the objects in the image pass by the users eyes, the more images the graphics processor must deliver to the users eyes in a unit of time (frame time) so that the viewer can still see them clearly. If too few images are delivered, ghost images occur. The object in the image still "glows" even though it should no longer be there. The new image, where the object would have disappeared already, could not be replaced in time, which is why an intermediate image of the "old" image is used, and that will "deliver" the "Ghost". DLAA, DLSS, FSR and TAA use a technique that inherently causes ghosting. This is in the nature by itself. The higher and more stable the frame rate, the less ghosting occurs with these techniques, as mentioned in other postings, but with those technics there will be always a kind of ghosting. More FPS in the given time = less to no ghosting Use of upscalers = ghosting (the less FPS, the more the ghosting becomes visible) Too few FPS + upscaler = even more ghosting. MR and ASW ill add ghosting to fast moving objects too. An upscaler, if it is not able to deliver the number of frames that would prevent ghosting, will increase the ghosting effect, and MR and ASW can increase this effect on top. To avoid ghosting as much as possible, the first step is to ensure that the number of images required for smooth perception is guaranteed (Game System Settings), without the need of any kind of software-helper (DLSS, FSR, MultiReprojection or Asynchronus SpaceWarp). And it should also be clear to everyone that even if there are enough images for a smooth image, an upscaler will always add a kind of ghosting effect to fast moving objects. How visible this is varies from viewer to viewer, but it will be there. To avoid Ghosting, you should ensure your system can deliver enough pictures for a time frame of 90 Hz (try to get always min. 90 FPS). If you are unable, you will see some kind of Ghosting. The first stage of ghosting is noticeable as blurring and increases until the reason for the blurring can be clearly perceived as intermediate images (ghosts). This also explains why we often only notice ghosting in fast-moving objects, even though it is already subliminally present in the entire image.

Hm? I can't follow you. I couldn't check if the wrong target was selected without the WPN becomes SOI before the change? I think I could do so without making the Weapon Page SOI. I did all the workload (Point-Track) within the TGP page, and after I was sure it was the right target, I was switching manually to the WPN page and did the fine-tuning, if needed, and after that I rifled. Now I am forced for every point track change to switch back from the weapon Page, and I really want to know for what the extra workload is good for!? If there is a "hidden" feature that will do godlike things, please tell me. But right now I can't see any benefit coming from that new behavior.

Thank you for the response. Yes, you should always double-check right before you fire your weapons. But since when is micromanagement in any way a workload reduction? But it is what it is.

Hm? I've tried ripple shots. Now they are a pain in the "long end back". It's exact how I thought it would be. You have to switch back to the TGP every time you want to designate a new target. For a ripple shot: make TGP SOI, designate target, automatic switch to WPN page (WPN page = SOI), you have to manually switch back to TGP and designate again the other target. The UASF add unnecessary workload for what reason for? Is there a better way to do fast ripple shots? And for what reason is this automatic switch for? If the wrong target was designated, you have to switch back to the TGP. I don't get it. "Hey Pilot, your workload wasn't enough, here is a gift for you, some unnecessary workload.. muhahahaha. Can someone explain for what this behavior should be good for?

Hi, firstly, congratulations on this very powerful system. It shouldn't let you down even in VR and should always run super smoothly. So yes, there is something wrong with it or DCS. I see a lot of error messages which, if I'm not mistaken, come from various mods. I would suggest the following: Disable all Mods Disable Tacview. Perform a slow repair. Delete the fxo and methashader2 folder. To check Windows for old or corrupt files, please open the console (cmd) as administrator and type the following: sfc /scannow. If Windows detects errors, restart the system after completing the repair and repeat this process until no more errors are detected. Also, try to let Windows manage the Windows system cache again. After you have done this, please post a DCS.log here again.

The fact that the stuttering starts from a certain viewing angle has to do with the fact that more objects in the near distance have to be transported across the screen more quickly. They appear and disappear more quickly than if a "few" were "slowly" approaching you from the front. Many tools can no longer compensate for this, for example by reducing the level of details (LoD). Also, more data has to be processed quicker by the GPU and CPU, which causes objects to enter and leave the field of view much faster. This is a good example of the fact that our brain can indeed perceive more than 45 FPS (or rather Hz). Your system will probably not be able to cope with all of this with your current settings in DCS, so you have to lower them.

Hi, disable DLAA (Anti-Alaising off, no other AA method enabled) and look if those streaks are still there.

Does a ripple shot still work like before, or do I have to DMS down after each target lock?

Da werden wohl einige am Fluchen sein, sobald die Dicke Berta am Limit geflogen werden muss oder soll. Technisch mit Sicherheit ein Highlight für DCS.

Sorry, aber deine Grafikkarte ist überhaupt nicht fürs Spielen gedacht. Das ist eine Profikarte für mathematisch anspruchsvolle Szenarien (KI). Die GPU ist für !!!! maximal 70 Watt !!!!! ausgelegt. Diese Leistung entspricht nicht mal einem 1/5 einer aktuellen GPU. Ich halte das Vorhaben damit DCS in der VR zu erleben für mehr als optimistisch. Edit: Sehe gerade @Ganesh hat dazu schon alles nötig geschrieben.

Tests with Air force pilots have shown, that they could identify the plane on a flashed picture that was flashed only for 1/220th of a second. Please explain. And if we want to discuss this, use the term of Hz please. Humans can't really see "Frames". https://www.reachcambridge.com/wp-content/uploads/How-many-frames-per-second-can-the-human-eye-see-.pdf

In what physics-free world should this take place? I myself have a G2, a Quest 3 and the Crystal here. Would you please post your settings so that my Quest 3 gets a better picture quality than my G2 in the sweet spot? What setting eliminates the Screen Door Effect of my Quest 3? My G2 is currently clearly superior to the Quest 3 in the sweet spot (no SDE). But it must be amazing settings if it is even to come close to the image quality of my Crystal. I would love to understand the physics behind how a device with significantly poorer values can almost outperform another device with significantly better values. My tests have all shown the exact opposite of what you describe here. I can't believe that you have ever experienced how good the picture quality of the Crystal is, otherwise you wouldn't have made this claim. I own the Crystal Pimax and the Quest 3 and I have to say: "You are wrong!" Do yourself a favor and leave it alone.

Well, it sounds more like my Crystal is either a completely different device or your Crystal is defective. The only thing I can share from your experience is that it's not so comfortable to wear without some modifications. If someone owns a G2 and a Quest 3 (which I do) and then writes that the sweet spot of the Crystal is very small, and only there the image quality is superior to the other HS, then this Crystal must be defective. The Quest 3 can't keep up with either the G2 or the Crystal in terms of BQ. The only area where the Quest 3 beats the G2 is the huge sweet spot (augmented reality aside). The Crystal is vastly superior to the other headsets in all aspects of image quality. Especially when it comes to colors, the G2 can't even be considered a comparison, and the Quest 3 also has its problems there. Your Crystal must be defective. Never ever will this come true.

I had to install it 2 times to get it "working". It works for me if I do all the changes before a VR session. I don't need ReShade at all anymore since the OpenXR Toolkit. Me can change all the for me necessary points with this nice tool (brightness, gamma, vibrancy, colors, shadow darkness and many more) directly during a VR session.