Kerbalism / KerbalismScienceOnly

A Kerbalism configuration that only enables the science mechanics in Kerbalism
The Unlicense
6 stars 3 forks source link

Problem with EVA propellant #2

Open Osthekake opened 3 years ago

Osthekake commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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

daantimmer commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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.