VTB switches

[FSKRipper]

Hey guys, I have a question regarding the VTB.

 

I have seen a facile description of the left and right parameter Input Switches in the manual and some detailed information in Chuck's guide.

 

Are these switches already functioning and if yes how (only got luck with the waypoint change switch)?

[Azrayen]

Not that I'm aware of.

Not sure it's worth it, by the way... (apart for "N", which is useful)

[FSKRipper]

Thanks for the reply, I thought it might come in handy for bullseye reporting. I'm very happy with this plane but having 8 switches from which I don't have a clue what they do made me feel sick :lol:

[Zeus67]

Hey guys, I have a question regarding the VTB.

 

I have seen a facile description of the left and right parameter Input Switches in the manual and some detailed information in Chuck's guide.

 

Are these switches already functioning and if yes how (only got luck with the waypoint change switch)?

 

There is one button that is working. The N button. It selects which waypoint becomes the bullseye. Default value is 0. Max value is the last waypointg. It does not cycle.

[jaguara5]

There is one button that is working. The N button. It selects which waypoint becomes the bullseye. Default value is 0. Max value is the last waypointg. It does not cycle.

Will the other switches (functionality of them was discussed in another thread in the past) be implemented in the future?

And by the way, is it realistic to complete the module until end of the year?

[Rlaxoxo]

There is one button that is working. The N button. It selects which waypoint becomes the bullseye. Default value is 0. Max value is the last waypointg. It does not cycle.

 

Hey Zeus I've tried your previous "How to" to display waypoints on VTB but it doesn't work for me could you tell us how to do it little more detailed in case i messed up something?

[Zeus67]

Hey Zeus I've tried your previous "How to" to display waypoints on VTB but it doesn't work for me could you tell us how to do it little more detailed in case i messed up something?

 

I am going to update it and then do a video.

[Rlaxoxo]

I am going to update it and then do a video.

 

Alright, cool

[myHelljumper]

As a note, it does work for me but you can display each waypoints multiple times

[Zeus67]

As a note, it does work for me but you can display each waypoints multiple times

 

Fixed in development. Undergoing test and will be released next update (We hope :smartass:)

[myHelljumper]

Nice !!

[VTJS17_Fire]

I am going to update it and then do a video.

 

Fixed in development. Undergoing test and will be released next update (We hope :smartass:)

Great news, Zeus. Thanks! :thumbup:

[Zeus67]

How to display the waypoints in the VTB:

 

1. Click on the PREP button

2. Enter the waypoint number

3. Click on the VAL button.

 

The waypoint will be displayed. If the waypoint was already shown then it will be removed from the display.

 

To remove ALL waypoints click on the VTB ALLEG switch.

 

Conditions:

- Only 5 waypoints can be displayed at the same time.

- Selected waypoint must be inside the VTB display range (radar range).

- Selected waypoint must be inside the radar aperture limits: +/- 60 degrees azimuth.

 

[Britchot]

Great video tutorial Zeus. It worked great for me tonight running the Sidewinder low-level route. The double tap of Prep is a lifesaver when down low trying to figure out your next heading, too.

 

Piece-by-piece I'm starting to unravel the navigation system.

[VTJS17_Fire]

Conditions:

- Only 5 waypoints can be displayed at the same time.

- Selected waypoint must be inside the VTB display range (radar range).

- Selected waypoint must be inside the radar aperture limits: +/- 60 degrees azimuth.

Has the display range to be great enough, before the waypoint is added to the VTB? Or in other words: Is the waypoint still added, but out of the VTB screen or does it not add the waypoint, when it is out of display range?

 

And do we have to set the radar elevation limits within the altitude of the waypoint or is it equal?

 

Thanks in advance!

[Azrayen]

And do we have to set the radar elevation limits within the altitude of the waypoint or is it equal?

What for??

 

WP altitudes are mostly on the ground. Radar will be set to avoid the ground (and enhancing detection) as much as possible. So what would be the logic behind implementing such a limit?

[david.lind]

Has the display range to be great enough, before the waypoint is added to the VTB? Or in other words: Is the waypoint still added, but out of the VTB screen or does it not add the waypoint, when it is out of display range?

 

And do we have to set the radar elevation limits within the altitude of the waypoint or is it equal?

 

Thanks in advance!

 

Fire it's already in the current release, try it out :)

"prepping" the way-points before they are in view works.

Doesn't work in B-scope I think.

[VTJS17_Fire]

Fire it's already in the current release, try it out :)

"prepping" the way-points before they are in view works.

Doesn't work in B-scope I think.

Yeah, I tried it some days ago but maybe it was before the latest patch (Nevada).

 

Tried it today again, but it didn't work. I have to say, that I always work in B-scope. This is, because I flew many years in the F-15C and the B-scope is like the VSD in the Eagle. :) Maybe I have to switch to PPI view for that feature.

 

Anyway, the added waypoint was always shown at the bottom of the VTB screen, independent of the display range.

 

 

Is it currently a bug for the B-scope and should work there, as well? :huh:

[Zeus67]

Yeah, I tried it some days ago but maybe it was before the latest patch (Nevada).

 

Tried it today again, but it didn't work. I have to say, that I always work in B-scope. This is, because I flew many years in the F-15C and the B-scope is like the VSD in the Eagle. :) Maybe I have to switch to PPI view for that feature.

 

Anyway, the added waypoint was always shown at the bottom of the VTB screen, independent of the display range.

 

 

Is it currently a bug for the B-scope and should work there, as well? :huh:

 

It should work on all scope modes. I'll check and fix if necessary.

[Rlaxoxo]

Zeus, Today I got this working before you released the video and thx for that as well cleared some other stuff at the same time.

 

Meanwhile what I originally noticed that If I display a Waypoint on the VTB and Do a roll or move in a certain way it behaves as the old contacts did on VTB they move across the VTB screen left and right

 

Is this fixed in your dev version cus it looks a bit different?

[Britchot]

If you turn away from the waypoint it should move laterally across the VTB screen. Perhaps I am misunderstanding, are you just speaking of a roll without a heading change?

[Azrayen]

Yes, that's what he was speaking about.

And it's already reported.

[Zeus67]

Yes, that's what he was speaking about.

And it's already reported.

 

And it is fixed in development. :smartass:

[jaguara5]

How to display the waypoints in the VTB:

 

1. Click on the PREP button

2. Enter the waypoint number

3. Click on the VAL button.

 

The waypoint will be displayed. If the waypoint was already shown then it will be removed from the display.

 

To remove ALL waypoints click on the VTB ALLEG switch.

 

Conditions:

- Only 5 waypoints can be displayed at the same time.

- Selected waypoint must be inside the VTB display range (radar range).

- Selected waypoint must be inside the radar aperture limits: +/- 60 degrees azimuth.

 

Aren't the mark points supposed to be shown on the VTB?

[Azrayen]

Markpoints are buts too, so you can select them the same way to be shown on VTB.