FSAirlines

OK folks, we all know there's an issue at the moment in terms of the flynet client suddenly announcing a crash in mid-flight for no very good reason.

Being naturally curious, I'd like to know why this is is happening so that we can:

a) help Konrad sort the problem after his holidays and
b) avoid doing it until the problem is sorted.

My current presumption is that there are several variables which might be contributing to the problem, but I need more data to work from.

Accordingly, I'd like to know the following for each inexplicable crash:

1. Equipment type
2. RW time of crash
3. Were you using RW weather at the time of the crash?
4. How long was the flight scheduled for?
5. Were you using time acceleration at the time of the crash?
6. Were you using FSX or FS9?

Please add your answers to this thread...

PS God knows it's tempting to blame Flynet for the hill you flew into on autopilot or a crappy landing... please don't!

Regards,

Mike,

I was flying the BAC 1-11 500. FL310, speed 290 knots, time of crash, I'm not too sure, but it was late morning, I used real weather - same as last times I did have this sort of cruise-crash. The flight was scheduled for 90 mins. I didn't use any time acceleration.

still using FS9

Cheerio

Jan

It might also be interesting to see if poeple were using FSX or FS9 at the time of these crashes, as i personally have never had one and i use FS9.

Added. Thanks Stan

sp762 wrote:1. Equipment type

FSX Stock CRJ700

2. RW time of crash

2130 EST - 0230 GMT (I think)

3. Were you using RW weather at the time of the crash?

yes, ASX

4. How long was the flight scheduled for?

Default in FLYNet

5. Were you using time acceleration at the time of the crash?

NO, had used 2X throughout flight buthad disengaged at least 5 minutes (or more) prior to crash

6. Were you using FSX or FS9?

FSX

Sorry to add, I'm done until problems can be addressed. Just too hard when you get whacked unfairly. Not going to waste my time trying to back to even when the possibility of getting hit out of the blue again is so likely.

Great idea though, hope everything gets worked out eventually.


EDIT: Apologies to the airline I leased the CRJ700 from. I forgot to repair/transfer before I disbanded my airline.

Konny and me discussed this problem and we might know the solution to it. After our big holiday I started reprogramming FlyNET from scratch, in order to make it more efficient and stable. Unfortunaley FlyNET is quite a complex C++ program and it might take 2 - 4 weeks until the new beta version will be available...

cheers DaKurt

Great to see that you are rewriting it entirely, often the best way to get rid of problems
While you're at it could you also check why the client crashes during (short) network hickups.
Last saturday I had a few internet connection problems during which I lost connection for only a few seconds, after such a hick up the client didn't respond at all (=crashed?) anymore and my flight (3 hours of it) was reset to booked al 3 times

yeh, it helps when you keep posting those kind of problems here. I'm quite far with the totally new client and will start to focus on such problems soon.

btw. sorry for the inconvenience...

You don't have to apoligize Konny, it's a good thing I like flying.
Maybe it's an idea to log all movements localy and upload them like every minute or so and if there's no connection just keep on logging and upload it when the connection is up again. It will make the client much more robust.

Keep up the great work!

jup, I'll try to work out something like that...and I'm DaKurt not Konny

Gents

I hate to be the bearer of bad news - but three of my pilots have experienced unexplained crsahes in the last 36 hours - all in cruise all toally without any kind of warning - just suddenly back at either the originating station or at an airport close to the point of the crash - I will also add that this exactly the same problem we had prior to the hiatus and the three people are spread across the world so its not a user problem - it seems there is something going on with the client again


Update

Konny - two of the guys have now done complete reinstalls of FS9 and basically have flown with no problems - so it now appears its NOT the Clients problem

Leif

Ok just crashed

1.PMDG 747
21600z
3.Yes
4.I think 2 days before was the flight added at our timetable
5.No
6.FS9

No salary,

Aircraft state after the flight,

Pilot Rating 50
Critique Aircraft crashed

Hull State % 99.19
Gear State % 98.41
Engine No 1 State % 99.83
Engine No 2 State % 99.83
Engine No 3 State % 99.83
Engine No 4 State % 99.83

Any help?

Operation, Aegean Airlines Virtual Express

And something i forgot, the aircraft is ready for flight

Just to give as much as possible detailed info for the crash.

At touchdown FlyNET crashed, PMDG 2d cockpit has switched from 2d in an an docked 2d window.

It was a successful landing at HKJK but what a mess for the client!!!

And something I have just discovered,

Type Reg Location Status State Fuel On Board

B744 SX-BE1 [LSD] HKJK Ready For Flight % 99.48 -2,147,483,648 Kg.

My Flight Rating (avg) has drop down from 99,8% to 98.2%.

Flight is normal recorded at Total Flights.

Regards

Just take a look at the aircraft info,

Manufacturer Boeing
Type 747-400
ICAO Code B744
Owner Aegean Airlines Virtual - Express
Leased by Ionathan Airlines
Deposit 0 v$
Returns Feb 10, 10:09
Registration SX-BE1
Location HKJK
Passenger capacity 416
Fuel on board -15032385536 kg
Normal/Econ Cruise Speed 490 kt
Range 7200 nm
Dry Operating Weight 178756 kg
Max Zero Fuel Weight 246074 kg
Max Take Off Weight 396893 kg
Cargo Space 34759 kg
Status 99.5%
Total hours 94.60
Total landings 24
Last maintained
Value 198.976.556 v$