49 minutes ago, Bobsk8 said:

I have worked on this update all morning. I only have two things I use FSUIPC paid version for,  When I press one joystick button, I want it to send a 0 key to my PF3 ATC program.  When I press the next joystick button I want it to send an X keypress.   My former version of FSUIPC does this perfectly. The new version will not. I have a backup of the older version on a Macrium drive, and if I reinstall the older version everything works perfectly. I run the update of the latest version, and the 0 and X  keypresses again are not transmitted to the ATC program, I have done this several times. I have even tried replacing the new ini file with the one that works, and still it doesn't work.  I cannot figure out why this doesn't work. I am going to post it on the FSUIPC forum. 

With none of your Macrium backup files loaded, does PF3 get the key strokes if you use the actual 0 and X keyboard keys?

Al

Edited March 22, 20233 yr by ark

53 minutes ago, ark said:

With none of your Macrium backup files loaded, does PF3 get the key strokes if you use the actual 0 and X keyboard keys?

Al

Yes, the keyboard keys work fine, so really all FSUIPC has to do is generate the 0 and X. The non updated version does this, the updated version does not. I suspect something was changed in the updated version that has screwed this up. 

Just now, Bobsk8 said:

Yes, the keyboard keys work fine, so really all FSUIPC has to do is generate the 0 and X. The non updated version does this, the updated version does not. I suspect something was changed in the updated version that has screwed this up. 

Maybe. I just tried a test by having a yoke button sent a keystroke to MSFS, and it worked. So all very strange. If seems like something may be trapping the 0 and X keystrokes from your joystick.

When you look at the FSUIPC7 buttons tab, does it show the 0 and X are being sent by the buttons?

Al

1 minute ago, ark said:

Maybe. I just tried a test by having a yoke button sent a keystroke to MSFS, and it worked. So all very strange. If seems like something may be trapping the 0 and X keystrokes from your joystick.

When you look at the FSUIPC7 buttons tab, does it show the 0 and X are being sent by the buttons?

Al

I am back on the old version now, about to start a flight. I made a log file for keypresses that FSUIPC forum wants to troubleshoot this issue. Hopefully he will come up with something. 

3 hours ago, Bobsk8 said:

I am back on the old version now, about to start a flight. I made a log file for keypresses that FSUIPC forum wants to troubleshoot this issue. Hopefully he will come up with something. 

When you load the old FSUIPC7 version, by any chance are you also loading a previous copy of PF3? If so, try the new FSUIPC7 with the saved Macrium copy of PF3.  I'm wondering if the copy of PF3 you are using with the new FSUIPC7 doesn't have hot keys defined in the same way the Macrium copy does.

Al

Edited March 22, 20233 yr by ark

1 hour ago, ark said:

When you load the old FSUIPC7 version, by any chance are you also loading a previous copy of PF3? If so, try the new FSUIPC7 with the saved Macrium copy of PF3.  I'm wondering if the copy of PF3 you are using with the new FSUIPC7 doesn't have hot keys defined in the same way the Macrium copy does.

Al

Hi, well it isn't a problem with PF3, because it works perfectly with the normal keyboard hotkeys.  All FSUIPC is doing when in the keypress mode is assigning a joystick button to a keystroke. It's been that way for years.  That is what the updated version wont do. 

It's one of those addons I have always avoided.

sp

 

1 hour ago, Bobsk8 said:

Hi, well it isn't a problem with PF3, because it works perfectly with the normal keyboard hotkeys.  All FSUIPC is doing when in the keypress mode is assigning a joystick button to a keystroke. It's been that way for years.  That is what the updated version wont do. 

Well, I have verified I can use buttons on my yoke and throttle to send keystrokes to MSFS, and hotkeys to TrackIR with SU12 and FSUIPC7.   And so far I have not seen any other problem reports of a similar nature which I would expect if there was a general problem.

Just as a test, see if you can use a button to send a keystroke to MSFS. For example, use a button to send a Z key to toggle an autopilot on and off. If that works, then we have narrowed the problem down a bit.

