mmann

I have an i7-4770 @ 3.90 GHz, 8GB ram and a ZOTAC GeForce 750 Ti 2GB video card. P3D only got 20 FPS at best then dropped to 15 FPS with clouds; I went back to FSX where I get 30 FPS (locked) with clouds. P3D didn't stutter but the frame rate hit was unacceptable with my system.

I have to agree with the "ADI with the light green area at the top": http://marvellouswings.com/Aircraft/Trainer/T-45/Pic/T-45%20Sim%20Patuxent.JPG

When P3D v3 came out, I installed and then shortly after uninstalled it. The same thing happened with P3D v3.1; I haven't bothered yet with P3D v3.2. So for now I fly with FSX Acceleration and FS9.1 only. The reasons: 1. 33% drop in frame rate overall. 2. 50% drop in frame rate when encountering clouds. 3. Extremely poor Anti Aliasing. 4. Compatibility with my existing addons. The probable cause for reasons 1 to 3 is that I am running with only a stock clocked i7-4770 and a GTX 750 Ti 2GB graphics card.

I came back to FSX. I first tried P3Dv3.0 but after a short while I dumped it to go back to FSX. I next tried P3Dv3.1 but have returned yet again to FSX. P3D would be great if I was willing to spend $1500 for a video card and another $1000 on a 4K monitor in addition to buying a newer processor than my existing i7-4770. Throw lots of money at P3D and it probably would look and perform fine; otherwise you just end out with a sim that has poor FPS and lousy anti-aliasing (in comparison to FSX).

Now 13.7.3.2.3 billion years.

That would be somewhat accurate if all FSX/P3D owners used stock textures (which are still twice the resolution of FS9). I would guess that a great many of us aren't; so we see the difference an Orbx Region makes and FS9 (or stock FSX/P3D for matter) isn't even close. Orbx CEO John Venema quickly realized the potential of FSX vs FS9 and went with FSX; he quit FS9 development after Vista Australis (VOZ).

Type in "fs9 fsx water" in your search engine and see all the posts from FS9 users wondering if they can get FSX water effects and/or textures into their sim. The other problem with FS9 water (besides the unrealistic textures and awful effects) is that FS9 water has the consistency of molasses which absolutely kills the sims float plane water handling abilities.

Not only the SDK but other development software as well. SBuilderX is much better than SBuilder for FS9. Airport Design Editor has many more functions enabled with FSX compared to FS9.

They are probably going to shift even more processing to the GPU and a NVIDIA Quadro M6000 will be required to handle this.

Which is a big step up from my GTX 750 Ti card with 2GB.

With an i7-4770 clocked at 3.9 GHz and a GTX 750 Ti, my system was obviously not up to running P3Dv3 properly. I was running it with no air or ground traffic and various other sliders set very modestly, but still had frame rates 30-50% lower than I get in FSX. The final nail in the coffin was the disappointing anti-aliasing compared with FSX. Yesterday I uninstalled P3Dv3, until such time as I can upgrade to a much more capable computer.

Not just flight sim's! Expect perfection and 100% satisfaction with anything you do and you are sure to come up wanting.

Except that the OP's equipment is about level with mine. OP's equipment: mine MOBO Asus M5A97: ASUS H-87 Plus Ram 8G: 8G CPU AMD Vishera 4.2 4530 QC: Intel i7-4770 3.90 GHz Video Nvidia EVGA GTX 750ti: ZOTAC GeForce 750 Ti PSU 450Watts: 500 Watts

To answer your questions: Are frame rates and smoothness better. My frame rates are 30 in FSX compared to 20 (dropping to 15 in clouds) in P3D. P3D is smoother, however. Are terrain features better and better rendered and modeled. Where I fly (Vancouver Island) the terrain looks identical (same mesh with same vector data). Are the default airports better than FSX. The airports I have seen were all identical in both sims.

Vector could be held up due to the developer, which is PILOT'S. Orbx just sell Vector rebranded.

Arno lives in the Netherlands, so you won't see any response from him until tomorrow. If for some reason you are not able to get a fixed version of ModelConverterX in a timely fashion, PM me and I can send you a Development release that was done a short time before the Anti-piracy version came out.

Which won't work with Orbx FTX Global Base Pack.

Just a quick note. Arno has released a new Development release of ModelConverterX that no longer has the Anti-piracy measures. Furthermore he states that "Given the complications to get such a protection working right, without restricting real users, I don't think I'll try again in the future." This is good news for those wanting the new features of the Development release without the frustration of the Anti-piracy measures.

Thanks Steve! Your little section on what and how to set made a world of difference on my system. Finally the AA in P3Dv3 is closing in on FSX.

FTX Global Vector is just an Orbx rebranding of PILOT'S! FS Global Vector, which is probably why it sucks compared to products actually developed by Orbx. My big beef with Orbx (besides rebranding) is the paucity of uninstallers, which is acceptable for freeware but amateurish for a payware developer.

Maybe I will have to re-download FTXORBXLIBS_151001. I just did a new install of FSX along with Orbx PNW, and the libraries are missing the exact same texture files as P3Dv3. If I install an older library in FSX first and then install FTXORBXLIBS_151001 the textures are all accounted for!

Those lines are not intended for the P3Dv3 cfg; you can generate error logging in P3Dv3 by enabling it in the Settings - General page. If enabled an error log (if you have any errors) will be created for you when you exit the sim. Note that the error log will only be generated if you start at Courtenay (CAH3) with FTX NA Pacific Northwest enabled.

If they were omitted intentionally then they better find a more competent modeller! Notice I said that the sim is indicating the textures as missing; which means models in the scene are calling on textures that Orbx has now left out. The only way they should have left those textures out was if they had also removed the models that call on those textures. If this is still confusing perhaps this article will be of help: http://www.fsdeveloper.com/wiki/index.php?title=Missing_textures

I could have posted this in either the FSX or Prepar3d forum but thought that this problem is more likely to be an issue for those using P3Dv3. According to Orbx: "There is no new content in this installer apart from the new installer routine to cater for P3Dv3 and dual installs of FSX:Boxed & FSX:Steam." Unfortunately, although there is no new content, there is certainly content missing! If you have FTX NA Pacific Northwest (FSX or P3Dv3) and set up the sim to warn you of missing textures, you will find that starting a flight at Courtenay (CAH3) will indicate 2 missing textures. After further investigation between FTXORBXLIBS_150331 and FTXORBXLIBS_151001, I discovered a total of 15 missing textures. All of these textures belong in the folder: ...\ORBX\FTX_AU\FTXAA_ORBXLIBS\Texture Note that if you have an earlier version of the libraries installed first, updating will leave the missing textures in place. If you are using P3Dv3 this becomes an issue because FTXORBXLIBS_151001 is the only version of the libraries designed to install into that sim.

Maybe Orbx is looking at the Lite version as both a 'beta testing' and 'crowdfunding' source.