[boskid] [2.0.18] Orbital logistics tips&tricks crash (position is missing)

[OdessaKwinn]

https://discord.com/channels/1396775903 ... 2779235378
Please report this bug to authors of Space-age scenario. Thank you.

[boskid]

When reporting bugs please follow 3638

Given no version was provided i will assume it was 2.0.15 (stable at this point in time)

I managed to get the picture that was deeply hidden under the link above:

Orbital logistics tips

11-14-2024, 16-30-10.png (170.43 KiB) Viewed 692 times

[boskid]

Ok, it looks the issue was actually introduced in 2.0.18 so my version deduction was incorrect.

Issue is now fixed for 2.0.20.

[lialuca]

I'm still having this issue on version 2.0.20. I'm playing on macOS 15.1 in case that's relevant and the error text is:

The scenario level caused a non-recoverable error.
Please report this error to the scenario author.

Error while running event level::on_tick (ID 0)
value for required field 'position' is missing
stack traceback:
[C]: in function 'move_cursor'

[string" require("__core __/lualib/story")..."]:311: in function 'condition'
__core __/lualib/story.lua:105: in function 'story_update'
__core__/lualib/story.lua:10: in function <__core __/lualib/story.lua:8>

[Stewart43]

In 2.0.20, it gets further into the orbital logistics tip, but a similar error message pops up after a few more screens, when the Cargo hub on Vulcanus aappears.

[n_slash_a]

I am seeing this as well, version 2.0.20. Screenshot and logfile attached. I can confirm it occurs shortly after arriving on Volcano.

Edit: Right after the scenario arrives, my character is still firmly on Nauvis.

[martinw89]

Unfortunately I don't think my log or screenshot give any new information other than it's repeatable on 2.0.20 across different machines, but they are attached just in case. It's also consistent that it happens right when the cursor clicks on the cargo landing pad on Vulcanus.

[Loewchen]

Reopened...

[boskid]

I am not seeing reasons to reopen this if its similar but new issue: version on first post is not correct for this new report and i am not willing to work on this anymore (its more of a Pard's territory). Moving back to resolved. For reopening either split this topic or create new report.

-- edit:

To be more precise, tips&tricks simulations are built on top of 2 extremally fragile foundations: GUI and control settings. If gui scale is wrong, some widgets may not be visible and simulation will fail with "position is missing" because widget was not found. Also if player's control settings are changed then simulation may not be able to perform certain interactions again causing widgets to not appear and it will again explode on "position is missing" error. That means just because tips simulation throws error that ends on "position is missing" tells absolutely nothing if this is the same issue or a new one. Please create new bug report each time such error is thrown and do not reopen this one.