All Activity

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).

Restarting this thread after some changes were made to the magic 1 functionality. Sadly nothing was changed about the missile after launch, just some changes to what happens before firing as I suspect is in line with the fact stated by @fausete that Aerges has no control on what happens to the missile after it leaves the aircraft. As it stands the missile is useless, being only capable of a hit on a non maneuvering target from dead 6 despite numerous evidence of its real life performance being very good for the time. This really hurts the module as a whole, as the magic 1 is an essential part the the planes weapons set on era constrained missions and servers. While I understand that it isn't a Aerges issue and that ED has shown evident disregard for this issue, having gone as far as removing the thread from the official DCS weapons bug forum, I am still hopeful that the developer Aerges can put some internal pressure on ED to address this, as some internal team members have the data and surely the interest to see this missile perform somewhat like it did in real life instead of being a useless paperweight, simply because ED can't be bothered to listen or care at all to change a single value in a LUA. Disgraceful. This is such a simple issue that the lack of attention ED shows towards it is quite infuriating and saddening about a product otherwise very enjoyable. Hopefully someone ends up giving a <profanity> somewhere and people end up doing their job...

Текстуры кабины всё-таки "пластмассовые". Неужели в 2025 году нельзя сделать текстуру металла, чтобы оно выглядело как металл.

Ahh, oke i gues you got the info then..thanks. Moving on patiently... Regards.

Yep, like I said, it can help in some cases. PC's (and Windows) are weird (and the infinite number of combinations of hardware don't help). I actually just replaced my gaming computer last spring and no issues with previous or current one. I only make the point that it's not an absolute requirement so people don't think it's the only cause/solution and are confused if it doesn't fix the issue. Some previous posts imply that "you must do it this way". It's a very easy thing to try and check so absolutely a good troubleshooting option, but may or may not be relevant.

Hello . Yes it is planned

I would agree that it's strange. I got a new gaming PC earlier this year. My three WW MFDs worked fine with the old PC, but with the new PC they kept showing up incorrectly (wrong orientation and positions) after every restart of the PC. I'd go into W11 Display, DisplayLink and SimAppPro to reset them, but the next restart would mess them up again. It was pointed out in the subforum that the three MFD usb cables should be plugged in next to each other in the powered usb hub. I did this and it fixed the problem. I'm not a PC system type, so I'm not sure why where the MFDs are plugged into a usb hub would matter, however in my case it clearly did. I tried asking my IT manager at work, he throw out some techno terms/concepts about how hubs handle what's attached to them and fed to a single PC port... Greek to Me ... but he wasn't surprised that changing the usb positions in the hub solved my issue.

Thank you! It seems like I can sometimes hear from the wingman, is this because the message from wingman is sent from another way?

It's not hard to rip the landing gear door off on the F-18 if you're careless with speed (which at a minimum means you can't drop A-G weapons).

I agree. I fly MiG-21Bis and don't speak Russian. Whenever you hover mouse pointer on certain switch, you get text which translates to English. Like that I am able to use it without problem. After couple of months you get used to all switches and don't even need any language.

Hello Silver I'll do. For the moment I change my Page File according to your post above, I had to much! Cheers

Not sure if Winwing have software to do this but it should be possible using Joy2Key. It can used for assigning mouse movement, mouse centring and mouse buttons to joystick controls.

Keep in mind that 4th generation is the most lasting generation of aircrafts. So considering this MiG-29 variant.It is early 4th gen and it is pretty good against 4th gen fighters in it's era. 1980s. Except for F-15C, but then again MiG-29 was never meant to go against it. F-16A is your primary. Problem is you cannot keep it realistic and within time frame in PvP multiplayer. Not enough playable aircrafts. I don't think they will, and no reason actually. There are still people who own FC3 modules and it would be wrong to exclude them from multiplayer.

Hi there! I started playing with JTAC and immediately faced with an issue. JTAC reports me wrong coordinates during the 9-line interaction. It should point me at group 18, which is something around WE0252905432. But it keeps pointing me somewhere over the sea: WE028xxxxx... No matter what unit I use, airborne or land, it keeps pointing me at the sea. Side quest: in the track, after it reports me wrong coordinates, I'm trying to find the target myself with the targeting pod. I'm creating a markpoint, but when I'm trying to use it (weapon designate), it points me to different location (looks like near the WP1). What is wrong with that? jtac-and-targeting-problem.miz jtac-coordinates-issue.trk

Gib es das noch in einer Mediathek ?

yep agreed, however my point was to the gentleman making the reference to the english cockpit, for those that want to fly in metric, keep the cockpit in its native form Cyrillic. Yep my point was someone was asking for metric in the english cockpit - when in the western world we don't use metric. If you want metric use the native Cyrillic, no need for additional waste of dev resources for people that want to fly metric but not prepared to think russian lol.

Это очень интересно, то, что Вы здесь написали. Только я не понял, зачем Вы это сделали. Вы, очевидно, не являетесь представителем ЕД и принимать мою кампанию не можете. Тем более, что этап приёмки пройден - ответ отрицательный.

Hey, had any luck with that back then?