Quick silly question

[BenSollis]

Hi all !

Using FSUIPC Button control, which entry do I need for the fule on/off switches?

These are the switches usually just below the throttles.

TIA

Ben

[Pete Dowson]

Using FSUIPC Button control, which entry do I need for the fule on/off switches?

The jet fuel switches in FS are the same as the mixture controls in props. Full rich = fuel enabled, Full lean = fuel cutoff.

You can program these in the FS assignments, but if you want the FS control names in FSUIPC's drop down I think they are "Mixture lean" and "Mixture rich". Separate ones for each engine are also listed -- Mixture N ...

Regards,

Pete

[BenSollis]

Thanks Pete, I spent ages with that one!

As an aside, have you any plans to set settings in FS depending on the state of joystick buttons on startup? Or is it there already?

I'm just thinking out loud on the last bit..

Ben

[Pete Dowson]

As an aside, have you any plans to set settings in FS depending on the state of joystick buttons on startup? Or is it there already?

No. What sorts of settings? As present all my joystick-based programming detects changes. Off to On or On to Off. It might be pretty dodgy otherwise. For instance many rotaries are alternately on and off and the state isn't clear when you leave it.

Even most other implementations using switches operate like that. The Aerosoft MCP and PM, for instance, needs me to ensure all the switches are down before I enable them by pushing them up. Similarly the EFIS range and mode dials need setting.

You either need to take care to switch everything off (or whatever state your startup-Flight is in FS) before closing down, or make a habit of toggling all the toggles after start-up, to initialise things to suit.

Otherwise, what are you suggesting? That I treat every button is see "off" as an initial on-to-off and every one I see as "on" as an initial off-to-on? I could probably do that, maybe as an overall option. I wouldn't want it defaulting that way else there might be some surprises. Timimg is also difficult. Changing some things whilst an aircraft is being loaded can cause crashes.

And what if you load a new flight, or restart a flight which has been autosaved? Should I detect the flight change and treat all the buttons as being uninitialised again? This is also possible, but is it desirable?

I can add this to my list but I think it needs more thought, and it won't fit into the next version, which I am targetting for the weekend, before I go on holiday.

Regards,

Pete

[BenSollis]

Hi Pete,

Gosh no, it is not something I am looking for or asking you to comptemplate any time soon :)

What I had in mind was a feature whereby if an input was based on the state of a button/switch and it was a toggle type setting, the code would check the state of the button/switch and then set the appropiate toggle in FS depending on the state of the button/switch.

Again Pete, an idea for the back-burner :) Enjoy your holidays ! I'm am sure they are well due and indeed well earned !

Ben

[Pete Dowson]

What I had in mind was a feature whereby if an input was based on the state of a button/switch and it was a toggle type setting, the code would check the state of the button/switch and then set the appropiate toggle in FS depending on the state of the button/switch.

Right. But all I know about the inputs is one bit -- a 0 or a 1. I don't know if it's a toggle or a button or a rotary or what, and I don't really want to have to know. So I would have to apply it as I described. It's all or nothing I fear. This is why it needs thinking through more -- i.e. what sort of adverse situations might be possible if I did this? Maybe none?

Perhaps, after I come back from holiday, I will add such an option in a test version and we can play with it and see if it is any good. Anyway, it is on my list. It isn't much work I think.

Regards,

Pete