That's weird. Barrier Gate works perfectly fine for me both in singleplayer, multiplayer and on the latest dev builds. It looks like the station part you're docking/undocking from failed to load the textures on your client.
Do you happen to know whether the other dockable parts of B and C were also missing? Might be a hash collision on the textures they use.
(11-26-2024, 11:33 PM)Sombs Wrote: That's weird. Barrier Gate works perfectly fine for me both in singleplayer, multiplayer and on the latest dev builds. It looks like the station part you're docking/undocking from failed to load the textures on your client.
Do you happen to know whether the other dockable parts of B and C were also missing? Might be a hash collision on the textures they use.
Just what I thought. I haven't been able to reproduce this issue. If this is persistent on your end, do me a favor and help us investigating.
- You're using a Longhorn in the screenshots. Does this issue still occur when you use a different ship? (You can make a new character very quickly with /restart FLCoronado, it will start you out at Barrier Gate Station A.)
- - - > If it works with a different ship and the station parts show up normally, switch back to your Longhorn again. Does the issue appear again?
- - - > If the issue only appears when using your Longhorn, please unequip all weapons and other equipment, then undock and see if the issue still occurs. If not, it might be related to your equipment.
- - - > Newport Station in Sigma-13, Noshima Freeport in Shikoku and Monte Carlo Freeport in Provence are using the same station parts for docking. If this issue persists at these locations too, it could be the result of a faulty model file on your PC.
Since I can't reproduce this glitch myself, your input would be most helpful!
That's a different station model used there. Something I wasn't able to replicate either. My suggestion is that you might want to try a clean re-install of Discovery and see if that fixes it.