Archive > Technical discussions

Flight Logger 3.0.9 - Bugs and suggestions!

<< < (3/7) > >>

EHM-1612 Paolo:
I don't know if I am committing an error, but when I select a class 4 flight and a class 5 plane I get the red sentence...I think it's "the plane and the flight class don't match"...
Any way to delete it? ;)

EHM-0471 Peter:
During the last and this week I have tested EHM 474-400F in F1 livery, used for all the testing flights PP and IVAO network. I must confess it has been a hard work, but I have decided that I'd like to do all F1 Flights with as minimum as possible of penalties. So, I have found out in this version of PP exist a few bugs which are real bugs and the pilot can have practically no influence on protecting not to occur.

1. Starting engines. You must go from No.1 to No 4 and no other way. If the row is not this one, you get a small penalty No. 3. What for? I think it's absolutely the right and a matter of decission how I want to start engines, regardles the standard procedure.

2. The procedures up to the FL 100 are normal and if you fly carefully and by the rules - no problems. The big mama will take off and climb to FL100 without any problems, if you set the speed on AP to 265 kts IAS and climbing rate to 1800 to 2000 ft.

3. Very serious problem may occur much later, when you are flying at your final FL, suppose FL 350 and all goes fine. You are drinking coffe, talk to nicest stewardes, all is fine and then, totaly unexpected, you get the red warning OVERSPEED, even if you have AP at 0.80 M and are allowed to fly 0.86 M. Before you are capable to react.....woooops.....PENALTY! This is uncorrect and unfair, since you simply don't have enough of time to react and slow down. By my oppinion every pilot who finds him or herself in such a situation, must have at least 3 to 5 minutes to react and slow down the bird. After that, the penalty may occur, but correct the PP program in the way I suggest.

3. Shut down engines. This is just the repetition of No. 1 problem. All the rest is okay so far and it is possible to make a flight with the final score zero.

4. In general I would like to suggest also the use of penalty system for too fast taxiing. We all know the speed limitations concerning taxi and this add-on to the system would be interesting in adding to reality.

Peter LGAV HM

EHM-1749 Hector:
1.- I don't know whether this is a bug or not but it happens when locking a flight.
For example, when flying a Class 5 plane and getting the possible destinations, it also shows Class 6 flights which obviously can't be flown.
2.- I agree that PP should give the pilot a minimum time to react in order to correct whatever problem may arise during flight. I got a penalty for "Engines on without the Strobes type" just because when at cruise level I mistakenly clicked the mouse when pointing at the Strobe light. It was only a microsecond but that PP whatchman was fully awaken and punished me.
3.- The unfamous "Overspeeding Penalty". I don't use Autothrottle any more because it reacts too slow to wind shifts. Of course this forces you to be watching wind speed and direction all the time. However, last month I got the penalty TWICE even with A/T OFF when flying the A320. As per the aircraft.cfg file the Maximum Indicated Airspeed is 350 kts. Well, the Overspeed warning was activated when the plane hit 330 KIAS on both ocassions. As when the Strobe Light time, I shut the engines in less than 2 seconds but the damage was already done.  Question: is the Overspeed flag tied to the aircraft.cfg file or it is a fixed number?
Hector Partidas
EHM-1749

EHM-1945 Christophe:
Hi All,

Just one idea regarding the STD 29.92 altimer: would it be possible to configure the Transition Altitude. AS this is different from country to country, it should be good to be able to select this transition altitude as Radar Contact allows it as well as FSPassenger. The goal is to have realistic settings and not being forced to use the US based TA of 18000 ft.  Obviously this is related to ProPilot, as I got several time the Altimer not set penalty.

Cheers
Kristoff

EHM-1945 Christophe:
New Problems I experimented while doing the ProPilot Event:

1) Beacon light not turn on : I used the Meljet Model for this flight: Even with engine off, i got this penalty when switching off beacon light => I guess this is because the engine rpm is different from 0 but this is unfair :!
2) STALL detection while the airplane was @ 270 kts !!
3) Penalty because one door was open while engine oN !! As for the topic 1, the engines were switched off, but I guess because of rpm not being 0, I got the PENALTY :!

I accept to get penalty when I do faulty actions, but not under that conditions ...:!

Navigation

[0] Message Index

[#] Next page

[*] Previous page