Braudoux

Hello John, All good now, thanks you very much. This experience made me understand better the structure of the INI file. Still not quite sure controllers are repeated 3 times in the [JoyNames] section... For example the MIAP is referenced as A, 1 and D. The same goes for the other 2 controllers... Anyway that works and I will upgrade to 6.2.2 version. Best regards and thanks again Bruno

Hello. Nope, I have no other software than FSUIPC... Then I have followed the checklist above: run the removeDevices software, Restarted my computer Launched P3D and loaded a scenario with C130 Exited the simulator. Here are the 3 files FSUIPC6.log FSUIPC6.ini FSUIPC6.JoyScan.csv

Dear John I have proceeded to the correction as per your advice. This is what I have set in the para [JoyNames] [JoyNames] AutoAssignLetters=Yes A=SAITEK PRO FLIGHT X-55 RHINO THROTTLE A.GUID={E94396F0-E721-11EB-8004-444553540000} B=MIAP STD << MISSING JOYSTICK >> B.GUID={4981D2D0-E40F-11EC-8001-444553540000} F=Saitek Pro Flight X-55 Rhino Throttle F.GUID={E942D3A0-E721-11EB-8002-444553540000} All assignments attached to F correspond to the joystick in fact. After launching P3D, my MIAP controller is still not detected, as specified earlier, despite it is detected by P3D itself. In the new FSUIPC.ini (attached): the system created [1] and [0], generating new duplicates again. a message shows that [E] is missing. [B] is declared MISSING I did not unplug any device. When I go to the configuration tool, any button I click on my MIAP are not detected. So I don't know what to do 😞 Regards FSUIPC6.log FSUIPC6.ini FSUIPC6.JoyScan.csv

Hello John, I reinstalled FSUIPC and it solved the problem of starting with P3D. So now I need to resolve the duplicates in the Joysticks Names. In order to test my MIAP controller with FSUIPC, I shut down P3D and deleted the FSUIPC.ini file. After relaunching P3D, I opened the new FSUIPC file and noticed that the controller is not detected (not listed). The same controller is detected by P3D itself and is reacting to the presets. Is it possible that the bindings set in P3D are preventing FSUIPC to detect the MIAP controller? Find attached the required files. FSUIPC6 (after reinstal).ini FSUIPC6 (after deletion).ini FSUIPC6.log

Thanks John. After modifying the ini file as per your suggestion, I am facing now a new issue: FSUIPC doesn't start (FSUIPC not availale in Add-ons menu in P3D). I might have done something wrong, for sure. I attach the FSUIPC6-copy.ini file which is the original file before modification, the FSUIPC6.ini file after modification and the FSUIPC6.log. Please note that the later was not modified since the program did not start, so it is the latest log file before I touch anything, I'd like to add that, for testing purpose, I have deleted the FSUIPC6.ini file and restarted P3D. expecting that a new .ini file would be created but nothing happened. Thanks again for your help Regards Bruno FSUIPC6 - Copy.ini FSUIPC6.ini FSUIPC6.log

