I have reported various aircraft specific voice command issues that needed to be tweaked. I know that most, if not all have been addressed in several recent version updates. The only way I know this is by testing each new version to see if the changes have been made. Some changes when made require me to make changes to my voice flow files. This is a time consuming process that I wouldn't have to do if I knew what changes where made version to version. Is there a way for me to find out what changes have been made so I don't have to re-test every new version to find out?

Thanks

7 hours ago, HarryS said:

I have reported various aircraft specific voice command issues that needed to be tweaked. I know that most, if not all have been addressed in several recent version updates. The only way I know this is by testing each new version to see if the changes have been made. Some changes when made require me to make changes to my voice flow files. This is a time consuming process that I wouldn't have to do if I knew what changes where made version to version. Is there a way for me to find out what changes have been made so I don't have to re-test every new version to find out?

Thanks

You'll be pleased to hear that most of them are already sorted.

Except those for TFDi 717 which will be addressed this week.

Either re-download and install latest V2.8.2.0 or save yourself an update by downloading this patch

Unzip and manually override files as per their respective locations.

In general, when it comes to updates, here is how we proceed...

When a user reports some imperfection on the forum or via e-mail, he/she would be the first to know about the change log.

Others are only notified when there is a major change or added support for another aircraft.

Keep in mind, more than 40 complex aircraft are supported in this single (eat as much as you like 😄) package.

There will always be the odd switch handling malfunction on one of the supported aircraft.

And contrary to common belief, our interfacing of those aircraft is much deeper than supposedly separate packages for specific aircraft.

We'd rather spend our time working, than plotting on how to milk users and get them to re-buy the reboot of the reboot of the second coming of the crew for PMDG 737 (because it was renamed U) if you see what I mean 😛.

Edited December 9, 20196 yr by FS++

I appreciate your response, but I'm not sure I got my point across very well. Let me try again.

Like most users of the app I'm really only interested in the functions related to the planes I fly.

PMDG 737/747/777
QW 787
Aerosoft Airbus 318/319/320/321 Professional
TFDi 717

Anytime I or another user of these aircraft report what might be an imperfection as you call it, how do I/we know it's been addressed and that an update is available? In some cases I may need to make changes to one or more voice flow files to include the changes you've made.

From what I can see so far you've already covered 99% of what's wanted/needed for the aircraft I fly, and I appreciate that the coding isn't as simple as 1-2-3. I'm not questioning what you do or how you do it.

I too have more customers than I can count, and when we make product changes they need to know what they are. In some cases letting them know is more time consuming for us than the time it took to make the actual changes.

The only time you'll hear from me is if a certain function doesn't seem to work, like a switch, or I might suggest the addition of a new function.

4 hours ago, HarryS said:

I appreciate your response, but I'm not sure I got my point across very well. Let me try again.

Like most users of the app I'm really only interested in the functions related to the planes I fly.

PMDG 737/747/777
QW 787
Aerosoft Airbus 318/319/320/321 Professional
TFDi 717

Anytime I or another user of these aircraft report what might be an imperfection as you call it, how do I/we know it's been addressed and that an update is available? In some cases I may need to make changes to one or more voice flow files to include the changes you've made.

From what I can see so far you've already covered 99% of what's wanted/needed for the aircraft I fly, and I appreciate that the coding isn't as simple as 1-2-3. I'm not questioning what you do or how you do it.

I too have more customers than I can count, and when we make product changes they need to know what they are. In some cases letting them know is more time consuming for us than the time it took to make the actual changes.

The only time you'll hear from me is if a certain function doesn't seem to work, like a switch, or I might suggest the addition of a new function.

It's very small operation here with only 2 people.

That's why it's agile and quick for trivial items (when you already know how to make it happen) like making a switch move the other side.

What I meant is that whoever is first to report something will know it's fixed when replied to either on this forum or via e-mail.

Package on website already includes the fix, as we have to keep the Demo in tip top condition. I pointed you to the patch just to save you un-installing and re-installing new package.

To all users, if you have an issue with any of the fully supported aircraft, start by updating to latest MCE here:

If you still have the issue, then report it.

And of course, suggestions regarding Co-pilot behavior always welcome,. even though you can't always get consensus on that 😋.

Quote

It's a very small operation here with only 2 people.

Wow !

I knew you were a small company but just Ben and yourself...

That makes your wonderful product and support even more impressive.

No wonder you have to burn the candle at both ends, as Ben was recently helping me with my Win 7 to Win 10 upgrade until well after midnight.

Many thanks for your excellent addition to Flight Sim and do try to take a break over Christmas!

4 hours ago, Tight Git said:

Wow !

I knew you were a small company but just Ben and yourself...

That makes your wonderful product and support even more impressive.

No wonder you have to burn the candle at both ends, as Ben was recently helping me with my Win 7 to Win 10 upgrade until well after midnight.

Many thanks for your excellent addition to Flight Sim and do try to take a break over Christmas!

Your're welcome, and thanks for your support.