dkavolis

Ferram Aerospace Research v0.16.0.3 "Mader" Updated version file for KSP 1.12 max Fixed picking up fairing would invalidate voxelization until reopening VAB/SPH Fixed aerodynamic simulations Fixed navball displaying wrong speed after switching back and forth from IVA view #112 Fixed voxelization error when a part is placed in the editor but not attached to a ship Haven't encountered any issues so far in my limited testing on KSP 1.12 but SAS seemed a bit wonky compared to 1.11

Should be fixed in 63a9c11

Ferram Aerospace Research v0.16.0.2 "Mader" Updated KSP version 1.11 Update to MFI 1.2.10 Added Dynamic Deflection for Control Surfaces Option #110, @Alioth81 Fixed Mk1pod.v2 voxelization by switching to mesh voxelization, colliders were missing top and bottom planes resulting in shell-only voxelization Rotor blades are no longer voxelized Reduced submerged lift and drag, multipliers are controlled by FARConfig/Settings/submerged[Drag|Lift]Multiplier with default value of 0.25 Renamed FARWind to FARAtmosphere and added overrides for gas properties

KSPBurst Burst compiler for Kerbal Space Program KSPBurst by itself will not provide any performance benefits. Mods will need to use Unity job system and decorate the jobs with [BurstCompile] to get any improvements. The Burst compiler is archived to prevent KSP from trying to load its dynamic libraries. The archive is extracted the first time the mod runs to <path to KSP>/PluginData/[email protected]<mod version>-<archive name>. Burst standard outputs can be found in <path to KSP>/Logs/KSPBurst/ and KSP.log. Repository: https://github.com/KSPModdingLibs/KSPBurst/ Installation Download the latest release from the GitHub releases and extract the archive into your KSP directory. plugins_only version does not contain the compiler, use it only if KSPBurst is a hard dependency and download size is an issue. Alternatively, KSPBurst can be installed from CKAN using KSPBurst identifier. plugins_only version is indexed as KSPBurst-Lite. Compiler version requires Mono, you can download it from here. Burst compiler version can be changed by replacing existing [email protected]<version>.zip archive with a different one. The mod expects the archive to follow <package name>@<package version>.<extension> naming scheme, where <package name> contains burst. If a matching archive was not found, KSPBurst will default to using a compiler matching <path to KSP>/PluginData/*burst*/package/.Runtime/bcl.exe with the greatest package version. Burst packages can be found here. Modders KSPBurst can be bundled with other mods. Bundling plugins_only version will keep the file size down but users will need to download the compiler version for Burst benefits. Burst compatible Unity plugins and their dependencies are also bundled: Unity.Burst 1.5.0 Unity.Mathematics 1.2.1 Unity.Collections 0.1.1-preview Unity.Jobs 0.1.1-preview Configuration Options All configuration options present in KSPBurst.cfg map directly to bcl.exe command line options. If ModuleManager is present, patched options will be used. Building Prerequisites KSP installation python Unity Editor 2019.2.2f1 (if building Unity packages) Configuration Tools read mod configuration options from config.json, users should create config.json.user and override the values there: Option Description unityBuildDir relative path to unity project build directory kspMin minimum compatible KSP version kspMax maximum compatible KSP version version KSPBurst version versionTemplate relative path to version template file unityPackages list of bundled unity packages unityDependencies list of managed plugins that unity packages depend on Tools tools contains python scripts: Script Description post_build.py copy libraries to the mod directory, archive the Burst package if it exists and copy the mod to KSP installation version.py update version information in source files and ReadMe package.py package mod into an archive at archives/, outputs 2 versions, one with and one without the Burst compiler Building the Mod Clone KSPBurst Create Directory.Build.props.user in the root directory with <Project> <PropertyGroup> <KSP_DIR>path to KSP</KSP_DIR> </PropertyGroup> </Project> Depending on the platform you may also need to set DATA_DIRNAME to match your installation. If not building Unity packages, go to to step 7 Open Unity project at Unity/KSPBurst in Unity Editor Build the Unity project and note the build directory Create config.json.user in root directory with { "unityBuildDir": "<relative path to unity build directory in step 5>" } Build KSPBurst with your IDE or from command line, the mod will be copied your KSP installation. If the burst package is present in Unity directory, it may take a while to archive it the first time. License Unity plugins are licensed under under the Unity Companion License for Unity-dependent projects--see Unity Companion License. KSPBurst is licensed under the MIT license Notes System.IO.Compression and System.IO.Compression.FileSystem plugins are used for archive decompression and are bundled with Unity Editor. NuGet package Microsoft.Extensions.FileSystemGlobbing is used for glob pattern matching.

@cmet24 I think this fits FAR goal perfectly, would something like FARWind work for pressure and temperature? I could extend FARWind to be a generic atmosphere model albeit it wouldn't be called FARWind at that point.

Ferram Aerospace Research v0.16.0.1 "Mader" Resized (again) toolbar icon to 64x64 All meshes in TransparentFX layer are ignored for voxelization, previously only visible non-skinned meshes had this check (f6a005d) Improve async config loading and saving (9e67b32) Enable debug voxels in flight mode (5560079) with: @FARConfig:FINAL { @Voxelization { %debugInFlight = true } }

With just WBI and MOLE I can't reproduce the issue. Can you try running with the following MM patch? @FARConfig:FINAL { @Debug { %logLevel = debug } } It will give more info on what FAR is working on when KSP crashes. Also, a comparison between logs with old and new FAR may give additional clues to what is going wrong.

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

Ferram Aerospace Research v0.16.0.0 "Mader" 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

Check out dev branch, stability derivatives and a few other buttons are now disabled while voxelization is active.

Yeah

Re launching vessels from SPH/VAB compared to revert to launch, can you try FAR from dev branch? FAR was voxelizing parts too eagerly, before KSP was done with disabling unused models like engine fairings on scene changes so it was working fine on return to launch. FAR now waits for physics to kick in before voxelizing so it should no longer voxelize what you can't see. Launch clamps will be mostly ignored in editor in the next release, there's still a barely noticeable effect on stability derivative values left that I'm not sure where it comes from. For now, you can use the dev branch version. For all the other issues, please provide KSP.log, ModuleManager.ConfigCache, the affected craft file and mod list in addition to description of the problem. Ideally, open an issue on github with all of the above.

It's not used currently.

Triangles can be anywhere in space so every triangle would need to be checked, this quickly becomes too expensive. And FAR needs to know the filled/shielded volume which plain triangles can't give.

I've added a workaround for now in dev branch (0033445)