Nedum

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.

Hi Nik, this Thread, page 2, my posting. Take a look and try my settings. You should get mind-blowing results.

Firstly, the Lighthouse is more >>precise<<, but has other big issues coming with it. As every system, none likes reflection from surfaces. The inside outside tracking system are more immune against reflection. If you want to be happy with a Lighthouse system, you have to minimize every reflection, best is none. Mirrors are a no-go! The same with reflection from any kind of glass (Windows). I had to switch my game room into a "dark room" to get the Lighthouse working without "dropping hands". After a while, I switched back. Till now, I never missed the Lighthouse. Pimax did a great job. It's not as >>precise<< with the >>hand controllers<<, but I can't feel any difference with the tracking of my headset. It's outstanding good. What you have to know. The IO-Tracking doesn't really like dark rooms and walls painted in only one color. If you have only white walls, put some stickers or paintings on it. Easy fix. Personally, I can't recommend investing money in a Lighthouse system. The effort exceeds the costs and the result. Too bright light can cause an issue too. IO-Tracking prefers indirect light. Don't blend the cameras of your Headset.

I can't see how the first point could be debatable? I clearly can see a Screen door effect within the Quest 3 (yes, I own one ;)), but I can't see one in the G2 (I own it too ;)). For me, it was and is an absolute downgrade in sharpness. You have the points with the overall clarity and the really HUGE sweet spot. That's awesome. Fully agree! The Point with the need of a better Strap, I told so. Over all, someone asked If he would miss something, and I told him, what he would miss if he buys a Quest 3. And I'm told him that he has to invest more money to fix it. None of my points were wrong. So, I have to ask why you guys let it sound like I told something wrong?

He asked if he would miss something, not if this isn't fair because of restrictions.

Thank you for that. I had the same problems but could solve them with doing all the Room settings sitting in my Flight rig. That fixed all the issues. Nice to know there is an easy way to do the same without doing all the room setting stuff.

Das mit der F18 habe ich auch so erlebt. Vor allen Dingen muss man richtig mit dem Stick kämpfen. Das hatte ich anders erwartet. Seltsam ist, dass man den Stick bis zu einem Punkt schwer heranziehen kann, um dann mit mehr Kraft über den Punkt rüberziehen zu können, was allerdings nicht zu mehr Ruderausschlag führt. So habe ich mir das immer in der MiG29 und SU27 vorgestellt. Dort konnte ich das allerdings so nicht feststellen. Ich glaube, da wird aber noch etwas von ED kommen. Wird aber mit Sicherheit keine Priorität haben. BTW: ist bei euch auch der Edit-Button verschwunden? Musste für die Antwort einen neuen Kommentar eröffnen. Edit: über die drei Punkte lässt sich ein Posting doch editieren. Jetzt erst gesehen.

@Sofapiloz Man kann die Federkraft ganz ausstellen. Ich muss mir das noch einmal ansehen. Ich glaube, das war, wenn man FFB in DCS im Menü abstellt (Haken rausnehmen). Dann funktioniert nur das Telemetrie FFB. Aber sicher bin ich mir nicht mehr. Ich habe mittlerweile einiges geändert und fliege die Huey leider nicht mehr so oft. Wenn ich mich richtig erinnere, hatte ich in der MOZA-SW die MI als Heli ausgewählt und FFB in DCS deaktiviert. Der Stick bleib ohne Trimmknopf nutzen zu müssen exakt dort wo ich hinbewegt hatte. Das war aber mit dem Apache. Versuch macht "kluch". ;)

Nicht gerade eine konstruktive Kritik. Ich besitze die MOZA FFB Base seit einem Monat und bin recht angetan. Auch die von dir weiter unten erwähnten Probleme habe ich überhaupt nicht. Nutzerbericht: Wenn man in der Software auf integrated FFB stellt, bekommt man einen Mix aus Telemetrie und FFB aus dem Spiel. Angebracht an meinem Simulatorsitz (mittig) von Next Level, werden alle Vibrationen komplett auf den Sitz übertragen. Selbst wenn ich den Stick nicht zum Fliegen nutze, weil ich den Sidestick der F16 benutze, bekomme ich alles mit. Egal ob ich Chaff und Flares ausstoße, die Fahrgestelle ein oder ausfahre oder wenn ich Waffen abfeuere oder Bomben abwerfe. Die Russenjets lassen sich jetzt auch viel besser fliegen, weil das Trimmen endlich so funktioniert, wie es soll. Geht viel feinfühliger. Aber so richtig gut wird es im Heli oder den Warbirds. Das ist ein ganz anderes Fliegen. Das Trimmen im Heli ist einfach nur traumhaft. Und in den Warbirds kann man jetzt genau am Rand zum Stall fliegen. Das Popometer ist zurück. Einfach genial. Es gibt aber auch Schwächen. Auf dem Boden vermisse ich die Rückmeldung beim Rollen, Abheben und Landen. Ob das an DCS oder an der Moza-Software liegt, kann ich nicht sagen. War bisher der beste Kauf einer Joystick-Base für mich.

