virgo47

After 2.9 update, the Gunsight Target Distance does not work - which is quite a serious usability problem as it affects a lot of weapon delivery procedures. I'm sure it is one of the 2.9 updates, as I tried the module and its training missions quite recently and it was working fine. It's not possible to move it with an axis, nor with buttons. Both the axis and buttons are responsive in the Controls setting. Can anyone else confirm it? (Just in case it's some upgrade+random mod problem, although I don't believe I have any mods that could affect this.)

With action binding Gun+PK3 Switch - ON (or ON/OFF) it is possible to move the switch even when the cover is closed: I'm not sure whether this is new after 2.9 or old. I tried some other switches with cover and they seem fine (but I didn't do an exhaustive test).

Ah, so that's why my marker alarm was beeping seemingly for ages. Definitely a regression here. I also noticed it while landing on Mozdok in any of the training missions.

I'm not sure whether I just missed this floating screw-head before, but now I see it in ZA variant (not in C though): Different angle: And there are more new bugs in 2.9, but I'm going to report them in a different thread... L-39 would really deserve a bit of love once again. I don't believe any refresh will come soon, but having a module that accumulates bugs and visual glitches is kind of a shame.

I don't know really, perhaps it surprised me in Yak-52 a bit more, because as a propeller it has quite fast gauges compared to jets. I'm not sure how much tuning ED can do on the DCS part or how much it would get better with newer DLSS versions (if it is even applicable to my RTX 3060). I don't play many other games nowadays besides DCS, and I wanted to make my GPU work less, if possible, for V-synced 60 FPS - which is perfectly fine with me for a flight simulator. I just honestly reported it, thinking something could be done with it. If not, then I'm a bit underwhelmed by DLSS. I expected more from the upscaling, these issues remind me more of frame generation problems than "just" upscaling. BTW, this seems to be a DLAA problem, perhaps DLSS makes it a bit worse, but DLAA alone shows the issues already. If there are minor differences between DLAA alone and DLSS (quality, BTW)+DLAA they would hardly translate to compressed video I guess. About making my card work less - which results in less fan noise in my GPU model - these are my results according to MSI Afterburner overlay: No AA: GPU 77%, 1140MHz, 56W -- ugly edges, etc. MSAA x2: GPU 77%, 1290MHz, 60W MSAA x4: GPU 77%, 1477MHz, 72W -- works hardest here, but very nice results DLAA only: GPU 77%, 1365MHz, 65W -- power draw between MSAA x2 and x4, but visual quality is worse for moving stuff DLSS Quality: GPU 77%, 1050MHz, 54W -- I'd like this , static scenes look great and smooth DLSS Balanced: GPU 77%, 990MHz, 52W -- I'd not use this, some thin lines (e.g. clock hands) are often very unclear CPU was always the same (11% utilization/36W in my simple hot-on-the-runway test). The numbers are interesting, as the reported % on the GPU is always the same (77%), but the needed power is not. This is all not a big deal, I'm just experimenting with that, I may still use DLSS and live with the ghosting - but it clearly affects the realism/immersion part here and there. I simply didn't expect so many instances of ghosting, blurring or various types of aliasing when no frame generation is used. I definitely don't plan to report it for all the planes. I didn't notice on the few others I managed to play with OB 2.9 yet but these were jets, perhaps with cleaner textures (the pattern on the Yak-52 stick is probably quite difficult for DLAA).

As the title says, levers, gauges (pointers), the stick, rotary knobs... it gets blurry or causes ghosting with DLSS/DLAA. It is perfectly fine with MSAA 4x. A short video comparison is here:

Lastest OB 2.9.0.47168 (MT), my installation files were cleaned recently, but the issue is still there, so it was definitely not caused by FMOptions.lua tuning.

I've got two icons pinned on my taskbar - DCS MT and Updater with parameter, so it doesn't start DCS - because otherwise, it starts default (non-MT) DCS. The end of my target looks like this: ...\bin\DCS_updater.exe update Also learned the hard way after being used to auto-update. This issue is not a problem for Steam users, but I'm sure it will be eventually gone when MT is our only version. Back to DLAA problems - or promises about the future of FC3 HUDs!

I can confirm it works well and the zone in the mission editor looks great too. Thank you very much!

The issue is fixed in the latest OB 2.9.0.47168. It is not blurry anymore, however, the HUD is of lower quality than the rest of the scene or when MSAA is used. Su-25T HUD now with DLSS+DLAA is quite jaggy (200% zoom): But otherwise, it works fine. It looks much better with MSAA though (different moment in the same mission, 200% zoom again): So I hope this is not the final version, but the most prominent problem is fixed. Thank you, ED.

