Ideal Flight Accessibility phase 2

This Forum is for Ideal Flight Users to ask questions about general use. Perhaps you have a suggestion which you think maybe of benefit to Ideal Flight

Moderators: Steve Waite, SysAdmin

Re: Ideal Flight Accessibility phase 2

Postby Orinks » Mon Dec 23, 2019 8:39 pm

Some initial thoughts on speech: too much information on climb.

Here's what I mean.

When a value changed in the autopilot, the information was said twice. First the value number, followed by autopilot heading hold/speed hold/etc.

The speech kept interrupting itself. In order to best fix this problem, a check should be made as to whether the autopilot is on, and then simply just say the value. For example, just say 56 degrees, don't need to say the bit about autopilot heading hold 56 degrees.

Also goes for vertical speed and speed. Values were changing on climb I think that's the biggest issue, values were being said twice when things were constantly changing. My graphics card crashed again during cruise while typing this, which hasn't happened in a while. :(

HTH.
Orinks
 
Posts: 255
Joined: Sat Mar 02, 2019 11:50 pm

Re: Ideal Flight Accessibility phase 2

Postby ke7zum » Mon Dec 23, 2019 9:22 pm

I have the installer, will probably be playing with it after work. Have some IRL stuff to take care of this holiday. Sorry was not around at all to comment, was sick with a head cold, and ear infection. Let's hope my graphics card does not crash. I made some changes in p3d so let's hope that won't interfeer, mainly put all of my traffic to 0 as my computer would barf all over the place otherwise. Look forward to testing, heading back to fill ou ta report. Hope to have a fun challenging adventure, happy holidays.
ke7zum
 
Posts: 61
Joined: Fri Mar 08, 2019 6:28 am

Re: Ideal Flight Accessibility phase 2

Postby Steve Waite » Mon Dec 23, 2019 11:23 pm

In Ideal Flight use zero traffic in P3D or only add a few at a time. It is mainly for filling in a few around whatever time the flight gets. Don't use the more complex ones like the connie, any aircraft as AI can cause problems in P3D. The voice items can be selected from the main IF menu. All the best.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)
Steve Waite
 
Posts: 5092
Joined: Wed Jun 29, 2011 12:02 am

Re: Ideal Flight Accessibility phase 2

Postby jessiepp » Tue Dec 24, 2019 12:06 am

i have been doing a small flight and agree with josh, there is to much info being given at once. it is a chatter box when at climb and some info is being missed cause of this will do some more testing and will say.
jessiepp
 
Posts: 20
Joined: Sat Mar 09, 2019 4:30 pm

Re: Ideal Flight Accessibility phase 2

Postby Steve Waite » Tue Dec 24, 2019 12:45 am

On the settings form you can turn stuff off and back on when you need it.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)
Steve Waite
 
Posts: 5092
Joined: Wed Jun 29, 2011 12:02 am

Re: Ideal Flight Accessibility phase 2

Postby Steve Waite » Tue Dec 24, 2019 12:46 am

...orchestration and general mechanics will have to wait.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)
Steve Waite
 
Posts: 5092
Joined: Wed Jun 29, 2011 12:02 am

Re: Ideal Flight Accessibility phase 2

Postby Steve Waite » Tue Dec 24, 2019 12:48 am

and check out your AI traffic if you are getting crashes turn it off as they can do anything in P3D.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)
Steve Waite
 
Posts: 5092
Joined: Wed Jun 29, 2011 12:02 am

Re: Ideal Flight Accessibility phase 2

Postby Steve Waite » Tue Dec 24, 2019 12:56 am

Orinks wrote:Some initial thoughts on speech: too much information on climb.

Here's what I mean.

When a value changed in the autopilot, the information was said twice. First the value number, followed by autopilot heading hold/speed hold/etc.

The speech kept interrupting itself. In order to best fix this problem, a check should be made as to whether the autopilot is on, and then simply just say the value. For example, just say 56 degrees, don't need to say the bit about autopilot heading hold 56 degrees.

Also goes for vertical speed and speed. Values were changing on climb I think that's the biggest issue, values were being said twice when things were constantly changing. My graphics card crashed again during cruise while typing this, which hasn't happened in a while. :(

HTH.


A number is followed by the description. If you hit the same setting twice or more you hear the next number, but the description is interrupted by you pressing the number again or with varying speeds, altituded HSI or VS you will hear more numbers. The description is overspoke so that doesn't matter. The only way to do it is to interrupt what's being said, when you or it changes, else it queues up and doesn't make sense.

But at the moment we have the mechanism to talk about everything, that was the plan, and it's a good stab at it. Sorting it all out to speak in some desired way comes later, and will be problematic. It's more a case of do we want it spoken or not.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)
Steve Waite
 
Posts: 5092
Joined: Wed Jun 29, 2011 12:02 am

Re: Ideal Flight Accessibility phase 2

Postby Steve Waite » Tue Dec 24, 2019 1:16 am

Already in place in the program there is a mechanism to allow certain phrases to complete, or to allow more time before they are overspoke. That is set to nominal values and has no setting available yet. Also the short descriptions will be available. Another thing under the hood is prioritisation, for when more than one thing changes at once, which is said first. What I'm looking into is how to orchestrate that with the most meaningful items given priority. They are set nominally right now so that the passing of waypoints is top, but can still be overspoke by something else in a couple of seconds. So we have to think how what we have now can be tuned to our liking.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)
Steve Waite
 
Posts: 5092
Joined: Wed Jun 29, 2011 12:02 am

Re: Ideal Flight Accessibility phase 2

Postby Steve Waite » Tue Dec 24, 2019 1:25 am

Regarding crashes in P3D...I must have made more than 50 landings, many many hours and flights a plenty - no crashes. If your sim does not close properly IF may connect then disconnect. If you get any funny behaviour or crashes be sure the sim is started up and closed clean before using with IF. Turn off AI traffic and anything new. There's a lot of stuff that can cause your problems, none by IF. When we load things into P3D there are many problems can surface, especially with older stuff from FSX days. So always go to a stock setup and work forward - start with lowest settings and nudge up gradually.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)
Steve Waite
 
Posts: 5092
Joined: Wed Jun 29, 2011 12:02 am

PreviousNext

Return to General Use & Ideas

Who is online

Users browsing this forum: No registered users and 10 guests