Sorry for the late reply, My internet connection is on the fritz, the isp is 1 of 3 companies in the middle of fusing, sigh.
Well sorry for the disagreements, but having a real pilot's guide lying here for the baron that specifically states you'll drown it if you only use fuel cut-off after shutdown and securing the aircraft, No offense, but I kind of trust the manufacturers own user manual :)
Well it's a problem of luxury I guess. No biggie just annoying.
:) you're reply to my text does not however, it's about all engines, I know the behaviour makes sense, it's just not what I want. Which was what I was explaining. The functionality was correct, it just isn't on enough valves :p
Sorry, I don't know what you are missing here, you said having a button for all fuel valves does not make sense, I disagreed on that and explained why I find it does make sense (at least for me in the baron).
One moment, looking, yes it has because I used to do it that way, but it can't bind release to it so I had the syncronization problems, wondering why the engine wouldn't start and then remembering, right it's a toggle not a release switch.
looking
The event is called "Engine fuel valves (all open/close)" under button/keys.
The problem I had with the Engine fuel valves (all open/close) event is that I wasn't able to bind button release to it and I want my controls to go through fsuipc.
Regards, Luggage
EDIT, forgot to mention.
Will do the editting in the ini, I guess this question has been answered, I just missed it browsing the post when I wasn't on my home pc. I wasn't aware you could have 1 button do x things at once in fsuipc (only recently started with fsuipc but I figured most out so far), thanks for the replies, if I run into a snag I'll post another reply, if not my personal wishes were granted :)