I can confirm that after removing the Clickable-FC3 mod and then running .\DCS_updater.exe repair from the installation bin folder the issue went away. I can easily live without the mod (which is cool, if for nothing else, for all the labels/tooltips it gives you), but I can't live without HOTAS in F-15C. I'm not sure whether this is solvable by ED or whether the mod authors have to update it for 2.9.

I'm not at home at the moment, but I do indeed have the FC3 clickable cockpit mod active. I'll try with the mod disabled or uninstalled on Thursday when I get back home.

I wish this got at least aknowledged by ED. In 2.9 I'm more affected by bugs than features, which I can understand IF the fixes are coming soon enough. I like FC3 planes and with Su25T ltv bug there are at least two bugs that are not related to DLSS but are clearly a regressions.

Yes, I can confirm this, only some part of the TV is usable after the upgrade. This is easily reproducible after a few steps in the training mission "Vikhr Laser Guided Missile and Mercury Pod". I played it just a few days ago before the upgrade, and everything was fine. Now it looks as in the picture above. (I also played this just a few days before the update and everything was OK.) I tried single-threaded version as well - and that is also bad - nothing is visible there at all.

I tried Su-25T HUD, Caucasus Free Flight, just turning a bit and pitching up/down. It was always ghosty/blurry, with DLAA alone or with DLSS Quality. I had head-tracking off, so the HUD was moving only against the sky/ground. I tried both with sharpness 0, 0.5 and 1, it seems to do something, but I'm not really sure, because it doesn't help.

I guess they are gone, not a problem to redo them from my list, but currently it is not possible, when it's "darker", it's not available. Somehow the definition of these bindings refuses gaming devices except for the keyboard. Many modules have similar bugs on a smaller scale, but this one came out of nowhere.

This is OK in general, I also have one momentary button as a modifier on my throttle. What I suspect more is the logic behind those <> bindings marked as "Special for joystick". I don't have this module, but these often have a logic behind them, e.g. "when the button is not on anymore, return to default position". Try the bindings above, they should cover the same switch positions, or not? Often the <> stuff is for switches without middle position "press", but if you have three position with three logical presses (as it seems), you should be fine with the absolute bindings.

Great, I can confirm that with Canopy Jettison + Ejection (3x) - in this or reversed order - I was able to eject. Thanks for the fix.

After the latest 2.9.0.46801 (MT) I can't reconfigure tons of previously bound commands to my HOTAS for F-15C. The scale is staggering: I'm a firm believer - if it can be bound to a keyboard, let us bind it to a controller/HOTAS buttons as well! I know, this is just a regression, but you should somehow make some order in these matters, please. I hope that F-15C is popular enough that we will get some quick patch for NOT being able to turn even the radar on with HOTAS!

Yup, noticed this with Su-25T as well. Seems to be caused by DLAA, as it blurs the HUD with or without DLSS when DLAA is enabled. RTX 3060 12GB in my case.

This makes sense! The zone is quite small - if the graphic is precise - because it is quite likely I aligned just in front of the numbers 09! I'm not sure if the zone can be enlarged without triggering lots of QA on your side, but I'd suggest to cover the wider area - e.g. anything fromt he start of the runway for the most "borderline" pilots. What could have happened when it did not work with the axis and then worked with the +/- binds is that I moved a bit, just to get to the zone. If it checks the gauge (and not the binding) it is generally the right logic. Thanks, Flappie, this all makes sense. EDIT: Why can't I remove/change the "solution" mark? Or is it possible somehow?

I'm totally puzzled now. I tried today and couldn't reproduce it either, although previously I definitely managed to repeat it a couple of times - otherwise, I would not be able to figure out the "workaround" and I'd not dare to report it. So I guess it's "cannot reproduce" for now. Sorry about it. If you see something suspicious in the script, cool, but while I'm not 100% sure it's OK, I can't do more about it now.

So it is flaky somehow? I'll get back to this and provide the trackfile, it was pretty reproducible in my case, I could repeat the test a few times and nothing, but I'll double-check and get back to you.

Yes, I forgot to mention I know the trick. The report is about official training missions that should just work. But thanks for mentioning it. I just copied the file from \games\dcs-openbeta\Mods\aircraft\Flaming Cliffs\Missions\Training\MiG29S - 8 - KMGU-2 CBU Dispenser.miz (installation directory) to my Saved Games DCS.openbeta\Missions\, opened it in the Mission Editor, saved it - and it started to work without even going to the zip.

The mission cannot be started as it requires WWII Armour and Technics? This must be some kind of misunderstanding, or leftover accident in the mission file. I don't remember doing this before, so I'm not sure if it's a regression or what. But I'd like to start it without WWII module.