a few things...

[flightsimer]

two things,

can the old sounds be put back? the sound for takeoff and touchdown are loud. liked the other ones better. first time i heard them i thought something was wrong...

and also what is the point of the client logging you out then you have to log back in to fly, but before that you have to delete the info from last flight? shouldnt that info be shown right after the flight like the current client? also why do we have to log back in, i might as well be shuting down the client and reopening it like currently. wasnt it suppose to be that you wouldnt have to do that?

[DaKurt]

Hi flightsimer,

is it possible that you are running the client without administrator rights? Right now the client writes some config files to the Windows directory and if you are not logged in as an administrator this action could be prohibited by the OS. I'm working on a fix for this right now.

Would be cool if you could run the app in administrator mode and report if the problem still exist.

P.S.: Actually I thought that we are using the old sounds?!

[flightsimer]

im am the admin for the comp.

and the for the sounds, the sound being used to indicate taking off and landing is the sound that is made when the flight is ended on the old client (the DING dong). on the old client the beep use to be a low sound that sounded like its coming from the actual computer itself not the client (more like a synthesizer or retro sounding).

[alasizon]

I have the same issue Claudio and I have ran the client under both my personal account and the default Admin acount

[DaKurt]

could you please go into your windows folder and look if there is an FSAirlines.ini file? You could also post the content. BUT: Don't forget to DELETE THE PASSWORD before posting it in here

[alasizon]

Only FSAirlines file in my windows directory that has anything in it contains this:

[login]
User=Alasizon
Password=**********
[settings]
AutoLogin=0
Tracker=1
FSMessages=1
SimpleFuel=1
[report]
Backup=0
Code=0

[DaKurt]

Well strange I would have expected that the client wasn't able to write this file. Anyway I think that this problem somehow comes from the client not being able to read it and if it is really so I'm close to a solution. I'll release a new version tonight or tomorrow which will fix 4-5 bugs and then we will see if we have to investigate further into this or not

[Tomb]

think thats my problem, it does not write that file (winXP)

[alasizon]

Claudio,

I believe the reason why this may be an issue is it doesn't right as an .ini file.

[DaKurt]

hmm I just checked the new client on another Vista PC with limited rights and it worked, as it now creates the .ini files in the working directory (and not anymore in the windows directory). Could you please give me a feedback who still has problems with this?

Furthermore I tried to edit a .ini file in the windows directory using a user with limited rights and it did NOT work. So it actually this has to be the problem and it should now be fixed.

[alasizon]

Claudio,

While I am about to start a flight with the new client, the first thing I noticed was that this section of the code was missing from the new config settings.

[report]
Backup=0
Code=0

[DaKurt]

don't worry, this part will be written to the file when it's needed. This is normal. Today at about 3-4 o'click I uploaded a the client again (with only a small change but still with the same version BETA 0.1). I hope you use this version and not the BETA 0.1 from yesterday night.

[alasizon]

Yes I am using that version and also Claudio, I noticed that FSAirlines_report is also missing, is that normal since it contained all the data of the penalties.

[DaKurt]

that's also normal. It is only created when a report has to be backed up.

I just had a flight and experienced the same problem with the logging in and deleting the backed up report. I'm trying to fix it right now...

[Tomb]

ok my problem has been solved

for some reason while i could log in and book a flight but the new client would not log in

solution

go to profile

change password

voila

it now works

changes password back to what it was originally and it still works

no idea why the password had to be changed to make the client work

suggest putting up an error code "wrong password/username" otherwise you could be sat thier for ages wondering why the client is not working.

it was tried on two PC machines so not likely to be a machine specific error.

hope that helps

cheers John for the help in nailing this down