OnCourse Software

I use Proflight Deluxe with FSX and win 7.
The problem is that no matter the altitude of the flight plan, the ATC Clearance always give me 10000 or 11000ft even if the cruise altitude of my flight plan is 36000ft.
In the FAQ document I read :

Quote:

Whenever I create an ADV Flight File the cruise altitude is always wrong (too low) and the cruise speed is showing a ridiculously high value.
A: Start ProFlight and select the Select Spec option to check the cruise speed set for your aircraft. Check the MACH setting is valid. ie. Mach .74 should be entered as .74 and not 74 (If you have a missing decimal point your ADV Flight File will be wrong.)

That´s another problem since Proflight always back the speed to 74 after changing the correct mach value and the problem with the altitude continues.

Your initial cleared altitude will always be low. Once you are at 10,000 or 11,000 feet you will be given further clearance.

I don´t think it´s normal since I was in a flight of 390 nm and I have flew 190 nm and ATC cleared me only to 10000 ft. Also, there is an annoying problem with the PF2000.cfg that I changed this wrong configuration:

Aircraft=737-400
ClimbRate=4000
DescentRate=-3500
EngState=0
SpeedSetting=1
CruiseSpeedIAS=42744
CruiseSpeedMACH=74
CruiseSpeedTAS=420
VSIPercent=65
MinAtcTime=15
MaxHoldTime=60
MaxHoldAlt=20000

In accordance with FAQ it has to have this values:

CruiseSpeedIAS=238
CruiseSpeedMACH=0.74
CruiseSpeedTAS=420

I always change the .cfg files to corrects and save the correct values but when
I back to program wrong values back again. The result is, in accordance with FAQ is wrong altitudes.
Quite frustrating.

What language settings do you use in Windows? Does it include a 'period' for a decimal separator?

Sent from my Dumbphone

dmarch wrote:

What language settings do you use in Windows? Does it include a 'period' for a decimal separator?

Sent from my Dumbphone

Dave,

I´m from Brazil, so Windows language is Portuguese. Actually as decimal separator we use comma (",") not period ("."). I think it happens with all countries that use decimal system.

That could be the problem. PFE should handle all international settings but sometimes can have problems. Try setting it to English to see if it does cure the problem.

Sent from my Nexus 10 using Tapatalk 2

dmarch wrote:

That could be the problem. PFE should handle all international settings but sometimes can have problems. Try setting it to English to see if it does cure the problem.

It´s working now. Thank you for your answer I appreciated that.