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

Problem with EVA propellant #2

Open
Osthekake opened this issue Feb 3, 2021 · 8 comments
Open

Problem with EVA propellant #2

Osthekake opened this issue Feb 3, 2021 · 8 comments

Comments

@Osthekake
Copy link

I have an issue in my game, where I am unable to use the EVA jetpack.

I am running Kerbalism and KerbalismScienceOnly. When I go on EVA, I get a Kerbalism message saying that there is no Propellant, and that I should not jump off the ladder. Jumping off the ladder reveals that while I can activate the jetpack, I am indeed unable to navigate.
Right-clicking on the jetpack in the inventory, reveals that it contains an EVA Propellant amount of 5.

Further, if I EVS (Easy Vessel Switch) from the helpless kerbal to another spacecraft which is controlled by a probe, I can not control this spacecraft either. Switching to a spacecraft that contains a pilot works as expected as far as I can tell.

I have tried to copy the EVA.cfg from KerbalismConfig, overwriting the one in KerbalismScienceOnly, with the same results.

I have not tested if this bug appears with the default config, but I assume you would have noticed by now if it did.

KSP.log
Note that I tested this with the bare minimum mods enabled, even if there were additional folders present as noted in the log file.

@Aceman67
Copy link

Aceman67 commented Mar 8, 2021

I am having the exact same issue, except with the 3.3.1 version. I love the science-only side of kerbalism and I want to use it with the new update.
KSP.zip
Player.zip

@Tagir-1
Copy link

Tagir-1 commented Mar 11, 2021

Had the same issue, my solution was to delete or comment out the config file at KerbalismScienceOnly\System\EVA.cfg

@daantimmer
Copy link

This part was added to the default config to patch 1.11+:

// KSP 1.11+ handling : propellant is stored on the jetpack inventory part
@PART[evaJetpack]:FOR[KerbalismDefault]
{
  @RESOURCE[EVA?Propellant]
  {
    @name = MonoPropellant
  }
}

// Patch the 1.11+ "eva fuel cylinders" inventory item with MP
@PART[evaCylinder]:FOR[KerbalismDefault]
{
  @RESOURCE[EVA?Propellant]
  {
    @name = MonoPropellant
  }
}

Which is missing in the ScienceOnly config

@Scorch5000
Copy link

This part was added to the default config to patch 1.11+:

// KSP 1.11+ handling : propellant is stored on the jetpack inventory part
@PART[evaJetpack]:FOR[KerbalismDefault]
{
  @RESOURCE[EVA?Propellant]
  {
    @name = MonoPropellant
  }
}

// Patch the 1.11+ "eva fuel cylinders" inventory item with MP
@PART[evaCylinder]:FOR[KerbalismDefault]
{
  @RESOURCE[EVA?Propellant]
  {
    @name = MonoPropellant
  }
}

Which is missing in the ScienceOnly config

so for the stupid people like me who don't know what that means, what do we do with this?

@daantimmer
Copy link

so for the stupid people like me who don't know what that means, what do we do with this?

Open the config file of the ScienceOnly kerbalism config: kspdir/GameData/KerbalismConfig/System/EVA.cfg

Add the above lines (just append at the end). Done

@Scorch5000
Copy link

so for the stupid people like me who don't know what that means, what do we do with this?

Open the config file of the ScienceOnly kerbalism config: kspdir/GameData/KerbalismConfig/System/EVA.cfg

Add the above lines (just append at the end). Done

Thanks so much!

@Osthekake
Copy link
Author

I believe I tried adding that part at the end, and it did not fix the problem for me. What worked for me was deleting the entire contents of the file. I don't know what EVA.cfg has to do with ScienceOnly anyway.
If you have tested that adding that content to the end of the file solved the problem, maybe you could create a Pull Request with that change?

@URInASim
Copy link

I believe I tried adding that part at the end, and it did not fix the problem for me. What worked for me was deleting the entire contents of the file. I don't know what EVA.cfg has to do with ScienceOnly anyway.
If you have tested that adding that content to the end of the file solved the problem, maybe you could create a Pull Request with that change?

Same experience. Adding those lines to EVA.cfg did not work for me. Deleting the file contents completely did fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants