paddler

Hi Thomas, Thanks for the suggestion, but there was no change. The screen remained black though switching to windowed mode allowed me to use the escape key to bring back the sim. It didn't when in full screen mode. Rick

I have a registered copy of FSUIPC 6.08 and am using the latest update for P3D v5. I also use a PFC C2 Professional Console and MFG Crosswind pedals. P3D loads fine and all controls for the rudder, except toe brakes, throttles and yoke perform well. However the toe brakes are not working and so I click on FSUIPC add-on on the P3D menu bar to set brakes. When I do the screen goes black. The sim continues to function in that I can still hear the engine etc but the FSUIPC screen does not show on the black screen. I also have P3D v4.5 HF2 and this also happens in that version. Last week there were occasions when I could get the setup FSUIPC screen to show and then try to set axis but they would no take. I have settings from before and thus my FSUIPC6.ini file includes those but it did not display on the screen when it did appear last week. This happens with P3D planes and A2A 172 Trainer in both sims. Thank you for any help. Rick FSUIPC6.log FSUIPC6.ini

Pete, Thank you. I had not scrolled down the page to see The Additional Free Software. Regards Rick

Hello John, I am running both P3Dv4.5 and v5. I downloaded and installed a paid version of FSUIPC 6 installing it for both P3D versions using a default install. I use a Precision Flight Controls C2 Professional console. It has always worked with FSUIPC 5 in P3Dv4.5 but is no longer recognized for axis assignment in FSUIPC. Have I missed installing something? Thanks. Rick

John and Pete, Thanks for the the upgraded program. Rick

Pete, Ack, and thanks for the advice. Rick

Pete, Thank you for the very quick response. I currently have a mixture of profiles. In some cases I have an aircraft specific profile (MilViz Beaver) and in other cases aircraft type (Single engine prop). I am using a PFC C2 Professional console with several different throttle quadrants and I now understand that if I set up aircraft type profiles (single engine prop / single engine turboprop etc) that FSUIPC will automatically keep axis assignments and calibrations for each throttle quadrant eliminating the need for me to re-calibrate using the PFC calibration program each time I change the throttle quadrant on the console. That being the case I want to set up only aircraft type profiles and assign aircraft to them and thus eliminate aircraft profiles. Having thought about it again, I may be best off deleting my whole INI file and starting from scratch with a clean one to avoid any "legacy" issues if I don't delete fully some profiles. What do you advise as the safest option for a non programmer like me? If starting over do I just delete the whole FSUIPC5.INI from the Modules folder and run P3D to regenerate it again without the profiles? Thanks again. Rick

I have a Registered copy of the latest version of FSUIPC. I have just converted my INI file from "use profiles =Yes" to "use profiles = files". If I want to delete a profile do I need to delete if from both the INI file and the sub folder or just one? Thanks for your help. Rick

John, Great, thank you. I am beginning to understand FSUIPC5 a little better now, bit by bit.

I recently re-installed my flight sim and OS. After installing FSUIPC I then wanted to make it easier to deal with Win 10 updates that have a tendency in the past to change the number assignments ( top of page 21 in the manual) and thus I changed {JoyNames} to AutoAssign letters. So my FSUIPC5.ini file now looks like this below with both number and letter assignments. Is this the way it should look or should I delete the number assignments and just leave the letter assignments? [JoyNames] AutoAssignLetters=Yes 0=PFC Cirrus II Pro 0.GUID={0E566030-DA0A-11E8-8007-444553540000} 1=MFG Crosswind V2 1.GUID={0E568740-DA0A-11E8-8008-444553540000} 2=Logitech G13 Joystick 2.GUID={8A513DA0-FCAA-11E8-8003-444553540000} A=PFC Cirrus II Pro A.GUID={0E566030-DA0A-11E8-8007-444553540000} B=MFG Crosswind V2 B.GUID={0E568740-DA0A-11E8-8008-444553540000} C=Logitech G13 Joystick C.GUID={8A513DA0-FCAA-11E8-8003-444553540000}

Pete, Bought FSUIPC5 from SIMMARKET 2107-06-04 and have only downloaded subsequently from this support forum. I trust that these are both authorized. if not please advise. Rick

Pete, Upgraded to P3D4.4 as indicated in my initial post. The manual I referenced I printed from the last download when I was using P3Dv4.3 I believe, and I obviously didn't key on the date of the latest v5.15 download manual included therein. I probably had the thought in mind that there would be very minimal changes in the manual with a minor change in the P3D4 versions vice a new P3Dv5. Rick

Pete, The manual I am using is "FSUIPC5: Application interfacing module for Lockheed-Martin's Prepar3D version 4" dated 1st June 2017. Version 5.102 of FSUIPC.dll. The reference is top of page 23 titled "PFC equipment controlled by PFCP3D.DLL" and the comment is on the first line. Is there a more updated copy that I should download? Thanks again for helping those of us who are strictly computer users and who understand little of the programming or terminology behind the magical workings. I fear that there are many like myself.We get great enjoyment from our simulators and I appreciate the software that you have created. Rick

Pete, My bad, I just used the download file name which holds both drivers and do understand that I only need the PFChid64.dll in the P3D Modules folder. I just tried a flight and it appears to be working fine with the PFC Console. Now I need to learn more of the FSUIPC capabilities for managing Profiles and Joystick naming etc. I am sure that I will have another question or two. On page 23 of the Manual you do mention a forthcoming PFCP3D.DLL for PFC equipment. Is that something that will be downloadable in the future? Thanks again. Rick

Pete, Thanks, as I understand then only copy the PFCHID into the Modules folder. Can you enlighten me about this PFCP3D.DLL please. At the moment I can't get FSUIPC to recognize my Cirrus II console for axis calibration. P3D recognizes the console as being present but FSUIPC doesn't respond to it. Thanks.

Recently I had a full OS failure and thus needed to reinstall all my programs complete. I am using Win 10 latest update, P3D v4.4 clean install, new download of FSUIPC5.15 registered copy.. My Precision Flight Controls C2 Professional Console is about 5 years old, USB connection. I am not sure which other files I need to download and place in the P3D Modules folder to be able to use and configure this console. Can I use PFCFSX+PFCcom64 or PFCHID? In the FSUIPC Manual you identify a PFCP3D4.DLL, but I don't see where to download it. Previously when I got my console none of the axis and buttons showed on FSUIPC and were no then programmable by me. They showed up in the supplied PFC calibration and test program, though some such as Tank Select didn't appear to work properly. It sounds as if this new DLL would be good to have. Thanks for any help. Rick

Mad Dog here, :???: PFC documentation and support is light to say the least ( would almost non-existent fit). I would need to pay for any support / advice so I rely heavily upon what scant documentation is available. I downloaded the PFCFSX as I believed, in the absence of any documentation, that as P3D is FSX based that it was relevant. I have no idea what "pfcfsx.dll" is, it appeared in the modules folder. So why PFCFSX was installed statement told me they were not required so I deleted all PFCFSX from the P3D modules folder. That then leaves only the PFChid.dll; PFChid config settings; PFChid text doc; and PFCmacroIndex.csv. Obviously I have very limited knowledge and skill with computers so need any help/advice possible. Thanks again for your help Pete, appreciate your patience and attention to this. Rick

Using P3D V3.2 PFC C2 Professional (USB) Win 10 Have following in P3D Modules folder: FSUIPC 4.94h pfcfsx.dll PFCFSX 4.410 PFChid.dll PFCmacroIndex.csv SimConnecP3D2.dll Problem: P3D Loads with scenario but within 10 seconds a screen appears "PFC Controls Connection Check" and stops at "COM serial Port port connection - none". I select continue FS and flight loads. I select Addons - PFC and the screen identifies " PFC equipment handled by this driver must be connected to a serial port (COM port) or USB port which has been made to look like a COM port by a separate driver". On the PFC site I see there is a Serial Device driver for FSX that will load PFC.DLL 4.376 /FSUIPC 4.706. Is this the solution to my problem? If so do I just download and install with everything else or must I remove something from the P3D Modules folder? Is there a different solution? I use FSUIPC for all of my varied controls. I did not have this problem using Win 7, FSX and the older PFChid. Would the old PFChid solve the issue? Thanks for your help. Rick