Jump to content

Wronk

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by Wronk

  1. On 8/31/2020 at 12:00 AM, dkavolis said:

    I will need more information than just a screenshot, at least provide KSP.log, please.

    Sorry, here's the ksp.log https://www.dropbox.com/s/3v7jdm9pxq46j63/KSP.log?dl=0

    and the output.log https://www.dropbox.com/s/220ggqvtnggvpky/output_log.txt?dl=0

    Having a scan over it myself, it seems like it might be a conflict with wild blue tools, but I don't really have the time to test myself with a full clean install and isolating those two mods, so it's not urgent just making you aware of it

  2. On 8/26/2020 at 11:15 PM, dkavolis said:

    Update to MM 4.1.4
    Update to KSP 1.10

    Added more config options (see FARConfig.cfg):

    • Additional log messages can be enabled
    • Log FAR flight variables to text file
    • Debug voxels are now colored by part (customizable)
    • Removed FARGUIColors.cfg and integrated it into FARConfig.cfg

    Added new DLL FerramAerospaceResearch.Base.dll which is independent of KSP
    Unchanged configs should no longer be saved to new files
    Update Chinese localization (thanks @tinygrox, #88)
    Workaround for KSPUpgradePipeline with removed stock control surface modules
    Fix KSP resetting shielded state on decouple
    Heating should now be closer (and higher) to stock values, KSP applies magic scaling to areas which made FAR calculated exposed areas significantly smaller than stock (can be reverted with MM patch)
    Meshes used for voxelization are now displayed in log with debug FAR log level
    Fix inconsistent voxelization when changing from VAB/SPH to Flight scene and reverting (#89)
    Fix voxelization starting before part is set up in editor
    Ignore launch clamps in editor simulations
    Fix NRE with MechJeb on destruction (#93)
    Resized stock button image to 36x36 px
    Simulation buttons are now disabled while voxelization is active
    Invisible meshes are ignored for voxelization by default

     Pc1uzUc.png

    I'm finding the latest FAR update is causing this error when I open the game, when I use the previous version it loads fine

  3. On 8/26/2019 at 7:45 PM, MOPC said:

    Updated the config for Airplane Plus mod with latest wing parts, except those which were already added by @Wronk and @theonegalen. If you guys okay with that, I can merge three configs together for ease of use.

    Also added simple configs for APP flaps, but not yet sure if they work correctly - would be great if someone tests them.

    Link: https://pastebin.com/rKCb1QaV

    @The-Grim-Sleeper, here, I inserted "proper" values for stock rotor blades, following the FAR wiki guide: https://pastebin.com/nnrcyB8L. Not tested that yet, still to open them in career.

    Maybe FAR will take over the deployment control if parts have configs, or perhaps we could assign deployment to thrust axis via Action Groups?

    Combining the three configs would be great

  4. 1 hour ago, kcs123 said:

    That wuestion is more apropriate for FAR thread. APP does not support FAR directly, but other community members that use both, APP and FAR have made configuration files to support it. I assume it is something with either, mesh configuration or colliders, but can't tell more about it.

    Ends up shortly afterwards someone one the FAR thread had a very similar problem and I found the solution:

    https://imgur.com/gallery/RvYPn8y

    Here's the MM patch config if anyone wants a template to edit/add other badly behaving parts:

    https://www.dropbox.com/s/pr7wp3phxd8jeow/miscpartsAPP-FAR.cfg?dl=0

  5. 8 hours ago, dkavolis said:

    Try patching GeometryPartModule on those parts with

    
    %forceUseMeshes = true
    %ignoreIfNoRenderer = true

     

    I had the same problem with some parts from the Airplane Plus mod and this fixed it:

    https://imgur.com/gallery/RvYPn8y

    Here's the MM patch config if anyone wants a template to edit/add other badly behaving parts: 

    https://www.dropbox.com/s/pr7wp3phxd8jeow/miscpartsAPP-FAR.cfg?dl=0

  6. I've noticed for a few updates now that some APP parts some to have no affect on FAR's area rule curve, as in the green line drops to zero for those parts. The parts I've noticed this on so far are the Mk1 buisness cockpit, Mk3S1.5 Viewer's cockpit, size 2 non-commercial cockpit and size 1.5 crew cabin. I suspect these parts might have some geometry that's messing with FAR but I'm not sure how I could go about figuring it out.

    https://imgur.com/oAOeuzG

     

×
×
  • Create New...