another flyNET client Problem
Moderator: FSAirlines Staff
another flyNET client Problem
twice this has happened now, I started a flight from BRS to VAL, and after about 1 hour 15 minutes in flight a screen pops up saying that the flyNET client has encountered a problem and needs to close, so that twice i have started that flight and not completed it.
I've had crashing problems myself.
Once on landing approach and another during mid-flight. I also have another pilot in my group having the same FlyNET crashing problem.
www.virtualcia.org
Once on landing approach and another during mid-flight. I also have another pilot in my group having the same FlyNET crashing problem.
www.virtualcia.org
After many (and I mean MANY) problems with the client crashing I found the cause - at least for most of the crashes.
In fact, until it just happened on my last flight I thought i'd cured it.
I have been running FS9 on 1 pc and the Flynet client on a 2nd PC - the two communicating via WideFS.
I found that if the FS9-PC was interrupted the client would reboot the client-PC at the next stage of flight, ie from cruise to descent, descent to touch-down, etc.
My definition of interruption includes anything from using a menu to change a graphic option or starting FSNavigator for the 1st time. The FS9-pc would continue as normal but the client-pc would reboot meaning i'd have to start again.
I got around this by starting FSNavigator before starting the client (opening FS Nav a 2nd or 3rd time doesn't cause a pause, just the 1st time) and of course, not touching the FS menus once started!
Anyway - I dont want to be negative about it because it is a beta version after all and it's a great little program and it is getting better with each release.
I haven't said this yet on this forum so:
Thanks very much to all involved with developing it and long may it continue
In fact, until it just happened on my last flight I thought i'd cured it.
I have been running FS9 on 1 pc and the Flynet client on a 2nd PC - the two communicating via WideFS.
I found that if the FS9-PC was interrupted the client would reboot the client-PC at the next stage of flight, ie from cruise to descent, descent to touch-down, etc.
My definition of interruption includes anything from using a menu to change a graphic option or starting FSNavigator for the 1st time. The FS9-pc would continue as normal but the client-pc would reboot meaning i'd have to start again.
I got around this by starting FSNavigator before starting the client (opening FS Nav a 2nd or 3rd time doesn't cause a pause, just the 1st time) and of course, not touching the FS menus once started!
Anyway - I dont want to be negative about it because it is a beta version after all and it's a great little program and it is getting better with each release.
I haven't said this yet on this forum so:
Thanks very much to all involved with developing it and long may it continue
Hi Pete,
I get the impression its not just Konny who can help you so if put out a help message to anyone and everyone you may get more response.
I dont know Konny but he probably has a job to do, maybe a family to look after, do the shopping etc and this is done in his spare time, so really we all need to be a little more patient when waiting for a reply, no matter how frustrating it can be.
Anyway if I can help:
are you the ceo? if not ask him the following, or if you are the ceo - try the following:
try creating another account with the same va and log in with that - at least you can then fly. If that works ask 'someone' to transfer your money/hours/logbook to the new account (delete the old one afterwards).
if you cant logon maybe your password is wrong/corrupted.
suck eggs time:
make sure your va has a plane and a route.
make sure your type rated to fly the plane.
book the flightplan and plane
make sure your at the same airport as the plane
get flightsim up and running, setup how you like it
finally - start the client.
hope that helps in some way
I get the impression its not just Konny who can help you so if put out a help message to anyone and everyone you may get more response.
I dont know Konny but he probably has a job to do, maybe a family to look after, do the shopping etc and this is done in his spare time, so really we all need to be a little more patient when waiting for a reply, no matter how frustrating it can be.
Anyway if I can help:
are you the ceo? if not ask him the following, or if you are the ceo - try the following:
try creating another account with the same va and log in with that - at least you can then fly. If that works ask 'someone' to transfer your money/hours/logbook to the new account (delete the old one afterwards).
if you cant logon maybe your password is wrong/corrupted.
suck eggs time:
make sure your va has a plane and a route.
make sure your type rated to fly the plane.
book the flightplan and plane
make sure your at the same airport as the plane
get flightsim up and running, setup how you like it
finally - start the client.
hope that helps in some way
-
- FSAirlines Developer
- Posts: 1564
- Joined: Sun Sep 25, 2005 10:40 am
- Location: Munich, Germany
- Contact:
Sorry guys, for the delay. I just didn't have the time to care about FlyNET the last two days. I know that this can be very anoying for you, expecially immediately after a release, when new bugs appear.
Well, apart from pete999 everyone's client here just crashes after some period of time and you get a windows error message. Guess you didn't have the problem with the old 0.4.0b, so could you please send me your log.out files after a crash and tell me if you use any other FS software during flight.
Well, apart from pete999 everyone's client here just crashes after some period of time and you get a windows error message. Guess you didn't have the problem with the old 0.4.0b, so could you please send me your log.out files after a crash and tell me if you use any other FS software during flight.
Konrad - FSAirlines Developer