Sandro Grohe Posted July 29 Report Posted July 29 Hi, if there are Button-Numbers greater 31 (example A,32 in line 1004), there is an error message. I have tried all version 7.4.16 to 7.4,12. The described behavior is the same. Can you help me? Best regards, Sandro Grohe [Buttons.PMDG 777] 1001=PA,13,K67,9 -{Key press: lshift+C}- 1002=PA,14,K35,8 -{Key press: End}- 1003=PA,15,K76,24 -{Key press: lalt+L}- 1004=CR(-A,32)B,18,C65758,0 << ERROR 15! Line ignored >> 1005=CR(-A,31)B,17,C65759,0 -{FLAPS_DECR}-
John Dowson Posted July 29 Report Posted July 29 That is very strange...can you please show me/attach your FSUIPC7.ini file. Why are your index numbers starting at 1001? This shouldn't cause issues, but you should start from 1 or 0 really. I can add that line to my button assignments and I don't get an error, so something else must be going on.... John
John Dowson Posted July 29 Report Posted July 29 Ah, its ok - I can see the issue now. Looks like compound button conditions have not been updated to use button numbers > 31. I will look into this and hopefully provide you with a new version to test, most probably tomorrow now. John
John Dowson Posted July 29 Report Posted July 29 Ah... there is no such button number as 32. Well, there is, but button numbers 32-39 are POV buttons and have a special meaning. For other buttons > 31, you need to add 100, so try button number 132. The easy way to check way the button number is is to see what is registered in the button assignment UI panel when you press the button - use that number. John
Sandro Grohe Posted July 29 Author Report Posted July 29 Thanks. Does it mean, POV buttons are not allowed?
John Dowson Posted July 29 Report Posted July 29 6 minutes ago, Sandro Grohe said: Does it mean, POV buttons are not allowed? Probably not...but buttons 32-39 that are not POV buttons should register as 132-139. So, as I said, try 132 - or see what the button you are trying to use is registered as in the button assignments panel.
Sandro Grohe Posted July 29 Author Report Posted July 29 (edited) The buttons are displayed as 32 to 39 in the button assignment panel. Buttons 132 to 139 do not work. Starting with Line 1001 ist to distinguish between my PMDG 737 and PMDG 777 in the config-File. Is there a better best-practice to navigate in the config-file? Sandro Edited July 29 by Sandro Grohe
John Dowson Posted July 29 Report Posted July 29 8 minutes ago, Sandro Grohe said: The buttons are displayed as 32 to 39 in the button assignment panel. Buttons 132 to 139 do not work. If they are displayed as 32-39, then they are POV buttons. You cannot currently use these for button conditionals. I could maybe allow this, but it has always been like this, so probably for a good reason. I could look into changing this, but probably better if you could use other buttons. Seems strange to use the POV for button conditionals... 10 minutes ago, Sandro Grohe said: Starting with Line 1001 ist to distinguish between my PMDG 737 and PMDG 777 in the config-File. Is there a better best-practice to navigate in the config-file? But why do you need to distinguish? If they have separate profiles, which they should, then it is the profile that distinguishes them. If you have a lot of profiles or want to distinguish them easily, switch to using profiles-in-separate-files, by setting: UseProfiles=Files in the [General] section of your FSUIPC7.ini. This will then create a separate Profiles folder under your FSUIPC7 installation folder, and each profile will be written to a separate file. The main FSUIPC7.ini file will still contain the [Profile.xxx] sections. John
Sandro Grohe Posted July 29 Author Report Posted July 29 Hi John, so I will avoid the POV-buttons Thanks for the hint to use separate files for each profile. Sandro
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now