Ideal Flight Accessibility phase 2

[Orinks]

Getting a floating point value error when attempting to go to the flight assistance page.

' is not a valid floating point value with an OK button.

Wonder if this has something to do with tAccessible only and non-screen reader users don't get it. This was with NVDA, will try Narrator next.

[Steve Waite]

OK thanks. Yes I expect that's it, bit of a shame. Unfortunately impossible to test everything before uploading.

[Steve Waite]

I can't test it at the moment so it will have to wait for my testing. So I expect in this case probably you wont be able to operate the Assist window with any screen reader present. It may be down to a certain feature present, not sure at this stage so try a few items.

[Steve Waite]

Getting a floating point value error when attempting to go to the flight assistance page.

' is not a valid floating point value with an OK button.

Wonder if this has something to do with tAccessible only and non-screen reader users don't get it. This was with NVDA, will try Narrator next.

Just testing at the moment but I couldn't get the error. Do you get the error when selecting Assistance from the popup menu, or is it when you get into the window controls?

[Steve Waite]

Not been able to find it so far...just in case there might be something to do with the airports in the plan, to do with runways or parking listed in the Assist maybe. If you can note the departure and destination airports for me and try other airports that might throw some light on the error as well.

[Orinks]

As soon as possible, you really need to add descriptions to the voice selections page so that we know what the differences are between, say, autopilot functions and navigation functions.

I had to turn off the flaps detail and flaps degrees; I wish it would say just flaps 5, flaps 10, etc. Pressing F7 to hear flaps 10 degrees, flaps 15 degrees, flaps... etc, can get kind of spammy.

TFM just says flaps 5, 10, etc.

Biggest thing is those descriptions, though, tried to help a friend set his voice phases and just had trouble.

As for attempting to help with the voice selection auto-switch, could it switch to cruise when we get to the IF cruise? For approach, I think 10000 or 8000 is a good altitude to switch to that. Perhaps we can put those altitudes for approach etc into the aircraft parameters.
Just some suggestions.

Despite my flight assistance page issue, great build thus far. I think only I am effected as I had a friend tested out and his assistance page is working just fine. Ugh.

[Orinks]

Okay, so making progress with this error.

It appears to be at least two of my planes. I have switched to the Mooney and no issue. I have switched to two of my Boeing planes and get the error.

I have also tried various departures, etc. I'm not sure what could be wrong with these planes. I haven't changed anything.

[Orinks]

Okay, I have finally tracked down this exception error and hope that it is reproducible on your end.

It's actually not departure specific, plane specific, or any of that. It's parking location specific.

I noted the location at KPHL where I got the error. Gate A 4.

I then moved to another medium gate using the flight generator and regenerated the flight at Gate B 21.

Shocking, it actually works at Gate B 21 with no error. I then use the working flight assist page to move back to Gate A 4, and I get the error once again.

I get the error at Gate A 4 even with the Mooney, which is how I know this is part of the problem is at that location. Similarly at KLAX, Gate A 12 produces similar results. This is default scenery with FSAerodata.

HTH.

[Orinks]

Well, just tried going to Gate A 4 on another PC that I have IF on and I don't get that issue there. Ugh.

Running out of ideas to try now since I found a reproducible problem consistent on my primary PC. FSAerodata is installed on that one as well.

[Steve Waite]

OK thanks for the info.