Jump to content
The simFlight Network Forums
quink99

Panning view in virtual cockpit

Recommended Posts

Ah, and a thing of beauty it is! My thanks, Pete, for this marvelous utility. My FS9 functions as never before and Iam a most happy virtual "airplane driver".

After climbing the rather steep learning curve and using the default C172 I have all my axis assigned, joysticks calibrated, and buttons programmed. All works as advertised with one exception.

When flying in the VC mode I am unable to use the default panning mode with the hat switch which would give a smooth flowing pan in almost any direction. Although I've tried using almost every "view" options in the button assignment page the closest I can come is is using the views 32-39 and that results in the same jerky and limited view changes that have always been available in the 2D cockpit when using the hat switch. Any help in resolving this problem would be most deeply appreciated.

Thanks again,

Frederick

Share this post


Link to post
Share on other sites

When flying in the VC mode I am unable to use the default panning mode with the hat switch which would give a smooth flowing pan in almost any direction. Although I've tried using almost every "view" options in the button assignment page the closest I can come is is using the views 32-39 and that results in the same jerky and limited view changes that have always been available in the 2D cockpit when using the hat switch. Any help in resolving this problem would be most deeply appreciated.

Have you tried using the panning controls instead of the viewing controls at all?

Not being a VC user I've never really experimented with any of that stuff. However, there have been other threads here with examples, and in fact the solutions shoown below are currently published in the FSUIPC4 User Guide (and due to go into the next update for FSUIPC3's User Guide):

Example of assignments for HAT programming for smooth panning

For FS2004 (should work in FSX too):

Assuming ‘j’ is the joystick number on which the Hat to be programmed is situated:

Push forward: program button j,32 as PAN UP on press, to repeat, and PAN RESET COCKPIT on release

Push forward & right: program button j,33 as PAN RIGHT UP on press, to repeat, and PAN RESET COCKPIT on release

Push right: program button j,34 as PAN RIGHT on press, to repeat, and PAN RESET COCKPIT on release

Push back & right: program button j,35 as PAN RIGHT DOWN on press, to repeat, and PAN RESET COCKPIT on release

Push backward: program button j,36 as PAN DOWN on press, to repeat, and PAN RESET COCKPIT on release

Push back & left: program button j,37 as PAN LEFT DOWN on press, to repeat, and PAN RESET COCKPIT on release

Push left: program button j,38 as PAN LEFT on press, to repeat, and PAN RESET COCKPIT on release

Push forward & left: program button j,39 as PAN LEFT UP on press, to repeat, and PAN RESET COCKPIT on release

