Replace crosshairs with current heading and flight direction marker when enabled in config section graphics with
<var name="draw_heading_marker" value="true"/>
Very very nice... except... did you notice the marker tends to stray off towards the sun for speeds below 10m/s ? What's up with that? I've been debugging it to no avail.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Very very nice... except... did you notice the marker tends to stray
off towards the sun for speeds below 10m/s ? What's up with that? I've
been debugging it to no avail.
From my understanding it is the velocity governor enforcing the target
velocity. In the modelview mission it is more apparent. The governor
seems to pick the nearby station/planet as frame of reference? And you
will get like 100m/s extra messing up the heading marker.
One could maybe try to figure out what the governor is up to and correct
for it. The pilot would have to be (made) aware of current possibly
moving frame of reference somehow though. And the moving part is not
very inuitive I fear.
Alternatively I've been thinking about displaing the whole velocity
vector(xyz) in addition to relative speed. This should give the pilot
enough info to see what the governor is doing.
No, it's not the governor, it looks more like a coordinate system snafu. You can see how it's drift towards the sun (which happens to be 0,0,0 in world coordinates) is inversely proportional to the speed.
It smells like a coordinate system mistake somewhere, because if indeed the camera was 0,0,0 in GL coordinates, and since indeed the velocity vector that is drawn "v" is normalized, then there is no reason for the marker's placement to be affected by the absolute speed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As soon as you make it relative to some moving reference frame you might
get erratic/unintuitive heading marker behavior depending on what yor
reference is doing(has changing velocity?). This is what I meant with
having to communicate to the pilot what his current frame of reference is.
Anyway, yeah, I thought so at first, but without making it relative it's nigh useless. I noticed near Cephid 17, near "fast"-orbiting stations, that the indicator is almost overriden by orbital velocity, all it shows is orbital velocity.
No, I think it needs to be relative to be useful. But it's also true what you say. Maybe we should have an item somewhere marking velocity reference units. Maybe on the radar, maybe showing its naem... dunno.
But that's water under another bridge.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Agree, the relative velocity variant seems to be more usable. The
reference frame display/marker issue can be handled as a separate item.
Maybe something for the forum, to see what ideas people might come up with.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Very very nice... except... did you notice the marker tends to stray off towards the sun for speeds below 10m/s ? What's up with that? I've been debugging it to no avail.
Am 30.03.2013 07:51, schrieb Klauss++:
One could maybe try to figure out what the governor is up to and correct
for it. The pilot would have to be (made) aware of current possibly
moving frame of reference somehow though. And the moving part is not
very inuitive I fear.
Alternatively I've been thinking about displaing the whole velocity
vector(xyz) in addition to relative speed. This should give the pilot
enough info to see what the governor is doing.
Related
Patches:
#53No, it's not the governor, it looks more like a coordinate system snafu. You can see how it's drift towards the sun (which happens to be 0,0,0 in world coordinates) is inversely proportional to the speed.
It smells like a coordinate system mistake somewhere, because if indeed the camera was 0,0,0 in GL coordinates, and since indeed the velocity vector that is drawn "v" is normalized, then there is no reason for the marker's placement to be affected by the absolute speed.
Scratch that, it has to be relative to the reference frame. I'll do that.
Am 30.03.2013 20:39, schrieb Klauss++:
Related
Patches:
#53What's this way you reply with all those quotes?
Anyway, yeah, I thought so at first, but without making it relative it's nigh useless. I noticed near Cephid 17, near "fast"-orbiting stations, that the indicator is almost overriden by orbital velocity, all it shows is orbital velocity.
No, I think it needs to be relative to be useful. But it's also true what you say. Maybe we should have an item somewhere marking velocity reference units. Maybe on the radar, maybe showing its naem... dunno.
But that's water under another bridge.
Agree, the relative velocity variant seems to be more usable. The
reference frame display/marker issue can be handled as a separate item.
Maybe something for the forum, to see what ideas people might come up with.