Ideal Flight Accessibility phase 2

[ke7zum]

I just grabbed the logs folder. I have no clue if this will even help, but there they are anyway.
https://ke7zum.keybase.pub/IF%20Log%200 ... 20.7z?dl=1

Thanks.

[ke7zum]

Ok, i was a corrupted profile folder, I renamed it and it is fixed, I do want to know how ever if there could be a fall back so this does not happen again? I can save the profile folder for you if you want to take a look and figure out what happened.

Take care all.

[Steve Waite]

Any saved flights won't work between 10 and 11, that should pop up a message.

Use of the throttle control in IF is for when the aircraft does not have it enabled. I mentioned it is only a rudimentary control right now so that there was something to activate and test out the hotkeys.

[Steve Waite]

I need Windows compressed files here please. Select or group select files and choose Send to Compressed (zipped) Folder. The logs probably won't show anything other than unable to load a file.

If a file was in use by another program then the error will appear that the file cannot be read.

The usual thing to do with any issues is that you should go into IF and load a default profile before updating.

Check that first. Could be anything in an aircraft file like the 2.0 error. Or any of a million system things. Wiping or reinstalling removes the clue until it pops up again since this would only default things.

[ke7zum]

It was a corrupt profile as if I recall I think I had this issue long before. I can convert the 7z file later using software if still needed. The file was not in use by any software. In fact the score board had ben corrupted. But now it works fine. I tested it last night.

[Steve Waite]

Do you mean the scoreboard did not look right before updating? In what way?
The profile zipped up might show me something or help me recreate the problem.

[Steve Waite]

...also did you go from preview 10 to 11? There's no changes in there with respect to loading the program between 10 and 11, only the saved flight won't load as there's more to a saved flight with the Assist module in place. Although it says can't load profile, that can be due to many types of problem. But if preview 10 loads up and preview 11 does not, that's more likely due to a new reading or assist feature, rather than the profile is 'corrupt', actual real file corruption is unlikely.

[Steve Waite]

...I'm thinking that from the report you installed pre 11 OK and can build a flight but cannot record a flight?

The message mentioned was most likely to have been:

"Cannot Configure Profile. Please try re-indexing from the start page popup menu: Maintain Indexes".

But you also mentioned the scoreboard and then at some point the app won't even open?

I have no clues to be honest what it is about. Is that the P3D version or the FSX version?

[Steve Waite]

What's actually happening is that I am putting in accessibility features on a daily basis that will most likely cause issues around the program. Errors and Omissions are expected and we are the Beta Testers, the program is untested with the new features.

Problems are expected to be fixed so there's no need to worry about them so long as they are reported in detail enough for me to understand them. Otherwise I can only hope to come across the problem in use myself or during programming, sometime in the future or that some other user finds the cause and reports it. Problems are usually fixed in a few moments. The hard part is knowing what the problem actually is.

Often I have to be able to recreate a problem. When a problem effects only one user it may be a particular feature in a plane or airport that is not handled properly by IF, remember the 2.0 issue was just a short term problem to do with finding the work arounds in place. Ordinarily IF reads all values as decimal so normally won't cause problems. The same thing comes up before now on a number of occasions.

Remember that IF has to assimilate every addon the same as the simulator does, but I don't have access to the code of the simulator. The program may yet be unaware of things found in aircraft and scenery. IF will always be behind the simulator In that respect. The planes and scenery come from older versions of the simulator and that incorporated work arounds built in over many years before IF was conceived.

Mostly IF will assimilate all aircraft and scenery that have been made and that are yet to be made. This is a tall order, but so far we find very few problems in addons. The 2.0 error was simply unfinished fleshing out of new features added the week before, it happens often that way. Including a feature may only be very small but may come with many caveats that we have to find out later. That's essential to software development.

So we can expect problems of any kind at any update. It's not possible to test out everything each time so we must use it to find out.

In order to track problems down I have to be able to recreate the problem or I might require some kind of elimination of possible variables from the beta tester. For example "does a default profile work OK". That would be best chosen to eliminate the addon aircraft and scenery so that it can be determined if the problem is associated with a particular addon. That would be a very simple procedure.

If it can be tracked to an addon, that would be easy to find if I know the addon. If it's an IF specific issue then I don't need an addon to find the problem. In either case I might need to recreate the problem to find out what it may be caused by.

Clearing and reinstalling wipes out any clues to a problem by setting all things back to defaults. What we need to know is what is different on that system that means the error arises on that system. If it's not an issue for everyone then why not? Could it be a particular setting is enabled? Could it be a particular plane loaded? could it be a particular airport installed?

[Steve Waite]

The index log records any problems during the index. The Flight Log records all other problems. When the program starts the log is recorded after a blank line in the file and checks things loading up. The log continues when choosing an airport or aircraft, problems are usually reported with a popup. Parts of logs can be copy/pasted in here, no need to send files or folders.

Sending entire profiles can be a problem when complicated they can only work on the system from which they came. Complex system profiles can be modified here to work, but that may be cutting out the error we are looking for, so we are back to square one.

Generally copy and paste in the few lines from the flight log leading up to the error. The log will repeat the error popup since events are recorded in the log. The reason for the problem may not be included in the log, but the popup event will be. It is not always clear what causes an unexpected errors and so they can only be logged as some error. Often that may result in a generalised error message, please try etc.