iFoxRomeo

According to the in-game aviation map the relevant portion is between 1°E and 2°W. But this map is not from the 1980. In-game with the compass rose you can measure it. Mission editor set to 1980: the mag var is between ~ -4.3° and +0.5° Set to 2025 : the mag var is between ~ +2.5° and +6° But that is actually not my point. The map (either ME or F10) is tilted. Use the compass rose, put it on a crossing of the lat long lines and you should immediately realize that something is really off. The longitude lines (at least in the center of the map, as DCS has a flat earth) should be parallel to the 0°(true) heading of the compass rose. Like this screeshot. But I must also admit that it did not occur to me that this is a general problem on other maps as well. So now I don't expect a fix for this. It was simply immediately obvious on the german map for me. Fox

The whole map is tilted 10-12° clockwise. Anyone else got this? The Sabre is at Hannover "Start from Runway". 283(Mag) and 282(True) does not fit for a Runway 27. Fox

205 gigabreit

Gerne. Dieser Bug hat mich an ältere, ähnliche Bugs erinnert.

Ich hab den Bug gefunden. Es ist nicht der Propeller Pitch. Wie schaltest du die Magnete ein? Vermutlich nicht mit der Maus, oder? Der Leistungsverlust tritt auf, weil bei dir nur 1 Magnet an ist, obwohl der Schalter auf M1+2 steht. Mach deinen Anlassvorgang so wie gewohnt. Dann erhöh die Drehzahl auf 1000U/min , schalte auf M2 und dann auf M1. Wenn auf M2 kein Drehzahlverlust aufgetreten ist, dann ist das ein Indikator dafür, dass du vorher schon nur auf einem Magneten warst. Gehst du nun auf M1 Stellung, geht der Motor aus. Wenn man nach deinem Anlassvorgang mit der Maus von der M1+2 Stellung auf M2 geht und dann gleich wieder auf M1+2, erhoht sich die Drehzahl, weil jetzt tatsächlich beide Magnete an sind. Dann hat die Karre wieder volle Leistung.

Sehr seltsam. Übernehme ich die Controls auf der Piste, wenn du das Gas reinschiebst, hat die Maschine Probleme auf Drehzahl zu kommen. Übernehme ich sofort, bevor du irgendwas machst, ist alles okay. Muss mir das nochmal genauer anschauen.

Interesting. Dann hoffe ich für die, die die Kiowa haben wollen, dass die Server nicht einknicken, wenn der Ansturm beginnt.

Ohne Pre-Sale?

Jetzt schon den Nachbrenner gezündet? Ruhig bleiben; is nich gut für den Blutdruck. Nicht nötig für nen random guy from the internet seine WFV zu riskieren.

Also: Wenn du beim Anlassen des realen Hubschraubers(mit force trim System) den Cyclic in die mechanische Mitte( 50% vorne-hinten und 50% links-rechts) positionierst und danach den Force Trimm Release button NICHT mehr wieder drückst und du keine AFCS hast, die den Stick nachführt, dann würde der reale Heli Cyclic sich so wie der PC Cyclic verhalten. Sprich, du musst ständig gegen die Federn drücken, denn alleine schon beim Aufnehmen musst du die Cyclic Position verändern. Self centering gibts nur mit force trim. Kein force trim, kein self centering. Aber den Null-Punkt des self centers, kannst du mit force trim release verschieben. Mein Text in rot Hast du doch gut zusammengefasst. Nichts Gefährliches dabei. Also wenn du was basteln willst... okay. Aber es bleibt bei ner Schnapsidee

Yes IPD setting adjusts the perception of the size of close objects(cockpit). For someone with a small IPD(e.g. little kid with 15 cm IPD) close objects are bigger as for someone with a bigger IPD. You are of course free to set what you want. Just be aware, if you mix physical HMD IPD adjustment AND DCS force IPD you throw the the scale of your virtual world around. For correct size of the cockpit use either physical setting of the lenses on the HMD that has this feature OR use force IPD if you have fixed lenses in the HMD. Here is an example of a HMD(HP Reverb G1) with fixed lenses where the IPD is adjusted via software, either WMR software or force IPD in DCS. This video is from 2020.

You probably won't see a big difference with LOD >1 in the Q3, but it will cost you performance. I have set it to 0.8 iirc. IPD is the interpupillary distance. You should measure your IPD. There are apps that can do that. Once you did that, set it in your HMD and deactivate force IPD in DCS. Negative Ghostrider. The Force IPD in DCS is generally the same as the IPD setting in a HMD. BUT if you set it in your HMD by physically adjusting the lenses AND activate force IPD in DCS it will mess up the IPD for the game. This setting is for HMD that don't have a physical IPD adjustment like the HP Reverb G1. The Q3 has a physical adjustment, so you should deactivate force IPD in DCS and set your IPD in the HMD. If you then adjust IPD additionally in DCS you fool yourself with the cockpit size.

Just tested the 16 and 18. It appears to be the same for me. But I can't remember how "clear" those numbers were with the reverb. Why do you use LOD switch factor "2"? Do you see a difference between "1" and "2"?

Hm. I have to check that. The 16 and 18 are full of spiderwebs in my hangar Did you try to increase the Res. of Cockpit Displays?

Den Satz unmittelbar davor, hast du überlesen?

