Hey Everyone,
Has anyone been successful in getting this Hornet to work in P3Dv2 yet. I've imported the aircraft, but none of the gauges that I've designed seem to work. Any ideas?
Hello Jimi,
funny that you mention that, now. I have just last weekend installed the new P3D v2.4 and tested it with my AMD R9 270X I got a month earlier, because I was keen on testing DX11 effects. I've got everything working perfectly but was somewhat disappointed with the overall results.
Installation:
1) Installed P3D v2 and latest updates into a VM. Then, copied files, license, and necessary registry entries from VM into my real system. I have had in the past several bad experiences, where installers (P3D, Rex, etc.) screwed my system up so badly it took me weeks in order to get things fixed (uninstall failed and reinstall too). So, this proceeding is standard for me, now, each time I tryout something. I did NOT startup P3D v2 in the VM, because I wanted scenery indexes, etc. generated on my real system. Created Prepar3D v2 folders in ProgramData and AppData manually with files from VM. First startup was without problems, adjusted some of the graphics settings, screen resolution and closed P3D v2.
Transfer from P3D to P3D v2:
2) Copied the following folders from my P3D installation into the P3D v2 folder, WITHOUT replacing already existing files in P3D v2 folder (so nothing new gets deleted, but all missing files will all be added!)
- AICarriers
- A2A
- effects
- gauges
- modules
- scenery
- Simobjects (just copy the Hornets first, all other planes later)
- sound
- texture
In order to get A2A and AIcarriers or FSUIPC working, you need to copy from
C:\Users\Administrator\AppData\Roaming\Lockheed Martin\Prepar3D ...to...
C:\Users\Administrator\AppData\Roaming\Lockheed Martin\Prepar3D v2
some xml files (make sure to open them and check/adjust the paths for the P3D v2 version accordingly!)
In order to get your scenery (index) working you need to copy scenery.cfg from
C:\ProgramData\Lockheed Martin\Prepar3D ...to...
C:\ProgramData\Lockheed Martin\Prepar3D v2
(make sure to open them and check/adjust the paths for the P3D v2 version accordingly!)
Once you have done that everything should be working fine.
3) Results:
- Although my new DX11 graphics card should be 4 times as fast as my old DX10 ones, fps in P3D v2 was NOT fluent with the same mid range settings I currently run under DX9 with P3D v1.4. Maybe my pc is too old, or graphics drivers are not jet optimized for P3D v2/DX11 (tessellation enabled/disabled made no big difference in fps, visuals just looked better, still lagging). Maybe NVIDIA is the way to go for P3D v2, at least what I have read.
- Although running P3D 1.4/DX9 gave me around 20/30 fps more compared to my old graphics card HD3870.
What made me switch back to P3D v1.4 finally was the following:
- Bad FPS compared to DX9, unless you have real killer hardware
- Blurry overall look (with AA+Anisotropic maxed out)
- Hornet effects AB, vapor trails, etc. if present did not look as good as before, a lot of them missing/not working!
- Captain Sim Hornet, canopy showed major errors.
- Water under DX11 looks too dark and unrealistic, even with HDR lightning tweak applied
- A lot of visual glitches and inconsistencies, flickering and NO smooth fps (reflections are not positioned correctly under objects such as bridges and buildings - it is somewhat irritating)
- some AIcarrier objects seem to be misplaced, e.g. hovering over the carrier instead of being placed on the deck.
On the other hand the original fsx hornet model and the New FSXBA Hornet model seem to be working without any glitches under DX11.
If you put all that aside for a while, and max out visual settings and have a look around, the overall visual experience is simply stunning and P3D v2/vX's will be the thing to go in the future.
As I personally prefer fluent fps and realistic flight behavior/FCS over visual bloom and lightning effects, I will stick with P3D v1.4 and DX9 for the time being.
Peter
