virgo47

BTW: Su-25T mission starts in the evening 7:45:00 on 14/02/2012, it's not totally dark, but it works really well. Of course, the ideal mission would: have the gates more as a guide with "close enough" working just fine voicovers could be cut by the action mentioned at the end (space, A-G mode, etc.) But that's probably unrealistic. About the K mentioned for full cannon, the line is similar, but not identical to the Su-25T mission. Su-25T has this weapon status panel: I'm not sure whether Su-27 should indicate it as well and it is some kind of regress, but the line says so - except the status panel is left from HDD, not HUD.

If I remember, the comment comes with the additional green-smoke targets. I've replayed your track and you missed many of the gates. Su-27 switches the waypoints just fine, but these old missions are pretty adamant when it comes to the gates. There are many lines you missed, e.g. the one about a low gate when you fly over the first ridge, and many other explanation lines on the way to the target.

Has anyone noticed that gates in training missions have spotting dots as well? Is it a feature or a bug? I think it's a bit distractive - and actually doesn't help with spotting the gate against the sun/bright clouds anyway. I guess the gate is just another plane for DCS.

I'd actually pay for FC4. I like full-fidelity modules, but I also like to have so much fun in a single package. I don't need massive visual or flight model revamps, I'd rather have bug fixes and function polishing and some more capabilities such as dropping single bombs or firing less unguided rockets... that is if the planes can do it (would be strange if not when Eastern trainer like L-39 can). Sure, I'd like to have newer Su-27 variants, but I know it's not possible - so I actually don't care. Not nearly as much as I care about the maintenance of existing modules.

I suspect these two controls should be the same - one on buttons and the other on an axis - but they both remember a different value for the vertical radar elevation. Is that normal or is it a bug? What I mean is, when I push the buttons (which, annoyingly and to my surprise, needs to be done repetitively) it goes to some position, let's say -13 (down). Then I move the axis, it starts in the middle, and I can move it up (e.g. 15). Then when I press the buttons, the elevation immediately goes to the "button" position (-13) and starts from there. That doesn't seem right. Or are there really two sets of different controls in the real Su-27 which remember different elevations? I assume these two (buttons and the axis) should be just two ways to control the same thing, or not?

This is just a reuse of Su-25T gun mission (or the other way around?) but the Su-27 happens way too late - in the morning, instead of in the night. All the voiceover remarks about the cockpit lights, darkness and flares sound ridiculous in such a setup. There is also a misleading line about K showing for cannon ammo full, this works for Su-25T gun panel, but not for the HUDs, here both planes show 4 for full.

I'm not sure this is the same, perhaps it's particular options dependent, but I've got an example of ships appearing, inflating and shrinking in Syria:

I'm talking only about the ships inflating and shrinking; I thought you said to Tippis that it is only a map issue. I didn't notice any flickering and random stuff yet.

OK, I also mixed the issues in this thread with this. My video of the same, also Syria, but from heights, it's more obvious: But that's all from me in this thread...

From the L-39 manual - element 1: The whole handle was turning previously, because that is the actual control - the distance bar on the sight is only an indicator. Both turned previously.

That's the reason why I thought it didn't work at all... not only the distance bar, but the twisty element on the throttle doesn't move either - that's where I was checking, not the HUD. Thanks, Flappie, always nice to hear from you. So to summarize: buttons don't work at all the axis seems to work on the HUD, so hopefully, it works properly in the action while in gyro mode, etc. graphics element in the cockpit don't work - that is the twist on the throttle and the distance wheel indicator on the gunsight.

My options.lua: options.lua

I noticed ships "growing" in one video showing OB 2.9 and it was quite distractive - that was the Marianas. Later I saw it myself in Free Flight mission for Yak-52 near Haifa - that is Syria map. Ships appear, then they grow as you close in - but not realistically, they really inflate - and then they shrink as you fly away. My DCS was repaired after OB 2.9 update. My LOD is set to 1, I can try again without DLSS whether that is an issue, although I doubt it.

I don't mind when the bugs appear, especially in OB, I understand they will not play all the missions and try all the features of all the modules. I'm not sure they have some kind of automation for it - if it is even possible. So I understand bugs in OB, especially after a big change like 2.9. I just hope they will not join the suit of many other long-standing bugs. Hopefully, this is considered a high priority as it should. But sometimes I'm not sure whether some modules are not low-priority as a whole... I like flying a couple of older modules and they often feel a bit abandoned.

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.