The A2A Simulations Community

May be a stupid question, but I like to post it : the A2A aircrafts function very well in Prepar3D, so can we assume that Accu-Sim can be applied as well??
And if yes, what has to be done to have it work like in FSX ??
Just bought WoP III P51+Accu-sim and wondering if I can fly her in Prepar3D
Italo

I've tried the Cub, B17 & B377 in Prepar3D and they do work OK but with a couple of problems.

First off all plane settings seem to be shared between FSX and P3D so if you take a flight in FSX then later load the same plane in P3D it will be in the same state it was in when you finished flying it in FSX (and visa-versa).
At first I thought this a problem but after a while I decided I like it. In fact if A2A where planing to release some sort of migrator it might be worth including an option to keep them synced or separate them (hint hint).

Secondly but linked to the above the controller config program doesn't work correctly in P3D, (not a problem in the Cub as it doesn't have one).
As above it doesn't matter if you set them with the FSX or P3D install, they'l be saved in both.
The big problem is although everything work OK in FSX, in P3D any axis only work over about 50% of there range.
For instance I like to setup the twist on my X52 as the AP bank handle, in FSX I can bank left and right perfectly but in P3D I can only bank right

As for installing the Cub, 377 and Accu-feel all install directly to P3D as long as you first place a copy of your FSX.exe in the Prepar3D folder. Once there installed you have to manually copy the dll.xml entries over from FSX to P3D.

The B17 and 3D lights wouldn't install directly and I had to copy them over manually but worked OK after that.

_________________


Asus P5Q3
C2D Q9650 @3.6
8Gb Corsair Vengeance DDR3 PC3-12800C9 1600MHz
GTX580 3Gb
Akasa 1000w PSU
Antec 1200 gaming case
Asus VE276Q 27" Monitor 1920x1080
Win 7 Home Premium 64bit SP1

I have problems with the Input Configurator in P3D.

I'm highly interested if there's any solution for this?


Here, eveything works fine as it should, even in the IC's axis preview it shows full range from 0 to 100%, but the VC levers are only moving from 50% to 100%!

I'm new to P3D ...



many thanks

I really see this benefitting A2A Simulations if they add support for P3D. I am starting to see a lot of FSX simmers move over to P3D, and this must be a big motivator for a lot of 3rd Party Add-ons to add P3D compatibility. I for one, can't see myself using FSX anymore, too buggy, too old, sick of reinstalls, corruptions, stutters, and it is no longer supported. I am only purchasing add-ons that have P3D compatibility from here on out.

So are you saying that Prepar3D has none of the instability issues, memory leaks that FSX has?

That ,then, interests me greatly!!

Darryl

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

what is dll.xml entries,and where do i find this in FSX

be baltzer

_________________


url=http://a2asimulations.com][/url]

I found the dll in fsx and copy it to p3d.athe a2a installer for the 377 wount let me install in p3d

br baltzer

_________________


url=http://a2asimulations.com][/url]

no forget it i dont want to risk any licens problems.

br baltzer

_________________


url=http://a2asimulations.com][/url]

I D/L'd P3D yesterday and last night. Got it installed today and then installed the
Accu-Sim P-51D. I had to put a copy of FSX.exe into the P3D root folder in order to
get the installer to do its thing.

I incorporated the TrackIR 'fix' that modifies the language.dll so that TrackIR thinks P3D
is FSX and connects.

The issue I have now is the "50% travel" problem on some of the axis. Particularly those
that are assigned via the A2A Configurator. I'm thinking I may need to send those to
an FSUIPC4 offset and massage them with a Lua script if there isn't a simple fix.
I attempted to set the sensitivity to max un the P3D Controls menu but that didn't help.

FSUIPC4 installed OK and I copied and pasted my custom P-51D assignments to the
INI file with no issues.

I hope to get my Accu-Sim'd B-17G, Spits and P-40's installed over the next week or so,
time permitting. And now, with the P3D forums added to my list of daily "reads" I have
less time than I had before!

Paul

I think I'll just wait a while before I jump on the P3D bandwagon.

Re the joystick problem ,did you adjust the sliders in the config. screen for the controllers for max sensitivity and minimum null?

Good to see that your diving into P3D.

_________________
Buzz313th
FASA Founder and dedicated Staff Member
TeamSpeak 3 @ "ts3.digitalthemepark.com"
Facebook @ http://www.facebook.com/FsxAirSportsAssociation
Website @ http://www.fsxairsports.com

That only 'works' for axis that are assigned to standard FSX controls. There is no way to do that
for the 'custom' controls in the A2A aircraft that require manipulating L:Variables.

I have solved the issue using FSUIPC4 and Lua scripts. I have all the axis working correctly now.
I also have the B-377, P-40, Spitfire and P-51 running in P3D with no issues now.

I also created a new user account on my Win7 partition so that I now have a completely separate
environment for the P3D setup. No more 'sharing' of the input configurator settings or the aircraft dat files.

_________________
Paul


i5-2500K @4.3Ghz OC - GA-P67A-UD7-B3 - 8GB Corsair 1600mHz

Hi!

I also tried to install the PiperCup with the trick of putting the fsx.exe into the P3D folder. Ok, the installation was ok, also the two Patches.

https://www.dropbox.com/s/e9594b7dzruw8bs/wj3.log
https://www.dropbox.com/s/euoygoi1zfi9q5m/wj3a.log

But it doesn´t work and P3D crashes with selecting the Piper. Then I read, that I have to copy dll.xml entries..... Please give me a hint where to find and what I have to copy.... Perhaps this is the probem...? Otherwise, perhaps there is someone who could take some time to read my logs to see what is wrong?

Thanks a lot!
Stephan

I have the same issue here - seems like it should be a trivial fix for A2A to make - hase anyone found a solution aside from scripts ?


Brian