Thanks for the report,

This is now fixed for the next release


Hi Klonan,

I'm on the latest experimental ( 2.0.47 ) but i see some names are still being cut.

05-01-2025, 00-47-27.png


He meant it will be fixed for 2.0.48. As long as the thread is still under "Resolved for the next ...

Twisted_Code wrote: Sun Mar 23, 2025 12:09 am It's still happening

2.0.43 is not out yet

You can actually go to Crowdin and make the changes yourself, they will take effect next release.

Given the amount of friction removal of this signal creates and pain of trying to migrate it to something else, this signal will be restored for 2.0.36.


Thank you, from what I see this is a good decision for now. Perhaps a different icon or other migration can be added in the future. I ...

I wonder if this means we're gonna have 2 identical-looking icons for signals.

Just to make it a bit clearer, this is the issue I meant to report:

The "Ghost cursor selection" part has extraneous top padding compared to other parts of a window when clicking on machines from remote-view.

1739440114_sd9Bs.png

White arrow that points out the misalignment caused by it:

1739440165_JqdBP.png

This was previously reported in https://forums ...

Lou wrote: Tue Feb 04, 2025 1:37 pm Thanks again for the report and for the reproduction steps. It has been fixed for 2.0.34

Thank you for fixing!

Thank you for fixing!

To add, based on what you said and what I'm seeing, I guess the simplest steps to reproduce this bug is to
- have 2 similar platforms, A and B
- make platform A have some temporary stops
- copy hub A to B
- flip B's "Automatic / Paused thrust" switch to "Automatic"
- wait for it to reach a ...

Thanks for reporting this. Your shattered planet platforms have no schedule, yet they are moving forward and when platform B transitions to the shattered planet connection, it causes the crash. Changing mods or updating the game temporarily fixes the issue because platforms recalculate their path ...

Hi, you guys probably already fixed this bug internally in 2.0.33 (several people in a multiplayer server got the same crash at the same C++ function from 2.0.31 and you guys probably already saw the anonymous logs) but I just want to report this nonetheless just in case since it wasn't mentioned in ...

Hi, someone in that multiplayer server's Discord said they could reproduce it by
- placing a furnace
- copying it
- pressing R once
- super-force-build it on top of itself
I can reproduce it myself with the same steps:

Thank you for the report, however, I am a bit confused by your steps.


Sorry for the confusing steps, I forgot that I had to enable editor mode to reproduce this by myself:
rotat.mp4
I'm not sure whether this invalidates the bug report itself... For the actual bug, I unfortunately do not know ...

I found this bug in a multiplayer session when someone pasted in a starter base blueprint rotated 90 degrees.

01-28-2025, 02-10-06.png

Attached fucked up furnace.zip is a save file post-paste post-build. Some things I noticed:
- Furnace works fine
- If you have a furnace in your hand and try to ...

Same issue here on space platforms (version 2.0.32).

StrangePan wrote: Thu Jan 23, 2025 11:58 am Hello, sorry about the miscategorization and thank you for the bug report. This issue will be fixed in 2.0.33.

Thank you so much for fixing this!

Hi, it seems my thread was moved to "Not a bug" without an explanation. Should I instead do a feature request/suggestion for the viewport zoom/position to be fixed for spidertrons?

When I open a spidertron and drive it around when the window is still open, its viewport (the part in the window where it renders the spidertron in its current state on a checkerboard grid) zooms in and out very nauseatingly.

spidertron_zooming.mp4

I think this can be fixed if the zoom was fixed ...