landerote

Just a petition, if possible. It would be nice if we could set the maneuver to a specific time (absolute or in x time) instead of having to go increasing it. It can be very useful when calculating the transfer windows externally or preparing gravity assist manouvers. Also, it would be nice to be able to interchange between "Manuever in x time" to "Manuever on Y1, d234, 4:56:08".

I imagine you have already solved it, but the issue, seems to be that the vessel appears with no stages and you can't add any, and therefore the engine is in no stage.... It happened to me a couple of times. The only thing you need to do is, while docked, to ensure that the engine you are going to use is set into stage 1. You can do it before undocking or, if you forgot, dock again, put the engine in stage 1 and undock again.

Hi m4v, First of all, thank you very much for your mod, it's a must in all my installations. I had an small issue with the mod since it created an empty settings.cfg file in it's folder, which was making KSP unable to start. Solved just deleting them. I can't tell you how it happened because I was using the game normally and I've been using the mod for long time, so just for your information. The threath about the issue is here: http://forum.kerbalspaceprogram.com/threads/99105-Empty-part-config-file?p=1521218#post1521218 Kind regards

Ok, found. It was RCSBuildAid, that it had an empty settings.cfg file on it that I don't know how was generated and why it happened now, since I've been using the mod for a while.

Well, after trying everything, I deleted the GameData folder content, and It worked. With MM also working. Now I'm reinstalling mod by mod to see which one is the buggy one...

Thanks both, I will try restarting pc, then deleting settings file and installing again MM. If not I will erase all GameData folder except squad parts. Let's see what's happening...

Nope, I didn't change anything at all. Some hours ago it was working, and now it's not.....

Hi nli22work, Yep, I have MM 2.5.1 installed, just one copy, and also Toolbar. But error is coming as the first event, so I think MM or TB are not even loaded...

KSP: 0.25 Windows 32bit Problem: With no apparent reason (no changes done in a working installation), KSP is unable to start due to a "Empty part config file" error. I tried to identify which one is the responsible to try to fix it, but I could not find. Mods installed: I find it irrelevant since it's happening at the very beginning, so at that stage I think just ATM could be involved. Reproduction steps: Just starting KSP (it was working a couple of hours ago) Log: Initialize engine version: 4.5.2f1 (9abb1b59b47c)GfxDevice: creating device client; threaded=1 Direct3D: Version: Direct3D 9.0c [nvd3dum.dll 9.18.13.3788] Renderer: NVIDIA GeForce 8400M GS Vendor: NVIDIA VRAM: 1006 MB (via DXGI) Caps: Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=0 INTZ=1 RAWZ=0 NULL=1 RESZ=0 SlowINTZ=0 Begin MonoManager ReloadAssembly Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\UnityEngine.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\UnityEngine.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-CSharp-firstpass.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-CSharp-firstpass.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-CSharp.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-CSharp.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-UnityScript-firstpass.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-UnityScript-firstpass.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-UnityScript.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Assembly-UnityScript.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Mono.Cecil.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Mono.Cecil.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Mono.Cecil.Mdb.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Mono.Cecil.Mdb.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Mono.Cecil.Pdb.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Mono.Cecil.Pdb.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\xmldiffpatch.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\xmldiffpatch.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\XmlDiffPatch.View.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\XmlDiffPatch.View.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\TDx.TDxInput.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\TDx.TDxInput.dll into Unity Child Domain Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\MiscUtil-r285.dll (this message is harmless) Loading C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\MiscUtil-r285.dll into Unity Child Domain - Completed reload, in 0.114 seconds <RI> Initializing input. <RI> Input initialized. desktop: 1360x768 60Hz; virtual: 2640x800 at 0,-32 Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\System.Core.dll (this message is harmless) Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\System.dll (this message is harmless) Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\System.Xml.dll (this message is harmless) Shader 'AtmosphereFromGround': fallback shader 'None' not found [KSP Version]: 0.25.0.642 (WindowsPlayer) Steam ==================================== (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) Launcher Settings File doesn't exist (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) Launcher after checking file: True (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) Error: Empty part config file (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) NullReferenceException: Object reference not set to an instance of an object at ConfigNode.RecurseFormat (System.Collections.Generic.List`1 cfg, System.Int32& index, .ConfigNode node) [0x00000] in <filename unknown>:0 at ConfigNode.RecurseFormat (System.Collections.Generic.List`1 cfg) [0x00000] in <filename unknown>:0 at ConfigNode.Load (System.String fileFullName) [0x00000] in <filename unknown>:0 at UrlDir+UrlConfig.CreateNodeList (.UrlDir parentDir, .UrlFile parent) [0x00000] in <filename unknown>:0 at UrlDir+UrlFile..ctor (.UrlDir parent, System.IO.FileInfo info) [0x00000] in <filename unknown>:0 at UrlDir.Create (.UrlDir parent, System.IO.DirectoryInfo info) [0x00000] in <filename unknown>:0 at UrlDir..ctor (.UrlDir parent, System.IO.DirectoryInfo info) [0x00000] in <filename unknown>:0 at UrlDir.Create (.UrlDir parent, System.IO.DirectoryInfo info) [0x00000] in <filename unknown>:0 at UrlDir..ctor (.UrlDir root, .ConfigDirectory rootInfo) [0x00000] in <filename unknown>:0 at UrlDir..ctor (.ConfigDirectory[] dirConfig, .ConfigFileType[] fileConfig) [0x00000] in <filename unknown>:0 at GameDatabase+ .MoveNext () [0x00000] in <filename unknown>:0 UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator) UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) :MoveNext() UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator) UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) GameDatabase:StartLoad() :MoveNext() UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator) UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) LoadingScreen:Start() (Filename: Line: -1) Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_Data\Managed\Boo.Lang.dll (this message is harmless) NullReferenceException: Object reference not set to an instance of an object at GameDatabase+ .MoveNext () [0x00000] in <filename unknown>:0 (Filename: Line: -1) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) HandleD3DDeviceLost HandleD3DDeviceLost: still lost Skipped frame because GfxDevice is in invalid state (device lost) (Filename: Line: 1617) Thanks in advance! Edit: Solved: It was RCSBuildAid that had an empty settings.cfg file in the folder. Deleted and now working again. Thanks all for your support!

