Jump to content

FCR TMS right wierd behavior

VarZat

By VarZat
in Bugs and Problems

 Share
Go to solution Solved by Lord Vader,

Recommended Posts

VarZat

VarZat

Posted
Posted (edited)

Linked is a video i made showing the issue. I dont know if this is intentional but this has been going on ever since the open beta 2.7.18.30348 patch.

What happens is when you press TMS right with the FCR as SOI in CRM mode it seems to move the current steerpoint very far away, or something else happens to it.

After you have pressed TMS right TWICE again (Interval between presses can be completely random) it returns to its ordinary place. You can see in the video after i pressed TMS right ONCE the steerpoint moves from 27.9NM, heading 295 to 517.8NM, heading 283. In the HUD you can also see the steering cue just completely dissapear.

Is this a bug or is it correct-as-is? 

The recording was on the instant action "Takeoff" mission in Caucasus in SP, though this happens anywhere.

Cheers!

Edited by VarZat
  • Like 3
  • Thanks 1

Varzat_signatur.png

SickSidewinder9

SickSidewinder9

Posted
Posted

Interesting.

I was also wondering what is going on with TMS right while in TWS mode.  doesn't wanna jump around targets quite right.  Haven't noticed what you're showing.  I'll have to check now.  Would explain some of the "drift" with ground level steerpoints too maybe.

VarZat

VarZat

Posted
  • Author
Posted
18 minutes ago, SickSidewinder9 said:

Interesting.

I was also wondering what is going on with TMS right while in TWS mode.  doesn't wanna jump around targets quite right.  Haven't noticed what you're showing.  I'll have to check now.  Would explain some of the "drift" with ground level steerpoints too maybe.

I used RWS in the video. I barely ever use TWS really so i dont know if there is any issues there. Im interested if it acts the same for you too in RWS

Varzat_signatur.png

SickSidewinder9

SickSidewinder9

Posted
Posted
Just now, VarZat said:

I used RWS in the video. I barely ever use TWS really so i dont know if there is any issues there. Im interested if it acts the same for you too in RWS

yeah, it's hard to use because I don't think it's working right.

  • Like 1
Moonshine

Moonshine

Posted
Posted

that is definitely an interesting one. see my track, somehow it seems to show range to the Bullseye compass circle on the F10 map, even though blue bullseye is much closer.. i have no idea how to explain that.

 

my approach:

1. tested behaviour shown in the YT video by OP. (TWS -> TMS Right -> range to STP shows distance as explained by OP -> TMS right again -> nothing happens -> TMS right again -> back to correct STP distance and heading). noted that he is on the ground, so i figured maybe "no-rad" due to weight on wheels

2. so i took off, gear up, tested again. still same issue.

3. tried to figure out where that 500+nm range comes from, checked map to see where bullseye is. found bullseye rather close, yet the neutral bullseye/the compass rose is right that distance away as shown in the plane

 

Track is here as it is 1.5MB too large: https://drive.google.com/file/d/1jZSJyVOFYHbxG6rzji87hXynh4hGbWdY/view?usp=sharing

  • Like 3
VarZat

VarZat

Posted
  • Author
Posted (edited)
2 hours ago, Moonshine said:

that is definitely an interesting one. see my track, somehow it seems to show range to the Bullseye compass circle on the F10 map, even though blue bullseye is much closer.. i have no idea how to explain that.

 

my approach:

1. tested behaviour shown in the YT video by OP. (TWS -> TMS Right -> range to STP shows distance as explained by OP -> TMS right again -> nothing happens -> TMS right again -> back to correct STP distance and heading). noted that he is on the ground, so i figured maybe "no-rad" due to weight on wheels

2. so i took off, gear up, tested again. still same issue.

3. tried to figure out where that 500+nm range comes from, checked map to see where bullseye is. found bullseye rather close, yet the neutral bullseye/the compass rose is right that distance away as shown in the plane

 

Track is here as it is 1.5MB too large: https://drive.google.com/file/d/1jZSJyVOFYHbxG6rzji87hXynh4hGbWdY/view?usp=sharing

Tested now, and it points right at the compass rose/ neutral bullseye. Wierd stuff

Edited by VarZat

Varzat_signatur.png

Moonshine

Moonshine

Posted
Posted (edited)

i am not sure, the compass rose does represent neutral bullseye. maybe test what happens if you move the neutral bullseye around. 

 

i am even more confused as how would anything thats done on the FCR affect the navigation to the selected steerpoint? and here we are in NAV mode, we did not lock any target that could switch symbology to the target range etc.. and even then the HSI should still give you info to the currently selected steerpoint...

 

also i am not sure if this issue presists in A-A mode or just in NAV as i did my test in NAV to try to replicate your YT video and provide a track for it (to avoid "missing trackfile" tag)

Edited by Moonshine
Moonshine

Moonshine

Posted
Posted (edited)

well, surely something is absolutely borked. no TMS input on the A-A FCR should change anything in regards to the selected steerpoint and therefore ownship navigation information. 

i get it, on the HSD you can select steerpoints with the cursor etc but on the FCR? especially in A-A radar. 

totally different for AG-radar thats clear

Edited by Moonshine
VarZat

VarZat

Posted
  • Author
Posted

Something is definitly acting odd. Ill add a track file soon. Either this is just a mistake or a half implemented feature that we dont now about

Trying it in missile override it automatically goes back to the original steerpoint when i go into missile override and it doesnt change like in NAV

Varzat_signatur.png

Moonshine

Moonshine

Posted
Posted (edited)

tested it again. only occurs in NAV mode by the looks of it. and yes it always points a the compass rose. and that compass rose is the default bullseye location (where they are when you start creating a new mission prior to moving them)  WS_TMS_right_Range_info2.trk

edit: new mission, default neutral bullseye location.

image.png

 

I am so confused 😄 

Edited by Moonshine
  • Like 1
Moonshine

Moonshine

Posted
Posted (edited)

so to summarize: 

in NAV mode with FCR as SOI and in TWS mode, no contact on scope at all, pressing TMS right changes bearing and range information to a steerpoint. however no inputs for steerpoint change has been made at all with either the rocker switch, on the DED or on the HSD itself. 

That new bearing and range points to the default start location of the neutral bullseye and therefore the position of the compass rose on the F10 map at all times (even moving the neutral bullseye wont change it).

Pressing TMS right a second time does not do anything. pressing TMS right a third time returns navigation information to the selected steerpoint as indicated in the DED.

If the original steerpoint is inside the radar range, the white steerpoint marker can be found on the FCR. upon pressing TMS right the first time, that disappears, only to return after pressing TMS right 2 more times

 

Edited by Moonshine
  • Like 1
  • Thanks 1
dorianR666

dorianR666

Posted
Posted (edited)
14 hours ago, VarZat said:

Its still pointing at crimea for me

crimea is the internal 0; 0 coordinate of the caucasus map.

the bug is not tied to the compass' position. its just a coincidence that the mission editor places it to 0; 0 in a new mission file.

Edited by dorianR666
  • Like 1

CPU: AMD Ryzen 5 1600X

GPU: AMD RX 580

VarZat

VarZat

Posted
  • Author
Posted
8 minutes ago, dorianR666 said:

crimea is the internal 0; 0 coordinate of the caucasus map.

the bug is not tied to the compass' position. its just a coincidence that the map editor places it to 0; 0 in a new mission file.

 

Alright that explains that

Varzat_signatur.png

Guest
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

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