Arismac

Peter, Peter, I know I am a septuagenarium and have been for some years but I am not ready yet to go and fly a kite just yet. The first grab is after running P3D just once from the exe file shown in the second grab. What I think has happened is that somehow I have managed to get a second file extension on the two files concerned. ie: "D3D.exe.exe" Don't get too grumpy Pete 'cause you have a lot of years left to get very grumpy and I know all about that. I will leave you my wheel chair when I go. LOL Cheers, Mac

G'day Pete, I have been out of the cockpit for awhile and am trying to return to the AFR.Friendly mode mentioned HERE. I am not able to use this method of convicing FSUIPC that I DO have a registered copy in AFR.Friendly mode. Waht have I done wrong, please. I have FSUIPC Ver 4.936 installed, registered and working just fine in P3D v2.3 without the SLI "tweak". Mac

Make sure you are running FSUIPC v 4.931 or later. First run P3D in SLI mode and confirm that FSUIPC is NOT registered. This will create two files FSUIPC4.AFR-FriendlyD3D.ini.and FSUIPC4.AFR-FriendlyD3D.log. Go to ../Locheed Martin/Prepar3D v2/Modules/and confirm the two files have been created. Now copy and paste the file FSUIPC4.key. Finally change the name of the new/pasted file to FSUIPC4.AFR-FriendlyD3D.key. Thats it. Start the sim in SLI and you should be good to fly. Many thanks for this, Pete.

Thank you Pete, I will try and follow instructions. I should say that I am not the only one that will be affected by this as a number of people are accepting the option to run P3D v2.2 in SLI mode, which I must say is a huge performance boost. Mac EDIT: OK got it, sorry a bit thick this morning. Thanks again, Pete.

G'day Pete, I have tried several times to install and register 4.931. Each time the registration appears to fail. My next move is to try purchasing a new License but thought I had better check with you first. I only have P3D v1.4 on my G:/ drive and P3D v2.2 on my E:/ drive. The issue first appeared after I installed the "Black Box" edition of the Airbus into P3D v2.2. I also perhaps should have said that I am running P3D v2.2 from an LM hack "AFR-FriendlyD3D.exe" file in order to enable SLI. Cheers, Mac EDIT: When I run P3D v2.2 from the "Prepar3D.exe" file FSUIPC 4.391 is showing as registered. So it looks as though LM have tricked us again. Currently SLI and FSUIPC do not seem to be compatible.

Many thanks Pete. FYI I have copied version 4.921f (7th October 2013) from P3D 1.4 to P3D 2.0 and it works perfectly.

Sorry guys it does not yet work for me. Thanks for trying. No problem, Pete should be back today or tomorrow.

A little more info for Pete when he returns: When I load P3D1 my SPAD setup screen shows in the bottom left hand corner "FSUIPC Status Connected" but in P3D2 the SPAD setup screen shows "FSUIPC Status Disconnected". As others have indicated if I copy the dll.xml filew into "\App Data\Roaming\Lockheed Martin\Prepar3D v2\dll.xml" Prepar3D V2.0 will not start. Prepar3D V1.4 is working fine on a seperate drive. Cheers, Mac

I would like to install FSUIPC into P3D 1.4 and P3D 2.0. Is this possible please. I am having trouble directing the FSUIPC install to P3D2.

They "hacked" it over at the P3D forum by setting the Sensitivity to 127 and the Null Zone to 1. Case closed from my stand point, Pete. I expect fis from LM with the next upgrade.. Cheers, Mac

Pete, you don't look a day older. Others have come out of the cupboard at P3D with exacxtly the same problem except with a different axis. P3D are looking into it. Cheers, Mac

A very, very happy birthday young man. Many thanks for your great contribution to my very best reason for staying alive these days. Mac

Last things first, Pete. I have double checked everything and all settings both through the P3D interface and the FSX interface are identical. I double checked this with P3D v1.3 as well and in that case the two sims responded identically to the quadrant. Having acheived that result I have basically used FSX as the template settings for P3D. This worked fine in v1.3. The fact that you have established the fault does not lie with my .ini file is good news. Unfortunately I am not brave enough to do a P3D install because if the fault vanishes I shall die wondering. Not my style at all. LOL What I will do however is retrack everything I have done since the upgrade and report back tomorrow. I can't thank you enough for your patience, Pete. We oldies greatly value that. I will report back. Cheers, Mac

Actually Pete, I think I sent you an .ini at my friends suggestion that he had modified for me. My origional .ini does not have an [Axes] section which I noiw realise makes a lot more sense, at least to me. I think Terry added that section in an attempt to over come my problem. I have now returned to the origional .ini which does not have an Axes section and rebooted P3D. This has returned me to the origional situation where the quadrant lever only initiates the flaps from position two to three. To clarify, presume full travel from 0 degrees to 90 degrees. I can only move the flaps between 30 degrees and 60 degrees and back. This applies with all aircraft in the P3D sim. The FSX sim is fine. I have exactly the same .ini file installed in both sims. This is why I was quite happy to accept the "P3D bug" theory. Cheers, Mac

OK Pete that part I can understand. All I have done in the past, without problems is to go into FSX and/or P3D and assign the Axis that way. I have never used your GUI ( Add-ons --> FSUIPC) to set the Axis nor have I looked at the Axis Assignment window after setting the controls through the Sim interface. But I am leaqrning and that part I enjoy very much, even at my age. You just have to forgive or at least ignore a few "seniors moments". LOL

Thanks Pete. Much of this is way over my head. They were still building aircraft out of canvas and timber when I was born. Fortunately I know a disciple of yours whom I am sure will understand this much better. I will pass your post to him and beg his assistance. I have tried and failed to follow the ducumentation so far, but between us I am sure we will sort this. Thanks again. Mac

Sorry Pete, should also have said that the I have my seeting up problem with all the P3D packaged aircraft and those that I have ported from FSX although there is only two of those the Brit by JBK and a BAe by PAD. Mac

Pete, please find my current FSUIPC4.ini on THIS LINK. Cheers, Mac

Understood, thank you Pete. I have reported at LM and suggested that it would do us all a favour if they provided you with a pre-release.

Thank you Pete I will keep watching for updates. Cheers, Mac

Correction, I have now installed 4.851 but I still have the same problem in P3D only.

A rare chance to post and say thank you Pete for FSUIPC. My first little problem in over three happy years of using. I have 4.827 installed for FSX and P3D. My Flaps Axis is working OK in FSX but in P3D the flaps will only move between positions 2 and 3. I have compared .ini files and Axis Assignment settings and they seem to be the same. It was working OK in P3D Ver 1.3 and this error has only appreaed since I did a fresh install of P3D 1.4 and reinstalled FSUIPC. Help please.

Thanks Pete. Bed time "down under". Will report tom oorw so this thread becomes useful to others. Cheers, Mac

Pete, those are the paths of the FSUIPC 'ini' files according to Win 7 Search. I have now deleted my "backup" copy of FSX from the G:\ drive. So there is an FSX installation on C:\ and P3G installation on G:\ Ther are FSUIPC.ini files (one only in each) at C:\ Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules AND G:\ Program Files (x86)Lockheed Martin\Prepar3D\Modules Mac

Thanks Pete. A little clarification. I have managed to wind up with three 'ini' files. The FSX installation is on drive C\: and the P3D installation on G:\ The paths of the three 'ini' C:\ Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X G:\ Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X G:\ Program Files (x86)\Lockheed Martin\Prepar3D It seems as though my problem is the second entry or the second FSX 'ini' file on the G\ drive? Mac