You will miss: 1: sharpness The resolution in the sweet spot of the G2 is much, much better! 2. Colors The Colors of the G2 are better 3. Playtime The battery will be empty in less than 1.5 hours if you play maxed out using VirtualDesktop 4. Comfort The Q3 with the standard Headstrap is extremely front heavy. Yes, the Q3 is light, but yes, the Q3 basic Headstrap is BS, to say it nice. You need an extra comfort Headstrap. 5. Sound The G2 has a so much better sound. No comparison! To make the Quest 3 Simulator ready, you have to invest 150-350+ extra Dollar. If you are looking for a Sim Headset, try a Pimax Crystal Light. This Headset is the better deal if you only want to play Sims.

There is a woman pilot voice all the time. Is that the voice overlay for the player pilot?

The only part I've missed, is the one where you stop telling me what I have to think. I read exactly what ED have written. Who are you, asking me such an insulting question? Are you a Mod or something else? Stop hitting always on people finding things not working anymore as before, and stop pointing to documents or Vids NOT explaining at all the changes ED have made. With every new patch, we find more and more things working not like they did before. And we are waiting since 2 Years for a new document which can explain why things have changed, in what way and the most important part, what we have to do to make all the stuff working like it should. Links to outdated documents, outdated Forum Post or Vids not hitting the issues I am looking for, are no fun. Especially if we have to know what part of the document is not outdated. Instead, we are running into trouble after spending an hour or more of flying a mission, because things are not working anymore like before after each new patch. And if we complain, people like you coming in, and I don't know why, telling us to read stuff within outdated documents or looking Vids, not even touching the problem we were running in. So what's up with YOU? Who are YOU that YOU are thinking YOU are allowed telling people they should learn to read and understand? Stop insulting people for getting upset if they spent hours, days, weeks, months to find issues, sort them, compare them and try to figure out is this a new feature or a new bug, because there is no fitting documentation, and their findings are perhaps not right. STOP to make it look like that all the people, the customers, are the problem and not all the bugs, bugs, bugs and the missing adapted documentation of all the new stuff! We have learned for years the wrong way to do things, because ED told us, that's the right way. And now we have to learn it in a completely different way WITHOUT any adapted documentation. We have to guess if this can be a new bug or a new behavior. And we have to figure out on our own how things should work and to let them work in the right way and how to set up the systems the new way, if it's not a bug. And If we become upset, after such a long time without any good documentation of all the new behaviors and new doings, people like you hitting on us? Are you for real? What many of us want is not the "in 2 weeks" excuses without any ETA. We want that ED start to fix the bugs WITHOUT adding new ones and give us the adapted documentation of the new features and the doings to let them work the right way. Only for understanding: With this patch they added a new bug, again, without fixing the old one, again. Not only TMS long right is not storing the TWS to the Mastermodes (AA or NAV), no, now TMS long right is emulating the OSB Button press, switching through the VIS Mode also. A new bug, without any reason, and the old one is still there. It's like this is becoming a tradition for the F16. If ED is still doing "bug fixing" in this strange way, who can believe they can do it later the right way? I've really lost all of my hope on that. The F16 is dead meat right now for me! I don't know what ED and you are thinking, but if you really think I am, a costumer, is the problem and not all the bugs, the missing communication and the missing documentation, then there is something wrong with both of you! All the problems coming from the massive amount of bugs, and how ED treats its customers. I can trust you, it's not me who is adding bugs or doesn't allow ED to deliver adapted documents for all the new features. If you were a costumer, buying a car from me. And I am explaining to you, you can have the unfinished product cheaper, but I have to add all the missing stuff later to the car, and you can help me with the bug fixing, and you are happy with it and buy the cheaper car. Would you are still happy with the following situation? You do all the bug fixing and spend hours of time, unpaid time. After a year, you drive hours into a vacation, and the car strikes. You spend hours to find the issue. You can't find a fix and call me. I am telling you your documentation is outdated, and you run into the issue, because the doings are new, and you have done them the wrong way. The new handbook will be sent to you "soon". 2 Years later you have the same old outdated handbook, but I've added more features to the car, added many new doings and not explained functionalities. Now you run into many problems, because you don't know that there are new steps added to make the car work like before. You become frustrated. So, after those 2 years, you're asking me for the still missing adapted documentation, but I say: "Look at the old one. It makes no sense to spend so much time into a new documentation if I have to change so many things again and again." So you have to live with it, and at the same time I will give you penalties if you are hitting me too often with YOUR "little" problems. Would you be happy with this situation? I don't think so. If I would have a free question about the DCS F16, I would really like to know why is ED not fixing the F16 bugs and why they are putting more and more bugs into the module without any visible reason? It's out of my mind, how one can always hitting the bullseye if it's about adding bugs. To make it short, you try to hit the wrong person. Without any fitting and adapted documentation, I have to guess what's right or wrong, and if my guessing is wrong, it's a problem installed by ED because of the old, not adapted documentation. But lesson learned. I have stopped supporting ED the same way they have stopped supporting me. I think it's not a "Win Win" situation, but the last thing I am able to do. And well-intentioned advice at the end: step down from your high horse. You try to wear clothes which are a way too big for you.

