Beta Client Released 2.6.0.*

[joefremont]

Hi Flyers.

I have just released a new beta client, version 2.6.0.2 this makes two changes.

* The folder where the client will store its files changes from Documents\FSAirlines to AppData\Roaming\FSAirlines. This is to fix a problem with M$ OneDrive where it was continually uploading the logs to the network. It will have the side effect of having the client forget your username/password but you can copy the files (at least the fsairlines.ini file) from one folder to other so the client remembers your past settings.

* Fixed a small bug where if you crashed over water it recorded a crash and a water landing, reducing flight rating to 0%. It should record one of those but not both.

Normally this would be the start of the path to v2.6.1 but none of the changes are significant enough to force everyone to upgrade.

There is no v2.6.0.1, it actually was a test build with some extra debugging, but the problem was not client related, so those changes were rolled back.

2.6.0.3 I fixed a bug where the client was not recording the arrival airport for technical stops.

2.6.0.4 Support for FS2024.

[joefremont]

I just released beta 2.6.0.3, described above.

Right now I am expecting the next official version (2.6.1) will be when we update the client for FS2024 in about a month.

[joefremont]

Brief note of some goals for 2.6.1 that are not yet in the beta (this is more a note to self than anything else)
- Support MSFS 2024
- If flight is aborted after landing, record the flight.
X Record in black box data that aircraft has crossed 500 ALG
- Remove option on if tracking data is transmitted to server, it should always record.
- If an aircraft that is not marked as float plane in the database tries to start in water, don't let it.

[Alan McGaughey]

Hi Joe,

Did you get chance yet to look at MSFS2024? Just wondering if it's going to be a problem connecting the client.

[joefremont]

Hi Joe,

Did you get chance yet to look at MSFS2024? Just wondering if it's going to be a problem connecting the client.

I have looked at it but I’m traveling this week and when I left the new version of FSUIPC was not out yet. I tried the current beta with it and it worked with sim connect but did not recognize the sim version, I am working on an update that I hope to get out by end of next weekend

[Alan McGaughey]

Great news, cheers Joe

[TSR2]

Hi All,

I know Joe hasn't done his testing yet, but today I flew for 3 hours + real time in FS2024 with the current client and everything I used worked as expected. Not suggesting you try it until Joe gives us the all clear if it's an important flight, but so far so good.

[joefremont]

I had done some testing with FS2024, finally got the new FSUIPC installed the other day and got by dev build working with it, tonight I made a release build of the next beta client (2.6.0.4) but need to test before I can release it but my copy of FS2024 wont load. Twice it started to load and got up to "68% Loading World Data" and the third time "63% Loading World Data". After about 30 minutes I would kill it and start again, but after three strikes I am done, try again another day.

[joefremont]

I just uploaded 2.6.0.4 which supports FS2024 and adds an entry to the black box data when your aircraft crosses 500ft ALG.

[Alan McGaughey]

Just done a quick flight, seems to work fine, thanks Joe

[280782]

I reviewed that the FSA client doesn't detect SimConnect in FS2020 if you open the client before the simulator load (main menu) is complete.

This results in confusion for new pilots, who in confusion finally end installing FSUIPC thinking it is necessary.

Is there any possibility to correct this?

Thanks.

[joefremont]

I reviewed that the FSA client doesn't detect SimConnect in FS2020 if you open the client before the simulator load (main menu) is complete.

This results in confusion for new pilots, who in confusion finally end installing FSUIPC thinking it is necessary.

Is there any possibility to correct this?

Thanks.

I just tried this, logging in before I started the sim, sure enough until the menu showed up it showed the sim not started message. Once the menu was loaded it showed 'wrong airport'. How do you expect me to correct this? Only thing I can think of is add a message saying that you should wait until the flight is loaded in the sim before trying to connect.

[280782]

I mean, if you open the simulator first, and then FSA, even if you load the aircraft and airport, FSA doesn't work until you close the FSA client and open it again.

Attached evidence.

[joefremont]

I mean, if you open the simulator first, and then FSA, even if you load the aircraft and airport, FSA doesn't work until you close the FSA client and open it again.

Attached evidence.

No that is not true. I just tried it myself. I restarted my computer, started the FSA client and signed in. Loaded FS2020, got to the main menu, started a flight. I then pushed the fly button and it worked perfectly.

Now I do have FSUIPC installed but I set the client to use SimConnect only. What concerns me more is that you have two copies of the client running at the same time, that is not supposed to happen. The client tries to detect if another copy is running and should stop you if it finds one.

[280782]

Maybe it is a problem with my computer. The second copy of FSA is a capture, not a second process.

I can make a video recording if it helps. I run the client without administrator permissions.