Bug BaseSyncMFD bug

aldarion

Member
Joined
Oct 20, 2007
Messages
47
Reaction score
0
Points
21
Location
Gdansk
This MFD loses sometimes the base name and it changes the name of the base to Surface. Can it be fixed?
Is the data actually lost too or only the name?

Sent from my SM-T310 using Tapatalk 4
 
This MFD loses sometimes the base name and it changes the name of the base to Surface. Can it be fixed?
Is the data actually lost too or only the name?

I hate this bug too. However, only the name is lost. When you select the base, note the Latitude and Longitude. When BaseSync resets to Target: Surface, the Latitude and Longitude remain the same, so you're still actually targeting the correct position on the surface body.

BaseSync-01_zpsc82c38a3.png


BaseSync-02_zps452e25ec.png


BaseSync-03_zpsb53b4587.png
 
Not always...

I hate this bug too. However, only the name is lost. When you select the base, note the Latitude and Longitude. When BaseSync resets to Target: Surface, the Latitude and Longitude remain the same, so you're still actually targeting the correct position on the surface body.

Well... didnt know about this post hehehe :facepalm: but not always remain the same parameters. Try it with DeltaGliderIV or any other vessel with Upper/Lower panels, just changing the views between panels, all that data will be full reseted to defaults. :chainsaw:
 
Well, Jarmonik is still around, though a bit silent lately after the D3D9 development tour de force, so if he feels like fixing this bug...
 
Last edited:
I could not confirm the bug.

On both the inline and DX9 clients, I targeted a base
base_sync1.PNG

and switched panels from middle to top and back several times.

Although BaseSync switched back to "surface", it still had the correct spot targeted :shrug:
base_sync2.PNG


Does the bug still occur when all modules are disabled except BaseSync?
 
Yes, I tested with my modules On and OFF (less the BaseSync and Sound) and have the same effect.

Targeted Cape Canaveral


After switch to upper panel (or lower one, its the same) I have this:


Im using WindowsXP SP3 and DirectX 9c
 
While I saw the bug reported by blixel and meson800, I've never noticed the one reported by McGalcri.
I'll try to reproduce it later today.
 
Back
Top