Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cargo Containers parts of Station Parts Expansion Redux compatibility #29

Open
SylvainLasnier opened this issue Nov 10, 2021 · 1 comment
Assignees
Labels
help wanted assistance, help, input solicited issue: compatibility/patch issue type issue: config issue type type: request Requested functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used.

Comments

@SylvainLasnier
Copy link

Cargo Containers from Stockalike Station Parts Expansion Redux mod (2.0.5) seems ignored by SimpleLogistics (2.0.5.0) on KSP (1.12.2).
I would share some Ore between 2 landed factories. These parts content are not display in SL UI. Squad Ore parts are OK.
Any patch I could apply waiting an improvement?

@zer0Kerbal zer0Kerbal self-assigned this Nov 11, 2021
@zer0Kerbal
Copy link
Owner

@SylvainLasnier thank you for the report!

Are the SSPx containers attached to a vessel? Does that vessel have a part with [ModuleCommand]? (aka a pod or drone)

Any vessel with at least one [ModuleCommand] and has SimpleLogistics! (SLOG!) installed should register all resources from all parts (except for ones that are on the 'blacklist' like [solidFuel])

The exception MIGHT be and I will look at it more when I do an update pass on SLOG! (near future) is the resources are hidden within the B9; however since SLOG! directly queries the vessel for its resources - that should not interfere.

When I find time I will create a copy of the game, install SSPx, B9, and SLOG! and see if is reproducible.

More news when there is new.

@settings settings bot removed bug labels Mar 21, 2022
@zer0Kerbal zer0Kerbal added help wanted assistance, help, input solicited issue: code issue type type: request Requested functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used. issue: compatibility/patch issue type issue: config issue type and removed issue: code issue type labels Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted assistance, help, input solicited issue: compatibility/patch issue type issue: config issue type type: request Requested functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used.
Projects
None yet
Development

No branches or pull requests

2 participants