NightMan Posted October 28, 2022 Posted October 28, 2022 In version 2.8, like the title says, "HUD Modes Reticle/Night/Day" control cycles from NIGHT to DAY and to GRID but doesn't cycle back to NIGHT. It looks like several controls are affected by this problem. Major screw up. Either add a control to cycle back or restore previous behaviour. 1
GrEaSeLiTeNiN Posted November 6, 2022 Posted November 6, 2022 Does make one wonder what kind of quality control checks (if any) go into the updates. 1 AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
NightMan Posted November 6, 2022 Author Posted November 6, 2022 Indeed. But I think they launched it in a hurry only to show off with the Halloween easter eggs.
NightMan Posted December 7, 2022 Author Posted December 7, 2022 The problem is transversal to all models.
Flappie Posted December 8, 2022 Posted December 8, 2022 On 11/6/2022 at 6:00 AM, GrEaSeLiTeNiN said: Does make one wonder what kind of quality control checks (if any) go into the updates. You are part of the quality control team since you're playing the OB version. And that's a good thing, otherwise this kind of errors would have slipped to the Release version. Kudos to you. 1 ---
GrEaSeLiTeNiN Posted December 8, 2022 Posted December 8, 2022 (edited) 32 minutes ago, Flappie said: You are part of the quality control team since you're playing the OB version. And that's a good thing, otherwise this kind of errors would have slipped to the Release version. Kudos to you. These are simple switch logic that use to work fine then got broken after an update. Are they now low on the priority fix list? If so, that would be quite annoying because they weren't there before and now that they are there they might be put on the back burner. Will they be fixed in the next update? Edited December 8, 2022 by GrEaSeLiTeNiN 1 AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
NightMan Posted December 8, 2022 Author Posted December 8, 2022 (edited) 12 hours ago, Flappie said: You are part of the quality control team since you're playing the OB version. And that's a good thing, otherwise this kind of errors would have slipped to the Release version. Kudos to you. I have an idea; how about giving some credits, or extra miles as ED calls it, for each valid bug or problem a member reports? Edited December 8, 2022 by NightMan 1
Flappie Posted December 8, 2022 Posted December 8, 2022 4 hours ago, NightMan said: I have an idea; how about giving some credits, or extra miles as ED calls it, for each valid bug or problem a member reports? That's a good idea from my point of view (reminder: I'm not an ED employee). 16 hours ago, GrEaSeLiTeNiN said: Are they now low on the priority fix list? Did I say anything like it? This is being fixed, yes. Will the fix be in the next update? I hope so. ---
NightMan Posted December 17, 2022 Author Posted December 17, 2022 (edited) I have just tested version 2.8.1.34437, and this hasn't yet been corrected. Instead ED changed the existing control to cycle forward/up/next and added another control to cycle in the opposite way. This is a good enough solution, but not ideal: 1 - it requires dozes of controls to be remapped; 2 - either do it for all the cyclable controls or for none of them, and simply restore the previous behaviour --- standardization is always the best way. And, once again, there is nothing about it in the ChangeLog: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/ Edited December 17, 2022 by NightMan 1
NightMan Posted December 17, 2022 Author Posted December 17, 2022 There are too many incongruences. For example: There are: - "Gyro/Mag/Manual heading - down"; - "Gyro/Mag/Manual heading - up". Ok, that's bearable. But there are: - "UV-26 Change dispensing board - next"; - "UV-26 Change dispensing board - prev"; - "UV-26 Change dispensing board - LEFT"; - "UV-26 Change dispensing board - BOTH"; - "UV-26 Change dispensing board - RIGHT". Please; standardize things. Either: - ALWAYS use "next/prev" and "up/down", as in the Gyro/Mag new method; - ALWAYS use "next/prev" and "up/down" combined with all the other possible settings, as in the "UV-26 Change dispensing board..." method. Mixing methods becomes VERY confusing and difficult to setup. 1
GrEaSeLiTeNiN Posted December 20, 2022 Posted December 20, 2022 BS3 - Why couldn't they bring back the cycle/toggle functions for 3-way switches (eg. weapon burst length, AP Baro/Alt)? It was all good in BS2/DCS 2.7. Now we need additional buttons or remapping. Such a simple task that would have closed threads like this. 1 AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
NightMan Posted December 20, 2022 Author Posted December 20, 2022 9 hours ago, GrEaSeLiTeNiN said: BS3 - Why couldn't they bring back the cycle/toggle functions for 3-way switches (eg. weapon burst length, AP Baro/Alt)? It was all good in BS2/DCS 2.7. Now we need additional buttons or remapping. Such a simple task that would have closed threads like this. Precisely.
Flappie Posted December 20, 2022 Posted December 20, 2022 On 11/6/2022 at 11:57 AM, bingbean said: I would just like to warn everyone who is waiting for it to work as before after the repair, that it probably won't. Be prepared to need a second button to move the switch in the opposite direction. All 3 and more positions switches affected by this, is now controlled in cockpit by right and left mouse button. So it will by same even with hotkey like it is in Mi-24P. So one key for one direction, another one for move the switch back. ---
NightMan Posted December 29, 2022 Author Posted December 29, 2022 I've been thinking about this and creating a control for every single position of every single switch (multi-position) is going to be a HUGE mistake. First of all it will represent hundreds if not thousands of controls to map. Secondly, from the point of view of the software developer, the more controls the program has to poll the slower it gets. So, I strongly insist in returning to the original solution, which was toggling forward to the last position and back to the first, or, alternatively, toggling forward and backward. Toggling forward and backward only is the one that makes more sense. 1
Schlomo1933 Posted January 3, 2023 Posted January 3, 2023 (edited) Many of us are working with 2 , 3 or like me up to 8 position switches (like on the unguided weapon selector on the back wall) so for us , toggle switches make no sense. ( without the those switches like the 5 autopilot Chanel’s or the targeting buttons for moving ground targets) . Edited January 3, 2023 by Schlomo1933
GrEaSeLiTeNiN Posted January 4, 2023 Posted January 4, 2023 Players have diff setups and binding preferences. Point is, it was there before, it was good for those who found it useful, why take it away. Yes, the new switch options (eg. button off state) are great. But is it so much to ask to put back a simple thing like the cycle option (just those that were there before)? AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Schlomo1933 Posted January 5, 2023 Posted January 5, 2023 Am 4.1.2023 um 02:54 schrieb GrEaSeLiTeNiN: Players have diff setups and binding preferences. Point is, it was there before, it was good for those who found it useful, why take it away. Yes, the new switch options (eg. button off state) are great. But is it so much to ask to put back a simple thing like the cycle option (just those that were there before)? Am 29.12.2022 um 02:12 schrieb NightMan: Toggling forward and backward only is the one that makes more sense. My post is related to NightMans post, because this is just not true.
GrEaSeLiTeNiN Posted January 14, 2023 Posted January 14, 2023 (edited) On 12/9/2022 at 1:08 AM, Flappie said: This is being fixed, yes. Will the fix be in the next update? I hope so. Title says "fixed" but that is not true to the OP. The cycle switch functions that were there before have still not been put back. Is ED planning to have them permanently removed? Edited January 14, 2023 by GrEaSeLiTeNiN AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Recommended Posts