All Activity
- Past hour
-
Sorry - these are't new and are already available.
- Today
-
John Dowson started following TUG Offset status and [P3D] Fouga Magister Fuel Dump Problem with FSUIPC6
-
That log is not available for some reason (I will delete the post shortly). Please also provide the log files for both FSUIPC5 (where it is working) and FSUIPC6 (where it isn't). Please also make sure that you have enabled logging for Events. As this is a freeware aircraft, I can also install and take a look. Could you let me know how to reproduce this problem - and quickly if possible. This may take me a while however as I recently suffered a severe crash and have had to re-install Windows. I haven't re-installed P3Dv4 yet - I will do this over the weekend. John
-
I don't think those offsets are working to control pushback. The state is reported correctly, but writing to the offsets does not trigger pushback. To trigger pushback, use the Toggle Pushback event. Not sure about controlling the heading or speed at the moment. There are 2 new sim event that I will add and test - Tug Heading and Tug Speed. I have tested Tug Heading here and that seems to control the direction once pushback is initiated. However, generally it seems pushback is controlled by the Ground services in MSFS. Also, more complex add-ons tend to use either the FlyPad/EFB or FMC to control pushback. They may also respond to the standard controls, but also these may not work for such aircraft. I will test/check this in a few complex aircraft - maybe the PMDG 737, FSLabs A321 and the FBW A321. I will add those 2 tug control events and look into this on more details, and maybe update those offsets to use these new control. But this will be after the next patch release of FSUIPC7. maybe next week... John
-
Hello I'm doing a new post about my problem with FOUGA MAGISTER of https://restauravia.fr/ In fact, under P3D4.5, there is a problem with FSUIPCv6, but it is working with FSUIPCv5 : I filled all three fuel tanks, but when the two wing tanks are empty, the engines shut down while the main tank is still full. With fsuipc5, it is working. https://forum.simflight.com/topic/99621-which-is-the-best-version-of-fsuipc-for-p3dv45/ https://www.pilote-virtuel.com/viewtopic.php?id=108503 I will try to give you a LOG but, not sure to know how to do it... Thank you very much Stephane
- Yesterday
-
MSFS2024 Multiple Commands Single Button Help (PMDG77W)
mpochylko replied to mpochylko's topic in FSUIPC7 MSFS
The file you sent seems to work perfectly as is!!! Thank you. If I have any issues I will look at the my events file. Thanks again. -
I have no idea what that is or where its from.
-
DaveSCUSA started following TUG Offset status
-
The TUG_HEADING and TUG_SPEED controls are listed in the FSUIPC7 Offsets Status document. The status of the Pushback was Read Tested. Would it be possible to test the other controls? I'm trying to emulate pushback and tug controls with buttons. There is a product "Toolbar Pushback" that performs the functions but requires screen space and mouse. I'm trying to get to a non-keyboard and non-mouse environment. Thanks
-
Nizednard joined the community
-
MSFS2024 Multiple Commands Single Button Help (PMDG77W)
John Dowson replied to mpochylko's topic in FSUIPC7 MSFS
For your landing light buttons (135 and 136), use the PMDG_B777_Landing_Light_All_On and PMDG_B777_Landing_Light_All_Off presets I showed you above. Presume you know how to define your own presets - if not, check the Advanced User guide, but basically you just need to add those preset definitions above to a file called myevents.txt (create this if not present in your FSUIPC7 installation folder). For the buttons that control the runway + taxi lights, define your own preset by combining the preset code from the other presets, e.g. PMDG_B777_Runway_Turnoff_Taxi_Light_All_Off#(L:switch_121_a) if{ 12101 (>K:ROTOR_BRAKE) } (L:switch_119_a) if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) if{ 12001 (>K:ROTOR_BRAKE) } PMDG_B777_Runway_Turnoff_Taxi_Light_All_On#(L:switch_121_a) ! if{ 12101 (>K:ROTOR_BRAKE) } (L:switch_119_a) ! if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) ! if{ 12001 (>K:ROTOR_BRAKE) } PMDG_B777_Runway_Turnoff_Taxi_Light_All_Toggle#12101 (>K:ROTOR_BRAKE) 11901 (>K:ROTOR_BRAKE) 12001 (>K:ROTOR_BRAKE) Otherwise, you could try adding a short delay after sending each preset. I have done this for you in the attached with a 25ms delay. If it still has issues, try increasing that. John FSUIPC7.ini -
I made a backup, so no problem here.
-
I don't understand this - I am on the exact same version of Security intelligence and get no issues, and have no allowed threats. Not sure what I can do - I already reported this to MS yesterday as I did get this, but was later fixed. Maybe you could report as well: https://www.microsoft.com/en-us/wdsi/filesubmission?persona=HomeUser Otherwise, just restore the blocked file - you may need to temporarily allow the threat (presume its Program:Win32/Wacapew.C!ml).
-
Same. It also gets deleted.
-
Strange - I am on the same version and don't get this. Also just ran a custom scan on it and it reorted no issues. Can you try the attached please: FSUIPC7.exe John
-
-
I also had that issue yesterday afternoon for a few hours. I reported to Microsoft, then updated my anti-virus definitions and now it seems ok. Could you try updating your anti-virus definitions and trying again.
-
MS Defender deletes this .exe file. I think I wait for the release.
-
MSFS2024 Multiple Commands Single Button Help (PMDG77W)
mpochylko replied to mpochylko's topic in FSUIPC7 MSFS
FSUIPC7.zip -
MSFS2024 Multiple Commands Single Button Help (PMDG77W)
mpochylko replied to mpochylko's topic in FSUIPC7 MSFS
John, Attached are the .ini and log files. I am not running a script or a macro. Overloading one switch via the .ini file. FSUIPC7.ini - Last week
-
Both FSUIPC5 and FSUIPC6 should be fine to use with P3Dv4.5. FSUIPC5 is closed for future development, and FSUIPCv6 has a few more additional features, and only FSIOPC6 supports P3Dv5 and P3Dv6. If you are experiencing issues with FSUIPC6 that are not present in FSUIPC5 then you should raise a support topic on this and I will look into it. Please provide logs with relevant logging enabled (most probably Events and Buttons & Keys), and if you have both FSUIPC5 and FSUIPC6 then logs from each would be usefult for comparison. John
-
vijidesign joined the community
-
Hello Peter, I have a question : I'm wondering what's the best version of fsuipc to use with P3Dv4.5, please? What does v6 bring over v5, actually ? I'm asking this because I'm using the Fouga Magister, which is experiencing fuel dump issues with fsuipc_v6, whereas everything works fine with v5. Thank you very much Stephane
-
kosoe joined the community
-
This should be fixed in the attached version, 7.5.4b. I will release this officially in the coming days. John FSUIPC7.exe
-
MSFS2024 Multiple Commands Single Button Help (PMDG77W)
John Dowson replied to mpochylko's topic in FSUIPC7 MSFS
It would help if you could attach your FSUIPC7.ini so I can see your assignments, and also maybe a log (with appropriate logging enabled: Buttons & Keys, Events and WAPI Debug level if using presets)) so that I can see what is happening . Are you using a (combined) presets for this assignment, using a macro or overloading your assignments? What you can try is dependent on what you are currently using. If using individual presets and have overloaded your assignments, you can try combining them to use one preset. Here are some combined presets for the 777, but I am not sure if they are valid for MSFS2020, MSFS2024 or both: //PMDG/B777 300ER/Lights PMDG_B777_Landing_Light_All_Off#(L:switch_22_a) if{ 2201 (>K:ROTOR_BRAKE) } (L:switch_23_a) if{ 2301 (>K:ROTOR_BRAKE) } (L:switch_24_a) if{ 2401 (>K:ROTOR_BRAKE) } PMDG_B777_Landing_Light_All_On#(L:switch_22_a) ! if{ 2201 (>K:ROTOR_BRAKE) } (L:switch_23_a) ! if{ 2301 (>K:ROTOR_BRAKE) } (L:switch_24_a) ! if{ 2401 (>K:ROTOR_BRAKE) } PMDG_B777_Landing_Light_All_Toggle#2201 (>K:ROTOR_BRAKE) 2301 (>K:ROTOR_BRAKE) 2401 (>K:ROTOR_BRAKE) PMDG_B777_Runway_Turnoff_Light_All_Off#(L:switch_119_a) if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) if{ 12001 (>K:ROTOR_BRAKE) } PMDG_B777_Runway_Turnoff_Light_All_On#(L:switch_119_a) ! if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) ! if{ 12001 (>K:ROTOR_BRAKE) } PMDG_B777_Runway_Turnoff_Light_All_Toggle#11901 (>K:ROTOR_BRAKE) 12001 (>K:ROTOR_BRAKE) If using a macro or overloading your assignments and sending multiple commands (one for each light), then you can also try adding a pause control (control number 1152) between sending each command (whether this is a preset, an event/control or an input event). John