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
NullReferenceException when using MKS/USI Nuclear Fuel Containers #70
Comments
Most of the USI patch is user-contributed, I do hope someone on the thread or perhaps @Wyzard256 can comment on this. My best guess is that the USI containers appear (from the screenshot) to have no DepletedFuel storage in them and that might be causing issues |
Your guess is correct, there is a dedicated container for the waste. The question is, why does it NullRef? Shouldn't the Plugin be able to handle this situation? |
The NFT waste transfer mechanic requires a container to have an equal amount of both fuels to transfer, so this use case was never examined. In this use case the transfer would honestly not function correctly. There is a question here of whether reactors, when installed, should all use USI's refuelling mechanics or whether they should all use NFT's refuelling mechanics. |
Mea culpa, it seems: I wrote that part of @ChrisAdderley FWIW, despite the exceptions, transfers do actually work — I checked again just now. It looks like the problem is in As far as I can see, the fix should be as simple as adding a null check in |
More like my fault given than the error handling is crappy enough to die on that :|. |
A fix has been prepared and is testing to include in 0.9.0 |
Hi! I get the following NullReferenceException spam, presumably in every frame:
This happens whenever I have either the large or small "Nuclear Fuel Container" part from RoverDudes USI/MKS Mod installed:
A workaround is to delete
GameData/NearFutureElectrical/Patches/NFElectricalUSI.cfg
.Mods: Near Future Electrical, UKS
KSP Version: 1.2.2
NFE Version: 0.8.7
USI_Core Version: 0.3.10.0
MKS Version: 0.50.18.0
The text was updated successfully, but these errors were encountered: