Jump to content
The simFlight Network Forums

Throttle assignments


Recommended Posts

Hello,

I have just registered FSUIPC, after a couple of months using the unregistered version.

However, on my multi engine aircraft, I can no longer use the keyboard inputs E+1, E+2, E+3 and E+4 to activate each engine (during start up) as i could before.

Pressing just E, will activate Engine no. 1. And I cannot bring back all engines to the single throttle lever action on my joystick by pressing E+1+2+3+4.

How can I get this function back?

I use a joystick with a single throttle lever to manage all engines.

Best Regards,

Anders

Link to comment
Share on other sites

I have just registered FSUIPC, after a couple of months using the unregistered version.

However, on my multi engine aircraft, I can no longer use the keyboard inputs E+1, E+2, E+3 and E+4 to activate each engine (during start up) as i could before.

Pressing just E, will activate Engine no. 1. And I cannot bring back all engines to the single throttle lever action on my joystick by pressing E+1+2+3+4.

How can I get this function back?

FSUIPC does not affect how FS interprets your keyboard inputs. It has no way to do that, unless you've reassigned them in FSUIPC.

If all you've done is Registered FSUIPC and not used any of its facilities, then it is exactly the same as not registering it -- unless, that is, you have used an illegal registration, or your PC's system date is wrong and makes the registration look illegal. Perhaps you'd better show me your FSUIPC log file (close FS first) so I can check? You'll find the file in the FS Modules folder.

If you post again, please state the version of FS and the version number of FSUIPC. These things are ALWAYS needed.

Regards

Pete

Link to comment
Share on other sites

Hello Pete,

It is FS9, and my version of FSUIPC.dll is 3.98a. And my OS is Windows 7/64.

I assume that the FSUIPC log file is it the file with these contents?;

********* FSUIPC, Version 3.98a by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "C:\MSsoftware\FS9\MODULES\FSUIPC.DLL" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Anders Nielsen"

User Addr="acnielsen62@gmail.com"

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=681C3709[681C3709]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=15

8377 System time = 17/06/2010 22:22:50

8377 C:\MSsoftware\FS9\

8393 System time = 17/06/2010 22:22:50, FS2004 time = 12:00:00 (00:00Z)

27409 FLIGHTS\OTHER\FLTSIM.flt

27534 AIRCRAFT\c172\Cessna172SP.air

27534 Aircraft="Cessna Skyhawk 172SP"

47143 AIRCRAFT\VA Dart Herald\Herald200.air

47143 Aircraft="HP Dart Herald Air Anglia"

50918 C:\Users\Anders\Documents\Flight Simulator Files\UI generated flight.flt

51277 Clear All Weather requested: external weather discarded

61948 Advanced Weather Interface Enabled

84615 Traffic File #15 = "addon scenery\calclassic traffic 1959\scenery\traffic_1959"

84864 Traffic File #17 = "addon scenery\calclassic traffic 1962\scenery\traffic_1962"

87267 Traffic File #13 = "addon scenery\calclassic traffic 1957\scenery\traffic_1957"

210773 WeatherOptions set, now 681C3709 (timer=0)

381516 Joy 0 taking too long to respond (> 80 mSecs). Removed from scan

381516 Joy 0 taking too long to respond (> 80 mSecs). Removed from scan

810846 System time = 17/06/2010 22:36:12, FS2004 time = 22:25:05 (05:25Z)

810846 *** FSUIPC log file being closed

Memory managed: 0 Allocs, 7698 Freed

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

Best Regards,

Anders

Link to comment
Share on other sites

I have now uninstalled FSUIPC, by deleting FSUIPC.dll. Problem still is there.

Strange!

As I said, it couldn't be a function of FSUIPC except by making special assignments to do so.

There is the possibility that the aircraft you are using is sending many controls to FS all the time. If one of these controls occurs between you pressing the E and the 1, 2, 3 and/or 4, then those subsequent presses will be missed -- or worse, apply to some other function. To see if this is what is occurring, reinstall FSUIPC then go to the Logging tab in its options and select "event" logging. When you get the problem, look at the FSUIPC.LOG file. You will see the controls sent, by name and parameter, for example:

238656 *** EVENT: Cntrl= 65554 (0x00010012), Param= 0 (0x00000000) ENGINE

239250 *** EVENT: Cntrl= 65538 (0x00010002), Param= 0 (0x00000000) SELECT_1

239484 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2

239734 *** EVENT: Cntrl= 65540 (0x00010004), Param= 0 (0x00000000) SELECT_3

240000 *** EVENT: Cntrl= 65541 (0x00010005), Param= 0 (0x00000000) SELECT_4

If another control gets between the ENGINE control (from pressing E) and any of the SELECT controls (1,2,3 or 4), then the latter's effect can be nullified -- depending on what sort of control it is.

Using FSUIPC you can monitor the state of the internal FS variable which selects the engines to be affected by the generic throttle, prop and mixture controls. This is as follows:

0888 (1byte): Active engine (select) flags. Bit 0 = Engine 1 selected … Bit 3 = Engine 4 selected.

In the FSUIPC Logging tab, enter 0888 as an Offset in the table on the right-hand side, select U8 as the Type, then check the option for "advdisplay" below. OK out. Now FSUIPC will display the value in 0888 in real time on screen.

15 = all engines

1 = engine 1 only

2 = engine 2 only

4 = engine 3 only

8 = engine 4 only

(add values for other combinations).

One possible solution: There is an option in FSUIPC, in the Miscellaneous tab, entitled "Fix control acceleration" (please look it up, page 21 in the current User Guide). To quote part of the description:

when this option is enabled there is now special treatment afforded to the SELECT controls. These are normally the 1–4 keys on the main keyboard. The action performed by FSUIPC ensures that when they are used after, for instance, the Engine select control (key ‘E’) or aircraft Exit control (Shift+E) they still do the appropriate action even when other controls have intervened. (There is a time limit on this, defaulting to 4 seconds, which can be controlled for the TimeForSelect parameter in the FSUIPC.INI file).

Regards

Pete

Link to comment
Share on other sites

Hello Pete,

Thank you very much for the thorough explanation.

Yes, there appears to be a time factor involved, especially when FS is busy during startup and/or when loading weather.

And the good news is, that "Fix Control Acceleration" feature in FSUIPC seems to solve it.

Thank you again,

Anders

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.