Jump to content
The simFlight Network Forums

Unable to Manually Edit & Save FSUIPC6.ini


Recommended Posts

I've performed a clean install of my OS and Flight Simulation applications and the last task I need to complete is configuring my GNS 530 GPS device with FSUIPC.

I've backed up a copy of my FSUIPC6.ini file for my GNS 530 that's running Reality XP as well as the RXP config. This maps RXP keys to the button keys in FSUIPC6.ini.

The issue I'm having which is a new one for me over the years with FSUIPC6 is that I need to update a few FSUIPC6.ini button entries to match my RXP configured keys. After I save my FSUIPC6.ini file (and confirm it's been saved by reopening it with the latest changes), I then start up P3D v5.3. When P3D v5.3 loads up, it reverts all my changes to what was in the FSUIPC6.ini file from before.

I'm not sure how FSUIPC6 is performing the config reverts and was hoping that someone could shed some light as to what's happening to my FSUIPC6.ini file when P3Dv5 starts. Is there some sort of cached options stores somewhere, or something else I'm missing? I don't recall this being an issue in the past when manually editing changes in the FSUIPC6.ini file.

I've included a copy of the JoyNames and Buttons section from both the in-game FSUIPC6.ini options as well as the options I've been trying to save. Let me know if there are other details needed from me or my FSUIPC configs.

These are the FSUIPC button settings I want configured, and have copied over to my in-game FSUIPC6.ini file.

[JoyNames]
AutoAssignLetters=Yes
A=CLSE NG Yoke
A.GUID={CCDFAA90-9026-11EC-8002-444553540000}
B=JAY Rudder
B.GUID={CCDFAA90-9026-11EC-8004-444553540000}
C=GarSim 530
C.GUID={CCDFAA90-9026-11EC-8005-444553540000}
0=CLSE NG Yoke
0.GUID={CCDFAA90-9026-11EC-8002-444553540000}
1=JAY Rudder
1.GUID={CCDFAA90-9026-11EC-8004-444553540000}
2=GarSim 530
2.GUID={CCDFAA90-9026-11EC-8005-444553540000}

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=PA,0,C65561,0 	-{PAUSE_TOGGLE}-
2=PA,1,C66653,0 	-{VIEW_COCKPIT_FORWARD}-
3=PA,2,C66654,0 	-{VIEW_VIRTUAL_COCKPIT_FORWARD}-
4=PA,4,C65906,0 	-{PANEL_1}-
5=PA,3,C66482,0 	-{TOGGLE_WATER_RUDDER}-
6=PA,5,C65567,0 	-{VIEW_MODE}-
7=PC,12,K112,11 	-{Key press: ctl+shft+F1}-
8=PC,0,K69,11 		-{Key press: ctl+shft+E}-
9=PC,13,K113,11 	-{Key press: ctl+shft+F2}-
10=PC,7,K74,11 		-{Key press: ctl+shft+I}-
11=PC,6,K73,11 		-{Key press: ctl+shft+J}-
12=PC,5,K76,11 		-{Key press: ctl+shft+O}-
13=PC,4,K85,11 		-{Key press: ctl+shft+N}-
14=PC,14,K78,40 	-{Key press: win+N}-
15=PC,16,K114,11 	-{Key press: ctl+shft+F3}-
16=PC,17,K115,11 	-{Key press: ctl+shft+F4}-
17=PC,18,K116,11 	-{Key press: ctl+shft+F5}-
18=PC,19,K117,11 	-{Key press: ctl+shft+F6}-
19=PC,20,K118,11 	-{Key press: ctl+shft+F7}-
20=PC,21,K119,11 	-{Key press: ctl+shft+F8}-
21=PC,10,K87,11 	-{Key press: ctl+shft+L}-
22=PC,11,K86,11 	-{Key press: ctl+shft+K}-
23=PC,8,K89,11 		-{Key press: ctl+shft+P}-
24=PC,9,K88,11 		-{Key press: ctl+shft+Q}-
25=PC,15,K77,11 	-{Key press: ctl+shft+M}-
26=RC,27,K66,11 	-{Key press: ctl+shft+B}-
27=RC,26,K65,11 	-{Key press: ctl+shft+A}-
28=PC,25,K123,11 	-{Key press: ctl+shft+F12}-
29=PC,24,K122,11 	-{Key press: ctl+shft+F11}-
30=RC,23,K121,11 	-{Key press: ctl+shft+F10}-
31=PC,22,K120,11 	-{Key press: ctl+shft+F9}-
32=PC,29,K67,11 	-{Key press: ctl+shft+.}-
33=PC,28,K117,11 	-{Key press: ctl+shft+,}-
34=PC,1,K68,11 		-{Key press: ctl+shft+D}-
35=PC,3,K71,11 		-{Key press: ctl+shft+G}-
36=PC,2,K72,11 		-{Key press: ctl+shft+H}-

 

