Jump to content

Gordon Dry

Members
  • Posts

    3,430
  • Joined

  • Last visited

Posts posted by Gordon Dry

  1. Just saying that the latest update of ROKerbalism not only adds what the changelog says but changes all .cfg files' encoding from "Unix (LF) UTF-8" to "Windows (CR LF) UTF-8" which makes a file synchronization software show all files as different, even as only those 2 files have been changed:

    •  GameData/KerbalismConfig/Support/ROCapsules.cfg
    • GameData/KerbalismConfig/System/Parts.cfg
  2. 4 hours ago, Poodmund said:

    with FAR

    Yes. I'm on RP-1, so RO, so RSS, so FAR as a dependency.

    Edit:
    I see two entries in MM cache for a conformal decal part:

    		physicalSignificance = NONE
    
    
    and then later
    
    
    		PhysicsSignificance = 1

     

    Edit:
    I found the culprit:
    GameData\RealismOverhaul\RO_SuggestedMods\RO-ConformalDecals.cfg
     

    //	==========================================================================
    //	Conformal Decals configuration
    //	==========================================================================
    
    @PART[conformaldecals-*]:FOR[RealismOverhaul]:NEEDS[ConformalDecals]
    {
    	%RSSROConfig = True
        !MODULE[GeometryPartModule] {}
        %PhysicsSignificance = 1
        %mass = 0.0001
        %maxTemp = 3000
        @MODULE[ModuleConformalDecal] { %scaleRange = 0.25 5.25 }
    }

    I will open an issue on the RO side.

    Done: https://github.com/KSP-RO/RealismOverhaul/issues/2746

  3. 1 hour ago, Lisias said:

    KSP.log

    Game booted up to main menu as I was eating, here's the log:
    https://www.dropbox.com/s/22p1o6jtoxemr4p/2022112601.7z?dl=1

    Mainly I use two start parameters; -force-d3d11 -single-instance

    but I also dare to launch the game this way, using a command batch file inside the game root folder which contains

    @echo off
    cd /d "%~dp0"
    cls
    start "KSP x64 with MemoryAllocationFix" /NORMAL "KSP MemoryAllocationFix.exe"
    KSP_x64.exe -force-d3d11 -single-instance
    taskkill /IM "KSP MemoryAllocationFix.exe"

    using

     

  4. Wow. I still use KSP 1.12.3 in another folder than Steam and so never had any issues with that obscure launcher - but after updating KSP Recall I get this popup message with a warning like the air raid is coming soon.

    And when I click "Ok" then KSP closes.


    Edit:
    This is the logged part:

    [KSP-Recall] Version 0.3.0.7 /L running on KSP 1.12.3 
    (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)
    
    [KSP-Recall] ERROR: pwd != Application Root! -- pwd=E:\Spiele\Kerbal Space Program\ ; AppRot=e:\Spiele\Kerbal Space Program\ at error:0 
    (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)
    
    Unable to use a named GUIStyle without a current skin. Most likely you need to move your GUIStyle initialization code to OnGUI 
    (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)
    
    Unable to use a named GUIStyle without a current skin. Most likely you need to move your GUIStyle initialization code to OnGUI 
    (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)
    
    [KSP-Recall] "Houston, we have a problem!" about "Your 'pwd' doesn't match KSP's 'Application Root'!" was displayed 
    (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)
    

    So, the only difference is the capital drive letter E: versus e:

     

  5. On 10/11/2022 at 3:27 AM, Rutabaga22 said:

    normal zip

    7-Zip is out there  for 23 years now and you can consider it being the better normal zip of today, especially as it's freeware. Like HEVC/x265 is the better normal video codec of today.

    On 10/16/2022 at 8:03 PM, KeaKaka said:

    Don't worry about the JNSQ folder

    The issue with stuff like this is that any other mod's patch that calls NEEDS[JNSQ] assumes that you installed it, even if there are only a few files left inside. That can create a borkyness of a next level.

  6. Spoiler

    Why are the ProcAvi still spamming the log in flight with stuff like

    [ProcAvi] RefreshDisplays() Controllable mass: 56, mass: 436.1kg cost: 511, Utilization: 28% 
    (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

    Is that still needed?
    Those values do not change over thousands of lines and it's the ProcAvi of the payload (a satellite), rocket still burning the first stage in atmosphere.

    Edit:

    After first stage cutoff and decoupling that log spamming stopped (at ~120 km altitude).

    Edit:

    I even dare to claim that this is the main reason for low fps during launch.

    see https://github.com/KSP-RO/RP-0/issues/1829

×
×
  • Create New...