For those familiar with the INI file parameters, this could look something like this (with comments added and joystick #0 assumed):

1=R0,32,C65734,0 ; PAN_UP

2=U0,32,C66415,0 ; PAN_RESET_COCKPIT

3=R0,33,C65856,0 ; PAN_RIGHT_UP

4=U0,33,C66415,0 ; PAN_RESET_COCKPIT

5=R0,34,C65672,0 ; PAN_RIGHT

6=U0,34,C66415,0 ; PAN_RESET_COCKPIT

7=R0,35,C65857,0 ; PAN_RIGHT_DOWN

8=U0,35,C66415,0 ; PAN_RESET_COCKPIT

9=R0,36,C65735,0 ; PAN_DOWN

10=U0,36,C66415,0 ; PAN_RESET_COCKPIT

11=R0,37,C65855,0 ; PAN_LEFT_DOWN

12=U0,37,C66415,0 ; PAN_RESET_COCKPIT

13=R0,38,C65671,0 ; PAN_LEFT

14=U0,38,C66415,0 ; PAN_RESET_COCKPIT

15=R0,39,C65854,0 ; PAN_LEFT_UP

16=U0,39,C66415,0 ; PAN_RESET_COCKPIT

For FSX (may work in FS2004 too?):

A suggested method for FSX is very similar to the one above, but uses “PAN_VIEW” with a parameter of –1 to restore the previous view in Virtual Cockpit mode, rather than straight ahead:

1=R0,32,C65734,0 ; PAN_UP

2=U0,32,C66416,-1 ; PAN_VIEW -1

3=R0,33,C65856,0 ; PAN_RIGHT_UP

4=U0,33,C66416,-1 ; PAN_VIEW -1

5=R0,34,C65672,0 ; PAN_RIGHT

6=U0,34,C66416,-1 ; PAN_VIEW -1

7=R0,35,C65857,0 ; PAN_RIGHT_DOWN

8=U0,35,C66416,-1 ; PAN_VIEW -1

9=R0,36,C65735,0 ; PAN_DOWN

10=U0,36,C66416,-1 ; PAN_VIEW -1

11=R0,37,C65855,0 ; PAN_LEFT_DOWN

12=U0,37,C66416,-1 ; PAN_VIEW -1

13=R0,38,C65671,0 ; PAN_LEFT

14=U0,38,C66416,-1 ; PAN_VIEW -1

15=R0,39,C65854,0 ; PAN_LEFT_UP

16=U0,39,C66416,-1 ; PAN_VIEW -1

Thanks to Barrie for this idea and its testing.

Regards

Pete

Share this post


Link to post
Share on other sites

Pete,

Voila! You nailed my first problem perfectly on your first try. What great support. I can't vouch for the FSX solution but the one for FS9 is the answer.

Thanks and regards,

Frederick

Share this post


Link to post
Share on other sites

A suggested method for FSX is very similar to the one above, but uses “PAN_VIEW” with a parameter of –1 to restore the previous view in Virtual Cockpit mode, rather than straight ahead:

1=R0,32,C65734,0 ; PAN_UP

2=U0,32,C66416,-1 ; PAN_VIEW -1

3=R0,33,C65856,0 ; PAN_RIGHT_UP

4=U0,33,C66416,-1 ; PAN_VIEW -1

5=R0,34,C65672,0 ; PAN_RIGHT

6=U0,34,C66416,-1 ; PAN_VIEW -1

7=R0,35,C65857,0 ; PAN_RIGHT_DOWN

8=U0,35,C66416,-1 ; PAN_VIEW -1

9=R0,36,C65735,0 ; PAN_DOWN

10=U0,36,C66416,-1 ; PAN_VIEW -1

11=R0,37,C65855,0 ; PAN_LEFT_DOWN

12=U0,37,C66416,-1 ; PAN_VIEW -1

13=R0,38,C65671,0 ; PAN_LEFT

14=U0,38,C66416,-1 ; PAN_VIEW -1

15=R0,39,C65854,0 ; PAN_LEFT_UP

16=U0,39,C66416,-1 ; PAN_VIEW -1

Thanks to Barrie for this idea and its testing.

I've got this programmed in and it works okay but it's not nearly as smooth and fast as when FSX handles the panning (vs. FSUIPC). My controls are disabled through FSX and I'm only using FSUIPC. I'd appreciate hearing from anyone who, using FSUIPC, has the panning working as smoothly and quickly as with FSX.

I'd like to use FSUIPC only and not enbale controllers at all in FSX.

Thanks.

Bruce

Share this post


Link to post
Share on other sites

I've got this programmed in and it works okay but it's not nearly as smooth and fast as when FSX handles the panning (vs. FSUIPC). My controls are disabled through FSX and I'm only using FSUIPC. I'd appreciate hearing from anyone who, using FSUIPC, has the panning working as smoothly and quickly as with FSX.

I'd like to use FSUIPC only and not enbale controllers at all in FSX.

I think FS treats it as an axis-type control rather than a set of buttons, and that is the difference. Try assigning it in FSUIPC's Axis Assignments instead of the Buttons section. If it is a proper DirectInput "POV" control" it should certainly be recognised. Assign it to the FS "PAN VIEW" control there.

This is only applicable to FSUIPC4 at present. FSUIPC3 doesn't see POVs as Axes at all.

[LATER]

I have one idea which might help answer this. Do the assignment in FSX and enable both Axis Event and normal Event logging in FSUIPC4. Operate the view hat, see it working, then look at the log -- or show it to me. Maybe we can see what it is doing and emulate it.

There are other axis controls for panning, ones for each direction, and these can be assigned in FSUIPC and calibrated. However, these would require a normal axis lever, one for each direction (well, at least left/right, up/down). But they are certainly smooth.

Pete

Share this post


Link to post
Share on other sites

Okay I enabled controls in FSX and did the logging:

Here's the log file with just Events (non-axis controls) logged and about a half-second in each direction on the pov:

1921121 Sim stopped: average frame rate for last 35 secs = 29.8 fps

1929452 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929499 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929530 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929561 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929592 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929623 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929655 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929686 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929733 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929764 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929795 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929826 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929857 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929889 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929920 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929967 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929998 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1930029 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1930060 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1930091 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1930123 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1930154 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1930201 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1930232 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

1930700 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930731 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930762 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930793 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930825 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930871 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930903 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930934 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930965 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1930996 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931027 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931059 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931105 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931137 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931168 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931199 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931230 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931261 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931293 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931339 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931371 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931402 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931433 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931464 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

1931495 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

1935317 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935364 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935395 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935427 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935458 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935489 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935520 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935551 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935598 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935629 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935661 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935692 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935723 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935754 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935785 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935832 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

1935863 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

1936300 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936331 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936363 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936394 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936425 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936456 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936503 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936534 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936565 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936597 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936628 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936659 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936690 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936737 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936768 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936799 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936831 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936862 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936893 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

1936924 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

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

Here's the log of just Axis controls:

2015611 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15935 (0xffffc1c1) AXIS_THROTTLE_SET

2015642 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2015689 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2017483 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2017530 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2018591 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2018622 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2018762 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2018794 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2019324 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2019355 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2020073 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2020104 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2020307 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2020338 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2020603 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2020634 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2022382 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

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

I don't know why I'm getting and Axis_Throttle_Set here as I've got the throttle axis disabled on this control in FSX (CH Fighterstick) but it probably doesn't have anything to do with the smooth Pan.

For the heck of it here's the log with both Events and Axis enabled in logging:

2112878 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15935 (0xffffc1c1) AXIS_THROTTLE_SET

2112909 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2112940 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2113408 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2113439 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2113907 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2113985 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2114719 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114750 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114781 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114812 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114843 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114875 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114921 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114953 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2114984 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2115015 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2115046 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

2115077 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

2115421 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115452 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115483 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115514 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115545 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115577 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115623 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115655 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115686 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115717 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115748 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW

2115779 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

2115811 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2115857 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2115982 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2116013 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2116091 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116123 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116154 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116185 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116216 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116247 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116294 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116325 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116357 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116388 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116419 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116450 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW

2116481 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

2116528 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2116559 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2116918 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2116949 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2116996 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117027 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117059 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117090 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117121 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117152 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117183 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117230 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117261 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117293 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117324 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW

2117355 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW

2117823 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2117854 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2118057 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2118104 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2119352 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2119383 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

2119882 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -15940 (0xffffc1bc) AXIS_THROTTLE_SET

2119913 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16068 (0xffffc13c) AXIS_THROTTLE_SET

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

Sorry I don't know how to post a log that is embedded and "scrolls".

Appreciate your thoughts Pete.

Regards,

Bruce

Share this post


Link to post
Share on other sites
Okay I enabled controls in FSX and did the logging:

Here's the log file with just Events (non-axis controls) logged and about a half-second in each direction on the pov:

1921121 Sim stopped: average frame rate for last 35 secs = 29.8 fps

1929452 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929499 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

1929530 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW

et cetera.

These are exactly what FSUIPC could send if you programmed it to. i.e. instead of:

1=R0,32,C65734,0 ; PAN_UP

2=U0,32,C66416,-1 ; PAN_VIEW -1

3=R0,33,C65856,0 ; PAN_RIGHT_UP

4=U0,33,C66416,-1 ; PAN_VIEW -1

5=R0,34,C65672,0 ; PAN_RIGHT

6=U0,34,C66416,-1 ; PAN_VIEW -1

7=R0,35,C65857,0 ; PAN_RIGHT_DOWN

8=U0,35,C66416,-1 ; PAN_VIEW -1

9=R0,36,C65735,0 ; PAN_DOWN

10=U0,36,C66416,-1 ; PAN_VIEW -1

11=R0,37,C65855,0 ; PAN_LEFT_DOWN

12=U0,37,C66416,-1 ; PAN_VIEW -1

13=R0,38,C65671,0 ; PAN_LEFT

14=U0,38,C66416,-1 ; PAN_VIEW -1

15=R0,39,C65854,0 ; PAN_LEFT_UP

16=U0,39,C66416,-1 ; PAN_VIEW -1

replace the "C65734,0 ; PAN_UP" with "C66416,0 ; PAN)VIEW 0

and so on -- i.e. use PAN_VIEW commands (66416) throughout but with the different Degree numbers -- 0, 45, 90, 135, 180, 225, 270 and 315 for the 8 directions.

You'll have to figure it out for yourself. I'm afraid I've nothing here that FSX properly recognises as a "hat" so I cannot do this for you.

Let me know exactly what yo arrive at which works the way you want, and I'll update the examples.

Did you try the axis assignment methjod I suggested? i.e.

Try assigning it in FSUIPC's Axis Assignments instead of the Buttons section. If it is a proper DirectInput "POV" control" it should certainly be recognised. Assign it to the FS "PAN VIEW" control there.

This is only applicable to FSUIPC4 at present. FSUIPC3 doesn't see POVs as Axes at all.

Mind you, this probably won't work as FS seems to rely on the axis repeating all the time, and FSUIPC cuts out repetitive values: possibly I should not do that for POV inputs. In fact I'll look at that next week. Maybe that will solve it in a tidier fashion.

On this point:

I don't know why I'm getting and Axis_Throttle_Set here as I've got the throttle axis disabled on this control in FSX (CH Fighterstick) but it probably doesn't have anything to do with the smooth Pan.

Well, you certainly have a throttle axis enabled somewhere -- and it is jittering between two values! But it doesn't have anytrhing to do with the present subject, you are right.

Regards

Pete

Share this post


Link to post
Share on other sites

I've tried PAN_VIEW (66416) as an Axis, Button & Keypress all with the same results - it's just not as fast and smooth as when using Pan through an fs enabled joystick.

Because pressing and holding Num8, Num6, Num2 etc (NUMx) on the keyboard works fine with the exception of the small initial hesitation of a keyboard press before repetition, I thought I'd just assign a repeating NUMx to POV buttons 32-39 in Buttons + Switches but no go. It's lacking the repetitive speed.

You mention:

"Mind you, this probably won't work as FS seems to rely on the axis repeating all the time, and FSUIPC cuts out repetitive values: possibly I should not do that for POV inputs. In fact I'll look at that next week. Maybe that will solve it in a tidier fashion."

I wonder if that might not do the trick? I note the speed & smoothness between a POV button enabled in FS appears to be identical to that of a NUMx held down on the keyboard except that the POV button is instant and constant whereas the keyboard is instant then followed by the slight hesitation before becoming constant.

Regards,

Bruce

Share this post


Link to post
Share on other sites
I've tried PAN_VIEW (66416) as an Axis, Button & Keypress all with the same results - it's just not as fast and smooth as when using Pan through an fs enabled joystick.

Does it work at all properly with PAN VIEW as an axis? It shouldn't, at present, because FSUIPC doesn't repeat values, it only sends changes -- from the lggoing it is obvious that FS makes use of the repeats.

Because pressing and holding Num8, Num6, Num2 etc (NUMx) on the keyboard works fine with the exception of the small initial hesitation of a keyboard press before repetition, I thought I'd just assign a repeating NUMx to POV buttons 32-39 in Buttons + Switches but no go. It's lacking the repetitive speed.

A keyboard repeat rate it normaly less than the Button repeat rate I use, so I don't understand that.

You mention:

"Mind you, this probably won't work as FS seems to rely on the axis repeating all the time, and FSUIPC cuts out repetitive values: possibly I should not do that for POV inputs. In fact I'll look at that next week. Maybe that will solve it in a tidier fashion."

I wonder if that might not do the trick?

Well I wonder too, but I don't understand how you got PAN VIEW working as an axis without it, in that case?

I note the speed & smoothness between a POV button enabled in FS appears to be identical to that of a NUMx held down on the keyboard except that the POV button is instant and constant whereas the keyboard is instant then followed by the slight hesitation before becoming constant.

If it is only the repeat rate which makes the difference I can probably speed that up, but I'd rather not. I currently operate repeats at about the same as the keyboard repeat rate, so it should be identical. I wonder if it is bunching up due to SimConnect latencies. If so a faster repeat rate wouldn't help, it might actually make it worse..

There's a point. What version of FSUIPC4 are you trying this on? Recent changes should make axis controls independent of SimConnect, but not normal button ones.

I'm also a bit confused as to what other users, before you, have said it is smooth? Maybe something else in the system has a bearing on it?

Pete

Share this post


Link to post
Share on other sites

Does it work at all properly with PAN VIEW as an axis? It shouldn't, at present, because FSUIPC doesn't repeat values, it only sends changes -- from the lggoing it is obvious that FS makes use of the repeats.

This line is generated by assigning it to P axis:

5=2P,1,F,66416,0,0,0

The effect is to move one click in the correct direction(s) which each click of the POV hat.

This line is generated by assigning it to P axis but on right side as a "Control to be sent when range entered" (parameter 90, Control to Repeat):

6=2P,BR,0,0,66416,90

The effect is repeating movement to the right, but jerky, not fast and smooth.

Adding this line directly below results in jerky movement in the 135 degree direction:

7=2P,BR,0,0,66416,180

A keyboard repeat rate it normaly less than the Button repeat rate I use, so I don't understand that.

I have my keyboard set to fast repeat and a "seat of the pants" test shows it repeats about 30 times per second.

There's a point. What version of FSUIPC4 are you trying this on? Recent changes should make axis controls independent of SimConnect, but not normal button ones.

I'm on V4.28.

I'm also a bit confused as to what other users, before you, have said it is smooth? Maybe something else in the system has a bearing on it?

If you're confused you can imagine how I feel! I can't speak to anyone else's experience esp. since I'm still such a pup in all this. That's why I hope someone might weigh-in and say "it's pretty smooth but not butter smooth like FS direct".

Share this post


Link to post
Share on other sites

This line is generated by assigning it to P axis:

5=2P,1,F,66416,0,0,0

The effect is to move one click in the correct direction(s) which each click of the POV hat.

Yes, without any repeats that's what I would expect. The Delta of 1 is okay, but it doesn't help with no repeats, and in any case POVs increase in 45 (6-way) or 90 (4-way) steps, usually. At least I've never heard of a 360 step one.

This line is generated by assigning it to P axis but on right side as a "Control to be sent when range entered" (parameter 90, Control to Repeat):

6=2P,BR,0,0,66416,90

The effect is repeating movement to the right, but jerky, not fast and smooth.

Adding this line directly below results in jerky movement in the 135 degree direction:

7=2P,BR,0,0,66416,180

Yes, nothing in that facility would be useful. I wouldn't expect it to be.

I have my keyboard set to fast repeat and a "seat of the pants" test shows it repeats about 30 times per second.

Ah, that might explain the difference you see, somewhat. I think the FSUIPC repeat rate is more like 18.

I'm on V4.28.

Before we do anything else, could you please move on to the currently supported version, 4.30. There are changes in that which may well affect all of this!

Pete

Share this post


Link to post
Share on other sites
Ok Pete I installed V4.3 but there was no difference that I could tell as far as this discussion is concerned.

Okay. I think the main difference is in how the axes directly assigned are sent to FS (by passing SimConnect now).

Look out for an update later in the week - I'll see about making the POV axis assignment auto-repeat.

Regards

Pete

Share this post


Link to post
Share on other sites

Just wondering if you've had a chance to give this any thought.

I thought you said you were going to keep your eyes open? I released the update (4.301) with the relevant changes a week ago, on the 31st July! Your eyes don't go through the relevant Announcements it seems -- in this case FSX Downloads?

Regards

Pete

Share this post


Link to post
Share on other sites

Just wondering if you've had a chance to give this any thought.

I thought you said you were going to keep your eyes open? I released the update (4.301) with the relevant changes a week ago, on the 31st July! Your eyes don't go through the relevant Announcements it seems -- in this case FSX Downloads?

Regards

Pete

Cannot find V4.301 in www.schiratti.com/dowson, neither in flightsim.com, where is it ?-

Share this post


Link to post
Share on other sites
Had it almost in my nose (here in the stickies)

No, not in the stickies, in the Announcements, as I said (remember I actually said "Your eyes don't go through the relevant Announcements it seems -- in this case FSX Downloads?".

The Announcements contain lots of things to keep users informed and up to date, including ALL interim versions. Between every version you see in the official download site (the Schiratti one) there are often up to 10 interim updates and usually lots of other information. That's what I meant when I said you don't "keep an eye out".

The Announcements are put at the top of the Forum, above everything else, for a purpose: so that they will usually be seen every time you visit. I make sure, with the two Downloads ones especially, that there's an update date in the title, but even if I didn't you should be able to see which ones have changed since your last visit by the highlighting of the entries icon.

Regards

Pete

Share this post


Link to post
Share on other sites

I downloaded V4.301.- I consists in a new dll; I replaced the old one with this one, and panning works almost the same, perhaps slightly smoother than before, but not as well as with FSX in control.-

Should I change something in my hat configuration ?

Share this post


Link to post
Share on other sites
I downloaded V4.301.- I consists in a new dll

Yes, of course it does. That''s what it says in the description! Interim updates are always by DLL replacement! Have you never looked before, not ever, in the years I've been doing this?

Incidentally, 4.301 has since been replaced by 4.302 and then 4.303, but neither of those affect this change.

I replaced the old one with this one, and panning works almost the same, perhaps slightly smoother than before, but not as well as with FSX in control.-

Should I change something in my hat configuration ?

Here it works absolutely the same as in FSX. I have no idea what your hat configuration looks like, so how can I suggest any change? I have a hat assigned to the Pan View axis in FSUIPC4's Axis Assignments. That's it, nothing else to assign.

It sounds like you are still using the Button assignments either instead, or as well. Check all this. The improved operation can only work with the axis assignment, and that is regulated to provide exactly the same repeat rate as demonstrated by FSX.

In other words, for the same assignment, FSUIPC4 is now doing the same as FSX, so I cannot do any more.

Regards

Pete

Share this post


Link to post
Share on other sites
"I replaced the old one with this one, and panning works almost the same, perhaps slightly smoother than before, but not as well as with FSX in control.-

Should I change something in my hat configuration ?"

Here it works absolutely the same as in FSX. I have no idea what your hat configuration looks like, so how can I suggest any change? I have a hat assigned to the Pan View axis in FSUIPC4's Axis Assignments. That's it, nothing else to assign.

It sounds like you are still using the Button assignments either instead, or as well. Check all this. The improved operation can only work with the axis assignment, and that is regulated to provide exactly the same repeat rate as demonstrated by FSX.

In other words, for the same assignment, FSUIPC4 is now doing the same as FSX, so I cannot do any more.

Regards

Pete

Pete - It's a huge improvement and is 100% FSX like except for a very brief intermittent stutter if you keep the hat "pegged" in one direction. A non-issue in practicality.

Thanks very much.

I'm guessing the person above is sending a right side button control in the Axis Assignment tab which you don't want to do. All I did was scan the hat button in Axis Assignment (in my case Joy #2 P) and "Send to FS as normal axis" on the left side as "Pan View". It works great, it's fast and smooth.

Thanks again.

Bruce

Share this post


Link to post
Share on other sites

Pete - It's a huge improvement and is 100% FSX like except for a very brief intermittent stutter if you keep the hat "pegged" in one direction. A non-issue in practicality.

I suspect the stutter will be related to the nature of the asynchronous interface used, the Windows messaging system, so it will vary from system to system depending on performance and workload.

It works great, it's fast and smooth.

Good. Thanks for confirming.

Regards

Pete

Share this post


Link to post
Share on other sites

I deleted all the buttons configuration related to POV and map only the ax to pan view, and now it works smoothly.-

Something strange although happens, the POV doesnt work at all when in instant replay, it works OK when joysticks are controlled by FSX.-

Share this post


Link to post
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...

×
×
  • 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.