[Klonan] [2.1.7] Platform-to-platform construction requests deadlock

[Ctri]

Description
I've noticed when building new platforms in orbit above Nauvis that they often were having random build pieces requested, but not fulfilled.
Another user in another thread said they'd had this problem, and that unchecking "Provide materials to other platforms" solved the issue; and this has allowed me to concretely isolate the issue.

Example of a deadlock:

06-25-2026, 11-33-47.png (103.58 KiB) Viewed 650 times

Platform 5 is requesting 28 lights.
Platform 2 has 50, and "Provide materials to other platforms" is enabled.
Platform 3 has 29, and "Provide materials to other platforms" is enabled.
Platform 4 had 8, and "Provide materials to other platforms" was enabled; it had no impact on the deadlock during experimentation, and I have deleted it for conciseness.

Steps to reproduce:Unclear, but 1 or more space platforms with the required items appears to be a component of the issue.
In my experiment, platforms 3 and 4 are able to request and supply other materials to other platforms and the surface, and have been in position for some time before I noticed.

Steps to resolve: Manually uncheck "Provide materials to other platforms" on all platforms with enough lights to fulfill the request, or have all providing platforms leave orbit.

[Klonan]

Thanks for the report,

This is fixed in the next release

[Ctri]

Thanks Klonan, ecstatic to hear it

I'm intrigued, what was the issue?
I came here to post a theory that it might have something to do with rocket payload default values not being met on supplying platforms, only to discover that you've solved it already!

[Klonan]

Thanks Klonan, ecstatic to hear it

I'm intrigued, what was the issue?
I came here to post a theory that it might have something to do with rocket payload default values not being met on supplying platforms, only to discover that you've solved it already!

There are 2 checks for platform transfers:
1. Platform has 'Provide to other platforms' enabled
2. Platform is at a stop with 'Unload' checked

But the transitional request logic had a missing check for the 'Unload' checkbox, so it thought the platform would send over the item, so did not schedule a rocket

[Senpai1337]

Thanks for the report,

This is fixed in the next release

I'm able to reproduce this in 2.1.8, but it seems to primarily happen around when another ship with provide materials to other platforms and is stuck in a "No path" state, and there are construction requests, this causes the construction requests to deadlock.

Ship 1:
* Be built and have "No path" state to Aquilo
* Have provide materials to other platforms enabled

Ship 2:
* Request construction materials
-> Dead locks waiting for other ship to give materials
* Have explicit planet request for materials
-> Still dead locked, because it seems to be prioritizing the ship-to-ship request (that is deadlocked)


Note:
Even if you pause Ship 1, so it is no longer in a "No path" state, the requests are still dead locked. You need to fully exit the "No path" state by going to your current planet or any other planet, then the issue gets resolved. Issue also gets resolved if you turn off "Provide materials to other platforms"

stuff

broken no path other ship.png (275.76 KiB) Viewed 332 times

dead locked request.png (145.58 KiB) Viewed 332 times

request direct from Nauvis.png (219.44 KiB) Viewed 332 times

Happy to attach a save with a reproduce if needed.

[Loewchen]

I'm able to reproduce this in 2.1.8

Fixed for the next release means the devs don't want to travel back in time to include the fix in the current release.

[Senpai1337]

I'm able to reproduce this in 2.1.8

Fixed for the next release means the devs don't want to travel back in time to include the fix in the current release.

Nice, hope it's fixed in 2.1.9. Wasn't sure if his original message meant 2.1.8 or if it will be fixed in 2.1.9

[Ctri]

Thanks Klonan, ecstatic to hear it

There are 2 checks for platform transfers:
1. Platform has 'Provide to other platforms' enabled
2. Platform is at a stop with 'Unload' checked

But the transitional request logic had a missing check for the 'Unload' checkbox, so it thought the platform would send over the item, so did not schedule a rocket

Aaah, I didn't even consider that setting! Just seen it in the change log today, tyvm!