virgo47

The same here, but I didn't make anything of it... until now! Now it seems like a conspiracy.

I understand this. I see the cheapest new RX 7700 XT here for 427€ (XFX), or 436 (Gigabyte) - available. But the prices got here only recently - month ago the cheapest one was 450. I'd never buy non-baseline 5060 Ti, it doesn't make sense. And yes, 460 was a borderline price for me as well. I could have waited, but I didn't like DCS visuals in 1440p with 3060. I also upgraded kids computer in the process from RX570, so it's like two upgrades for the price of one. I'm not really proud of buying nVidia product for in these times, I know I have sinned . But if I can choose NOW, assuming I want to buy something in this level, I'd rather have the newest 5060 Ti for 460 than RX 7700 XT for 430. More memory, sucks less power, newest DLSS (that really is improved, even in DCS, not that it is perfect). It could be interesting to see how RX 7700 XT performs with similar settings and FSR. I have no idea whether DCS is strong for AMD or nVidia or the same. And the prices in the current climate... I don't know if they're going down anytime soon. If they do, I'll wish it for all the other potential buyers, I don't think they will fall so much I'll regret this purchase. That said, if you can hold - hold, of course.

True, the same experience with DLAA. However, the technology really progresses here. The same settings with new HW (3060->5060Ti) were noticeably better, sharper, etc. I finally switched from bearable DLAA-only to DLSS, because suddenly it looked better. I believe FSR and related technologies will also help (e.g. FSR 4 is much better). So eventually we'll get there. I don't know why MSAA shimmers so much. It seems it doesn't like shaking. I thought MSAA treats every frame independently, so shaking should not be a factor.

In Europe, we've been lucky to have some reasonable prices for cards like Palit and Gainward, so I snatched one. To summarize my 1440p VSYNC 60fps gaming experience, I made this video: tl;dr: You can fly in the very nice DCS 1440p, with most detail sliders at the top. I'm very satisfied.

I used MSAA year(s) ago, with RTX 3060 I left the job to DLAA (better performance, with some quality issues). After a recent upgrade to RTX 5060 Ti 16GB I revisited MSAA and compared it to DLSS and DLAA-only, and I was quite surprised by its shimmering. But this happened in a shaking F-4E cockpit, so I can't say whether it's good or bad. I don't have any RTX Dynamic Vibrance or other out-of-game options on. The video moment demonstrating the shimmering shake for MSAA 2x and a bit later 4x is here:

It should not work this way. I have 60 FPS cap, VSYNC ON and 60Hz monitor. I regularly see any number between 30 and 60 when the detail/complexity is too much for 60 FPS. I assume the card just waits with the frame presentation for the next VSYNC, but not really with the preparation of the frame - that one should start right away when the previous is ready (and waiting for that VSYNC). At least that's how it worked for me with my GPUs and DCS until now.

I've just tested this, it looks really cool. One thing I noticed is the label for my plane turning with the map. I guess the labels should be put on the rotated map in normal reading orientation. Another thing would be to have R (rotate) and F (follow) work independently. As of now, with Follow, I can't disable map rotation to my heading. I was just messing around with it for a while, but as an independent NS430 alternative which can be put on another screen, it's very, very nice!

Ideally via web, so it doesn't have to run any fat client... so we can get the pure Linux server later.

Today, I upgraded to RTX 5060 Ti 16GB. I haven't tried the situation above before the upgrade, but I clearly remember that F3 flyby views showed ghosting regularly on my previous RTX 3060 - even on pure DLAA without upscaling. With RTX 5060 Ti, I tried DLSS Quality just to push the limit a bit - and to my positive surprise I see no ghosting in F3 view, I see beautiful and crisp cockpit in Yak-52 (even zoomed out a bit), needles are sharp enough with no obvious ghosting... it's great! It seems this problem had a HW solution - and perhaps some SW updates helped a bit as well - but as I said, ghosting in F3 was pretty obvious even recently. HW change changed it for much better. Now I seriously consider using DLSS. Problem solved - and yes, this was not even Yak-52 specific problem.

I noticed this - and I thought how smart I am to override this in Saved Games\...\Config\View\Server.lua. And then I came to HB Coldwar server and all these customizations were back to original limits. Yeah, second pilot is seriously short-sighted.

I would love that too... I own L-39 module and it's one of my favourite planes (if not THE one). But NG really is a different beast altogether - even when using the time-tested airframe (more or less). I've heard DCS players trying L-39 talking about an "obscure" or "unknown" plane... now imagine how popular the NG would be. The module would need to be built virtually from scratch, as any other new module, and the market potential is very limited, I'd assume. Even if I'd love NG and buy it instantly, it's simply not enough. On another note, it's great NG is getting produced, I hope it will continue!

Thanks, man, I appreciate the explanation. I thought some of the stuff would be beyond HB control. I just summed up my fresh confusing experience - while it was fresh - without feedback there is no progress. Obviously, I write more about problems, not about the good stuff, but I'm really enjoying my baby steps with the module and all the features. HB modules are like DCS on steroids.

