Naki wrote:Well I'm loving the smoothness, even at low framerates...the cloud shadows, the cockpit shadowing and the clouds in general..
Mikes Hamiton & Taupo (although Taupos aerial underlying photo is a bit washed out - if anybody could let me know how to disable the aerial in this and Hamilton it would be appreciated))
Taupo: Go to your Taupo folder, then scenery subfolder and disable taupo_ground.bgl (I chose to keep mine activated as it is quite a good match for Rob's subscription photoscenery of that area).
Hamilton: Go to your Hamilton folder, then scenery subfolder and disable HamiltonX_Photo_02.bgl and HamiltonX.bgl (which is the higher resolution airport background).
Naki wrote:When I have time I wil try get all my Sibwing Aircaft installed and my Aerosoft An-2, Wilga and Catalina
Aerosoft aircraft are the only ones I've had problems with so far. Because of the custom sound configuration, they all need a new ASC.dll for 3.0 which hasn't been issued yet. I have the Bronco, Catalina and Polar Twin Otter (from Antarctica X) installed but the engines power down after startup. Perhaps I should learn how to start from cold and dark?
Naki wrote:The biggest issue is that my A2A aircraft don't work unless I buy them all over again with P3D installers!
I use symlinks and registry hacks to get around the lack of P3D 3.0 installers, and have done since P3D 2.0. It's a similar approach to what's used by the Estonia Migration Tool except I do it manually to keep full control of what's going on. It fools any installer to install into P3D 3.0. Once it's set up, it works like a charm.
Basically, in ProgramData\Lockheed Martin, Users\NAME\AppData\Roaming\Lockheed Martin and \Documents, I have symlinks for Prepar3D and Prepar3D v2 which point to the actual P3D data folders, Prepar3D v3. I've also recreated the registry keys for both P3D 1 and 2 which point to the actual P3D root folder. If you also change your FSX registry key to point to the P3D root folder and pop a copy of fsx.exe in that folder, FSX installers will install to P3D.
For the A2A Spitfire, I changed the FSX registry key to point to P3D before installing the aircraft and Accu-Sim. Then the Spitfire update was a P3D 2.0 installer so it went to P3D 3.0 via the symlinks. The latest Accu-Sim core was P3D 3.0 compatible anyway so installed directly into the correct folder.
Hope that helps,
Ade