-
Posts
24,947 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by linuxgurugamer
-
[1.12.x] Filter Extensions (No localization)
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
Fixed, thank you -
[1.9.x, 1.10.x, 1.11.x] Persistent Rotation Upgraded
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
I'll get an updated release, for some reason it included two dlls New release, 1.9.1.6 Added Normal and Anti-Normal Fixed multiple dlls in release -
[1.9.x, 1.10.x, 1.11.x] Persistent Rotation Upgraded
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
New release, 1.9.1.5 Fixed Prograde & Retrograde from snapping during timewarp IF there is any current movement Added Radial out and Radial in Renamed DLL for CKAN compatibility Added AssemblyFileVersion Updated version file for 1.12 -
[1.12.x] Minimum Ambient Lighting Updated
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
New release, 1.2.6.1 Renamed DLL for CKAN compatibility Added AssemblyFileVersion Updated version file for 1.12 -
[1.9.x, 1.10.x, 1.11.x] Persistent Rotation Upgraded
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
I will look into this, thank you for the report -
No. ClickThroughBlocker only works on mods which use it. The game does not use it at all, therefore clicks and mouse wheel will always fall through to the game.
-
[1.12.x] Click Through Blocker - NEW DEPENDENCY
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
I've tested this, and neither ToolbarController nor ClickThroughBlocker needs SpaceTuxLibrary to work. It is NOT a dependency of the two mods. I also tested Mechjeb with both mods, but without SpaceTuxLibrary, and it worked fine. So you must have something else going on. Logs would be useful, as I said before: No logs, no support -
New release, 0.0.2.8 Renamed DLL for CKAN compatibility Added AssemblyFileVersion Updated version file for 1.12
-
New release, 3.4.3.5 Added AssemblyFileVersion Updated version file for 1.12 Removed some whitespace (formatting issues in code only) It actually DOES work, and works the same way. You just have to toggle the angle snap using the C key until the number of the angle snaps in the lower left changes to a circle. Unfortunately, I cannot do anything about the text in the tooltip instructions.
-
[1.12.x] TAC Atomic Clock Irradiated
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
New release, 1.6.0.1 Renamed DLL for CKAN compatibility Added AssemblyFileVersion Updated version file for 1.12 Removed unused code -
[1.12] SOC: Simple Orbit Calculator
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
New release, 1.6.0.1 Fixed display of Orbital Period not displaying data when period was huge Now displayes correct periods based on homeworlds orbit (was previously using Earth standard) Adds new dependency of SpaceTuxLibrary -
How about a button to display a window with the crew, or possible a small scrollbox?
-
[1.12.x] Portable Rover Components
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
New release, 0.1.0.2 Moved .version file into PRC directory to make MADLAD happy Updated version files for 1.12 -
[1.12.x] Portable Rover Components
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
Thanks. It's annoying, but I'll fix it when I update this for 1.12 Your alternative is to remove MADLAD -
Written by @stevehead who hasn't been around for 4 years, original thread is here: https://forum.kerbalspaceprogram.com/index.php?/topic/104465-122-soc-simple-orbit-calculator-v150-1122017/ Instructions for the orbit calculator You can access the calculator by clicking the AppLauncher icon (or Blizzy's Toolbar icon) with the image of "SOC". Select the celestial body on the left. To the right of the celestial bodies, select two orbital elements (you cannot select both semi-major axis and orbital period; it would create an ambiguous case). The other elements will be disabled from input at this point. As an option, you can use either apoapsis/periapsis as altitudes above sea level of parent body or as distances from the center of the parent body. Just toggle the Use Altitudes for Apsides option near the bottom under Options. Enter your target values. The S button on the same row of the orbital period will set the orbital period to the parent body's rotation period (useful for synchronous orbits). Click the Calculate button, which will fill in the other elements and display below more in-depth information of the calculated orbit. Any errors will be reported. Optionally, if you are currently in a flight scene, you can click the Use Current Orbit button to use your current orbit or click the Use Target Orbit to use your target's orbit. Because the calculation will fill in other elements that you did not choose, you will be free to use those easily in other calculations. Just de-select the elements you do not need, and select the new ones. This is very useful for calculating Hohmann transfers. Instructions for the Hohmann transfer calculator Once you have calculated an orbit above, click either Save as Orbit 1 or Save as Orbit 2. When two orbits are saved that have the same parent body, the delta-v for the transfer will be calculated and displayed below. Click the C buttons to clear their respective orbits. Instructions for the info mode Select the celestial body on the left. Toggle on Celestial Body Info Mode from the options on the right. Current Features Will automatically detect all celestial bodies known to KSP and their properties, including changes/additions by RSS or Planet Factory like mods. Allowed inputs include: Apoapsis, Periapsis, Semi-Major Axis, Eccentricity, Orbital Period. Other information displayed after calculation: Orbital Speeds at Apoapsis and Periapsis, Mean Orbital Speed, Launch Delta-V (the minimum dV required to launch to or land from the orbit), Max Darkness Length (useful for Remote Tech satellite electric charge calculations). Can use your current vessel's or target's orbit as input. Can save two orbits to calculate the delta-v required for a Hohmann transfer. Blizzy's Toolbar support. Celestial Body Info mode will display orbit and physical characteristics of the selected body, similar to that found on a wiki page. Dependencies Click Through Blocker ToolbarController SpaceTuxLibrary Availability Download: https://github.com/linuxgurugamer/ksp-SimpleOrbitCalculator/releases Download: https://spacedock.info/mod/2816/SOC: Simple Orbit Calculator Source: https://github.com/linuxgurugamer/ksp-SimpleOrbitCalculator License: GPLv2 Now Available via CKAN
-
[1.11.1] Hullcam VDS Continued
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
New release, 0.2.1.2 Renamed DLL for CKAN compatibility Added AssemblyFileVersion Updated version file for 1.12 -
[1.9.x] Hangar Extender Extended
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
New release, 3.6.0.1 Renamed DLL for CKAN compatibility Added AssemblyFileVersion Updated version file for 1.12 -
New release, 0.3.3.1 Renamed DLL for CKAN compatibility Added AssemblyFileVersion Updated version file for 1.12
-
Following up on this, I've made some time and investigated. Seems that there is a new feature in 1.12 which causes this bug if there isn't a "AssemblyFileVersion" setting in the file, and for this mod, there wasn't. For all of you, and especially @theleg I could have fixed this weeks ago IF the proper log files had been provided. I don't have time to investigate every single report, especially when requested information is not provided. I've also taken [x] Science out of beta and added it to CKAN for 1.12 A more general comment is that I have about 260 mods to support. I'm slowly going through all of them to make these changes needed for 1.12, but it's going to take about 2 months to finish, assuming nothing interferes. So if you come across a specific problem, please provide ALL the requested information, start off with the COMPLETE log file (Player.log is preferred). Snippits are fine to point out something you feel might be significant, but many times the needed information is buried in the rest of the log file.