All Activity

I built my F-14A in 1/72 scale, so, uhmmmm... I did nothing and left it clear.

As fascinating as the Yak-38 is, I really can't see it coming to DCS, never mind being some sort of 'saviour' for it. I suspect that finding adequate documentation would be problematic, and its operational capabilities seem to have been rather limited.

@-Cipher- Thanks .trk file. Yup, on your plane trim is sensitive, just like it used to be mine. I've attached mine, you can see how stable the plane is even if I move the trim from one extreme to another. What kind of setting should I have for FF? I've checked what I have for "Elevator Trim - axis" in FF Tune, and I have exactly the same stuff as for all other axes that work just fine. P51D-useless-elevator-trim.trk

I've tried it and unfortunately it's not for me. I am sending it back. I am not saying it's bad headset and it will be a good upgrade for many users. However, I think the Quest Pro is a better option IF you can get one for a decent price. I paid £300 for my mine. I was lucky to get such a good deal for a mint headset that had hardly been used. There are still some bargains.

we clearly have a different meaning for the word "stolen"

Well it occurred to me that Lazur could be faked to some degree with new navigation by spawning/de-spawning RBSN car. (not fully, but HSI would behave similar to the way Mig-21 behaves with Lazur)

I just hit it off overnight and can't remember - I last did the process last year or so on Kola after an update since it's a once it's done it's done sorta thing - also used the f10 to bring it into combat flite via QGIS / transform files Since the F10 is rendered on demand, you have to sleep for a bit between setting the camera position and taking the screenshot to pre render - the screenshot collection is of course the main time sink but is a one time thing

I'd rather have a Mystère IVB or SMB2 for the Sinai campaign and subsequent military operations in the Levant. These would fit well with the current lineup of MiG-15, 7 and 19 and F-86 and F-100

Как, например, где? Если можно, то со скринами.

checked your track and the coordinates reported by JTAC are correct. WE02530543. Try a slow repair, maybe a file broken. Your uploaded Mission is missing a JTAC.

That's my old config, check a few posts later. Something is very strange on your end. You have set 150% now and the SS resolution is 5872x5992 ??? That is crazy high, before that 160% was ~3200x3200... (???) You may have bricked your VR render pipeline somewhere in your system sometime ago. Something is messing with your settings. I'm into VR for 11 years now, always looking to get the best out of it. The PSVR2 is one of the most color correct headsets i've seen. Also very powerful with brightness and contrast (it can do HDR so no wondering here). And it's a relieve to see OLEDs in action again after years with LCD headsets. Sure QLED in the QP is not that bad when it comes to similarities in image quality, but these PSVR2 OLEDs absolutely shine in VR.

Not going to lie I learned originally in metric when doing flight Sims flying German and Russian planes in IL-2, and then with the MiG-21 and MiG-15 as my first planes in DCS, and I actually prefer flying metric. However for the Mi-24P I had the labels in English for the first couple of weeks to help rapidly learn her. Then when I had it down I switched back to Cyrilic. I'll probably do the same for the MiG-29. Sorry learning morse code, and nautical flags are the first 2 side quests on my SIM agenda. Cyrilic is a distant third.

It's by Grinnelli so he might still have the 3d files still. Won't harm to ask.

Ehh I don't think you really need to make any allowances. Most DCS players prefer to go FF Master Race anyway if it's a decent option, and the ones that don't are going to have to face a bit of hopefully just friendly ribbing from both their teammates and oppenents likely. Then when LAZUR datalink becomes availible, you'll get some interesting options the are unique to the FF MiG-29. I feel the FC3 should still be around though so new players can get their feet wet, but I think when people see the difference between the somewhat crude (though good for the time it was made) FC3 and the FF people will go for the more authentic feeling one.

We still have to wait longer for GCI. In RL MIG-29 has been instructed by ground EWRs. Rarely by AWACS.

433 SQN

Was anyone able to mod it in order to have a more Hawkish loadout? This will be the closer we will ever get to recover the Bae Hawk they've stolen from us.

It would be fun for a while with the FM and the Kiev class operations, but being subsonic, radar less and with a negligible payload, it will be old very fast.

