Jump to content

[Investigating] SLV VV (Slave to Velosity Vector) Designate way off in A/G mode


Recommended Posts

Posted (edited)

Have been trying this out and each time I Designate from SLV VV mode on Tpod in A/G mode I get a random point no where near the VV.

Usually it is designating somewhere near to where Snowplow would be.

Tried it in NAV mode it works fine... switch to A/G it's not

cheers, Hbomb

Edited by Hbomb
  • 2 weeks later...
Posted (edited)
On 9/1/2021 at 8:26 PM, Hbomb said:

Have been trying this out and each time I Designate from SLV VV mode on Tpod in A/G mode I get a random point no where near the VV.

Usually it is designating somewhere near to where Snowplow would be.

Tried it in NAV mode it works fine... switch to A/G it's not

cheers, Hbomb

 

For me, the TPOD designates to where the gun pipper is pointing, not the VV. I think this makes sense since that's where the plane (and therefore the TPOD) is actually pointing. The VV shows where the plane WILL GO, not where it's currently pointing.

Edited by Sandmonkee

"...I just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

Posted

Hey,
In A/G mode, when going ou of TPOD mode and undesignating, the TPOD is correctly slaved to the VV from what i've just tried.
When entering the SNWPLW the TPOD piper is indeed slaved a bit lower.
Can you submit a track or a small video of what you describe ? 
Otherwise i'll close the topic

Posted

Alpha Juliet,

I was just pointing out when slaving the Targeting Pod in A/G mode to the Velocity vector is not designating exactly to the Velocity Vector as the mode requires.

 

I said that when designating In Nav mode it works fine as in Slaves and designates exactly to the Velocity Vector.

 

If it works in one mode should it not the other ??? considering A/G mode it the primary mode to use this?

 

 

Posted

Alpha Juliet,

"In A/G mode, when going ou of TPOD mode and undesignating, the TPOD is correctly slaved to the VV from what i've just tried."

 

Ok I have just tested and with the Targeting pod Un-Selected It works.

 

but still with the Tpod selected in A/G mode It Does not Slave to the Velocity Vector as stated.

Posted

You are right, it doesn't slave it to the VV. I'm adding it to our bug tracker.
To help the devs seeing the faulty combination of inputs, could you submit a small track of the issue here ?


Thanks for the report 🙂

  • AlphaJuliet changed the title to [REPORTED] SLV VV (Slave to Velosity Vector) Designate way off in A/G mode
  • 1 month later...
  • 1 month later...
Posted

AlphaJuliet,

Just to re visit this.... was trying to slave the DMT as well as the TGP today and it still was out of wack in A/G Mode... 

YES the TGP does slave to the VV now in A/G mode (in a certain way of doing it), but it also tries to slave to the Waypoint when you Undesignate it .

Shouldn't it work the same every time in A/G mode, Nav Mode, ETC?.

Also as you can see in the Track, The DMT is now not Slaving to the VV Point when in A/G Mode....

Thanks,

Hbomb

 

DMT TGP VVSLV .trk

  • 2 weeks later...
  • AlphaJuliet changed the title to [Investigating] SLV VV (Slave to Velosity Vector) Designate way off in A/G mode
  • 1 year later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...