FSAirlines Beta Bugs

[TSR2]

Hi Dave, runway is definately not important, but altitude might be, and funnily, I can find anyone using FSX having the problem. :think:

[DaveB]

Hello Mate..

No, I can confirm runway is not important having just taken off from the taxiway at Liverpool and landed near the trees at Barton There are so many versions of Windows knocking around these days, I'm surprised anything works to be honest. We have WinXP SP2, SP3, Professional, Vista Home, Home Premium, 32bit/64bit, Ultimate.. add in FS9 and FSX SP2 FSX/ACC :roll: Good old Win3.1 I say

ATB

DaveB :tab:

[simondix]

OS Vista Home Premium 32bit, OS Vista SP1, Sim Version FS9, Client Version Version 1 on 1st and 1.02 on second., Airports See below, Aircraft See below, Addon scenery Silver Wings, weather Real weather by Active Sky,Comments. Hard to pin down which Airfield as the client does not sound when penalty incurred. Only find out when end flight pressed which is too late.

Flight 1. EGCC-EGBB in Viking. Also Got No Parking Brakes on that one. 90%
Flight 2. EGLL-LFMN in Lanc.

Interesting enough on the return trip in Lanc Started client at end of runway. Took off straight away. Showed aircraft taxying on the run followed by flight. I did not incur a penalty.

Hope this is useful.

[DaveB]

Hi Simon..

I start the majority of my flights on the runway.. especially if I'm on limited time (make that most of the time) and need to get going sharpish and this is exactly what I see. Start the takeoff roll and up comes taxy I still think the old system was better.. a beep above 5kts.. you knew exactly where you were ;-)

ATB

DaveB :tab:

[TSR2]

Hi Simon,

Something odd here and I can't pinpoint it. I'm deffinately getting the bing bong when either the flight state changes or I incur a penalty. Also is there any chnace you could try a flight with real weather switched off? (preferably a flight were you've had the problem before) I'm trying to ascertain if by doing a particular flight you always get the error or if it something Random. :think:

When you run the client I'm assuming your right clicking on it and selecting "Run as administrator"?

[simondix]

I get the bing bong when I taxi,take off and end flight. Not when it changes from climb-cruise-descent and vice versa. Start with 'Run as Administrator' as will not run otherwise. Have to wait to run a flight again as already booked so will be about 3 flights time by the time I get to a suitable flight. Thanks for the help.

Dave,
Tested the gauge against the GPS on the Vanguard. Works fine. It goes on after I have hit 20 on the GPS so that may point to the fact that the GPS is not totally accurate for Ground speeds.

Thanks again.

[DaveB]

You're welcome ;-)

BTW Guy's..
Claudio has found a bug in the client with the 'Comment's' field which he'll have fixed on the next release. In the meantime.. DO NOT put comments in the comments field.. skip that page ;-)

ATB

DaveB :tab:

[simondix]

Ben and Dave,

Did the Viking flight EGCC-EGBB-EGCC. No problems at all. In fact had no problems all day. Perhaps it was the C/Windows fix that did the trick.

Speed gauge warning flashes on when GPS states 20 but only after it has been on 20 for a few seconds. GPS cannot be relied on. So could be on 24 when actually over 25. If it behaves as a real world one does that could be feasible.

As to Bing bongs. None on the outward leg at all. On return leg it did on taxi and takeff and landing, but not on cruise,climb etc.

Hope that is useful. What I had forgotten to say is I use Radar Contact for ATC.

[TSR2]

Great stuff Simon. Fingers crossed thats you sorted now, and it does sound like the GPS speed is iffy.

Good luck!

[RAF_Quantum]

Hi Guys,

Talking with Joe tonight about engine wear. When the client gets fixed it is time based so all engines will wear equally. This means that attrition for a four engine will be higher than a three engined aircraft. With this in mind the T3 is now back as a tri-jet and the database is amended accordingly. The whole aircraft check thing is being looked at as there are always ways to circumvent any measures to try and get folk into the correct aircraft. I think the way things will go is as they were for FlyNET and the flights will get marked as cheats if fuel use/hours are not in accordance with the type and the flights would be re-calculated for correct values. This is hours/time check still in force on FSAirlines so the 'correct aircraft' check may get dropped - hopefully.

Regards

John