Assignment issues

[nawarren]

Hi Pete,

I have fsuipc v 3.75 and I use Level D sim a lot. I find that after setting up the axis and buttons under fsuipc everything is fine. Then when I quit FS9 and later restart, select same aircraft, the buttons no longer work, sometimes the axis do not work either. The problem seems worse if I select the tick box for 'aircraft specific?'.

I have searched forum and not found anything. I tried deleting FSUIPC.cfg and starting again but I have the same problem. Please can you help.

Cheers

Neil

[Pete Dowson]

I have fsuipc v 3.75 and I use Level D sim a lot. I find that after setting up the axis and buttons under fsuipc everything is fine. Then when I quit FS9 and later restart, select same aircraft, the buttons no longer work

Well, all your settings go into the FSUIPC.INI file and are reloaded when FS is reloaded. Do you get the same if you ask it to "reload settings" in the relevant Option Tab?

Axes, buttons and calibrations all have their own sections, and are all saved independently. Buttons and Keys have global assignments (for all aircraft) as well as aircraft-specific ones.

All this has been working fine for many years, so I can only assume you are misunderstanding something fundamental. Maybe the "same aircraft" is actually a different one, a different paint-job or something, so not matching the stuff you saved?

Or possibly you marked the FSUIPC.INI file as "read only", so preventing anything being changed there at all?

I tried deleting FSUIPC.cfg and starting again but I have the same problem.

There's no file "FSUIPC.CFG" used by FSUIPC. If you mean FSUIPC.INI, and you deleted it, you have lost all of your settings in any case.

Please note that 3.75 is not supported as of today. The current release is 3.80. Get it from http://www.schiratti.com/dowson

After upgrading, if you still cannot figure out what you are doing wrong, please go into specific examples, because there's no way I can really help with a general "I can't get it to work" complaint.

Regards

Pete

[nawarren]

Hi Pete,

Thanks for the reply.

Sorry I did not explain myself very well. I am now infront of Fsim. I have got new version. 3.80 installed. I will describe exactly my problem.

Under Buttons and switches, I program buttons on my ch throttle & Side Winder 2 joystick. ie gear up, gear down. Auto throttle disconnect, etc. When I program them without ticking the Aircraft specific box, they all work fine next time I load FS.

The problem occurs when I tick the box for Aircraft Specific. Then when I reload FS all the Aircraft specific commands have gone. I am loading the same A/C at all times. [DXT] Level D Simulations B767-300ER

Any ideas.

Cheers

Neil

[Pete Dowson]

The problem occurs when I tick the box for Aircraft Specific. Then when I reload FS all the Aircraft specific commands have gone.

Sorry, please explain further. I need a blow-by-blow description. You program all your buttons THEN check the aircraft-specific box? Or vice versa?

Have you a mixture of aircraft-specific buttons and other buttons?

Maybe you should show me the [button ...] sections from your FSUIPC.INI file. Just cut the sections and paste them here.

I am loading the same A/C at all times. [DXT] Level D Simulations B767-300ER

And is this name showing at the top of the FSUIPC options window when you are programming these aircraft-specific buttons? If not, you are not programming them for that aircraft.

It sounds to me as if you are not following the simple rules -- select aircraft-specific WITH the specific aircraft loaded (and its name showing on the title bar of the options window), THEN program the specific buttons. These override any general programming for those buttons when that aircraft is loaded.

It works fine here, 100%, so I am sure it is some misunderstanding you have about how this works. But at present I cannot fathom out what that is because you are not telling me what you are doing.

Regards

Pete

[Pete Dowson]

Sorry, I appear to have pressed the "Edit" button and edited your last message instead of the "quote" button. So yours is lost now. However, the relevant parts are quoted here. Apologies for any confusion.

Attached is my FSUIPC button settings.

Good grief! No wonder it doesn't work. Every single assignment is in a separate section -- only one of those will ever be readable!!!

I think the problem is caused by the [ ] characters in the Aircraft name. The Windows INI file routines aren't handling that correctly -- it is probably reading "[Axes.[DXT3] Level D Simulations B767-300ER - First Choice Airways]" as just [Axes.[DXT3] -- which of course won't match the aircraft name. Why on Earth Windows writes each parameter into its own section, all with the same name, I don't know -- but it probably does the same sort of thing, reading and not finding a match, so it assumes it is new.

Odd that in six or so years of this facility this has never come up before, and really annoying that it does come up just after I've made major releases for FSX and FS9 and am about to go on holiday! Grrr! Isn't that just typical?

I'm afraid this isn't something I can fix now for three weeks or so. So you need to work around it for now. There are two ways of doing this:

1. Edit the Aircraft.CFG file to change the name of the aircraft -- it's the Title=... line you'd need to edit. Delete the [ ] characters. Then delete the entire section you showed me from the FSUIPC INI file, and start again.

Alternatively, and maybe more productively:

2. Edit the INI file. Change the "ShortAircraftNameOk" setting (in the [General] section) to

ShortAircraftNameOk=Substring. Then delete all of the stuff you showed me, and add this in its place:

[Axes.B767]
0=1X,256,D,7,0,0,0
1=1Y,256,D,8,0,0,0
2=1R,256,D,3,0,0,0
3=2X,256,D,22,0,0,0
4=2Y,256,D,9,0,0,0
5=2Z,256,D,10,0,0,0
6=2R,256,D,23,0,0,0

[JoystickCalibration.B767]
ExclThrottleSet=No
SepRevsJetsOnly=No
ApplyHeloTrim=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=0
RudderTrimControl=0
CowlFlaps1Control=0
CowlFlaps2Control=0
CowlFlaps3Control=0
CowlFlaps4Control=0
MaxSteerSpeed=60
Rudder=-15620,377,377,15819/8
LeftBrake=-16383,16383/8
RightBrake=-16383,16383/8
Throttle1=-15602,-10791,-9361,15488/8
Throttle2=-16252,-11702,-10791,14976/8
Spoilers=-14720,15732/24
Flaps=-15732,13952/24

[Buttons]
1=P2,1,C65752,0
2=P2,11,C66080,0
3=P2,10,C66079,0
4=P2,2,K122,11
5=P2,3,K122,11
6=P2,5,K123,11
7=P2,4,K123,11
8=P2,9,K84,11
9=P2,8,K84,11
10=P0,0,K65,11
11=R0,2,C65607,0
12=R0,3,C65615,0

[Buttons.B767]
0=P2,3,K122,11
1=P2,5,K123,11
2=P2,2,K122,11
3=P2,4,K123,11

[Axes]
0=0X,256,F,65695,0,0,0
1=0Y,256,F,65694,0,0,0
2=1X,256,D,7,0,0,0
3=1Y,256,D,8,0,0,0
4=1R,256,D,3,0,0,0
5=2X,256,D,22,0,0,0
6=2Y,256,D,9,0,0,0
7=2Z,256,D,10,0,0,0
8=2V,256,D,23,0,0,0

Now this will make these assignments work for any aircraft in your collection with "B767" anywhere in its name. That may be more useful for you in the long term. Or if you want it specific to the LevelD, you could use "Level D Simulations B767" as the name in the lines above. Just don't use anything with [ ] in it.

I'll fix FSUIPC to strip out such characters automatically in future, but as I say I can't do this for a few weeks. Interesting that it has never come up before.

Regards

Pete

[nawarren]

Hi Pete,

You are a star. Excellent support as usual. I have had this problem for ages, looked all through forum and could see nothing. Thought it was me being stupid. Many thanks again and enjoy your holiday.

Bon Voyage.

Neil