chrisworld Posted February 9, 2005 Report Posted February 9, 2005 Hello all, I´m having a problem programing my "autostart engines" (CTRL+E). When pressing these two buttons on the keyboard it always works. When pressing a button (EPIC USB) and programming FSUIPC->Buttons page->Keypress-> CTRL+e, only the generator starts but my engines don´t start up. Even when I check the "repeat while held down" function it doesn´t work. I use a on/off button, no pushbutton. I also tried it with "Engines autostart" (FS control in FSUIPC). It didn´t work,too. Found nothing about that problem here in the Forum. What might be the reason? Thank you, greetings Toby
Pete Dowson Posted February 9, 2005 Report Posted February 9, 2005 When pressing these two buttons on the keyboard it always works. When pressing a button (EPIC USB) and programming FSUIPC->Buttons page->Keypress-> CTRL+e, only the generator starts but my engines don´t start up. The Ctrl+E keypress is only assigned that way in FS's Options-Controls-Assignments. It can be assigned to any keypress - or button - in FS. If your button is assigned to Ctrl+E in FSUIPC and Ctrl+E is still correctly assigned in FS's assignments, then it will work. It certainly does here. Are you using FSUIPC 3.45? If not, download and install that. Then, in the Logging page you can select "Event logging". With this you can actually see the controls being sent to FS -- the ENGINE_AUTO_START control is sent no matter how the Ctrl+E arrives. If this isn't occurring it sounds like something else is also happening when you press that button. Perhaps you have it already assigned in FS itself to do something else, and that is interfering with the auto-start? I also tried it with "Engines autostart" (FS control in FSUIPC). It didn´t work,too. Well, I think that certainly indicates that you have forgotten to de-assign the same button from other actions in FS. Assigning it directly to the FS control is much more efficient in any case than assigning it to a keypress which is in turn assigned (in FS) to the control. In fact, for all FS controls already assignable in the FS Options-Controls-Assignments dialogue you do not need to use FSUIPC at all -- why not simply assign it in FS? If you do that, FS will automatically deassign it from whatever else it is doing there. You seem to be making a very complicated job of it? Regards, Pete
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now