The PF3 controllers told you to fly to 11,500ft because of your badly set up fpl.
JohnY wrote: It wasn't only the flight plan that gave me 11,500' to fly at, it was the PF3 controllers too. Starting at 2000' they gradually increased to altitude instructions to 11,500. So why were they giving these instructions :
I've increased all the FAF altitudes now to 18000' and hope this will resolve the problem until perhaps an update can include the alterations necessary to prevent these ATC contradictions?
Oh, and by the way. I didn't set the flight plan up. All I determined was the airplane, departure airport, destination airport and that it was VFR. P3D did the rest!
John
I don't have P3D but setting up a fpl in P3D must be somewhat similar to FS9 and FSX in which a cruising altitude is "offered" so that's the point where you need to change it.
I've increased all the FAF altitudes now to 18000'
You should not have to do that as it is not FAA territory. Reset Lisbon control to the default 8,000 and remake your fpl so that it does not exceed 3,500ft. The whole point is to inject some realism isn't it? Otherwise why bother!
and hope this will resolve the problem until perhaps an update can include the alterations necessary to prevent these ATC contradictions?
The ATC contradictions as you put it are down to your incorrectly made fpl and not PF3's fault. So if Dave does not find an actual error there will be nothing to update.
The moral of this story is garbage in garbage out. If you want to make a VFR fpl then make sure it stays in "uncontrolled" airspace. Which btw is real life! If during the fpl you want to cross or climb into controlled airspace then get IFR clearance which is also real life and also covered in PF3.