I ran another test using your settings. The QP resolution is lower at these settings but still looks better than the PSVR2. The cockpit is sharper than I managed but is still a bit fuzzy compared to the QP. It is similar to what I saw with the Pico 4. I tried a few runs over Syria, and the oversaturation is less noticeable compared to a green map like Normandy. BTW thanks for these settings. I like them. I have tried lots over the years but did not have much success with the edges. 0.33x0.33 with 0.33 edges works a treat. QVFR config smoothen_focus_view_edges=0.33 sharpen_focus_view=0.33 turbo_mode=0 horizontal_focus_section=0.33 vertical_focus_section=0.33 peripheral_multiplier=0.33 focus_multiplier=1 debug_eye_gaze=0 debug_focus_view=0 Here is an excerpt of the log for the PSVR2 set at 150 in Steam VR 2025-09-14 16:20:06 +0100: Found option 'smoothen_focus_view_edges=0.33' 2025-09-14 16:20:06 +0100: Found option 'sharpen_focus_view=0.33' 2025-09-14 16:20:06 +0100: Found option 'turbo_mode=0' 2025-09-14 16:20:06 +0100: Found option 'horizontal_focus_section=0.33' 2025-09-14 16:20:06 +0100: Found option 'vertical_focus_section=0.33' 2025-09-14 16:20:06 +0100: Found option 'peripheral_multiplier=0.33' 2025-09-14 16:20:06 +0100: Found option 'focus_multiplier=1' 2025-09-14 16:20:06 +0100: Found option 'debug_eye_gaze=0' 2025-09-14 16:20:06 +0100: Found option 'debug_focus_view=0' 2025-09-14 16:20:06 +0100: Eye tracking is supported 2025-09-14 16:20:06 +0100: Recommended peripheral resolution: 1938x1978 (0.330x density) 2025-09-14 16:20:06 +0100: Recommended focus resolution: 1938x1978 (1.000x density) 2025-09-14 16:20:06 +0100: Stereo pixel count was: 70370048 (5872x5992) 2025-09-14 16:20:06 +0100: Quad views pixel count is: 15333456 2025-09-14 16:20:06 +0100: Savings: -78.2% 2025-09-14 16:20:16 +0100: Session is using quad views 2025-09-14 16:20:16 +0100: Edge smoothing: 0.33 2025-09-14 16:20:16 +0100: Sharpening: 0.33 2025-09-14 16:20:16 +0100: Turbo: Disabled Here is an excerpt of the log for the QP set to 150 in VD. 2025-09-14 16:44:56 +0100: Found option 'smoothen_focus_view_edges=0.33' 2025-09-14 16:44:56 +0100: Found option 'sharpen_focus_view=0.7' 2025-09-14 16:44:56 +0100: Found option 'turbo_mode=0' 2025-09-14 16:44:56 +0100: Found option 'horizontal_focus_section=0.33' 2025-09-14 16:44:56 +0100: Found option 'vertical_focus_section=0.33' 2025-09-14 16:44:56 +0100: Found option 'peripheral_multiplier=0.33' 2025-09-14 16:44:56 +0100: Found option 'focus_multiplier=1' 2025-09-14 16:44:56 +0100: Found option 'debug_eye_gaze=0' 2025-09-14 16:44:56 +0100: Found option 'debug_focus_view=0' 2025-09-14 16:44:56 +0100: Eye tracking is supported 2025-09-14 16:44:56 +0100: Recommended peripheral resolution: 1520x1592 (0.330x density) 2025-09-14 16:44:56 +0100: Recommended focus resolution: 1520x1592 (1.000x density) 2025-09-14 16:44:56 +0100: Stereo pixel count was: 44457984 (4608x4824) 2025-09-14 16:44:56 +0100: Quad views pixel count is: 9679360 2025-09-14 16:44:56 +0100: Savings: -78.2% 2025-09-14 16:45:04 +0100: Session is using quad views 2025-09-14 16:45:04 +0100: Edge smoothing: 0.33 2025-09-14 16:45:04 +0100: Sharpening: 0.33 2025-09-14 16:45:04 +0100: Turbo: Disabled

Yeah I see it now, it has a total 300 rounds of mixed AP and HE rounds, so the ammo slider is missing for the mission editor. I'll report it to the team, thanks.

Das ist recht unterschiedlich, da nicht alles bei jedem Fluggerät möglich ist und die Regeln offenbar variieren. Ich kann dir nur sagen, wie ich es in DCS handhabe: Bei friedlichen Missionen schalte ich das Beacon Light vor dem Triebwerksstart auf Dauerlicht und danach auf Blinklicht. Ansonsten ist bei mir alles an, auch tagsüber. Auf dem Flugzeugträger aktiviere ich die Beleuchtung erst, wenn ich die Freigabe am Katapult erhalten habe. Im feindlichen Luftraum nutze ich die Beleuchtung nach Bedarf. Die Formationsleuchten sind bei militärischen Flugzeugen und Helikoptern normalerweise so verbaut, dass man sie nur von der Seite und von oben sieht. Meist habe ich nur die an. Im Zielgebiet schalte ich dann alles mit dem kleinen Schalter am Schubregler aus. Ansonsten würden mich auch interessieren, wie Andere das handhaben.

Great list. I have been compiling a list like this for myself too. I will compare and add things I have found out. I run a Quest 3 at x2.0 Supersampling in VD in a 9800x3d and 5090 at buttersmooth performance. From the top of my dome, this hasn't been mentioned before: Download MSI_util_v3.exe (find on GitHub) and enable MSI mode for everything. Also set priority of graphics adapter to high. If running a USB VR headset, also set the corresponding USB controller to high. It has nothing to do with the manufacturer MSI. It means message-signalled interrupts. In easy terms, it is a superior way of managing and optimizing CPU interrupts. Most recent devices like graphics cards, soundcards, USB controllers, LAN adapters etc should be able to run MSI, but for most, it is not activated by default. MSI_util can change that. If anything goes wrong, run Windows in secure mode and disable MSI again. I had good results with it. I reduces input lag of peripherals and the odd CPU spikes. System feels snappier.

I think, one way for server owners to make room for the FF 29 could be to allow EWR reports without AWACS/EWR datalink. Anyhow, we'll find out soon enuf (hopefully).