Jel

This issue has been around longer than 2.9. So I seriously doubt it has anything to do with DLSS and SSS

Thought so, they behave the same after all. Kind of weird tho, i thought the Bird would show me the exact payload instead of "kind of"

When loading jdams, PACS always shows GBU38 on CFT stations - also when i have loaded GBU54s. How do i load up the 54s ? They don´t show up in A/G Load Page...

I´ll try that one, thanks for the input !

Yep thought so already. No worries, system can handle that resolution just fine without DLSS, i was just hoping i could maximize the results on terrain and objects. ATM it looks like i´d better stick to MSAA.

1920x1080 - tried all modes so far without visible changes

I don´t know if this already has been reported so forgive me Using DLSS since Stable 2.9 Update, all Cockpit labels as well as Gauges and LCDs seem quite blurred and partially unreadable. Without DLSS, using good old MSAA instead, the labels are significantly clearer WITH DLSS: WITHOUT DLSS: I played around with sharpness first from 0 to 0.3, to 0.5 and even above, no value had any effect on that issue. Combined it with other new features such as SSS, nothing. At that point i don´t know enough about those features to try anything else, so if anyone has any ideas - i´m listening

Got the same issue without DLSS. (could use DLSS but don´t for DLSS causes blurred instruments on my end) So no relation to DLSS. Had this in 2.8 on just the F15E module - since 2.9 i see this on all modules and all maps.

Today i was refuelling the F15E, having another 5K lbs to take, as the KC135 suddenly tells me "Ford 1-1 (that´s me), chicks in tow, 1 mile trail at 11.000" I already was latched and taking fuel, so 1. why that in the first place ? And more importantly: AN A.I. F16 came from precontact position and flew right into me - both of us crashing and gone. Just like i wasn´t there at all. I was connected to the boom the whole time, no disconnects, no "return precontact", nothing. A clean fuel flow. And A.I. Viper thinking "meh, just proceed. He´ll move" Anyone seen this before ?

Kann man wissen. Oder auch nicht Jetzt tu ichs - danke für den Hinweis.

List of available comm devices in the VOIP settings as well as in the VOIP overlay window do not match the individual modules. For Example on AH64: Overlay has UHF - VHF - FM1 - FM2 - HF (from top to bottom) but the EUFD reads different: VHF - UHF - .... can be quite confusing sometimes. Another example A10CII: Arc210 is comm1 in the plane - sitting top above comm 2 and 3, Overlay got the arc164 listed on top.

We currently need 2 buttons - one for voip ptt and one to open comms menu for contacting AI. I suggest voip ptt button opens that as well - while holding. release closes menu again. Or at least make this as optional setting.

I´m talking about HOTAS Buttons on the A10 I want to keep bindings realistic instead of rebinding buttons that shouldn´t be. That´s why i wrote above - could be so easy with just the suggested additional functionality.

Naja vor der 2.9 waren die APKWS unter "Luft Boden Raketen" einsortiert - was deutlich mehr Sinn macht. Das ist erst seit der 2.9 fürs Deutsche derart widersprüchlich verändert worden.

My personal biggest problem is that when using hotas binds for voip, i no longer can open the ai comms menu for any device with the same hotad buttons. This means i have to bind additional buttons which is not very convenient. Try the A10: mic fwd,dn,aft each for voip. When i want to contact ai (tanker, airfield, jtac, etc.) i have to use keyboard with additional 3 binds. Why not make it so by pressing the mic switch (voip), it also opens the comms menu ? Releasing the button then closes it again. Or make it optional in settings at least. Or did i miss anything ? Voip has been tested for long, some1 must have had this issue already.

Ah such a shame. I was looking forward to finally drop SRS after the announced VoiceChat progress. Unfortunately we encounter so much issues, as stated above by other users already. Feels sad. Yes it may be another year until we test voice chat again. Theres just no point in testing hours after hours while we're already having an already working solution: SRS. Please focus VoiceChat more. It really has potential but is of no actual use currently.

A10CII Bewaffnung, Station 2: "Ungelenkte Raketen" beinhaltet die APKWS ? Irgendwie widersprüchlich oder nicht ?

So since latest Stable Patch 2.9.1.48335, the loading of cockpit textures and liveries of ANY module takes really long. Before, i only noticed this in the F15E as well as the AH64, sometimes taking 10 to 20 seconds to get fully textured cockpit (i call this "long time" compared to all other modules textures getting loaded instantly). Now after 2.9 update, those modules sometimes take a solid 30seconds up to a minute to texture the cockpit. All other modules such as the A10CII, F16, etc. also got significantly higher texture loading times. I tried with DLSS but as this makes many switches and gauges look blurry, i switched back to MSAA again. So no effect here. Didn´t change anything else. System also is the same as before: I76600K, 3070, 32GB, SSD, Win10 Anybody else encountering this ? Any ideas ?

Just looked into current Stable - Mic Test still horrible

2.9.1.48335 Stable: Optionen -> System Punkt "DLSS-Perf-Qualität", (DLSS aktiv): Auswahl im Dropdown zeigt "Qualtität"

Nach Missionsstart sollten meiner Erfahrung nach ein paar Sekunden Puffer existieren damit so ein Trigger zuverlässig funktioniert. Ich würd das so bauen: 1. Die Gruppe mit deiner Eskorte auf "unkontrolliert" setzen. 2. Triggerzone Parkposition erstellen 3. Trigger: Prüfung auf "Einheit am leben = Du" + "Einheit außerhalb Zone = Du" (Alternativ geht auch "Mehr Zeit 10" + Einheit außerhalb Zone = DU") 4. Trigger Aktion "Gruppe KI an = Deine Eskorte" (oder sinngemäß, ich hab den exakten Wortlaut grade nicht im Kopf". Faktor: Nach Aktivierung der KI dauert es etwas bis die Maschinen rollbereit sind - dafür schaut es einfach besser aus wenn Maschinen nicht einfach so erscheinen Wenn du das beschleunigen möchtest, stell die Gruppe bei Punkt 1. nicht auf "unkontrolliert" sondern auf "späte Aktivierung" + "Start von Parkposition, Triebwerke an" sowie bei Punkt 4 dann auf "Gruppe aktivieren = Deine Eskorte".

Quite a feature: Set a flight of Hornets to launch from CAT 3 and 4 - works perfectly. Go into mission editor and change the birds´loadout or anything on the carrier deck - the cat resets to CAT 1. You have to set it again despite you never changed it back.

Hoffen wir einfach, dass das Teil mit stabilem Deskmount kommt

*bump I´m still curious if and how i could disable the F10 map for certain units or groups. I´m not referring to hiding a unit - that´s already possible. What i´m planning is for a client not being able to use the F10 map at all. There are some trainings in which i really don´t want people to "cheat" navigation but rather learn how to use VOR, ADF, TCN, etc.

Thanks, explains a lot.