WarHorse47
SOH-CM-2024
What is the recommended procedure for updating to SP5? Total uninstall, then reinstall? Save all addon textures? Other suggestions?
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
Just when you think you have everything running some what better...
You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.
If all goes well we should be back online on November 8th.
To keep you updated we will post updates on AVSIM forums.
Thank you for your support.
I am running the P3dV4 sp5 version outside the "Prepar3D v4" sim folder, no issues so far (I also moved the custom font file and effects to external folders which are aliased in fonts.cfg and effects.cfg).

Hmm, I attempted to install outside of the main dir, but the installer complained it couldn't find P3d. Haven't tried manually moving the files yet.
Good to have this back though.![]()
I haven't updated as yet. Seems some folks are reporting these problems on the JF forum, so I'm going to wait and see what happens. Still not sure if these issues are with P3D or FSX or both.Anybody else having problems turning on the E-Scope, TV, HUD and RWR?
Anybody else having problems turning on the E-Scope, TV, HUD and RWR?

Meanwhile I've uninstalled V.5 and reinstalled the previous-right-working V.4 with all repaints (alias wasting time).
For sure I'll think more than TWICE before rely in future upgrades
( downgrades is far better).
Is there someone ready to tell me that I shouldn't say things like this
in this forum?
Don't want to point out the obvious here but I assume that those who have installed the new version of the Tornado also uninstalled their old version before doing so. Just a thought.
Ticket submitted ( post 328 above).As mentioned above, this is already being discussed on our forum and I've asked that anyone encountering these issues to please submit a support ticket to help us identify the cause.
I appreciate the frustration but the update wouldn't have been issued if we had encountered the same issues during the conversion and testing process, and I'm confident that we'll find the cause and fix it quickly.
If you are using FSX:SE then please also ensure that you have the legacy version of SimConnect installed (https://www.justflight.com/support/flight-simulator-x-steam-edition/384bffb)
Thanks
Martyn