target11 Posted January 12, 2023 Report Share Posted January 12, 2023 Hello I always do my aircraft profiles on a separate file. as I added a device, my key assignments changed. So I changed the key assignments manually in the file, and when I reload all buttons, the old assignments rewrite themselves in the file. For example the original line in the file is 0=HC,6,K113,8 -{Key press: F2}- I change it in the file to 0=HC,6,K113,8 -{Key press: F6}- I do reload all button, I open the profile file and I find the line in the file 0=HC,6,K113,8 -{Key press: F2}- hence my question he will look for this information or, to change this on his own thank you for your reply Link to comment Share on other sites More sharing options...
John Dowson Posted January 12, 2023 Report Share Posted January 12, 2023 Your ini files are re-written when you open the assignments window, so this will overwrite any changes you have made. If you want to manually edit an ini, open the assignments window first, make your changes and save the file, then click the reload button. John Link to comment Share on other sites More sharing options...
target11 Posted January 12, 2023 Author Report Share Posted January 12, 2023 Hello Thanks for your reply, I will try what you suggest. Have a good day Link to comment Share on other sites More sharing options...
target11 Posted January 12, 2023 Author Report Share Posted January 12, 2023 Hello No it always overwrites the file Link to comment Share on other sites More sharing options...
John Dowson Posted January 12, 2023 Report Share Posted January 12, 2023 13 minutes ago, target11 said: No it always overwrites the file No it doesn't... 1 hour ago, target11 said: 0=HC,6,K113,8 -{Key press: F2}- I change it in the file to 0=HC,6,K113,8 -{Key press: F6}- But you are not changing the key press - you are changing the automatically generated comment. To change the keypress from F2 to F6, you need to change K113 (F2)to K117 (F6). But I do not understand why you are doing this by editing the ini file - you should use the UI, especially if you do not fully understand what you are doing.... John Link to comment Share on other sites More sharing options...
target11 Posted January 12, 2023 Author Report Share Posted January 12, 2023 Hello because the definition of the keys have also changed because I added a device, for example the line on the old file was 3=HB,6,K117,8 -{Key press: F6}- and I manually transform it into 3=PC,6,K117,8 -{Key press: F6}- but as the file is overwritten each time, I will have to press each key and redefine the key combination. whereas if I could change directly in the file, save it, and do reload all buttons by taking the file without overwriting it would be easier. Link to comment Share on other sites More sharing options...
John Dowson Posted January 12, 2023 Report Share Posted January 12, 2023 Well, in your original comment, you were only trying to change the key, not the button/device. Anyway, it doesn't matter - you can delete the original assignment and create a new one. However, I guess its easier to do this by editing the ini if you have lots of assignments that you want to change. Anyway, I hope you understand what you need to do now to change assignments by editing the ini file... John Link to comment Share on other sites More sharing options...
John Dowson Posted January 12, 2023 Report Share Posted January 12, 2023 ...and you can always exit FSUIPC (not MSFS!), make the changes to the ini and then restart FSUIPC...! Link to comment Share on other sites More sharing options...
target11 Posted January 12, 2023 Author Report Share Posted January 12, 2023 Hello, I understood, but I wonder why it is not enough to make the changes in the file, which is very simple, takes very little time, rather than assigning each key and key combination again, as much as deleting the file and redo it, so I don't understand this way of doing duplicate work when there is a simpler way. But it is obvious that I would not redo all my profile files too much work for nothing. Just put a question it resumes it's information or, if we can get around it it will be simpler Have a good day Link to comment Share on other sites More sharing options...
target11 Posted January 12, 2023 Author Report Share Posted January 12, 2023 yes i tried it without success Link to comment Share on other sites More sharing options...
John Dowson Posted January 12, 2023 Report Share Posted January 12, 2023 39 minutes ago, target11 said: I wonder why it is not enough to make the changes in the file But you can....if you do this correctly, as I explained (i.e. with assignments window open, and change the assignment line, NOT the comment). I am now having difficulty understanding what your issue is or what you are doing... 41 minutes ago, target11 said: yes i tried it without success Are you saying that you edited the ini file with FSUIPC7 not running, and when you started FSUIPC7 your changes were ignores, and the original settings restored? Sorry, but that is just impossible. I am now confused as to what you are doing. I suggest you re-read this thread and try again. It really isn't that difficult. John Link to comment Share on other sites More sharing options...
target11 Posted January 12, 2023 Author Report Share Posted January 12, 2023 Hello it does not matter I will manage to find a solution, it is very possible that I explain my problem badly, it's just that I added a peripheral, so fsuipc took care of it, so the axes (for the example for the keys it was the same thing) were for example before I added the peripheral [Axis] RangeRepeatRate=10 0=BX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }- 1=BY,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 2=CZ,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }- 3=CR,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }- 4=CS,256,F,66382,0,0,0 -{ TO SIM: AXIS_SPOILER_SET }- after adding the device [Axis] RangeRepeatRate=10 0=CX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }- 1=CY,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 2=DZ,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }- 3=DR,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }- 4=DS,256,F,66382,0,0,0 -{ TO SIM: AXIS_SPOILER_SET }- so I manually changed BX to CX, BY to CY ..... and I wanted to do the same thing with the keys, but the file is overwritten each time, so you told me to change the assignments then to open buttons&switch assignments to do reload all buttons to take into account the new assignments but the file crashes then I tried to press a button perform a keyboard key done ok and it works. But then I wondered why we couldn't change the key assignments manually, I tried I close fsuipc to open it again but it takes the same old assignments, and the file is overwritten again and saves the old assignments, but you tell me that it is impossible, which is logical, but which I do not understand, so I'll see if I find a solution, by the way it's a clean install of win 11 msfs2020 and fsuipc 7.3.16. Good day Link to comment Share on other sites More sharing options...
John Dowson Posted January 13, 2023 Report Share Posted January 13, 2023 12 hours ago, target11 said: it is very possible that I explain my problem badly Well, your initial question was on how to change a keypress assignment to a button, which I explained how to do.... 12 hours ago, target11 said: it's just that I added a peripheral, so fsuipc took care of it, so the axes (for the example for the keys it was the same thing) were for example before I added the peripheral [Axis] RangeRepeatRate=10 0=BX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }- 1=BY,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 2=CZ,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }- 3=CR,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }- 4=CS,256,F,66382,0,0,0 -{ TO SIM: AXIS_SPOILER_SET }- after adding the device [Axis] RangeRepeatRate=10 0=CX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }- 1=CY,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 2=DZ,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }- 3=DR,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }- 4=DS,256,F,66382,0,0,0 -{ TO SIM: AXIS_SPOILER_SET }- I can't see how this can occur, unless maybe you connected the device with FSUIPC running and windows assigned the same id to the new device as an existing device, but this does not explain why B was changed to C an C was changed to D....but really this doesn't make sense to me.... 12 hours ago, target11 said: so I manually changed BX to CX, BY to CY ..... Rather than doing this, you should just switch the device letter mapping in the [JoyNames] section of your FSUIPC7.ini file. 12 hours ago, target11 said: but the file crashes What does this mean? Files can't crash... 12 hours ago, target11 said: I tried I close fsuipc to open it again but it takes the same old assignments, and the file is overwritten again and saves the old assignments, but you tell me that it is impossible, You need to exit FSUIPC, not close it. When you close it, it is still running in your system tray. If GSUIPC7 is not running, there is no way it can remember old assignments, as the assignments are saved in the ini files which you have modified, and so FSUIPC does not know what these were, which is why I say that this is impossible. As you are using profiles in separate files, do you have a profile file that you have not used yet which still has the original assignments? If so, we can test with that. Make a backup of it first, then load an aircraft with that profile, and see if the profile ini is re-written as you say your other profile file was. Then show me the two profile files (backup and re-written), as well as your FSUIPC7.ini and FSUIPC7.log files. John Link to comment Share on other sites More sharing options...
target11 Posted January 13, 2023 Author Report Share Posted January 13, 2023 Hello so on fsuipc 7.3.10 in fsuipc.ini the joystick assignments were [JoyNames] 0=Flight Rudder Pedals 0.GUID={13FDBA90-34E6-11EB-8005-444553540000} 1=Joystick - HOTAS Warthog 1.GUID={13FDBA90-34E6-11EB-8006-444553540000} 2=Throttle - HOTAS Warthog 2.GUID={13FDBA90-34E6-11EB-800A-444553540000} A=Flight Rudder Pedals A.GUID={13FDBA90-34E6-11EB-8005-444553540000} B=Joystick - HOTAS Warthog B.GUID={13FDBA90-34E6-11EB-8006-444553540000} C=Throttle - HOTAS Warthog C.GUID={13FDBA90-34E6-11EB-800A-444553540000} D=Logitech G13 Joystick D.GUID={96C6A660-4B9A-11EB-8003-444553540000} in version 7.3.16 they are [JoyNames] 0=Flight Rudder Pedals 0.GUID={3AE44B50-8D55-11ED-8001-444553540000} 1=Logitech G13 Joystick 1.GUID={3AE69540-8D55-11ED-8007-444553540000} 2=Joystick - HOTAS Warthog 2.GUID={3AE69540-8D55-11ED-8009-444553540000} 3=Throttle - HOTAS Warthog 3.GUID={3AE90640-8D55-11ED-800E-444553540000} A=Flight Rudder Pedals A.GUID={3AE44B50-8D55-11ED-8001-444553540000} B=Logitech G13 Joystick B.GUID={3AE69540-8D55-11ED-8007-444553540000} C=Joystick - HOTAS Warthog C.GUID={3AE69540-8D55-11ED-8009-444553540000} D=Throttle - HOTAS Warthog D.GUID={3AE90640-8D55-11ED-800E-444553540000} I had removed the G13 between the two versions, then I put it back why such a change I do not know. when I spoke of key in version 7.3.10 it was defined as such 2=PB,8,K118,8 -{Key press: F7}- in version 7.3.16 they are defined as such 2=PC,8,K118,8 -{Key press: F7}- so I just wanted to change 2=PB to 2=PC I just had to click on a button on the joystick to know the letter to change, it was simple same thing for axes in version 7.3.10 0=BX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }- in version 7.3.16 0=CX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }- I just had to move an axis to know which letter to change 0=BX through 0=CX again I do not understand why these letters have changed. I wanted to keep it simple, but it became complicated. Again when I said close the program I did exit program so it was no longer in function, but when restarting FSUIPC it resumed the old assignment, I agree with you that makes no sense. I gave up, I'll watch it with my head rested. Have a good day Link to comment Share on other sites More sharing options...
John Dowson Posted January 13, 2023 Report Share Posted January 13, 2023 You should really attach your FSUIPC7.log file as well - this is always needed for joystick scanning issues. And also please attach your full FSUIPC7.ini, and not just paste segments. It is a lot easier for me to tell what is happening if I see your full files rather than extracts. In future, please do this... 2 hours ago, target11 said: so on fsuipc 7.3.10 in fsuipc.ini the joystick assignments were [JoyNames] 0=Flight Rudder Pedals 0.GUID={13FDBA90-34E6-11EB-8005-444553540000} 1=Joystick - HOTAS Warthog 1.GUID={13FDBA90-34E6-11EB-8006-444553540000} 2=Throttle - HOTAS Warthog 2.GUID={13FDBA90-34E6-11EB-800A-444553540000} A=Flight Rudder Pedals A.GUID={13FDBA90-34E6-11EB-8005-444553540000} B=Joystick - HOTAS Warthog B.GUID={13FDBA90-34E6-11EB-8006-444553540000} C=Throttle - HOTAS Warthog C.GUID={13FDBA90-34E6-11EB-800A-444553540000} D=Logitech G13 Joystick D.GUID={96C6A660-4B9A-11EB-8003-444553540000} in version 7.3.16 they are [JoyNames] 0=Flight Rudder Pedals 0.GUID={3AE44B50-8D55-11ED-8001-444553540000} 1=Logitech G13 Joystick 1.GUID={3AE69540-8D55-11ED-8007-444553540000} 2=Joystick - HOTAS Warthog 2.GUID={3AE69540-8D55-11ED-8009-444553540000} 3=Throttle - HOTAS Warthog 3.GUID={3AE90640-8D55-11ED-800E-444553540000} A=Flight Rudder Pedals A.GUID={3AE44B50-8D55-11ED-8001-444553540000} B=Logitech G13 Joystick B.GUID={3AE69540-8D55-11ED-8007-444553540000} C=Joystick - HOTAS Warthog C.GUID={3AE69540-8D55-11ED-8009-444553540000} D=Throttle - HOTAS Warthog D.GUID={3AE90640-8D55-11ED-800E-444553540000} I had removed the G13 between the two versions, then I put it back why such a change I do not know. I really can't understand how the joystick letters have changed...but, rather than changing your assignment lines, why not just change the letter mapping back to the original mapping: Quote A=Flight Rudder Pedals A.GUID={13FDBA90-34E6-11EB-8005-444553540000} B=Joystick - HOTAS Warthog B.GUID={13FDBA90-34E6-11EB-8006-444553540000} C=Throttle - HOTAS Warthog C.GUID={13FDBA90-34E6-11EB-800A-444553540000} D=Logitech G13 Joystick D.GUID={96C6A660-4B9A-11EB-8003-444553540000} ? 2 hours ago, target11 said: when I spoke of key in version 7.3.10 it was defined as such 2=PB,8,K118,8 -{Key press: F7}- in version 7.3.16 they are defined as such 2=PC,8,K118,8 -{Key press: F7}- so I just wanted to change 2=PB to 2=PC But it is already PC (as written), so nothing to change...or was it PB, as in 7.3.10, and you want to change this to PC as the mapping has changed? If so, that should be ok, but better to change the mapping back to the original mapping. I think you are confusing me as it is you that are changing the assignment letters to match the new mapping, not FSUIPC which is what I previously understand and also understand when you say 'in version 7.3.16 they are defined as such'. 2 hours ago, target11 said: I do not understand why these letters have changed. Nor do I... 2 hours ago, target11 said: I wanted to keep it simple, but it became complicated. I think you are over-complicating things... The mapping should not change, but if it has, as you say, then why not just change the mapping back, as I keep saying? 2 hours ago, target11 said: Again when I said close the program I did exit program so it was no longer in function, but when restarting FSUIPC it resumed the old assignment, I agree with you that makes no sense. Have you installed in a windows protected folder, or one that is using OneDrive or other cloud-service for back-up restore? Otherwise, this really can't be possible. Are you sure you are opening/editing the files from the correct location - try using the File -> Open Installation Folder... menu option to confirm. Your FSUIPC7.log and FSUIPC7.ini files will be there, and your profile files under the Profiles folder. If you want any further assistance with this, PLEASE attach all of your full files: FSUIPC7.log, FSUIPC7.ini, and your profile .ini file. If you have back-ups of the original files, why not restore those and try again.... It seems to me the only issue is that the manual changes you are making to your ini file get reset when you start FSUIPC7 - is this the case? As I said, and as you understand, this is impossible - there is no way that FSUIPC7 can know what your old settings were, it just reads and then re-writes your ini files. Maybe you have duplicated sections? But I can't really tell or help you any further unless you show me attach your full files - I don't understand why you are not showing me these, as I have asked. So, if you want any further assistance, please attach all of the file - FSUIPC7.log, FSUIPC7.ini and your profile .ini files. John Link to comment Share on other sites More sharing options...
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