DomiKamu

Members
  • Content count

    60
  • Joined

  • Last visited

Community Reputation

5 Neutral

About DomiKamu

  • Rank
    Rocketry Enthusiast

Profile Information

  • Location Chartres (France)
  1. Tested the AppLauncher button hiding -> now the button remains hidden between flights, it's perfect ! Great stuff! Thanks a lot Teilnehmer for this mod and this useful 1.3.0.3 update. Greetings from Chartres, France. EDIT: this is my "config.xml" (gauge will appears only if required, and located below KER HUD). As you can see, I've disabled "Hightlight Critical Part". <?xml version="1.0" encoding="utf-8"?> <config> <vector2 name="SettingsWindowPosition"> <x>254</x> <y>255</y> </vector2> <vector2 name="GaugeWindowPosition"> <x>440</x> <y>91</y> </vector2> <bool name="ShowAppLauncherButton">0</bool> <bool name="LockGaugeWindow">1</bool> <bool name="AlwaysShowGauge">0</bool> <double name="GaugeShowingThreshold">0.5</double> <double name="GaugeHidingThreshold">0.40000000000000002</double> <bool name="ShowTemperature">1</bool> <bool name="ShowTemperatureLimit">1</bool> <bool name="ShowTemperatureRate">1</bool> <bool name="ShowCriticalPart">1</bool> <bool name="HighlightCriticalPart">0</bool> <bool name="PartMenuTemperature">1</bool> <bool name="PartMenuTemperatureLimit">1</bool> <bool name="PartMenuTemperatureRate">1</bool> <bool name="UseExclusionList">0</bool> <string name="ExclusionList" /> </config>
  2. Please can you take a look about the option to hide definitively the button in (stock) toolbar? (I don't use blizzy78 toolbar, but only stock). Because the button always comes back on stock toolbar everytime I begin a new flight - despite Show AppLauncher button checkbox is unchecked. Having <bool name="ShowAppLauncherButton">1</bool> entry saved in config.xml, of course it's normal. So, from next flight, the icon appears again, by clicking it, the "Show AppLauncher button" is unchecked, we must click twice the checkbox to remove the button from toolbar. Hope my explanation is understandable. Many thanks in advance, and thanks again about Critical Temperature Gauge plugin, it's amazing!
  3. Hi, Having strange issue too, KPS 1.3.0.1804 (x64 Windows), unmodded/fresh installation: Year 999 Day 499 - 05:59:59 when returning to vessel (the clock remains stucked at this time bcoz it's the maximum/limit I suppose). To reproduce (KSP 1.3.0 x64 for Windows): - Create a new sandbox game, any save name, any mission flag (keep default), no difficulty modification (staying as "Normal"). - From KSC, click on Launchpad, select stock Kerbal X spacecraft (or any stock spacecraft), then click "Launch vessel" (green) icon/button (but no takeoff, staying on launchpad). - Return to Space Center by using the button above the altimeter: from KSC, date/time is Years 0 Day1- 0h 6m seems good but badly formatted (IMO) no space between Day and 1, no space between 1 and "-"... - Returning to vessel from Tracking Station, or by clicking on vehicule icon on launchpad: date/time is corrupted as indicated above Year 999 Day 499... Core i7 4790 @ 3.6 GHz, 32 GB RAM, GTX 660, Windows 7 Pro SP1 64-bit. EDIT: this issue was reported in bug tracker (bug #15389) by another user (11 days ago). Video here.
  4. I don't have the high CPU load issue I've mentionned by using your config xml file (link you've provided - thanks again), even I've done some customizations without problem. Without this XML, this bug comes back... I precise by default this value is (xml created on exit to KSP menu): <?xml version="1.0" encoding="utf-8"?> <config> <vector2 name="SettingsWindowPosition"> <x>0</x> <y>0</y> </vector2> <vector2 name="GaugeWindowPosition"> <x>0</x> <y>0</y> </vector2> <bool name="ShowAppLauncherButton">1</bool> <bool name="LockGaugeWindow">1</bool> <bool name="ForceShowGauge">0</bool> <double name="GaugeShowingThreshold">0.5</double> <double name="GaugeHidingThreshold">0.40000000000000002</double> <bool name="ShowTemperature">1</bool> <bool name="ShowTemperatureLimit">1</bool> <bool name="ShowTemperatureRate">1</bool> <bool name="ShowCriticalPart">1</bool> <bool name="HighlightCriticalPart">1</bool> <bool name="PartMenuTemperature">1</bool> <bool name="PartMenuTemperatureLimit">1</bool> <bool name="PartMenuTemperatureRate">1</bool> <bool name="UseExclusionList">0</bool> <string name="ExclusionList" /> </config> The GaugeHidingThreshold value seems stange (bold red), in my opinion... in your separate xml, the value is 0.4. Tell me if you need some KSP logs, don't hesitate!
  5. I'll try this 1.3.0.2 ASAP (this afternoon) and I'll report if it works fine or not without, then with your xml file (thanks!) In case of I'll encounter similar issue, I'll try it from fresh (unmoded) KSP 1.3.0, then I'll add mods I'm using but one after one (in case of conflit with another).
  6. Hi Sarbian, Using MechJeb 2 v2.6.1 Build #710 (Dev), KSP 1.3.0 (x64 Windows), I have an issue concerning Landing Guidance module: sometimes, the distance between desired landing point and real, is enormous. This is an example (Mun landing), difference is 219 kilometers. Just before deorbit burn, they're a normal plane change (very small burn). Link to both logs + .craft + screen capture : https://www.dropbox.com/sh/7ynf8h5eb1xmsdb/AABFhmiYWxI9V2XHd1H45-cQa?dl=0 Spacecraft is KerBus (homemade, Apollo-style), using stock + MechJeb2 AR202 cases (one mounted on each vessel) + optional DPAI (for named docking ports) Thanks in advance. EDIT: perhaps "HyperEdited" (lastest 1.5.4) "Apollo-style" vessels around the Mun first (directly, without KSC launch), prior landing, may be the culprit... After removing HyperEdit, doing a real flights, no issue found.
  7. Thanks for this tip, I've reported an issue above, and probably I've picked it from Spacedock (I don't remember). I'll retry it because I love this mod too! EDIT: I have checked my FireFox browser history, and I confirm I've downloaded it from Spacedock last night. Re-downloaded from GitHub (v1.3.0.1), but MD5 comparison reports that same files/folders, BTW Spacedock is up to date (12:10 France time).
  8. Hi, For me the mod doesn't crash (I don't see exceptions), but I have a high CPU load, even setting window and gauge aren't displayed (only the icon in stock toolbar), KSP in unplayable due to very low framerate. CPU is Intel Core i7 4790 @ 3.8 GHz, 32 GB RAM, NVIDIA GTX 660... Using KSP 1.3.0 (1804) Windows/x64 (fresh install), OS is Windows 7 Pro SP1 64-bit edition. Installed mod: MechJeb 2 v2.6.1.0 (Dev build 710), ModuleManager v2.8.0, BetterBurnTime 1.5.4 (lastest), DPAI v6.7.0 (lastest) and Chatterer v0.9.93 (lastest). KSP runs fine when I remove Critical Temperature Gauge. Thanks for this usefull mod - I've used it (previous version) under KSP 1.2.2 without issue. Greetings from France.
  9. You're welcome NavyFish! don't worry about this, I (we) understand we've a life alonside KSP (fortunately lol). Of course, it's not a critical bug, fortunately! Your DPAI gauge is simply fantastic, assuming it is always installed in my KSP.
  10. [1.3.x] Kerbal Alarm Clock v3.8.5.0 (May 30)

    Excellent! Thank you very much TriggerAU.
  11. This bug exists since KSP 1.2 (including KSP 1.2.1 and 1.2.2), I'm surprised because other mods I'm using never have this issue : MJ2, Critical Temperature Gauge, KAC, Chatterer, [x] Science!, KER and KSP Alternate Resource Panel. I suppose some additional code must be added in source. Probably some changes in KSP API since 1.2...
  12. @LameLefty@Jebs_SY This plugin works fine in KSP 1.2.2, and it's one of my favorite, stable, useful... just simply a small bug (not critical, however) about "DPAI icon" staying in KSP menus (top-right side of screen), as I've described in previous page (47) - post date: 6-Oct-2016. I'm not alone. I suppose it's not too difficult to fix. Versioning is only for update checker such MiniAVC or perhaps CKAN (I don't use them).
  13. No code change l'Ami... (mate in En) Only .version file was updated, not the plugin!
  14. Hi NavyFist, I don't understand why this fantastic addon (really) wasn't recompiled for KSP 1.2.2. Also the "bug icon" in menus isn't solved. Thanks anyway, really I love this plugin, in particular the rename port feature, useful for stations having many docking ports. Happy New Year!