dueb

I think I got rid of the NaN errors / disapearing solar system. So, if anyone is willing to test I made a quick recompile for KSP 1.3.1 x64. I've included the only source file I changed so you can check what I did here @katateochi. (I know you're gonna hate the changes, but I had to make it idiot-proof for the compiler to exclude compilation errors. And it seems to have done the trick! ) It doesn't solve the exotic craft design errors tho. ( @katateochi: If you want me to remove the download, please feel free to ask. )

Glad to help (for once )! Thank you for the new release @linuxgurugamer!

I'm sorry to bother you again @linuxgurugamer...but in EVAFuel.cfg, isn't it a typo line 19? evaFuelResource = MonoPropellent Shouldn't it be: evaFuelResource = MonoPropellant ? Please forgive me if that's a dumb question...

Thank you for continuing this mod @Alshain !

Oh, ok ! Thank you @linuxgurugamer ! Something new to learn everyday ! (That's why I left a question mark)

From what I can see on Github, there's an hard depencie on KIS: https://github.com/linuxgurugamer/EvaFuel/blob/master/EvaFuel-KISCompat/EvaFuel-KISCompat.csproj <Reference Include="KIS"> <HintPath>R:\KSP_1.2.2_dev\GameData\KIS\Plugins\KIS.dll</HintPath> I think Evafuel have to be recompiled with each new KIS versions (?).

Yeah, from what I can remember it worked fine (from the few tests I ran) when I recompiled it. If there was tons of errors I wouldn't have released it, for sure. But since it's just the original source recompiled, I guess it's kidda stable.

There is a 'workaround' to this problem (but doesn't fix the problem itself) since you are using VesselViewer in IVA mode only: You can delete the file VesselViewPlugin.dll in plugin directory since VesselViewer does not depend on this dll to operate in IVA mode. It's an optional dependency, and it's the one causing your issue. (At least, last time I checked. Tell me if that's works! )

Thank you for the clarifications!

I think you're referring to Clr Heap Allocation Analyzer. Am I right? In any case: thank you!

Oh, nice! Thank you for your answer!

I'm sorry if it's a dumb question, but does it work with IVAs modifications like this?

Thank you sir!

Yeah, but you know...sometimes...life... But without willing to speak in name of @AliceTheGorgon, I don't think it would be a really big concern if you publish a fork of EvaFuel in the meantime? (Correct me if I'm wrong @AliceTheGorgon)

Looks like you missed the edit here:

If you want, and while waiting for an official update, you can give try this quick & untested recompile and tell me how that work for you: https://www.dropbox.com/s/8kotf6nnru6zr3a/kOSPropMonitor_RecompileForKSP1.2.2x64.zip?dl=0 (If for any reason you want me to remove this link feel free to ask, I'll do so.) Edit: I forgot to include JsonFX.dll

Nice! Thank you @linuxgurugamer!

I made a Pull Request to fix this issue. Let's hope @linuxgurugamer will make a new release.

@HebaruSan: So after fiddling around a bit with it, I can confirm you that's exactly what I was searching! I didn't liked the other method: I don't know why. I had the apprehension like it was not the right one... So, again: thank you very much! You really helped me there!

Oh yeah! Good call! Thank you again!

Yes, there will be only one of it ever. Will investigate that! Thank you @HebaruSan!

I have one instance of class A, and several instances of class B that have no idea of the existence of class A. I need to access class A in class B. Is there a better way/practice to access this class than using something like FindObjectOfType?

Yes, I know, I saw your post @JPLRepo. Thank you. I was just saying that I didn't expected to learn in an unofficial topic that the next major version release was part of this -I quote the announcement topic- "The Localization Pack pre-release". I didn't thought it was going to be part of a next major milestone: just a "Localization Pack pre-release" (like an 1.2.3 version if you will)... But don't get me wrong: it is! It absolutely is! It's a big feature that -I know- required a huge amount of work! So, maybe the choice of words was not the best here? I don't know... But after all, if we put back together everything into context here: yesterday announcement was not a KSP Weekly! (And your post was sort of a hint!) So, maybe the hype about the announcement made me guess something wrong and see that as a KSP Weekly-type announcement? (Sorry for my poor English. Welcome Localization update! )

I did! Yesterday...it was late... But there is no mention about "1.3" (Ctrl-F3 doesn't give anything), for sure.

I'm a bit confused... I (obviously?) missed something here... [This is more a message for Squad than anything]: Why do I have to learn here (a fan-made topic) that 1.2.9 / 1.3 is coming?