Might also be worth trying to use PF3 with a different aircraft to see if that makes any difference for some strange reason. Is your use of PF3 button assignments profile (aircraft) specific?

Al

Edited March 23, 20233 yr by ark

I don't even use it. What are the benefits ???

2 hours ago, Beagle12 said:

I don't even use it. What are the benefits ???

A bit off topic, perhaps, but as a quick overview, programs like SPAD.next, FSUIPC7, AAO, etc, can be used to make controller bindings that are not MSFS default bindings. For example, if you wanted to assign a key or button or knob to activate the wing deice boots on the Flysimware C414, you won't find a MSFS default binding that will do that because the developer used custom coding to implement that feature. Another example would be controlling the custom coded HJet throttles with your hardware. But you can use third party programs like the above to do this, because these programs let you access the variables the developer used to implement the custom code. 

You can also create scripts, little programs, to do special things. Just for example, you could develop a script that would let you enter a com or nav frequency, or target altitude, or nav course or heading, just by typing the digits on the keyboard numberpad rather than using the mouse to do the same things. Or you could write a script to manipulate a cockpit tablet, or to operate the switches on the aircraft's panel clock, or provide radar altitude callouts when landing for those aircraft that don't have that inherently implemented, etc.

The overall point being these types of addon programs help users, especially those with a variety of external hardware (e.g., cockpit builders), implement control bindings or other capabilities that are not sim accessible by default.  Certainly not everyone is interested in doing that.

To each their own.

Al

Edited March 23, 20233 yr by ark

3 hours ago, Beagle12 said:

I don't even use it. What are the benefits ???

In addition to what ark mentioned above, some external programs like Pilot 2 ATC or my VACARS program for my Virtual Airline I belong to, require it in order to communicate with the sim.

I personally try to stay away from programs that require FSUIPC. I don't like to be too depending on addons because things may go wrong after an update of the sim and what if the developer decides to call it a day...? I like to use MSFS as default as possible. And if I do use an addon I'd like it to be non dependant on another addon because that only makes the chain more complicated. I did buy FSUIPC some 20 years ago or so but actually never really used it: it just was THE program you had to have in those days for some reason LOL. I fly with a simple joystick and rudder pedals and so don't need it for that. I still have the idea some people buy FSUIPC because they think it's almost mandatory. It isn't.

7 hours ago, Beagle12 said:

I don't even use it. What are the benefits ???

This is a program that has been around for 20+ years for all versions of the old Microsoft flight sims and then P3D. It’s been described as the Swiss Army Knife for flight simming. It’s been the best seller on SimMarket for years.

One enormous benefit is the AutoSave function. If your sim CTD you could reload the flight from the last save. I don’t have MSFS so don’t know if that function is available.

Being able to assign any command to a button for any aircraft is very useful. Anyone who had those older sims invariably found it a indispensable utility. Many more features too.

Thanks Ray 🙂

2 hours ago, Ray Proudfoot said:

This is a program that has been around for 20+ years for all versions of the old Microsoft flight sims and then P3D. It’s been described as the Swiss Army Knife for flight simming. It’s been the best seller on SimMarket for years.

One enormous benefit is the AutoSave function. If your sim CTD you could reload the flight from the last save. I don’t have MSFS so don’t know if that function is available.

Being able to assign any command to a button for any aircraft is very useful. Anyone who had those older sims invariably found it a indispensable utility. Many more features too.

Funny thing: I remember now using FSUIPC a short time for that autosave function indeed...! Unfortunately that function has no use in MSFS where all the planes I fly can't be saved in midair... which btw is a big shame. 😉

Anyway, the fact that it is the best seller probably is because it's the only addon that has been for sale that long LOL I know a lot of flightsimmers regard FSUIPC as the best thing since sliced bread but while that may have been the case a long time ago (FS2004, FSX, P3D) it certainly isn't the case with MSFS. A Swiss Army Knife can do a LOT of different things but in MSFS I do think FSUIPC is only used for control assignements and er... that's about it. I'd called that a basic run of the mill knife. Correct me if I am wrong and missing something utterly cool! 😉