FSUIPC4: Buttons & Switches

[CaptainFS]

Dear Pete,

I had the gear up&down separated in fs2004 and assigned to a switch (btn 5&4). Tried to do the same in FSX FSUIPC4 but it wouldn't allow me:

"This has conditions attached! Please edit it in FSUIPC.INI"

So I did: copied and pasted the [buttons] section from the FSUIPC3 ini file and this works.

Is this allright?

Jamie

[Pete Dowson]

I had the gear up&down separated in fs2004 and assigned to a switch (btn 5&4). Tried to do the same in FSX FSUIPC4 but it wouldn't allow me:

"This has conditions attached! Please edit it in FSUIPC.INI"

Ahthat happened once a few weeks ago, during Beta testing, but I could never reproduce it. Something seems to corrupt part of the internal tables. If you can reproduce it can you give me the starting [buttons] section and tell me the exact sequence you are using to enter the data, please? I need to nail this one.

So I did: copied and pasted the [buttons] section from the FSUIPC3 ini file and this works. Is this allright?

Yes, of course. In fact I think I point out in the documentation somewhere that all of the [buttons ...], [Keys ...], [JoystickCalibrations ...] and [Axes ...] sections of FSUIPC 3's INI file can be cut and pasted directly into the FSUIPC4.INI file.

The only things you may need to watch out for are slight changes in the FS controls, or how they work, and, of course, aircraft name changes if you are using aircraft-specific assignments.

But I still need to locate and fix that Button assignment problem.

Regards,

Pete

[CaptainFS]

If you can reproduce it can you give me the starting [buttons] section and tell me the exact sequence you are using to enter the data, please? I need to nail this one.

Well, I can reproduce this all the time :) FSUIPC does not allow me to assign buttons from within the Buttons&Switches program tab.

My first action after you reply: I removed the CH Manager 3.6 and installed the new one 4.1, rebooted a few times, yoke and pedals back in business, still no access in the B&S tab.

I logged some (maybe) interesting info of me pressing button 5 then 4:

********* FSUIPC4, Version 4.00 by Pete Dowson *********

User Name="Jamie Janssen"

User Addr="jamie@********" < i hid this :)

FSUIPC Key is provided

WideFS Key is provided

[Continuation log requested by user]

Running inside FSX

Module base=61000000

LogOptions=00000001

334375 System time = 17:03:38, FSX time = 16:59:21 (15:59Z)

378438 *** Entered Buttons option page ***

378438 FirstButtonChange res=00000020 (0.0, 32)

379641 FirstButtonChange res=00000105 (0.1, 5)

380391 FirstButtonChange res=00000104 (0.1, 4)

382782 *** Exiting Buttons option page ***

[Log closed by user request, and continued in new file]

386125 System time = 17:04:30, FSX time = 16:59:59 (15:59Z)

386125 *** FSUIPC log file being closed

Memory managed: 163 Allocs, 162 Freed

********* FSUIPC Log file closed ***

This line below looks odd to me, although it's the first time I ever looked into the UIPC logs:

378438 FirstButtonChange res=00000020 (0.0, 32)

I put this section manually in the INI file which works like a charm:

[buttons]

1=P1,5,C66080,0

2=P1,4,C66079,0

Very neat options FSUIPC has, it's the first time I dig into this stuff :)

[Pete Dowson]

Well, I can reproduce this all the time :) FSUIPC does not allow me to assign buttons from within the Buttons&Switches program tab.

All the timE! Hmmm.

Hmmm. I will go around testing it on each of my PCs. Must be something reasonably obvious if it is that consistent.

Thanks,

Pete

[RichardL]

I get the same note when trying to assign FSX view buttons to a PFC yoke. I was about to configure them manually. Decided to check here. Cut and paste is a good idea. Never thought of that. Will wait and see what you find Pete.

Regards,

Richard

[Pete Dowson]

Okay, I thiink I've nailed the problem. It simply *never* happens with a debug build of the program, and of course most development and testing is done with added diagnostic information so we can fix stuff more quickly.

I did manage to reproduce it solidly on one machine, with the Released 4.00 build only (oddly not with a previous 'test' release build), and luckily it still occurred when I added some debug outputs near the check that was failing. It was due to using an index of -1 as if it were correct, when it actually means "not present". Duh!

It'll be fixed in FSUIPC version 4.01 which I'm putting together now.

Thanks for all the info!

Pete

[CaptainFS]

It works! Supersmashing great! Thanks!

Jamie