A2A B17 & P3Dv3

dougal

dougal

Charter Member 2016
Having a very hard time getting my login details from A2A so I'll bring it up here...

I'm fully aware that the beautiful B-17 is not 'officially' supported for P3Dv3, but I'm also aware that a good number of people have it running ok.

I've installed it simply by changing the install path, and the latest AccSim core updater locates it well enough.

However.... Two major issues are grounding my all time favorite war bird:

1) From cold or auto start, only engine 1 will fire up and the sound file "engine 1 starting" keeps looping.

2) If I switch to the aircraft with engines already running, then they keep cutting out for something like 1/2 a second, every 1 to 2 seconds.

If anyone has any ideas I'd be most grateful

Cheers M'dears!
 
Usually, if the Accusim planes don't work properly in P3D (any version), the typical origin of the problem is the missing SimConnect. The installation of SimConnect can be triggered from the "redist" folder inside the main P3D folder. Just try to trigger the one for FSX Acceleration (the titles of the folders are explicit) and then launch your sim for a new try.
If it's still not enough, then I would check if all the DLLs and gauges went to the correct places.
I have the Accusim B-17 but I haven't installed it in P3Dv3 yet (even though I was using it successfully in P3Dv2). I'm interested in the feedback here.
 
Daube said:
Usually, if the Accusim planes don't work properly in P3D (any version), the typical origin of the problem is the missing SimConnect. The installation of SimConnect can be triggered from the "redist" folder inside the main P3D folder. Just try to trigger the one for FSX Acceleration (the titles of the folders are explicit) and then launch your sim for a new try.
If it's still not enough, then I would check if all the DLLs and gauges went to the correct places.
I have the Accusim B-17 but I haven't installed it in P3Dv3 yet (even though I was using it successfully in P3Dv2). I'm interested in the feedback here.
Click to expand...

Still exactly the same after installing all versions of simconnect. Will look at file structure compared to FSX. Will also try it without Accusim....
 
I have this in my FSX dll.xml but it doesn't appear in the P3Dv3 version:

<Launch.Addon>
<Name>A2A Service</Name>
<Disabled>False</Disabled>
<Path>A2A\Shared\A2A_Service.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>

Might try inserting it
 
Ahh yes, this is perhaps the problem... although, in my remembrance, only Accufeel requires some entries in the DLL.xml... but my remembrance are often bad :)
 
Daube said:
Ahh yes, this is perhaps the problem... although, in my remembrance, only Accufeel requires some entries in the DLL.xml... but my remembrance are often bad :)
Click to expand...

No, can't get it working. I've got access to A2A forums now so will try there, tho I expect i know the answer;-)
 
I just reached home. I'm going to give it a try by myself from now, and will report here.
 
Ok, I guess I got lucky :)

daube_image0068.jpg


Here is what I did:
- I unzipped 5 archives in total: the plane, the accusim pack, and the three updates up to 1.21 (these updates might not be necessary, see below)
- I ran the installer of the plane by right-clicking and choosing "run as an administrator", as always.
- the installer asked me to locate the FSX folder, I pointed it to the main P3D folder (g:\Prepar3D v3\ on my computer), where a fake FSX.exe also exists.
- the installer ran fine.
- I did exactely the same for the Accusim extension, as well as for the updates
- I also downloaded the latest Accusim Core update and ran it as well. It detected the B-17 and updated it to version 1.30.
- then I launched P3D with the default Baron. I had not created a default cold and dark flight yet, so this was the opportunity.
- I switched the plane off (electrics, lights, engines etc....) then saved as default flight.
- I changed the plane to the B-17.
- Upon loading the plane, I got an error message about failure to create a child window... no idea about that. I pressed OK and then loading continued.
- Then I was in the cockpit, and I could hear the copilot talking to me.

The plane was working correctly from there, but I only started two engines, to check the various stuff. Everything seemed fine though.
 
I didn't try the autostart, only the option to put the aircraft cold and dark (even though it was already shut down, since I switched from a cold Baron). All functions were reacting correctly.
One last check: did you verify the "automixture" setting in the realism options of the sim ? Accusim hates that one.
 
Thanks for the help here. Finally got it working. Tried everything without success, but after reverting to a backup version of a default installation, it works;-)
 
You must log in or register to reply here.
Back
Top