Jump to content
The simFlight Network Forums
Sign in to follow this  
tex1763

NEXT_VIEW and PREV_VIEW not working?

Recommended Posts

I cannot get these FS controls working when I associate them to the yoke buttons. I tried to do that both via FSUIPC user interface and via FSUIPC.INI editing.

This is from my FSUIPC.INI:

14=P0,7,C65827,0 ;NEXT_VIEW

15=P0,6,C65828,0 ;PREV_VIEW

I also tried editing fs9.cfg and changing the default lines NEXT_VIEW=9,10 and PREV_VIEW=9,11 in 83,8 and 83,9 which makes more sense to me, but without result.

The only way for cycling views via FSUIPC seems to associate the buttons to keypress S and shift+S, but my aim was to program my yoke with Fsuipc only through FS controls, avoiding keyboard commands as far as possible.

All others FS controls I'm using on yoke assignations are working fine.

What is wrong?

Regards

Share this post


Link to post
Share on other sites
I cannot get these FS controls working when I associate them to the yoke buttons.

All FSUIPC does with FS controls is send them to FS in exactly the same way as FS itself does, through its messaging system. There's absolutely no difference.

14=P0,7,C65827,0 ;NEXT_VIEW

15=P0,6,C65828,0 ;PREV_VIEW

I think those controls move between different view windows you may have opened with the View menu entry "New View". Is that what you are trying to do?

The only way for cycling views via FSUIPC seems to associate the buttons to keypress S and shift+S

S and shift+S are assigned in FS by default to the controls VIEW_MODE (65567) and VIEW_MODE_REV (65749). I think you are getting confused between different view windows and different view modes.

What is wrong?

If you are not sure what controls do what, simply enable FSUIPC's Event logging, then operate the control via the normal keyboard or FS button assignments, and view the result in the FSUIPC log file. You will see lines like this logged:

158062 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE

Note that the names, like VIEW_MODE, used in FSUIPC are obtained from FS's "CONTROLS.DLL", and are the same as those used in its own CFG files. I knowe they aren't always self-explanatory, so checking is really the only sensible way.

Regards

Pete

Share this post


Link to post
Share on other sites

I think those controls move between different view windows you may have opened with the View menu entry "New View". Is that what you are trying to do?

Not exactly...I just want to cycle among 2D Cockpit, VC, Observer and Tower views

S and shift+S are assigned in FS by default to the controls VIEW_MODE (65567) and VIEW_MODE_REV (65749). I think you are getting confused between different view windows and different view modes.

I think this was definitely the point...I completely missed it :oops:

If you are not sure what controls do what, simply enable FSUIPC's Event logging, then operate the control via the normal keyboard or FS button assignments, and view the result in the FSUIPC log file. You will see lines like this logged:

158062 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE

Note that the names, like VIEW_MODE, used in FSUIPC are obtained from FS's "CONTROLS.DLL", and are the same as those used in its own CFG files. I knowe they aren't always self-explanatory, so checking is really the only sensible way.

This will be very, very useful for the future...thank you

Best regards

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...
Sign in to follow this  

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