Hi Felbourn! First of all, I've to say that I love your videos (previous getaway project and actual odyssey one)! I specially like how you share this with your daughter, a good way to send them into the science path . I'd love to the the same with mine, but she is still too young, anyway, you gave me good inspiration. About the series, I'm sorry about your loss, but is a good way to improve the models, as you did. I just wanted to ask you something, because I do a different approach, why you don't use the Eart-Moon L4 and L5 relays to connect with your DSN in Sun-Earth L4 and L5? This will give continuous link with the DSN, something that a Molniya orbit is not giving unless you deploy more than one satellite... Is just my approach because I like continuous links and I don't like the "point active vessel" option, since I consider it unrealistic. (not being critic, I'm just curious). By the way, still waiting for your explanation of why you prefer Kethane to Karbonite. I moved to this last one even if I don't like the idea of infinite resources areas, I like the concentration Idea but they should have made it possible to deplete... In my case, I also use a completely recoverable SSTO rocket family, even if I need to "cheat" a little bit with DR to make nice re-entries, just waiting for this to be available and make it more realistic. I think you should move into 0.25 as soon as possible, not to have the same problem again when updating. In my case I did it last monday, but still modifying, since I found some odd things, like KW rocketry motors being undersized.... But well, hope to solve it soon. By the way, there is a new version of Ubiowelder for 0.25 here. One last thing, do you know if there is any mod that makes the radiation issue more realistic? Interstellar is measuring, but is not giving any consequence or parts to solve it (I simulate the shield increasing the weight of some command modules and using other heavy ones as an emergency refuge) Cheers!

Hi Krupski, What about the inverse? I understand that using png files will be worst since they need to be decompressed, so, could we use somthing like http://www.xnview.com/en/xnconvert/ to converte them back? Or is not working well?

Wow Nertea, amazing threat, I've been admiring your models for hours. I didn't update yet to .25 and I'm keeping my old installation till I got everything compatible, so I've some of the parts missing and dying to start using them Mmm, nice. If you are not motivated with this, what about a Airbus-Beluga type spaceplane, with frontal loading. I'm starting to sketch myself, but there is a lot to learn yet...

Hi Ippo! First of all, congratulations for starting this. I was looking for something similar. I have some doubts, probably because of my missunderstanding... - First of all, I think that apart from the skills, we could go further and handle also things like morale and other kerbal's characteristics. In any case, this type of characteristics would need to use another system than the perk points, or use the perk points to increase the max or min amount of them, being numerical... - As far as I understand, there will be common trees and perks to be used by everybody, right? Lets see, if we have the "Pilot" tree, under this one we will have different "levels" or skills, like Noob, Student, Silver Wings and Golden Wings. This levels will be unlocked with perk points, and the "harvest" of those perk points and the effects of those skills will be in mods side. - I see a problem with this, and I think that if we go for this structure, all the mods should use the same formulas to obtain the specific perk points, for example for pilot skills we could use sub-orbital flight hours, as if we were defining resources we would need to agree in the mass, volume etc. Because otherwise different mods would collide. If we use different formulas to obtain the perk points, we could ruin the functionality of the other mods, as we share the same "skill". For example, let's say that two persons make a mod to handle the morale, and one increases it when there are many kerbals in a ship (because of social chat) and the other one decreases it... Then none of them would work. I agree that the consequences of having those skills should be handled by the mods, but I think we should define the threes and the formulas, and any mod that wants to use the OPS should agree with those formulas. Anyway, there could be changes, like someone creating the "Kerbal university" and the formula to get perk points being added to the OPS. So.... who is starting the mod for the training center?

Oh, Ok, I didn't see that, not even CrewFiles. Probably the best thing will be to contribute there.... Thanks nismobg!

Mmmm, Thanks CalculusWarrior. That would be perfect. Anyway, I think I will continue doing some research, in case is not done or all the features are not there...