Ok, success (I think). After discussing things that also load with the Sim I started thinking what really does load? This morning I checked both the exe.xml file and the dll.xml files. The exe file only held two programs. . .an old version of REX that isn't installed any more and this (as_btstrp_config_manager). . .never heard of it so both of those were removed leaving nothing remaining for the exe file. Next I looked at the dll file and it loaded quite a bit. A few programs were not even installed anymore (Accu-feel and Abacus PremierCollection). . .deleted those but that made no difference to the Bounty. . . .moved about half a mile and quit.
Next I removed the People_Flow module from Orbx. . .No change
Next I removed Instant Scenery 3. . .No change
Next I removed FSTramp. . . .Success!!
Currently I have sailed out from Pensacola to Bills Carriers (about 10nm), rounded the Carrier, changed wind directions and am currently headed back to Pensacola. . .maintaining a steady 15kts.
What I don't yet know for sure is this:
Was FSTramp the culprit or was it a combination of FSTramp and one of the other three I removed? For now I'd have to say I'm disappointed that it turned out to be FSTramp. I use it on a daily basis when I'm flying. I don't know if there's a way to load P3DV2.5+ using multiple setups or not. . .something to look into.
Hi Ed,
Well, whatever the problem is, glad you have it working now .....
As a sidenote:
It demonstrates again - in general - the weakness of addon development for FS; because addon development is uncoördinated between developers, one nevers know if/when/where they might conflict.
Even if everything is made according to an SDK.
Just an example: If another addon would also manipulate the groundspeed (like I do in the Bounty, and all of my VSTOL stuff), there's definitely a conflict.
Another example: Accu-feel doesn't "like" my VSTOL implementations, resulting in funny behavior when in VC View.
Also - and I think all P3D users need to realise this - P3D is an addon-developers nightmare, because it's a moving target with it's constant stream of new versions and hotfixes.
Even worse: it may introduce new incompatibilities (or even "bugs" ) with every new version or hotfix.
That said:
I just had a look at what FStramp actually does.
But since it's a simular addon as FSNAV for FS9, I would be very surprised if this really is the culprit.
The only feature in it, that could be conflicting, is re-positioning of an aircraft to a waypoint ...
So let's not blame FStramp yet ....
One of your earlier screenshots clearly demonstrated, that your "doesn't move" problem, is caused by my groundspeed commands via FSUIPC are being blocked (or overwritten) in P3D V2.5.
In YOUR setup.
What the cause is, is still unclear.
Anyway, you seem to have it working now.
Can you please do another test too:
Enable CrashDetection (with "Aircraft Stress Causes Damage" enabled too), and see if that makes any difference ?
No problem in FS9/FSX, but I'd like to know if that works in P3D as well.
Rob