FSAirlines

I did my flight on FlyNet and while the client looks fine I have noticed the following things that either need investigation or need correction:

1. The download must come with a documentation! we are not psychics here, while it is relatively simple to use (interface) it is definitely not fool proof and has bugs.

2. What is that autoupdate.exe for? when I try to run it it says something about it not being installed properly. How can it be properly installed if it only comes in a zip file with no instructions?

3. I have a Pentium IV 3.0 GHz with 1GB RAM PC and it is quite heavy on my system. I do flights on IVAO so at least when I have IVAO's IvAp (pilot client) and FlyNet client the system is very sluggish in the frame rates. I think the client just does too much picking into FS as opposed to the IVAO client.

4. Sometimes it does not give you a report/PIREP to upload and then your flight is lost forever. I find that unacceptable, it should at least have some preliminary info stored as "proof of flight" in case of problems.

5. Some more info on the client please! if it hints about the landing lights on the FS, then why not hint upon landing about "put parking brakes to get your report"

6. VERY IMPORTANT!!! it not always detects the parking brake being set (and so no PIREP!!!). I use the CH Pro Pedals and when you have them connected pressing the "." for Parking Brakes is not properly detected by most planes. It does see that the BRAKES are applied but then not all the aircraft panels out there have a subpanel with a Parking Brake Lever.

Hi, I don't use rudder pedals but...

6. VERY IMPORTANT!!! it not always detects the parking brake being set (and so no PIREP!!!). I use the CH Pro Pedals and when you have them connected pressing the "." for Parking Brakes is not properly detected by most planes. It does see that the BRAKES are applied but then not all the aircraft panels out there have a subpanel with a Parking Brake Lever.

Ctrl+. works fine

The forum search function works great too.

1) We're working on documentation. This is still a BETA and things have been changing with enough regularity that documentation is difficult to do because it'd be getting re-written every-other-week during the active period of development we had last year.

2) Ignore Autoupdate.exe. It was supposed to be removed from the package, but I guess it wasn't. It's not worked on very many systems and is still in development.

3) Funny, I've got an AMD Athlon 64 of a similar speed and when I pull up the task manager and look at the "Processes" tab, Flight Sim is by far the biggest user. FlyNET only uses 3-5% of my processing. You have something other than FlyNET causing your issue.

4) Funny... there's a file called "log.out" that does EXACTLY that. Again, the forum search function works great for finding this info.

5) Again - the forum search function is working on this forum. Suggest you use it before trying to fly so you know what's going on. There is a forum called "Tips and Tricks" that has most of that information on it, and the "Important Announcements" forum has most of the rest. They're at the top of the forum for a reason.

6) It *ALWAYS* detects the parking brake set if you set it. What you're describing, you're not setting the parking brakes. If you hit "Ctrl+.", you should see "Parking Brakes Set" in the lower right corner of your FS window. If you don't, your parking brakes aren't set. And they have to *STAY* set for the system to register, not just be on for a split second. Not only that, but the aircraft has to be perfectly motionless on the ground. So be sure you've got the engines shutdown too, because that can cause a problem.

Sorry Emilio, but most of these issues that you call "bugs" are just due to not reading the information available here on this forum before going and flying the client and expecting it to work like a finished product and not a piece of software still in development.