Jump to content
The simFlight Network Forums

Copy to FSUIPC .ini Problem.


Recommended Posts

New Mobo, processor, ram and video installed. FSX on a internal seperate Hardrive. FSUIPC v.4.8 new installed and registered. Run:WIN7/64bits as before. Use same hardrives, a new window 7 was created and the previous was renamed to windows.old

Problem: when I copy and past from my former FSUIPC Ini-file the [Profile.Piston] entry, it won't work. I did made a new Profile, same name, for the [Profile.Piston] 1=Cessna Skyhawk 172SP Paint1. I can make new assignments, but if I copy and past from my former saved Ini-file, Those Buttons are not responding from my Saitek Joystick. It look like a security problem, but I can't lay my hands on. Any help? Herb

Snippet of Ini-file:

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=Yes

0=Saitek Pro Flight Rudder Pedals

0.GUID={AB57C550-9A9B-11E1-8001-444553540000}

1=Saitek X52 Flight Controller

1.GUID={2E827200-9BCC-11E1-8001-444553540000}

A=Saitek Pro Flight Rudder Pedals

B=Saitek X52 Flight Controller

A.GUID={AB57C550-9A9B-11E1-8001-444553540000}

B.GUID={2E827200-9BCC-11E1-8001-444553540000}

[Profile.Piston]

1=Cessna Skyhawk 172SP Paint1

2=Mooney Bravo

[buttons.Piston]

0=PA,8,C66079,0 ;//Gear Up

1=PA,9,C66080,0 ;// Gear Down

2=PA,31,C65564,0 ;//ATC

4=CP(+A,23)A,2,C65725,0 ;//Autopilot Hold ;//Mode1,Btn#2

5=CP(+A,23)A,3,C65811,0 ;//Autopilot Nav Hold On ;//Mode2 Btn#3

6=CP(+A,23)A,19,K50,9 ;//2D RadioStack-Panel (Cessna);//Mode1

7=CP(+A,23)A,20,K51,9 ;//2D GPS-Unit (Cessna)

8=CP(+A,23)A,21,K52,9 ;//2D Throttle-Unit (Cessna)

9=CP(+A,23)A,22,K53,9 ;//2D

11=CP(+A,24)A,2,C65724,0 ;//Autopilot App ;//Mode2

12=CP(+A,24)A,3,C65726,0 ;//Autopilot Alt Hold

13=CP(+A,24)A,19,K54,9 ;//2D Throttle Quadrant (Beech-Baron);//Mode2

14=CP(+A,24)A,20,K55,9 ;//2D Electric Switches Beech-Baron)

15=CP(+A,24)A,21,K56,9 ;//2D Backup Instruments (Beech-Baron)

16=CP(+A,24)A,22,K57,9 ;//2D Landing/Gear,Trims (Beech-Baron)

17=CR(+A,25)A,2,C65892,0 ;//Autopilot AP_ALT_VAR_INC ;//Mode3

18=CR(+A,25)A,3,C65893,0 ;//Autopilot AP_ALT_VAR_DEC

19=CR(+A,25)A,19,C65775,0 ;//2D Throttle-Unit Mixture DECR (Beech-Baron);//Mode3

20=CR(+A,25)A,21,C65777,0 ;//2D Mixture INCR (Beech-Baron)

21=CR(+A,25)A,20,C65771,0 ;//2D Throttle-Unit Prop-Pitch DECR (Beech-Baron);//Mode3

22=CR(+A,25)A,22,C65769,0 ;//2D Prop Pitch INCR

23=PA,10,C65759,0 ;// Flaps

24=PA,11,C65758,0

25=PA,12,K87,10 ;// Water-Rudder

26=PA,13,K71,9 ;//Tailwheel-lock on/off

27=PA,28,C66653,0 ;//VIEW_COCKPIT_FORWARD

28=PA,14,C65567,0 ;//View-Mode-Trigger

//0=PB,11,C65758,0

