Page 1 of 1

[2.0.35] "Request not satisfied" interruption doesn't work

Posted: Mon Feb 24, 2025 1:54 pm
by erkki772
This new update broke that interruption. Cargo count works but not request.

Re: [2.0.35] "Request not satisfied" interruption doesn't work

Posted: Mon Feb 24, 2025 4:29 pm
by Muche
It seems only requests of the planet the platform is in orbit of are checked.
Not-checked requests are satisfied by default.

Your request Legendary superconductors from Gleba is not checked above Nauvis, so it's satisfied by default; not-satisfied condition is therefore false and interrupt doesn't trigger.

Re: [2.0.35] "Request not satisfied" interruption doesn't work

Posted: Mon Feb 24, 2025 4:44 pm
by erkki772
Muche wrote: Mon Feb 24, 2025 4:29 pm It seems only requests of the planet the platform is in orbit of are checked.
Not-checked requests are satisfied by default.

Your request Legendary superconductors from Gleba is not checked above Nauvis, so it's satisfied by default; not-satisfied condition is therefore false and interrupt doesn't trigger.
This condition did work before this new version. Maybe it was changed to read only current planet routes

Re: [2.0.35] "Request not satisfied" interruption doesn't work

Posted: Mon Feb 24, 2025 4:56 pm
by Muche
If it worked in 2.0.32 then it might be related to the fix for 119181 Interrupts stop working on space platforms when left alone and time passed doesn't go up that went into 2.0.33.

Re: [2.0.35] "Request not satisfied" interruption doesn't work

Posted: Mon Feb 24, 2025 6:32 pm
by Muche
I tried it with v2.0.14 I had laying around and it works the same way.
127100-NonActiveRequest-satisfied.jpg
127100-NonActiveRequest-satisfied.jpg (53.26 KiB) Viewed 372 times
127100-ActiveRequest-notSatisfied.jpg
127100-ActiveRequest-notSatisfied.jpg (53.56 KiB) Viewed 372 times