Ah, thank you for the info. Yep, this "feature" is an old one. Many reports about this issue pointing in a slightly different direction, like the picture in VR is in both eyes different (in VR like in RL it can be different). The problem is, the shader is always too bright and always only on the right side. Couldn't force making it happen on the left side. People thought it can be a reflection from the kneeboard. It can be, but I hardly doubt that there is such a big bright reflection in RL coming from a kneeboard.

Hi, I had a similar issue. The only thing that helped me was to uninstall the whole Pimax Software, restart the PC, and install all the Pimax SW again. That did it for me. But you did that already, so I would really like to read if and how you can fix it. Edit: Perhaps you can try a Windows repair. With that, you have the possibility to only reinstall all the drivers. For me, it looks like there is a driver conflict. Try to check step by step if there is one USB Device which fight the Pimax drivers. I can't believe that this has something to do with the Pimax Hardware. Edit 2: Have you tried only the Pimax without any other USB Device? No Stick or other USB stuff, only M+T and Pimax. Cheers

It's an extreme old bug, you can find several Threads about it in the bug section. It has nothing to do with it. I am playing without any mod. I did so many slow repairs, but this bug is always there. It happens during some special weather and flight conditions. You have to enable the Canopy reflections to see this behavior, and only of the right side of the Canopy. NEVER on the left side. Do the quick Free Flight Action Mission in Syria. Fly above the clouds and then fly a circle with different bank angles. You should see this behavior and always only on the right side. Shadows on Ultra? There are new settings? Since when? Is this new? I have to take a look later this day.

Old Bug. It's on every map and only of the right side oft the canopy. The left side doesn't have that "feature". Some say it's the reflection of the kneeboard, but it can be seen, even without the Pilot body. And if it would be a kneeboard reflection, the shielding of the cockpit would cut a big part of this reflection out. So it seems to be a reflection of the shielding itself, which is wrong, because the shielding is black colored. It can't reflect white. It's one of the 100+ stone old bugs.

No, it is not correct, and it is not a normal behavior when using GPS. Every GPS will autocorrect itself, even the one in my car which is not able to connect to military GPS. So please explain, why this behavior is hitting only the DCS F16 and no other plane in DCS? All "modern" planes in DCS, so the DCS F16 C, should be able to correct the drift by itself. There is no need to manually "fix" it, as long the GPS of the plane is working. Most of the current DCS F16 Systems are not normal and working the false way. Since the INS drift was implemented, most weapons systems and sensors are working not the way they should. To say or write people should take a look into some vids or the documentation, looks like someone try to fool them. The current documentation leads to false doings, and described doings leading to wrong assumptions. >>Nothing<< really works like it should, and many "new" doings have not find their way into the current available documentation. I would really like to know when we will get a proper documentation of all the stuff we have to do and why. But the most interesting part for me is, why >>all<< other US planes don't run in the same issues, even they all share the same systems!? The GPS Fix is done from the F18 without any needed touch from the Pilot. What "special" GPS is the F18 using? To be clear, a manual "Fix" should be only needed if the GPS isn't working correctly. So, no, it's not a normal behavior.