Re: [Release] Navigation MFD 1.3.1
Posted: Tue Nov 04, 2014 6:45 pm
Thanks, cim - I should've posted that in the Bugs section, as it affected my hud's built-in target system display too.
For information and discussion about Oolite.
https://bb.oolite.space/
is
rather confusing to have two systems with the same co-ordinates. Is there some hand-wavium that explains this?It's no mystery - the two planets orbit the same star. There are a few other such pairs.phkb wrote:I think both these systems have the same co-ordinates which is probably causing the confusion. Actually, it is rather confusing to have two systems with the same co-ordinates. Is there some hand-wavium that explains this?
I would suggest that they are binary stars, not planets (they are different suns).Wildeblood wrote:It's no mystery - the two planets orbit the same star. There are a few other such pairs.phkb wrote:I think both these systems have the same co-ordinates which is probably causing the confusion. Actually, it is rather confusing to have two systems with the same co-ordinates. Is there some hand-wavium that explains this?
I'm having trouble reproducing this. I launch, switch the MFD on and it works ok. I switch to F5 and back to F1 and it still works. Did I understand you correctly?phkb wrote:Another minor bug report: If you have a compass destination set (like Planet), then go to the F5, F6, F7 or F8 pages, and then go back to your main screen, the "Space Compass Target" shows "Initializing..." but never goes back to the original setting.
I've seen that happen too, but don't recall the exact circumstances.phkb wrote:Another minor bug report: If you have a compass destination set (like Planet), then go to the F5, F6, F7 or F8 pages, and then go back to your main screen, the "Space Compass Target" shows "Initializing..." but never goes back to the original setting.
Code: Select all
this.compassTargetChanged = function(whom, mode) {
this.$targetName = "Initializing...";
if (!whom) return;//null case
whom
" is showing up as null on my machine when returning from any of the display screens (F5-F8) (I put a debug message in here), so "this.$targetName
" never gets set back to the original setting. compassTargetChanged
event is firing for each of the F5-F8 screens, even if the compass target hasn't changed. I suspect this is only happening on Windows.Code: Select all
this.compassTargetChanged = function(whom, mode) {
var hold = this.$targetName;
this.$targetName = "Initializing...";
if (!whom) {
this.$targetName = hold;
return;//null case
}
Only if your mods include a simplified HUD with no compass in GUI views. (I haven't tried Numeric HUD, but know it's popular and assume it changes to a simpler HUD because of the mess it puts centre of screen.)phkb wrote:Actually, no. I'm using the coluber hud with personal mods. You suspect the hud is the culprit?
Pro-tip: Place the compass off screen by setting both x and x_origin positive. To avoid the problem you had, the compass has to be drawn on the HUD, but it doesn't have to be drawn on the screen.phkb wrote:Wait, just had a thought. One of my mods was to switch the hud from the full version to a cut down version when going to one of the F5-8 screen.s. I'm turning off the space compass, then turning it back on when an exterior view is selected.