//1=PB,10,C65759,0 Those are the new 4 entries, they did worked. I unabled for testing.

//2=PB,8,C66079,0

//3=PB,9,C66080,0

Link to comment
Share on other sites

8=CP(+A,23)A,21,K52,9 ;//2D Throttle-Unit (Cessna)

9=CP(+A,23)A,22,K53,9 ;//2D

11=CP(+A,24)A,2,C65724,0 ;//Autopilot App ;//Mode2

12=CP(+A,24)A,3,C65726,0 ;//Autopilot Alt Hold

13=CP(+A,24)A,19,K54,9 ;//2D Throttle Quadrant (Beech-Baron);//Mode2

Hi

Did yoy see the missing number 10 (ten), should be in line I think (8 - 9 - 10 - 11 - ...).

Link to comment
Share on other sites

Yes, I see, but this was working before on my old system. From 11 start a new sequence. Pete explained it some time before. I change it now, did not helped. Herb

What I notice the Joystick assignment is now reversed. But, this should not make any different to the Buttons numbers. Here is the old one:

[JoyNames]

AutoAssignLetters=Yes

1=Saitek Pro Flight Rudder Pedals

1.GUID={23313DE0-C80B-11E0-800B-444553540000}

A=Saitek X52 Flight Controller

B=Saitek Pro Flight Rudder Pedals

B.GUID={23313DE0-C80B-11E0-800B-444553540000}

C=<< MISSING JOYSTICK >>

J=<< MISSING JOYSTICK >>

0=Saitek X52 Flight Controller

0.GUID={23313DE0-C80B-11E0-800A-444553540000}

If this is the problem, How do I correct it? Herb

I updated to FSUIPC v.4.27 No changes

Link to comment
Share on other sites

What I notice the Joystick assignment is now reversed. But, this should not make any different to the Buttons numbers.

Well of course it will do if the buttons numbers refer to the wrong device. How did the letter assignments get changed? The whole point of letter assignments is to keep the same assignments no matter what!

You will notice in your new INI that

A=Saitek Pro Flight Rudder Pedals

and all your buttons are assigned to A, the pedals!

Just swap the As and B's over in the [JoyNames] section. Only 4 lines to change, one character in each.

I updated to FSUIPC v.4.27 No changes

I cannot support such old versions - that is years old! Current is 4.827 with interim update 4.828 due out later today.

Pete

Link to comment
Share on other sites

Well of course it will do if the buttons numbers refer to the wrong device. How did the letter assignments get changed? The whole point of letter assignments is to keep the same assignments no matter what!

You will notice in your new INI that

A=Saitek Pro Flight Rudder Pedals

and all your buttons are assigned to A, the pedals!

Just swap the As and B's over in the [JoyNames] section. Only 4 lines to change, one character in each.

I cannot support such old versions - that is years old! Current is 4.827 with interim update 4.828 due out later today.

Pete

Hello Pete!

Thank you for your reply and advice to swap A and B. On my 2nd reply I stated that I updated to v.4.27 last night, but it did not changed anything. I know, you do dislike if we are using older version. Thanks again and I will be OK. Herb

Link to comment
Share on other sites

Thank you for your reply and advice to swap A and B. On my 2nd reply I stated that I updated to v.4.27 last night, but it did not changed anything. I know, you do dislike if we are using older version.

But why go back to such an ancient version? In fact, I don't think 4.27 even supports lettered IDs for devices! The current version is 4.828, the previous version is 4.827 as I said.

Pete

Link to comment
Share on other sites

But why go back to such an ancient version? In fact, I don't think 4.27 even supports lettered IDs for devices! The current version is 4.828, the previous version is 4.827 as I said.

Pete

Pete! I'm very sorry, made at typo, I updated to v.4.827 last night. I'm a Dumkopf. I fixed the 4 entries and no more problems. I did copied the rest now and all is working fine. Thanks again, you helped me saving many hours of work. Herb

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.