Wrong TWA in game UI
Post by iconPost by mak08 | 2018-10-23 | 21:29:16

Another bug warning here,
I often see incorrect TWA values in the VR game UI - sometimes more than 10° higher than the value reported by the server messages.

I have no idea how the game UI get at those numbers.

commenticon 8 Comments
Post by iconPost by Alex Wind | 2018-10-30 | 16:20:19
Same bug at me.
Post by iconPost by mak08 | 2018-11-23 | 11:22:40
Currently the heading readings differ by 10° between game UI and dashboard even immediately after an update (in Odyssey).
I'll go by the dashboard values and see what happens.
Post by iconPost by zezo | 2018-11-23 | 12:36:13
I'm sailing fixed TWA. Should avoid some unexpected sail changes, and the exact 125-130-135 timing should not be that important at those boat speeds.
Post by iconPost by mak08 | 2018-11-23 | 13:25:06
Yep. I've just verified that TWA sailing doesn't work well in those light winds :-)
Looks like neither the UI nor me can handle light winds really well, but I'm learning.
Meanwhile, the two TPNs at the top of fleet have done an incredible job.
Post by iconPost by zezo | 2018-11-23 | 15:33:47
Oops. The game UI just showed that he boat turned from TWA 135 to 140 by itself, and subsequently refused to set TWA 140. All that with TWA lock on.
Post by iconPost by Flying Phil | 2018-11-23 | 18:14:31
Exactly the same problem for me on odysee.
Post by iconPost by zezo | 2018-11-23 | 19:29:05
This it how it looks like. The client projects one directions, then gets the proper position from the server every 5 minutes and plots it.


Post by iconPost by zezo | 2018-11-23 | 19:31:00
I've seen better examples, but don't have the screenshot.

The track is smooth after a reload, so you can't see the effect later.
border
Topics list
Posts
border
2
border
border
4
border
border
6
border
border
8
border
border
48
border
border
17
border
border
4
border
border
Copyright 2009 by ZEZO.ORG. All Rights Reserved.