These are the settings FSUIPC keeps reverting to when starting P3Dv5.

[JoyNames]
AutoAssignLetters=Yes
A=CLSE NG Yoke
A.GUID={CCDFAA90-9026-11EC-8002-444553540000}
B=JAY Rudder
B.GUID={CCDFAA90-9026-11EC-8004-444553540000}
C=GarSim 530
C.GUID={CCDFAA90-9026-11EC-8005-444553540000}
0=CLSE NG Yoke
0.GUID={CCDFAA90-9026-11EC-8002-444553540000}
1=JAY Rudder
1.GUID={CCDFAA90-9026-11EC-8004-444553540000}
2=GarSim 530
2.GUID={CCDFAA90-9026-11EC-8005-444553540000}

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=PA,0,C65561,0 	-{PAUSE_TOGGLE}-
2=PA,1,C66653,0 	-{VIEW_COCKPIT_FORWARD}-
3=PA,2,C66654,0 	-{VIEW_VIRTUAL_COCKPIT_FORWARD}-
4=PA,4,C65906,0 	-{PANEL_1}-
5=PA,3,C66482,0 	-{TOGGLE_WATER_RUDDER}-
6=PA,5,C65567,0 	-{VIEW_MODE}-
7=PC,12,K112,11 	-{Key press: ctl+shft+F1}-
8=PC,0,K69,11 	-{Key press: ctl+shft+E}-
9=PC,13,K113,11 	-{Key press: ctl+shft+F2}-
10=PC,7,K74,11 	-{Key press: ctl+shft+J}-
11=PC,6,K73,11 	-{Key press: ctl+shft+I}-
12=PC,5,K76,11 	-{Key press: ctl+shft+L}-
13=PC,4,K85,11 	-{Key press: ctl+shft+U}-
14=PC,14,K78,40 	-{Key press: win+N}-
15=PC,16,K114,11 	-{Key press: ctl+shft+F3}-
16=PC,17,K115,11 	-{Key press: ctl+shft+F4}-
17=PC,18,K116,11 	-{Key press: ctl+shft+F5}-
18=PC,19,K117,11 	-{Key press: ctl+shft+F6}-
19=PC,20,K118,11 	-{Key press: ctl+shft+F7}-
20=PC,21,K119,11 	-{Key press: ctl+shft+F8}-
21=PC,10,K87,11 	-{Key press: ctl+shft+W}-
22=PC,11,K86,11 	-{Key press: ctl+shft+V}-
23=PC,8,K89,11 	-{Key press: ctl+shft+Y}-
24=PC,9,K88,11 	-{Key press: ctl+shft+X}-
25=PC,15,K77,11 	-{Key press: ctl+shft+M}-
26=RC,27,K66,11 	-{Key press: ctl+shft+B}-
27=RC,26,K65,11 	-{Key press: ctl+shft+A}-
28=PC,25,K123,11 	-{Key press: ctl+shft+F12}-
29=PC,24,K122,11 	-{Key press: ctl+shft+F11}-
30=RC,23,K121,11 	-{Key press: ctl+shft+F10}-
31=PC,22,K120,11 	-{Key press: ctl+shft+F9}-
32=PC,29,K67,11 	-{Key press: ctl+shft+C}-
33=PC,28,K117,11 	-{Key press: ctl+shft+F6}-
34=PC,1,K68,11 	-{Key press: ctl+shft+D}-
35=PC,3,K71,11 	-{Key press: ctl+shft+G}-
36=PC,2,K72,11 	-{Key press: ctl+shft+H}-

 

