Jump to content

PFPX - Professional Flight Planner X

All your comments and support for PFPX

4018 topics in this forum

    • 40 replies
    • 5158 views
    • 2 replies
    • 608 views
    • 4 replies
    • 826 views
    • 3 replies
    • 1359 views
    • 0 replies
    • 1418 views
    • 0 replies
    • 2001 views
    • 1 reply
    • 911 views
    • 4 replies
    • 2640 views
  1. OALL Wind 000/000 How?

    • 5 replies
    • 899 views
    • 9 replies
    • 1504 views
    • 0 replies
    • 530 views
  2. Emtpy CFMU Error

    • 10 replies
    • 864 views
    • 8 replies
    • 4920 views
  3. LAT/LONG CODING

    • 2 replies
    • 4323 views
    • 1 reply
    • 849 views
    • 2 replies
    • 1173 views
    • 0 replies
    • 611 views
    • 0 replies
    • 495 views
  4. topcat speeds

    • 3 replies
    • 887 views
    • 0 replies
    • 507 views
  5. Problems with PFPX

    • 0 replies
    • 1210 views
  6. Route export list

    • 0 replies
    • 524 views
    • 6 replies
    • 5845 views
    • 3 replies
    • 3245 views
  7. First Error

    • 4 replies
    • 540 views


  • Posts

    • Then there is something else broken on your system. I strongly advice you to get rid of all tweaks/tools that change your system to look "better", leave everyting to default, including graphiccard settings etc. Also I suggest to calibrate your monitor.
    • Alle Treiber sind aktuell auf dem PC
    • That the issue happens to happen with Aerosoft airports doesn't mean it's Aerosoft's problem to fix. All those airports work perfectly well with standard FSX and each other, which is what they're guaranteed to do. No developer/publisher can be expected to support problematic interactions with other's software however. That a third party product like PSXT works with some other scenery add-ons is meaningless. There are countles examples from way before and after FSX as well as outside the flight sim world where combinations of products work for some and not others.   As your title of this post states "Final" and as you received a definitive answer to your earlier question, along with the reason for closing it, this one also is closed.
    • So in other words, maybe there will be an update, maybe there won't. Nobody knows.   Of course you could try installing the P3D v4 scenery in P3D v5 to see if it works. This is not officially supported, but it does work on some sceneries. But it's all at your own risk, don't blame Aerosoft if it doesn't work.   As a last resort, Inibuilds has created a number of compatibility patches to make P3D v4 sceneries work in P3D v5. Note that in that case Aerosoft cannot provide support for this scenery (they couldn't anyway since it's not officially P3D v5 compatible) and Inibuilds only gives support on the patch. Not on the rest of the scenery.  
    • If you say so that might be right. Nothing changed on the Scenery Manager since 2.0.6.x so that cannot be the cause. I don't understand what you mean by "[...] ORBX xml files are stuck within default scenery files [...]". In general the Layering of ORBX scenery will be done by ORBX Central and should not be changed by you - please follow the instructions of ORBX. No idea what MK scenery has to do with that reported issue. I cannot really understand what happens on your system but I am happy that it is working again. 😉
×
×
  • Create New...