Hello, My controller AXAIR is no longer recognized by FSUIPC, whatever USB I use on the computer. While checking the FSUIPC6.ini file, I noticed that there are twice the same reference and I suspect that it is the origin of the problem. Could you confirm? [JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Throttle A.GUID={E94396F0-E721-11EB-8004-444553540000} E=Saitek Pro Flight X-55 Rhino Stick E.GUID={E942D3A0-E721-11EB-8002-444553540000} B=MIAP STD B.GUID={4981D2D0-E40F-11EC-8001-444553540000} C=MIAP STD C.GUID={E942D3A0-E721-11EB-8002-444553540000} D=Saitek Pro Flight X-55 Rhino Stick D.GUID={E9436FE0-E721-11EB-8003-444553540000} Thanks in advance Regards Bruno

All good, thanks John for quick assistance. Cheers

Hi John, Here they are... I will wait for your confirmation prior to running the above solution. For info, only the macros [Select AA Weapon] and [Radar Range] are active, the others have been removed from the Modules folder... ThanksFSUIPC6.logFSUIPC6.iniFSUIPC5.ini

Hello, I have upgraded my FSUIPC to version 6 for my P3Dv4.5. I discovered that my macros and controllers settings were not transferred to the new FSUIPC. I tried to modify the FSUIPC6.ini file but my sim crashed. So I reverted to initial ini file. Is there a way to recover the macro and control setting that was existing in the version 5: And if yes, how to do it please... Thanks Bruno

Hello, I could do the job 🙂... I was really disappointed by the UI of this feature. It was not obvious to me that I had to type the name of the macro within the black panel on top... II could not set 2 macros within the same the same file because only the latest command was recorded in the file. So I did 2 separate macros/files for Range Plus and Range Minus. So I did learn something useful with the Mouse Macro. Thanks for your help. Best regards Bruno

It is said: If OK enter a name,(else press ESC)... but I was not presented a box to enter a name. The windows closes immediately 🙂

I can see these displays. I told you that the macro works when I test it with the TAB key.

Sorry nut I could see only one field where I was ask to enter a name at the beginning of the process. Will try again 😞

Yes and that is what I call the Macro name: RDR RANGE UP. This because I assume that I need to create another macro for the range down

It is the name of the macro... I don't know how to set the name of the file. Also I was assuming that the name of the macro and the file are the same. Yes as per explained in the document...

Hello John, I could find the console. I did what you suggested, monitoring the events. I was able to see many events related to flaps, views, NAV2 set etc... but no event is logged when I modify the radar range scale. Therefore, I decided to go for Mouse Macro. I have proceeded as explained in the Manual but face the following issues against the expected result: I created the macro with name "RDR RANGE UP". The TAB action to control the macro is okay. Then I click OK. The macro with the name is not available in the list of "Control sent when button is pressed" There is no file created with .MCRO anywhere in my computer (search *.mcro) So yes, the process of creating a mouse macro is easy, but I am stuck in the middle of the process. Did I forget anything? Was I wrong somewhere? I have attached my .log and .ini files... Regards Bruno FSUIPC5.ini FSUIPC5.log

Hello John, I did that because the TAB and ENTER buttons are not recognized when I press them... Now, thanks to your latest explanations, I have understood and successfully set my 2 buttons. Thanks for your patience but keep in mind that what is obvious for you is not always the same for us... Cheers Bruno

Hello John, Why do you take it bad... I am willing to try but only if I understand what it is about... I spent an hour looking for "logging console" and "listing lvar" on Google and could not find anything match... Is your last statement {it is not difficult - just go to the logging tab and select the appropriate options.} referring to FSUIPC software? Regards

Thanks John for your reply. Unfortunately I do not understand anything in logging console, LVARS and LUA scripts and stuffs like that... Unless there is a friendly for me to understand, I will forget. But really this would be helpful because it is tough to change the scale during a merge... Bruno

Hello, I am trying to assign 2 actions to buttons of my throttle using the technique explained in the Advanced Manual (Format of buttons definition). I am not a developer and all these things are not familiar to me. I want to assign the TAB key to a button and the ENTER key to another one. After some studies, I wrote the following statements in the FSUIPC5.ini file but expected actions are not occurring: 16=P7,13,K,4 -{Shifts: TAB}- As there is no Key press, I have left K with no data... Is that correct? 20=P7,14,K13,8 -{Key press: ENTER }- This one looks correct regarding the syntax but it does something else (full throttle...) The statements in {...} are entered manually by me. Can someone help me fixing this? Thanks Bruno

Hello, I am flying Metal2Mesh M2000 on P3Dv4.5. I would like to be able to change the radar scale of my radar. Ranges are preset to 10/20/40/60. A button UP and a button DOWN would be lovely on my X55 controller throttle. Which command can do the job in the list of existing ones? If not, how to proceed? Thanks in advance Bruno

As final confirmation and after few flights, everything is fine now with my throttle, including the Windows calibration that is now also available... thanks John again. cheers Bruno

Hello John, I think that you made my day 🙂 After editing the .log file with your proposed text, all seems to be fine now. Event the calibration through W10 is now possible, both calibration panels are available... I just mad a quick flight to validate m settings and everything is good. I will keep the system under observation for some time. I will shut down computer and wake it up this afternoon to see if everything is solid. Will keep you advised. Thanks again for your assistance Best regards Bruno

Hello, Yes, files after id changes. Done as I get used to 🙂 Yes I found some entries after typing SAITEK. See attached file {Entries SAITEK.png}. Entries deleted. Rebbot done and new search in Registry... but with search criteria VID_0738. I used this criteria because I saw the format during the first search. And then I found some other entries {Entries VID_0738.png}. But I CANNOT delete these entries. {Message Entries.png} Done in sequence. Noticed that my Stick is not detected and the throttle controller is linked to the aircraft joystick axis. I was using USB 3 but this time files are related to controllers connected to USB2 FSUIPC5.log FSUIPC5.ini FSUIPC5.JoyScan.csv

Good morning John, I was asleep when you replied, therefore I did not anything else than the above checklist. When I click here, I reach a page from Air Group 52 within which there is no link to download the software... But I could find something with the same name here, expecting that is is the same. I ran the program and swapped ID2 to ID1. The result in P3D is that none of the controllers reacts... FSUIPC5.log FSUIPC5.ini FSUIPC5.JoyScan.csv