Switch logic a bit....illogical. Or at least inconsistent

[Nealius]

I recall someone mentioning that they wanted the switch logic to be more logical before the recent updates, but with the current updates the switch logic is very inconsistent. Some switches move up on right click, some move down on right click. Some knobs turn CW on right click, some turn CCW on right click. Some drums increase numbers with right click, some decrease numbers with right click (i.e. radio, autopilot altitude, bomb ripple).

 

Instead of having to memorize how right/left click affects each switch or drum, why not have a universal outcome? Right click always being CCW/down/decrease, for example.

[NeilWillis]

Yes, we would definitely like standardised switch throws, and as it has already been pointed out on other threads, RAZBAM will no doubt already be aware of it.

 

You cannot however expect all the bugs to be cured overnight, so a little fortitude is the order of the day here I think.

 

I am quite sure that they want this module to be a superlative, so our observations are very unlikely to just be ignored if that is what you're thinking.

[Wizard1393]

+1 RAZBAM please go over switches and make them left/right up/down click consistent.

[Nealius]

I apologize if I gave the impression that I was being impatient. I didn't realize this had already been made aware to the team, as I did not see it listed in the update fix list. I just recall the majority of switch throws being more consistent before the recent 1.5 update.

[NeilWillis]

Updates appear in the list AFTER they have been addressed. With any bug report, it is wise to do a search first, because I can almost guarantee someone else has noticed it sooner.

 

In all the time I have been flying Beta modules, I have noticed loads of issues, but never been the first to post them. I'll get there first some day!

[Wizard1393]

Updates appear in the list AFTER they have been addressed.

 

 

Is that AFTER they're "internally addressed" or addressed as in AFTER actual update released?

[NeilWillis]

Is that really relevant? Or are you just being ironic? All that really matters is that just because an issue hasn't been added to the updates fixed list, doesn't mean it isn't on their list of things to fix.

 

After RAZBAM have dealt with it. The release of updates is not something they can control. They list the fixed problems, and ED add them into the next available updates.

 

So, for the ones struggling with how bug fixing works, first, it is reported. Next, the developer investigate, and if required, provide a fix - which will involve finding the resolution and testing. Next they announce it is fixed. Next, the update is passed to ED, and finally, it is released with a scheduled update.

 

Simple really, and clearly explained in the very list referred to:

 

These are the candidate changes we have in our dev build right now that we have corrected and are testing internally:

 

Edited January 29, 2016 by NeilWillis

[Zeus67]

We are reviewing the issue.

We erroneously applied FSX standards to DCS, so we have to check ALL the switches but sometimes a few will slip through the cracks.

[Nealius]

Updates appear in the list AFTER they have been addressed. With any bug report, it is wise to do a search first, because I can almost guarantee someone else has noticed it sooner.

 

In all the time I have been flying Beta modules, I have noticed loads of issues, but never been the first to post them. I'll get there first some day!

 

Searched. Only found one thread for 2.0 NTTR which had no indication that it was actually brought to the devs attention.

[StormBat]

Is that really relevant? Or are you just being ironic? All that really matters is that just because an issue hasn't been added to the updates fixed list, doesn't mean it isn't on their list of things to fix.

 

After RAZBAM have dealt with it. The release of updates is not something they can control. They list the fixed problems, and ED add them into the next available updates.

 

So, for the ones struggling with how bug fixing works, first, it is reported. Next, the developer investigate, and if required, provide a fix - which will involve finding the resolution and testing. Next they announce it is fixed. Next, the update is passed to ED, and finally, it is released with a scheduled update.

 

Simple really, and clearly explained in the very list referred to:

 

So you say but that doesn't make it the truth now does it.(not a question)

for instance JTAC and Buddy Lasing is suppose to work for the M-2000C but it broke something else in the process and most people can't get it to work or get a CTD(for JTAC at least). So even if it's reported, the devs investigate and provide a fix, resolution, testing, whatever you said, saying it's fixed obviously isn't always the case is it brother.

 

So just in case your struggling with it buddy, don't get all high and mighty because people don't want to go through text after text after text to find out if someone else reported it okay, do you have time for that? if so don't expect we all do or know the best way to get that info if it exists at all. Now I know this is beta and the bugs are being squashed and systems implemented(Much appreciated BTW!)but if you can't be diplomatic or personable about it then don't say a bloody word, because it gets lost on us real fast your words and your way of handling it. Look I may be being a little hard on you but just don't get impatient with people because they ask questions or the same questions, or just have concerns. Or get someone else to deal with the public that can be a people person to their customers. Cheers.

Edited January 30, 2016 by StormBat

[CHRISXTR3M3]

Updates appear in the list AFTER they have been addressed. With any bug report, it is wise to do a search first, because I can almost guarantee someone else has noticed it sooner.

 

In all the time I have been flying Beta modules, I have noticed loads of issues, but never been the first to post them. I'll get there first some day!

 

Sometimes even if you search it and are the first to post it your bug report goes unnoticed. So stop giving grief. As long as it finally becomes acknowledged by Devs that is all that matters.

 

http://forums.eagle.ru/showthread.php?t=158985

Edited January 31, 2016 by CHRISXTR3M3

[Fab]

So you say but that doesn't make it the truth now does it.(not a question)

for instance JTAC and Buddy Lasing is suppose to work for the M-2000C but it broke something else in the process and most people can't get it to work or get a CTD(for JTAC at least). So even if it's reported, the devs investigate and provide a fix, resolution, testing, whatever you said, saying it's fixed obviously isn't always the case is it brother.

 

So just in case your struggling with it buddy, don't get all high and mighty because people don't want to go through text after text after text to find out if someone else reported it okay, do you have time for that? if so don't expect we all do or know the best way to get that info if it exists at all. Now I know this is beta and the bugs are being squashed and systems implemented(Much appreciated BTW!)but if you can't be diplomatic or personable about it then don't say a bloody word, because it gets lost on us real fast your words and your way of handling it. Look I may be being a little hard on you but just don't get impatient with people because they ask questions or the same questions, or just have concerns. Or get someone else to deal with the public that can be a people person to their customers. Cheers.

 

+1

[Zeus67]

I am ignoring this thread from now on. It seems that you are more interested in your little quarrels than in listening to what I have to say regarding the issue at hand.

 

Best regards

[Nealius]

Thanks for derailing my thread, guys.

[Zeus67]

Thanks for derailing my thread, guys.

The issue is being reviewed. I hope it will be ready for the next update.

[Nealius]

Thanks. Didn't know there was a connection to the FSX Mirage and just recently learned you guys make FSX add-ons as well.

[StormBat]

I would like to apologize to Zeus67 and anyone else if I seemed over aggressive with my message. If you have read my first posts on this I love and support all you folks working on the Mirage-2000C hands down. My only thing was making sure you don't A: get impatient with customers and their same questions ( yes it can be frustrating, but don't expect that we are all going to go or even know where to go for that info.) and B: Yes it's beta, but some people are very ignorant of beta-alpha and all that jazz and when they purchase your product they expect all that and a bag of chips to load, work or look like it's Michelangelo or something. So sorry if I helped derail this thread, Love your work thus far Razbam (no not sucking up ) and am patient till the work is completed. Again sorry if I contributed to any negative posts, just do not want to see confused but good people get discouraged for asking the same questions or being somewhat computer illiterate but love aviation and want to get into combat or even normal flight sims. Again sorry. My name never came up nor was I pressured into this message, but I was a little aggressive trying to look out for the little guy. Other then that Love Peace and much Respect for all your hard work! Cheers.