virgo47

What about other Warsaw Pact countries? As far as I know, Czechoslovakia got MiG-29s just before the 1990s started, similarly GDR... so it's a matter of interpretation to some degree, but realistically, MiG-29 was not the backbone of any air force, not even Russian during most of the 1980s. I can only translate the page, but it doesn't seem to firmly suggest there were 600 units in 1985, even generous estimates are more in the 200-300 range. And when it comes to the potential front line, e.g. Germany/Czechoslovakia - we had MiG-23, many 21s as well, and various Su bombers. MiG-29 was a sci-fi for most of the 1980s here.

Yeah, my thoughts exactly. I assume this will be higher on their priority list than, say, Yak-52, but how high with all the other top-tier ED modules still in the development, that's the question. That said, I'm glad there are many people who like and buy the module. For me, it's a pass, at least for now. Maybe I'll add it later, but right now it would just be a hangar queen - and I've got quite a lot of those already. But the module looks impressive, at least from the video.

I tried F-15C - and there was no problem. There was no problem with Su-25T either. But there was a problem with F/A-18C, F-5C and L-39 (as originally demonstrated). Track is in the attachment, video is here: I was a bit suspicious about video settings, so I halved the quality sliders, but there was no visible difference. However, I enabled max FPS and disabled VSYNC for this one. I tried to recreate the same problem with MiG-15 (non-FC) and TF-51D... no luck. So it's not one plane, but it's not all the planes either. And I'm confuses what the problem is. I hope you are more knowledgable about it than I am. I had a similar problem with the Dover Castle on The Channel map - and I know it's not yours - but again, it is more confusing after today. I couldn't recreate the problem reliably and repeatedly, so it seems to be something with some map models and something else as well. rovaniemi.trk

This is my experience with the latest patch. I'll be away from the game for a few days but later I can add more info such as track, configuration, etc. Oh, and thanks for coming back to me.

Thanks, I encountered it over this Rovaniemi building: These are the coordinates: This seems to be a unique Rovaniemi building. Of course, I'm not 100% sure it's that one causing the FPS drop, but it seems the most probably culprit.

I'm just trying, but it's not making the experience easier from the typical DCS bug reporting perspective. 1) Discord is another platform. 2) It's mixing DCS and MSFS content. 3) There is still no clear bug reporting channel - at least not for newcomers.

I made one more (shorter) video - and with DCS stats. Even though the Afterburner doesn't show anything suspicious on the CPU, DCS stats show clearly that that area is CPU bound. This is not a speciality of Dover castle only, I found similar stuff on other maps and with other buildings - so it seems there is something about some buildings that cause a massive problem. But I don't want to diverge here.

Dear Kola users, what is your experience? Does Orbx regularly respond to bug reports? I was surprised that the Bugs & Problems link leads to "Suggestions for DCS: Kola Map by Orbx" on the external forum, which is annoying (another registration). And bugs are definitely not the same as suggestions - there should be some dedicated subforums for just bugs/problems. And the other subforum link is 404, which seems a bit amateurish - or at least disconnected from our DCS world. I wanted to report low FPS over a particular building model, but I don't see many responses in the bug reports there - or was I just unlucky in my search?

I've encountered the same issue recently. Flying around the castle causes extreme stutters. Track file attached. Video demonstration here: I've got 5060 Ti 16GB in PCIe 3.0, that's true, but the FPS drop is massive compared to the reasonable FPS before. Something fishy is definitely going on there in that spooky castle. One more observation - when the simulation time is slowed down (1/2, 1/4)... the FPS drop is not that massive. It seems like DCS is very quickly loading something or what (wild guess), because the FPS is not caused by the scene itself, but by the fact we pass around very quickly. test-channel-down-dover.trk

MSI Afterburner seems to report pretty good number (most of the time within 10 MB difference, rarely more): However, the total amount of taken VRAM (~7G here) is clearly affected by DCS, whether it is explicitly use by it or not. So even if DCS reports usage way under 8GB, it doesn't guarantee good experience on 8GB card, because what DCS does affects the other usage of the card - even if it is not used by the process itself. It's not quite about the OP problem, but DCS definitely needs more VRAM than it reports. Way more. It's not just "add 2.5GB for other usage" or "it's just the browser and Windows itself" (not quoting anybody here ). On Germany, I have a much bigger difference between the numbers (example picture is not from Germany map).

I hardly ever use The Channel map - but for whatever reason, I bought that one first on some 50% sale. And it was nice to fly around, but it really is small. And I don't have any campaigns for it yet, so... that's why I don't use it. But with it, I could buy Normandy 2.0 (without having the first version at all) for close to nothing (was it 15? I don't remember). That one was a steal, really. Normandy is beautiful, much bigger, and has both London and Paris for fun flying. So I don't say The Channel is bad, but it is the best way to get both for a very good price. Is it an exploit? I don't know. I just wanted the Channel because I saw it in some other low-level-flying videos - but now we have many more good options for that. Syria, Normandy, Marianas, and obviously Germany now... these are all great low-level (and good also from mid-level, unlike AF/IQ). But back to the maps... get both, starting with The Channel and then Normandy for an unbelievable price as well.

Great news, especially the assets - and especially being part of the core game for free. Absolutely fantastic. I have a strangely good vibes about the last couple of DCS updates, quite a lot of bug fixes... maybe because a few fixes important for me were added, but still. I like the updates since the version unification quite a lot, including the cadence, etc. Keep up the good work.

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?