I was watching a video where the Explain function was demonstrated, but I couldn't quite reproduce the result exactly. I guess this is fluid right now and while the video creator got into RWR Handoff section directly, it only opens RWR to me. Messing around with the function I was a bit confused, but after a while I (hope I) figured out why: There is no indication whether the explanation is available or not - this could be improved with custom cursors, that is, if DCS supports such a function. It would be great to know if it makes sense to even try to click on the knob while holding the explain function. The Explain function works also as a manual toggle, which is mostly neat, but does not do what I expect every time - especially in combination with the point above. E.g.: If there is manual section linked to the feature, it will work as advertised - the manual opens on the section, or shows the section if open already. This is great. If I click and don't get anything, releasing the "Explain" button will toggle the manual - which is not what I wanted. The case when it opens the manual without showing what I want is most confusing. Why is it so laggy and doesn't open it on click? Why does open it after the release? And why doesn't it show the section? (These are the questions that came to me, of course, I know how it behaves after a few minutes.) Some controls HAVE the right link but don't show it as expected - it seems like the area for the explain function is decoupled from the cursor change on the controls, e.g.: In the picture above, I previously clicked on the OPR ERS/Contrast button, then moved to the Brightness/Horizon Line Knob - and I clicked it with the knob cursor obviously active. It did not do anything (or toggled manual when I released the Explain key). But that knob HAS a section - you just have to find it, I accidentally did, and it reminded me old-style pixel hunting in old 2D RPGs. So when the feature works, it really is a great thing - this pushes the DCS boundaries! But it would be great if I knew if the section is available or not, e.g. via cursor. And when I click already (successfully or not), perhaps don't make it work as a toggle?

Thanks, I know this camera stuff and how to move my head - I forgot to mention I'm a control/view/snapview freak. Head position can make this marginaly better, but the core issue (and as I said, no biggie) is the mirror angle, not the head position. Changing the head position messes up with too many other things - e.g. the HUD.

Nope. Yup, no biggie, I've seen the whole thread, just wasn't sure about the current state. It will wait.

Thanks for explaining the initial position - although it's not useful while starting in the air (e.g. Free Flight), but let's focus on this adjustment: "Might" meaning already, or in the future? If now, how? I tried to click/mouse-wheel-roll/drag... nothing. (BTW: Sorry for starting my F-4E journey with the mirrors... this will not spoil it for me, of course. )

OK, so to clarify, this is my whole screen in 1440p resolution, but that's not important - FOV of 78.8° is: 78.8 is pretty narrow, that's what I meant. But that's not the problem, the mirror angle is. Even in your picture there is still too much of a cabin and helmet and not enough stuff behind. Of course, I DON'T know what the real mirror view was, but if it was adjustable at all, I'd set it higher.

I didn't have TrackIR enabled at that moment, no repositioning, it was the first time I used that plane (today)... I don't know. Yours is definitely better, but also much wider, I guess you already readjusted it.

I haven't configured my views/snapviews yet, I'll do that very soon (one of the first things I do). But from what I tried so far (moving the camera around), I have to go quite low (the pipper being barely visible) to get a reasonable view. This is the default view you get without any adjustments, free flight, Caucasus (I snipped the middle-to-top portion of the screen only):

I've just bought F-4E, it looks great (obviously ), but the center mirror in the front pit is really useless with its current angle. I'm really looking forward to either the adjustability, but even a fixed mirror actually looking behind/above me would be great.

You're welcome. Check tip #1 from https://www.digitalcombatsimulator.com/en/files/3319022/ - it helps with debugging these things although the output may be overwhelming. Alternatively, try a button like this: This will tell you what is happening as you change the stuff in the cockpit for that control.

It's just reversed RWY and wind, it really is that simple. Not sure why someone turned the wind around, because besides flying much longer you also don't overfly the markers mentioned in the voiceover. I changed the wind to this, and the mission is much better - close to the original one (EDITED, at first I left the wind north-to-south, now fixed so it matches the voiceover):

I'm glad the old Instant Action missions will be preserved - it's true that the split between Instant Action and Missions was often arbitrary and seemingly random, good we will find all prepared missions in one view. What about Create Fast Mission? I don't see it mentioned here at all - but isn't that "Instant Action Generator" of some sort as well? Will it be replaced by new IAG?

The problem is in the representation of the flaps lever position - it goes from "0%" to "100%" - yes, with the % character - with 100% meaning UP (0°) and 0% meaning down (50°). I made two experimental TP pages, they are in the attachment if you are interested. One works with % only. It requires one backing value (numeric 0-100 range, but without %). The other page works with degrees range (0-50) internally, but requires another value for intermediate calculation in both ways - when the value comes from DCS, and when I need to construct the value 0-100 with %. The degrees version requires two values - one for the original range and one for degrees. This is the implementation of the button displaying the value - this also updates the internal value from the DCS BIOS/COINS value: Here is an example of FLAPS UP button: Flaps DOWN is the same, just increments by 10 and checks greater than 50, set to 50, the lower two blocks are the same. PageExport_2025_04_04_17_23_38.tpz2

I don't want to sound harsh, but I'm pretty sure many of these things are mentioned in the Su-25T tutorials - and the manual is also not that long. Even if it feels overwhelming, it's not - compared to other so-called "full fidelity planes". Su-25T is very similar (in controls) to so-called FC (Flamig Cliffs, or FC3, newly FC2024) "low-fidelity" planes which are really fun to fly with and RELATIVELY easy to control. If you learn a few tricks in one, it will be very similar in the other planes as well. But - not to hijack my own thread. I've noticed a few threads of yours that are very basic and I believe a bit of search would do the trick. No hard feelings. DCS can be overwhelming, I remember myself. The guy I tagged is not a dev, but helps with testing/bug reports... I'd say we have a bit of history (I hope a good one ;-)), but I can tell you for sure, the mission WAS designed for RWY 10 for sure. I know, I remember.