Link to comment
Share on other sites

12 hours ago, Sea2Sky said:

The issue I'm having which is a new one for me over the years with FSUIPC6 is that I need to update a few FSUIPC6.ini button entries to match my RXP configured keys. After I save my FSUIPC6.ini file (and confirm it's been saved by reopening it with the latest changes), I then start up P3D v5.3. When P3D v5.3 loads up, it reverts all my changes to what was in the FSUIPC6.ini file from before.

Why are you updating your ini manually? You should be updating your button assignments using the FSUIPC UI panel for this.
If you want to do this manually, you need to know what you are doing. It seems that you are just updating the comments/annotations, and not the actual keys that are being sent (i.e. the assignment itself). The comments will get re-written, based upon the actual assignments. You cannot just change the comment and expect the assignment to change.

John

 

Link to comment
Share on other sites

Hey John, thanks for the speedy reply.

The idea was not have to update the ini file manually, but to back it up and have the ability to restore FSUIPC6 without the need of re-configuring the buttons in the FSUIPC application.

I've done this in the past; this time around my backed up copy of the INI file restored all buttons except for a few rotary knobs. I've decided to use the FSUIPC application to reprogram the rotary dials and have backed up my recent changes.

After making the necessary adjustments, I see that K# value is what appears to maps the keys. I was initially looking for documentation on FSUIPC6.ini key/values, but I don't think it's publicly available. I've been trying to decode the values using common sense with some process of elimination. I understand that the 'A' and 'C' in PA, and PC map to the JoyNames. Still trying to determine what the P and R represent; initially I thought it was Push vs Rotary.

In response to 'Why am I updating your INI manually?'. My career is in systems engineering so I prefer working on text configurations for any quick changes utilizing the key/value pair data. I misunderstood the INI functionality and didn't realize that the -{Key press: }- portion was a comment, thank you far clarifying.

Link to comment
Share on other sites

13 hours ago, Sea2Sky said:

The idea was not have to update the ini file manually, but to back it up and have the ability to restore FSUIPC6 without the need of re-configuring the buttons in the FSUIPC application.

Yes, it is a very wise thing to backup your INI file. You shouldn't have a problem -- it is just a text file after all, in the FSUIPC installation folder.

13 hours ago, Sea2Sky said:

After making the necessary adjustments, I see that K# value is what appears to maps the keys. I was initially looking for documentation on FSUIPC6.ini key/values, but I don't think it's publicly available. I've been trying to decode the values using common sense with some process of elimination

What's wrong with looking it up in the FSUIPC Advanced User's manual, provided as part of the FSUIPC installed documentation? The section on button programming provides a complete list of the Key codes used.

13 hours ago, Sea2Sky said:

Still trying to determine what the P and R represent; initially I thought it was Push vs Rotary.

No, 'Press' and 'Repeat', as described fully in the document. If you want to find things out, supplied documentation is a good place to start!

Pete

 

Link to comment
Share on other sites

16 hours ago, Sea2Sky said:

I was initially looking for documentation on FSUIPC6.ini key/values, but I don't think it's publicly available.

All documentation is public and available, and should be installed in an FSUIPC6 sub-folder of your Windows Documents folder.

John

Link to comment
Share on other sites

7 hours ago, Pete Dowson said:

Advanced User's manual, provided as part of the FSUIPC installed documentation? The section on button programming provides a complete list of the Key codes used.

I should have known better, I have all the documentation spiral bound. Thanks for letting me know.

Keep up the great work!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.