USB 3.0 ist das Minimum um grün "Compatible connection" zu bekommen. Im Oculus debug tool kann man die Bitrate "nur" bis 500Mbps hochdrehen; regulär. Mit Tricks geht auch, ich glaube, 960Mbps. Ich konnte zwischen 500 und 960 keinen wirklichen Unterschied feststellen. Bei Airlink weiss ich nicht, wie hoch die Datenrate ist. Bei Desktop VR geht der Stream nur bis 200Mbps. Da habe ich schon den Eindruck gehabt, dass es der Kabelverbindung unterlegen ist. Der Ladezustand des Akkus kann auch am Kabel während der PCVR Nutzung nicht gehalten werden und sinkt kontinuierlich ab. So lange der Akku recht neu ist, kann man sicherlich 6-7h rausholen, bevor das HMD meckert, dass es leer ist. Aber wenn der Akku irgendwann mal nicht mehr seine 100% Kapazität hat, wirds weniger. Und einfach mal den Akku tauschen is nich. Gibt Tear-Down Videos, wo ich Tears bekomme, wenn ich sehe, wie verschachtelt der Akku eingebaut ist. Hoffentlich macht der Akku lange mit. Passthrough geht, wie Phantom bereits sagte, durch Doppeltippen ans Headset. Das ist kein dediziertes Feld, das man antippen muss, sondern einfach eine doppelte Erschütterung des HS. Erfolgsrate liegt so bei 80%. Wenns nicht klappt, war man idR zu zaghaft. Das geht jederzeit und unterbricht DCS nicht. Aber das geht nicht per Tastendruck(Joystick/Keyboard). Und das bringt mich zur Frage: Bist du nur auf das Passthrough scharf oder sind da auch andere Eigenschaften, die dich zum Wechsel anregen? Ich kenne die Pico 3 nicht. Das Passthrough ist zwar ne tolle Sache, aber damit kann man nicht wirklich vernünftig/schnell Tastatureingaben während des Spiels machen.

Das ging ja schnell Danke dir

Geilo! Sooo, wer meldet sich freiwillig das "Diskokugel"-Skin zu erstellen, damit HB es zu den offiziellen Skins dazupacken kann?

I have the following specs: Ryzen 9 5900X, 3080ti, 64GB RAM, Oculus Quest 3. I had a HP Reverb G1 and G2 before. Your system should be at least same or likely better performing than mine. What does the test say to the 1.6Gbps, is it compatible(green) with this speed? My settings in OCULUS: My settings in DCS I really don't like the picture DLSS currently produces. Performance gain is great, but the picture even in quality mode is not good. If that changes in the future, I will gladly use it. You can set the PD in DCS or the OCULUS software. But be careful to not set horrendous products. 1.3*1.3 will kill your fps. I went with 1.0 in Oculus and 1.3 in DCS. I might change that, as other games don't have a PD setting in game. Contrary to popular believe it doesn't matter where you set your PD. Only the resulting resolution counts. I currently don't use the OpenXR toolkit. It is installed but deactivated. Now it is important to use either Oculus debug tool or the tray tool. Unfortunately the tray tool has issues with Windows 11. I haven't found a solution for it, hence I use the oculus debug tool. BUT some settings are saved, some are not. So you have to set them before you start DCS. Settings in the "Oculus Link" area are saved. FOV, Visible HUD is not saved. You said cartoonish graphics? That was my first thought when I made the first flight with the Q3. Set "Link Sharpening" DISABLED ! Reduce sharpening in DCS. I have 0.3. Play with that. FOV is a individual thing. Reduce it as much as possible. But only so much that it doesn't disturb you. I can live with small black areas that are visible, but are not too disturbing. Why? A FOV of 1.0*1.0(default) renders high resolution images outside of your FOV (which is depending on the distance between your eyes and the Q3 lenses) for nothing. Play with FOV settings till you find a good compromise. You gain a lot by reducing FOV: 9.114.624 Pixel is the total amount the Q3 has. If you increase PD by 1.3 the PC has to calculate 11.849.011 Pixel (*refresh-rate) per second. In my case I reduced FOV by 0.9*0.62=0.558. So my PC has to calculate 6.611.748(*72) per second but with a 1.3 times higher PD in the visible area. This gives me headroom in DCS, so that it runs most of the time with 72fps, without the need of ASW. Currently I fly a lot with the old warbirds. So with more modern modules that might be different. Use "Visible HUD" - Performance in the Oculus debug tool to see the headroom and the performance overall. Make a routine to compare the different settings. E.g.: create a simple mission, where you sit in your ac in the air and fly the same route. Otherwise it is difficult to assess the changes in performance with different game/PD etc. settings. How to start DCS: Start OCULUS software Start OCULUS Debug tool Change the settings like FOV Activate the link, and you should immediately see the reduced FOV in the OCULUS VR area. If NOT then something didn't work, but you noticed it before launching (and waiting) for DCS to start. Start DCS Fox

Do you see this anywhere else? Passthrough, video playback from the HMD, standalone game on the Q3, different game on PC.

Wie geil is das denn?? Danke @ex81 für die Info darüber.

Flyable B-1B?!

Good luck with this bug. I reported an altimeter setting bug for the K4 about 8 years ago. After only 6 years it was acknowledged, but... I updated from 2.8.8 to 2.9 today. But before that I made a few screenshots. Altimeter setting on the Spitfire was ok on 2.8.8(Caucasus, QNH 2992/1013). Interestingly the scaling direction also changed with 2.9. 2.8.8 QNH 1013 Caucasus 74ft Elevation, check scale and scale direction 1000 -> 1020 2.9(latest) QNH 1013 Caucasus 74ft elev., altimeter set to 74ft results in 992 setting, check scale direction now 1000 -> 980 2.9(latest) QNH 1013 Caucasus 74ft elev., altimeter set to 1013hPa ->approx. 550ft below elevation Fox

FANTASTIC! Within reasonable range, the Bullets hit the MiG15 very precisely and to my surprise, they are extremely deadly for the MiG. Great Job! Has the V0 of the bullets been adjusted?

Oh boy, that looks great. The problem now will be that, sitting in the Mustang I will be looking at the Bombers instead of watching out for bogeys.