Jump to content

GCBraun

Members
  • Posts

    64
  • Joined

  • Last visited

Everything posted by GCBraun

  1. I understand that there are business reasons to say that the P3D version will look very similar to the XP11, but having both platforms and a pretty high-end machine, I don`t believe this can be the case. The rendering engine of XP11 is far more advanced, and it is really hard to go back to P3D after flying on XP11 for a while.
  2. I would also support a subscription service. In the times of Netflix or Spotify, it is really hard to deny the advantages of this model.
  3. Very good! Even though I already have 4Tb of Orthoscenery for XP11, I would gladly pay to get guaranteed compatibility and a hassle-free experience. Day one costumer here!
  4. Very good! I have always been a MSFS/P3D user but today I am using XP11 about 50% of the time. Even though I have no real use case for Meigs, I have bought it regardless to support further development for the XP platform. Looking forward for the new releases!
  5. I already have the whole of Europe in Orthophotos for XP11 but, as I`ve said before, I would gladly pay for a product that offers a superior quality/experience!
  6. Ok, my mesh setting was 1m. Just placed it at 5m AND unninstalled FTX Vector. Still facing elevation problems at CZST. Is it possible to get a refund on this airport? It seems not be working for me, no matter what I try.
  7. I am sorry for the mistake. So, I have unninstalled both PFJ and CZST. On the first picture, you can see the result right after re-installing just PFJ (no elev. problems). On the second, the one I just took after installing CZST (again, the aircraft floats some centimeters above the ground). I am really at a loss here on what should I do next...
  8. So, the name of the file was ADE_FTX_PFJ_CZST_elevation_adjustment.bgl. I had already deleted it and it makes no difference. Still experience elevation problems. Also, is it normal to have such a low resolution on the runway?
  9. Yes I did. There is a file CSZT_Elevation_correction.bgl that I assume was generated from Vector.
  10. Ok, I had Vector, all regions for NA, OpenLC NA and just bought a bunch of airports, including CZST. I`ve already lost some hours trying to figure what is wrong, considering that I am having elevation problems in this airport (also in many others, but it seems I was to be able to fix them). I have already run the Vector Tool multiple times, renamed some BGLs for these airports that were installed before downloading CZST, and other measures. I thought ORBX software was able to talk to each other and detect what is installed to prevent these kind of issues? Any hints on what I should do? Attached is the picture showing the problem and my scenery.cfg scenery.cfg
  11. Fine, but please don’t call it reliable. Not even P3Dv4 or XP11 achieve that.
  12. I`d love to have Orbx regions using photoreal scenery. I do have several TB of Orthophoto, but I would gladly pay for a hassle-free experience with the Orbx quality touch and customizations on top. Being that said, starting with Airports and getting a feel of the XP platform as a general is also a fine approach!
  13. Huh....? What is this all about then? "That said I guess the cat is out of the bag that Orbx is developing for XP (I revealed this in a recent interview at Cosford FlightSim show), and I would be interested to hear if there is interest in a NetherlandsXP as a payware product with all the usual Orbx 3D POIs modelled etc?"
  14. I have almost ALL Orbx Products and cannot wait to have at least some of it also on XP11. This sim has so much potential. We just need top tier developers like Orbx to divert some resources to it.
  15. I have the same problem with Antennas in P3Dv4 and I do not use EZDok. This just happens in the US, where I have FTX Global, NorCal and SoCal installed.
  16. I have the same problem in P3Dv4. Antennas everywhere in the US. I have just FTX Global installed in this country, but I did install and then uninstall Vector.
  17. Yes, the issues are gone for me. As I said, I just clicked on the Force Migration option inside settings after installing FTX-AU and that solved it! Since then, I installed other ORBX Scenarions but the problem did not come back (I also did not need to run Force Migration again). Hopefully you will also figure it out what is going on.
  18. I think I solved it: the problem started after I installed FTX-AU. I did not know I should run the migration process, therefore after runing it on FTX Central, the glitch stopped!
  19. I have a similar problem, as described here: It also starts after 20 minutes of flight or so! Already reinstalled everything and updated nVidia drivers without luck
×
×
  • Create New...