ColinM9991

Multicrew at last, looks like DCS is on the menu again this weekend!

Been merged to stable now. What's that saying again about Open Beta being a test branch?

This is the weather wishlist section. Unfortunately they won't move the Core Wishlist section to the DCS World Core Features subforum, so this Weather Wishlist is easily mistaken as a general wishlist subforum since it's the first that appears in the list.

Chizh has replied again and said that they'll consider my request/suggestion to make certain font elements have a bit more weight to them. I'm going to mark my previous identification of the issue, on page 3, as the answer to this thread as an answer has been provided that confirms it's an intentional change made by the dev team. Why the community managers couldn't put these questions forward, since that's ultimately the job of a community manager, and why I had to reach out directly are two things I'll never understand with bug reports on DCS. It really doesn't take that long at all to speak to a developer - I am a developer and often have these engagements with business analysts, product owners, 1st and 2nd line support, testers, the list goes on.

Спасибо большое

I'll check those out. Admittedly, I haven't played DCS since this change as I was in the middle of an A-10C campaign and the support received as well as the issue were both very disheartening. Fingers crossed that the developers are able to make some adjustments as a trade-off just to find some balance in between these two opposite ends of overexposed to hard readability.

Chizh has kindly provided an answer on why sRGB was enabled in 2.8. It was indeed an intentional change because the text was overexposed with sRGB disabled. This is true, the text has clearly been overexposed for years. I've asked, using shoddy Google Translate, if it's possible to increase the font thickness for the smaller bits of text just to make them a bit more readable.

Спасибо за объяснение. Можно ли увеличить толщину шрифта? Текст очень трудно читать в VR в 2.7 а в 2.8

Кто-нибудь?

Still waiting. I'm sure ED will have some accountability one day by making clear whether this is an intentional change or not. No time to investigate and fix this one line problem but plenty of time to introduce it.

This has happened time and time again with preorders on popular modules, releases of popular modules etc. They'll never take this feedback on board. Scaling costs money and there'll certainly be no appetite for spending more money, as little as it costs for droplets, on splitting the auth API out. Nonetheless, great to see Sinai released. In reading some thoughts in various Discords, it apparently has some great performance in VR while also looking great.

It's probably because they've never actually looked at spotting properly. Recently a mod was released that proved ED's argument to be wrong. Now, after a decade, they're potentially going to look at it.

Извините, я использую Google Translate. Бессмысленно спрашивать об этом на англоязычных форумах. Почему вы добавили SRGB в MFCD A-10CII в DCS 2.8?

Excellent, this is great news. Thank you

The IC is checksum based and uses the contents of the file as they are in the default, unchanged version. Any changes to the file will change the checksum, which in turn fails the integrity check. Obviously @BIGNEWYhas muted or is ignoring this thread. If any other community managers, staff or testers see this thread then please do reach out - as long as you are, no offense, a bit more open minded to the idea of there being an issue here and that it's not just a one sided investigation. I will be happy to work through reproducing the issue and demonstrating the knock-on impact of this change when playing VR.

In fairness, it wasn't in the DCS Updater thread until I mentioned it back in 2021. https://forum.dcs.world/topic/94816-guide-info-dcs-updater-usage-version-numbers-module-ids/?do=findComment&comment=4683068 Even then, it's mostly you & me that have mentioned the switch on these forums, and there's no --help command that would pop-up a UI to show the available commands.

@BIGNEWYstill no update...

Or, you know, just leave users decide how to bind their controls without yet another work around. The point isn't to remove the convenience of having them pre-assigned to the OSB keys of an MFCD. It's to remove the restriction that forces them to be locked so they can only be mapped to the MFCD OSB keys. It really doesn't have to be any more complicated than that. That's exactly how joysticks and throttles work. They are pre-mapped for your convenience, you can remap as you see fit.

Still there. null @BIGNEWY - yet again, is there any chance one of the following two things could happen? This be acknowledged as an intentional change and covered in a changelog This be acknowledged as a bug that's causing a degradation in visibility and readability of the MFCDs. Are either of those two really that difficult?

Thank you for confirming as I haven't actually tested this on MP since I mainly do SP. It's been 6 months now since this issue, introduced by a single line of code, was first raised. I'm hopeful we'll get an answer at some point within the next decade, though I won't hold my breath. @NineLine@BIGNEWY

@BIGNEWYIt has been a little over 2 months now since last said you'd mention it to the devs. Has it been mentioned? Have they given any indication as to why SRGB was enabled, on the MFCDs, in 2.8? Surely that's no more than a 2 minute conversation to ask and for them to say "It was added because of X".

What do you mean by this? What buttons are locked? This is typical and likely how it'll be for the next 7 years. It's not like ED to fix an issue that could be addressed in seconds. Even when the community provides evidence as to something being an issue that they introduced.

If you use OvGME, this should make it a bit easier to patch

What does this mean?

Still there in 2.8.3.37854.1, and so the cycle continues.