Jump to content

mdapol

Members
  • Posts

    265
  • Joined

  • Last visited

Posts posted by mdapol

  1. @linuxgurugamer  So I tried your suggestion.  After reloading a clean install I noticed that there were two MiniAvc.log files still present.  I tracked it down to two mods that ZeroMiniAVC is apparently missing:  RecoveryController  and KISKIS uses something called MiniAVC-V2.dll.

    I manually pruned both of those and now I don't get any MiniAVC logs being generated.  I also do not get the exception in Trajectories in the KSP.log file.

    However

    I still don't see the Trajectories mod in the Toolbar in the Space Center view or in the Tracking Station view.

    Player.log is here:  https://www.dropbox.com/s/htybjlqavqozcme/Player.log?dl=0

    KSP.log is here:  https://www.dropbox.com/s/vkp26espzad8b0z/KSP.log?dl=0

     

  2. @linuxgurugamer  No success.  Uninstalled those mods and still get the same exception.

    [LOG 08:52:12.154] [Trajectories] v2.4.1 Starting
    [ERR 08:52:12.159] Exception loading ScenarioModule Trajectories: System.TypeInitializationException: The type initializer for 'Trajectories.Settings' threw an exception. ---> System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.
      at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
      at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0
      at AssemblyLoader+LoadedAssembyList.GetPathByType (System.Type type) [0x00020] in <cd473063d3a2482f8d93d388d0c95035>:0
      at AssemblyLoader.GetPathByType (System.Type type) [0x00000] in <cd473063d3a2482f8d93d388d0c95035>:0
      at KSP.IO.IOUtils.GetFilePathFor (System.Type T, System.String file, Vessel flight) [0x00005] in <cd473063d3a2482f8d93d388d0c95035>:0
      at KSP.IO.PluginConfiguration.CreateForType[T] (Vessel flight) [0x00000] in <cd473063d3a2482f8d93d388d0c95035>:0
      at Trajectories.Settings..cctor () [0x00007] in <54b43012425c4547b2c53f8eb9f179ca>:0
       --- End of inner exception stack trace ---
      at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_generic_class_init(intptr)
      at Trajectories.Trajectories.OnLoad (ConfigNode node) [0x0000b] in <54b43012425c4547b2c53f8eb9f179ca>:0
      at ScenarioModule.Load (ConfigNode node) [0x0000e] in <cd473063d3a2482f8d93d388d0c95035>:0
      at ScenarioRunner.AddModule (ConfigNode node) [0x0005e] in <cd473063d3a2482f8d93d388d0c95035>:0

    As you can see, I have ZeroMiniAVC installed already.

     

    [LOG 08:45:24.392] [AddonLoader]: Instantiating addon 'ZeroMiniAVC' from assembly 'ZeroMiniAVC'
    [LOG 08:45:24.396] ZeroMiniAVC: Awake

     

    Any more ideas?

    KSP log here: https://www.dropbox.com/s/d5qlbftp8ylukap/KSP.log?dl=0

  3. On 8/26/2021 at 4:42 AM, mhoram said:

    I can also recreate the same exception with the following minimal setup:

    - KSP 1.12.2
    - Trajectories 2.4.1
    - Toolbar 1.8.0.7
    - MechJeb 2.12.3.0
    - RCSBuildAid 1.0.6

    Uninstalling a single one of them resolves the exception.

    @linuxgurugamer I have ZeroMiniAVC installed already.  That is not the issue.

    @mhoram I also have ClickThroughBlocker and ToolbarControl installed already and still have the issue.

    I will try uninstalling RCSBuildAid and TacFuelBalancer (separately) and see what happens.

    I install everything via CKAN which should handle addon requirements like this (usually)

  4. I'm getting this error in my 1.12.1 game with Trajectories 2.4.1

     

    [LOG 19:53:04.415] [Trajectories] v2.4.1 Starting
    [ERR 19:53:04.420] Exception loading ScenarioModule Trajectories: System.TypeInitializationException: The type initializer for 'Trajectories.Settings' threw an exception. ---> System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.
      at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
      at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0
      at AssemblyLoader+LoadedAssembyList.GetPathByType (System.Type type) [0x00020] in <cd473063d3a2482f8d93d388d0c95035>:0
      at AssemblyLoader.GetPathByType (System.Type type) [0x00000] in <cd473063d3a2482f8d93d388d0c95035>:0
      at KSP.IO.IOUtils.GetFilePathFor (System.Type T, System.String file, Vessel flight) [0x00005] in <cd473063d3a2482f8d93d388d0c95035>:0
      at KSP.IO.PluginConfiguration.CreateForType[T] (Vessel flight) [0x00000] in <cd473063d3a2482f8d93d388d0c95035>:0
      at Trajectories.Settings..cctor () [0x00007] in <54b43012425c4547b2c53f8eb9f179ca>:0
       --- End of inner exception stack trace ---
      at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_generic_class_init(intptr)
      at Trajectories.Trajectories.OnLoad (ConfigNode node) [0x0000b] in <54b43012425c4547b2c53f8eb9f179ca>:0
      at ScenarioModule.Load (ConfigNode node) [0x0000e] in <cd473063d3a2482f8d93d388d0c95035>:0
      at ScenarioRunner.AddModule (ConfigNode node) [0x0005e] in <cd473063d3a2482f8d93d388d0c95035>:0

     

    KSP Log: https://www.dropbox.com/s/d5qlbftp8ylukap/KSP.log?dl=0

  5. Getting this error in my 1.12.1 game:

     

    [LOG 19:53:04.415] [Trajectories] v2.4.1 Starting
    [ERR 19:53:04.420] Exception loading ScenarioModule Trajectories: System.TypeInitializationException: The type initializer for 'Trajectories.Settings' threw an exception. ---> System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.
      at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
      at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0
      at AssemblyLoader+LoadedAssembyList.GetPathByType (System.Type type) [0x00020] in <cd473063d3a2482f8d93d388d0c95035>:0
      at AssemblyLoader.GetPathByType (System.Type type) [0x00000] in <cd473063d3a2482f8d93d388d0c95035>:0
      at KSP.IO.IOUtils.GetFilePathFor (System.Type T, System.String file, Vessel flight) [0x00005] in <cd473063d3a2482f8d93d388d0c95035>:0
      at KSP.IO.PluginConfiguration.CreateForType[T] (Vessel flight) [0x00000] in <cd473063d3a2482f8d93d388d0c95035>:0
      at Trajectories.Settings..cctor () [0x00007] in <54b43012425c4547b2c53f8eb9f179ca>:0
       --- End of inner exception stack trace ---
      at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_generic_class_init(intptr)
      at Trajectories.Trajectories.OnLoad (ConfigNode node) [0x0000b] in <54b43012425c4547b2c53f8eb9f179ca>:0
      at ScenarioModule.Load (ConfigNode node) [0x0000e] in <cd473063d3a2482f8d93d388d0c95035>:0
      at ScenarioRunner.AddModule (ConfigNode node) [0x0005e] in <cd473063d3a2482f8d93d388d0c95035>:0

     

  6. 7 hours ago, CessnaSkyhawk said:

    If u r still trying to combine them, I'm currently trying to frankenstien together JNSQ and OPM for my own personal use, and I could send u a copy of my files when I'm done

    Thanks but I wasn't trying to combine them.  I am only interested in JNSQ and I don't know how OPM got installed.

  7. 17 hours ago, Gotmachine said:

    @mdapol It's probably doable, maybe we can put this in the tooltip that appear when you hover on the file/sample in the file manager.


    We will look into it when we can, there are many more urgent issues to deal with at the moment.

    Putting this in https://github.com/Kerbalism/Kerbalism/issues/488
     

    Thanks, I appreciate it. In the meantime I’d like to look into it myself. Could someone tell me where in the Kerbalism code it handles the current experiment result messages?

  8.  

    8 hours ago, Sir Mortimer said:

    problem is, the database of messages looks like this:

    
    #autoLOC_501327 = The surface is very brown and lumpy. You poke at it with your glove and notice how hard it is.
    #autoLOC_501328 = Everywhere you look it appears the planet is sharp. You don't think you want to sit down or fall on anything.
    #autoLOC_501329 = You lay down and give the planet a hug, just so it knows it's not alone out here.
    #autoLOC_501330 = You Observe the Goo.
    #autoLOC_501331 = The Goo doesn't seem to be doing much right now.

    Unless you have a way to map "goo observation done in low space above mun" to "autoLOC_501331" *without hard coding it* this will be a lot of manual work, and thusly won't be done.

    I guess I’m not quite understanding you. There already is a way to map the science messages. IIRC, the stock Science Config file has a list of all messages organized by experiment an location. All that would be needed is to read in the file and convert it to whatever format Kerbalism uses. 

    Can you explain what I’m missing?

    And could you point me to where in the code the Kerbalism science messages are generated and displayed?

    Thanks. 

  9. It seems to me that the current mod is not really compatible with the basic Tech Tree. In the sense that you're getting rockets that are way, way overpowered too early in the tech tree. Most of them seem to show up in Basic Rocketry with is not consistent with stock. Are there any plans to configure the parts to fit the stock tech tree better? And after that perhaps the Community Tech Tree?

  10. Has the issue where a probe that has not been focussed in a long time (and the relay satellite has not been focussed in a long time) will become stuck in "Not Connected" state even though both the probe and the relay are (1) pointed at each other, (2) in range, and (3) have clear LOS been solved yet?

    My Jool probes will quite reliably get "Not Connected" since I don't look at them for a while, requiring me to edit the persistant file to force them back into "Connected" state. I have reported this problem before but I haven't been on the forum for a while so I was wondering if this issue has been fixed, or will be fixed for 0.24?

  11. Has the issue where a probe that has not been focussed in a long time (and the relay satellite has not been focussed in a long time) will become stuck in "Not Connected" state even though both the probe and the relay are (1) pointed at each other, (2) in range, and (3) have clear LOS been solved yet?

    My Jool probes will quite reliably get "Not Connected" since I don't look at them for a while, requiring me to edit the persistant file to force them back into "Connected" state. I have reported this problem before but I haven't been on the forum for a while so I was wondering if this issue has been fixed, or will be fixed for 0.24?

  12. D-Magic, would it be possible to introduce a science boost for Kerbal-based experiments (EVA/crew reports, surface sample) based on the crew of the spacecraft? This would make multi-Kerbal crews useful and finally give a reason, other than role playing, to unlock multi-crew pods in career mode. I imagine it'd also be wise to introduce diminishing returns to this boost, so that 100-man ships doing a report on the KSP launch pad aren't OP. In the case of EVA report and surface sample, the boost would be based on the crew of the last spacecraft the experiment performing Kerbal belonged too (if it still exists, so that a crash survivor doesn't get a boost from his dead colleague).

    I respectfully disagree. I'm already getting way too much science in the standard career mode as it is. In my next career game, I think I'm going to have to double the cost of all science tiers to make it more realistic. If you do you do this, at least make it optional so that people can turn it off please.

  13. Superb! Been waiting on something like this for ages since B9 stopped being updated.

    Unfortunately I can't access dropbox (banned by the internet here) so will be a few days until I'm elsewhere and can try it out.

    B9 hasn't "stopped being updated". There's an update in the works in fact.

×
×
  • Create New...