[1.10.0] NanoGauges - tiny ana1og gauges for kerbalnauts -1.10.0-3463

[Nereid]

14 hours ago, Apurva Kawthalkar said:

hi nice mod , Please make it compatible with 'Kerbalism ' mod

I'm working on it. CO2 is missing. Does the resource "CRAP" belong to Kerbalism?

 

EDIT: done.

Edited May 8, 2016 by Nereid

[bigwookiee]

This is an awesome possum mod.  I thank you for taking the time to make it.  Could you add a suicide burn gauge styled like the terminal velocity gauge?  You would ride the zero down instead of up.  I like Engineering Redux  read out.  I tend to lose track of it unlike the gauges.

 

Thanks for considering it.

[Minowara]

On 5/6/2016 at 5:31 AM, Nereid said:

Thisa may be a bug. You can turn  it off by holding down the hotkey (RIGHT-CTRL) and clicking the red X. But you cannot turn it on again then if the buttonb in the config is missing. I will check this.

Confirmed. Fixed in the next release (hopefully tomorrow).

This should not be very difficult in general. But a generic approch is not that easy. I can test RF myself and see how many in there. If there are to many, I need a list of the important ones.

Let me know. I am more than willing to provide a list of the resource names used by RF. And thank you 

[N_Molson]

Hello, excellent mod but I can't find a way to save the gauges positions, which is a bit annoying.

Of course, I tried the "Save" button in the NanoGauges menu and then exited it by clicking "Close", but when I exit and restart KSP, all the modes are back to default settings.

I'm using 1.2 x64. I also made sure that the files were not "read-only", just in case. I however do have a 8ko "Nanogauges.dat" file in KSP/Gamedata folder, so I'd say that the info is saved but not loaded.

Thanks for any hints !

[Minowara]

The seismometer's gauge is fully working now, but it seems that TAC's life support gauge for solid waste is missing.

[CobaltMongoose]

On 5/10/2016 at 3:28 PM, N_Molson said:

Hello, excellent mod but I can't find a way to save the gauges positions, which is a bit annoying.

Of course, I tried the "Save" button in the NanoGauges menu and then exited it by clicking "Close", but when I exit and restart KSP, all the modes are back to default settings.

I'm using 1.2 x64. I also made sure that the files were not "read-only", just in case. I however do have a 8ko "Nanogauges.dat" file in KSP/Gamedata folder, so I'd say that the info is saved but not loaded.

Thanks for any hints !

Confirmed. Custom gauge positions are not working. I spend time arranging them only to restart the game and SET 1 2 and 3 along with other layouts like Standard, Launch, Orbit etc. that were edited, are defaulted when the game restarts. I deleted nanogauges.dat and re-installed the Ng Mod. ran ksp.exe as admin, Moved a few gauges and copied/pasted into Set(s) one two and three, restarted. no luck still default.

[N_Molson]

Well it seems that the addon thinks he is doing everything right :

Spoiler

[LOG 19:50:16.439] log level INFO
[LOG 19:50:16.440] NG: loading configuration from E:/KSP_win/KSP_x64_Data/../GameData/NanoGauges.dat
[LOG 19:50:16.457] NG: log level loaded: DETAIL
[LOG 19:50:16.458] NG: loading window positions for gauge set STANDARD
[LOG 19:50:16.461] NG: loading window enabled/disabled states for gauge set STANDARD
[LOG 19:50:16.463] NG: loading window positions for gauge set LAND
[LOG 19:50:16.464] NG: loading window enabled/disabled states for gauge set LAND
[LOG 19:50:16.465] NG: loading window positions for gauge set DOCK
[LOG 19:50:16.466] NG: loading window enabled/disabled states for gauge set DOCK
[LOG 19:50:16.466] NG: loading window positions for gauge set FLIGHT
[LOG 19:50:16.467] NG: loading window enabled/disabled states for gauge set FLIGHT
[LOG 19:50:16.468] NG: loading window positions for gauge set ORBIT
[LOG 19:50:16.469] NG: loading window enabled/disabled states for gauge set ORBIT
[LOG 19:50:16.470] NG: loading window positions for gauge set LAUNCH
[LOG 19:50:16.471] NG: loading window enabled/disabled states for gauge set LAUNCH
[LOG 19:50:16.471] NG: loading window positions for gauge set SET1
[LOG 19:50:16.474] NG: loading window enabled/disabled states for gauge set SET1
[LOG 19:50:16.474] NG: loading window positions for gauge set SET2
[LOG 19:50:16.475] NG: loading window enabled/disabled states for gauge set SET2
[LOG 19:50:16.476] NG: loading window positions for gauge set SET3
[LOG 19:50:16.477] NG: loading window enabled/disabled states for gauge set SET3
[LOG 19:50:16.478] NG: log level is INFO
[LOG 19:50:16.479] NG: static init of NanoGauges
[LOG 19:50:16.487] NG: creating gaues
[LOG 19:50:16.494] NG: defining resources
[LOG 19:50:16.495] NG: loading resources
[LOG 19:50:16.496] NG: loading resource LiquidFuel of id 374119730
[LOG 19:50:16.497] NG: loading resource Oxidizer of id -1823983486
[LOG 19:50:16.497] NG: loading resource SolidFuel of id 650317537
[LOG 19:50:16.498] NG: loading resource MonoPropellant of id 2001413032
[LOG 19:50:16.499] NG: loading resource XenonGas of id 1447111193
[LOG 19:50:16.499] NG: loading resource ElectricCharge of id 1576437329
[LOG 19:50:16.500] NG: loading resource IntakeAir of id -1909417378
[LOG 19:50:16.501] NG: loading resource EVA Propellant of id -792463147
[LOG 19:50:16.502] NG: loading resource Ore of id 79554
[LOG 19:50:16.502] NG: loading resource Ablator of id 466598945
[LOG 19:50:16.503] NG: loading resource Food of id 2195582
[LOG 19:50:16.504] NG: loading resource Water of id 83350775
[LOG 19:50:16.504] NG: loading resource Oxygen of id -1918734912
[LOG 19:50:16.505] NG: loading resource CarbonDioxide of id -609904529
[LOG 19:50:16.506] NG: loading resource Waste of id 83350266
[LOG 19:50:16.507] NG: loading resource WasteWater of id -2035364291
[LOG 19:50:16.507] NG: loading resources done
[LOG 19:50:16.508] NG: defining stock resources
[LOG 19:50:16.509] NG: defining TAC life support resources
[LOG 19:50:16.509] NG: optional resource 'Food' found
[LOG 19:50:16.510] NG: optional resource 'Water' found
[LOG 19:50:16.511] NG: optional resource 'CarbonDioxide' found
[LOG 19:50:16.511] NG: optional resource 'Waste' found
[LOG 19:50:16.512] NG: optional resource 'WasteWater' found
[LOG 19:50:16.513] NG: optional resource 'Oxygen' found
[LOG 19:50:16.513] NG: defining Khetane resources
[LOG 19:50:16.514] NG: optional resource 'Kethane' not found
[LOG 19:50:16.515] NG: optional resource 'KIntakeAir' not found
[LOG 19:50:16.515] NG: defining Deadly Reentry resources
[LOG 19:50:16.516] NG: optional resource 'AblativeShielding' not found
[LOG 19:50:16.517] NG: defining Real Fuels resources
[LOG 19:50:16.518] NG: optional resource 'Karbonite' not found
[LOG 19:50:16.518] NG: resources completely defined
[LOG 19:50:16.539] NG: layout of gauges in set STANDARD (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.541] NG: layout Nereid.NanoGauges.ClusterLayout, set STANDARD
[LOG 19:50:16.547] NG: layout of gauges in set LAND (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.548] NG: layout Nereid.NanoGauges.ClusterLayout, set LAND
[LOG 19:50:16.549] NG: layout of gauges in set DOCK (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.550] NG: layout Nereid.NanoGauges.ClusterLayout, set DOCK
[LOG 19:50:16.550] NG: layout of gauges in set FLIGHT (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.551] NG: layout Nereid.NanoGauges.ClusterLayout, set FLIGHT
[LOG 19:50:16.552] NG: layout of gauges in set ORBIT (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.553] NG: layout Nereid.NanoGauges.ClusterLayout, set ORBIT
[LOG 19:50:16.554] NG: layout of gauges in set LAUNCH (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.555] NG: layout Nereid.NanoGauges.ClusterLayout, set LAUNCH
[LOG 19:50:16.556] NG: layout of gauges in set SET1 (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.557] NG: layout Nereid.NanoGauges.ClusterLayout, set SET1
[LOG 19:50:16.558] NG: layout of gauges in set SET2 (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.558] NG: layout Nereid.NanoGauges.ClusterLayout, set SET2
[LOG 19:50:16.559] NG: layout of gauges in set SET3 (screen: 1680x1050) with ClusterLayout
[LOG 19:50:16.560] NG: layout Nereid.NanoGauges.ClusterLayout, set SET3
[LOG 19:50:16.562] log level DETAIL
[LOG 19:50:16.563] NG: new instance of NanoGauges

But obviously something goes wrong...

Edited May 12, 2016 by N_Molson

[Nereid]

3 hours ago, N_Molson said:

Well it seems that the addon thinks he is doing everything right :

[...]

Quote

But obviously something goes wrong...

This looks quite normal to me. So what do you think is going wrong?

If there is an issue with the gauge positions, then its because the fix for the gauge size has introduced this. I'm currently checking this. The sizes of 120%, 150%, etc was added later on and didn't fit well into the old concept. EDIT: I'm not sure about this anymore...

Without a QA its a little bit difficult to do regression tests with every release. Developers tend to test changed funtionality only. This is why such tests are done by other people.  And even then often weird things happen...

Until this is fixed, use the previous version of NG. I will revoke the current one from spacedock and try to fix this tomorrow. But this is not an easy one.

Its late; hopefully there are not to many typos.

Edited May 12, 2016 by Nereid

[Nereid]

7 hours ago, CobaltMongoose said:

Confirmed. Custom gauge positions are not working. I spend time arranging them only to restart the game and SET 1 2 and 3 along with other layouts like Standard, Launch, Orbit etc. that were edited, are defaulted when the game restarts. I deleted nanogauges.dat and re-installed the Ng Mod. ran ksp.exe as admin, Moved a few gauges and copied/pasted into Set(s) one two and three, restarted. no luck still default.

I'm currently investigating this. Maybe I have introduced this with the new layout options, maybe later on. Its a high priority issue and should be fixed in one or two days. I will do my best to fix this until late friday evening (CEST).

 

EDIT:

??? Why is there a             

 configuration.ResetAllWindowPositions(gauges);

following the settings (and window positions) load?

Ok, this was causing this. I will upload a hotfix for this...

Edited May 12, 2016 by Nereid

[N_Molson]

Thank you very much. Tell me if more info can help, I can set the Log on "TRACE" and post it again if you want.

[Nereid]

It should (!) be fixed in: 1.1.13-2311.

 

Please let me know if there are still issues.

6 minutes ago, N_Molson said:

Thank you very much. Tell me if more info can help, I can set the Log on "TRACE" and post it again if you want.

Please try 1.1.13-2311.

It's 01:00 AM now. I will go to sleep now. Well... literally "nightly fix" and "nightly build"  

[N_Molson]

1:41AM here

But good news, as it seems we have a winner ! Nice work !

[CobaltMongoose]

On 5/10/2016 at 3:28 PM, N_Molson said:

2 hours ago, Nereid said:

It should (!) be fixed in: 1.1.13-2311.

 

Please let me know if there are still issues.

Please try 1.1.13-2311.

It's 01:00 AM now. I will go to sleep now. Well... literally "nightly fix" and "nightly build"  

You sir are a wizard!  Nice work once again!

[Nereid]

15 hours ago, N_Molson said:

1:41AM here

But good news, as it seems we have a winner ! Nice work !

Not really. 

Because unfortunately this hotfix has still an issue and there was a purpose for the call of

ResetAllWindowPositions

If you start NG for the very first time or if you delete the Nanogauges.dat, all gauges are stacked on the top left position. If this is the case, just reset the positions in the config window.  (fixed)

At the end this was caused by the gauge size option, because this was added later on and only works if the gauge scale value was set before they are created. 
Just before KSP 1.1 I was adding a new layout feature for a more convenient standard positions. But this layout needs the gauges to be created first. 

And now there is a chicken egg problem:

1. load config first to get the gauge scaling working
2. create the gauges first to adjust the default positions

The last broken release had done it this way:

1. load config (and set positions)
2. create gauges
3. reset positions to default

Which obviously ignores the stored positions completely.

There is no other way as to fix the gauge scaling to be adjustable at runtime and not only at the very first start of NG. And then the order should be

1. create gauges
2. reset positions to default
3. load config (and set positions)

And such kind of bugs are the reason why developing software is an expensive task. You need quite a few people to write software and avoid such issues. Software architects that creates the basic design, a team of developers, a team leader, some people for quality assurance, some testers, a group of people for version control and release management, often a database administrator (if you are using a database), a group of system admins, sometimes specialists for certain frameworks, ...

Edited May 13, 2016 by Nereid

[Nereid]

On 11.5.2016 at 3:40 AM, Minowara said:

The seismometer's gauge is fully working now, but it seems that TAC's life support gauge for solid waste is missing.

It should be there "Waste gauge enabled (TAC life suppord required)". If not, then NG do not find the corresponding resource.

[Nereid]

8 hours ago, Nereid said:

If you start NG for the very first time or if you delete the Nanogauges.dat, all gauges are stacked on the top left position. If this is the case, just reset the positions in the config window. 

I think this is fixed, too. I will upload the new release ASAP...

 

Done

Edited May 13, 2016 by Nereid

[Nereid]

 

On 11.5.2016 at 3:40 AM, Minowara said:

The seismometer's gauge is fully working now, but it seems that TAC's life support gauge for solid waste is missing.

You were right. It is fixed in 1.2.1.

 

There is a new feature in NG 1.2.1: Profiles.

After enabling profiles (in the configuration window) the gauge sets are switched automatically if the vessel enters a new situation. E.g. if a vessel establish a stable orbit the ORBIT gauge set (or some other set) is shown. If you are leaving an orbit to the suborbital situation (i.e. descending to the surface) the gauge set LAND  is automatically selected. There are three hotkeys to select a gauge set on keypress, too.

Edited May 16, 2016 by Nereid

[p1t1o]

Just stopping by to mention that this mod is on my list of essential-must-haves. Should be stock.

Great work bugfixing over the last few days too.

Peace! 

[Nereid]

On 10.5.2016 at 1:44 AM, Minowara said:

Let me know. I am more than willing to provide a list of the resource names used by RF. And thank you 

Well, there are many resources in RF. I can do 5 or 6 but not all. We can add some kind of generic gauges that can be assigned to a specific resource, but they will get generic names (like "G1", "G2", ...).

Anyway. I have added an indicated airspeed gauge and because I cant do all or even most resources  of RF, I will release this minor change now.

 

EDIT: I have added a list of hotkeys on the first page of this thread:

Hotkeys:

• RIGHT-CTRL: disable gauges / drag as group
• RIGHT-CTRL-TAB: hide/unhide gauges
• RIGHT-CTRL-DEL: hide/unhide gauges
• RIGHT-CTRL-BCKSPC: reset all gauge positions and their enabled/disabled states to their defaults
• NUMLOCK: hide/unhide gauges
• RIGHT-CTRL-1: select STANDARD gauge set
• RIGHT-CTRL-2: select LAUNCH gauge set
• RIGHT-CTRL-3: select LAND gauge set
• RIGHT-CTRL-4: select DOCKING gauge set
• RIGHT-CTRL-5: select ORBIT gauge set
• RIGHT-CTRL-6: select FLIGHT gauge set
• RIGHT-CTRL-7: select S1 gauge set
• RIGHT-CTRL-8: select S2 gauge set
• RIGHT-CTRL-9: select S3 gauge set

Changed in 1.2.5

Edited October 9, 2016 by Nereid

[hawk_za]

hi all i was just wondering is there any plan to update the ckan repository for this plugin or are we awaiting 1.2

 

ps just want to clarify this is not a demand and in no way feel that the author is obligated to do anything

but really love this mod and would hate to see it fade

[Nereid]

On 2.9.2016 at 7:47 PM, hawk_za said:

hi all i was just wondering is there any plan to update the ckan repository for this plugin or are we awaiting 1.2

but really love this mod and would hate to see it fade

I can't say anything about ckan. But I have already updated it for the KSP 1.2 pre release.

But I will wait until the official release of KSP 1.2 to upload it.

Edited October 9, 2016 by Nereid

[Nereid]

Update:

The indicator gauge (gear, brakes, airbrakes, flaps, afterburner) is working again. And because of the hotkey conflicts with the default KSP hotkeys (especially action groups) I will make them configurable.

Edited October 8, 2016 by Nereid

[Nereid]

Updated for KSP 1.2

[hawk_za]

wow thanks a ton for the hard work the mods are what make this game great and keep it fresh and new

[Nereid]

Updated to  1.3.6-2654.

Warning: if you install this update all of your previous saved NanoGauges hotkey definitions are reset to their defaults because of a change in the config file structure.

This version has two changes:

1. It fixes the minor bug that caused the gauges to be shown at launch regardless if the gauges should be shown in flight or not.
2. A missing hotkey is added.
3. It splits the SUBORBITAL profile into three profiles:
   1. FLIGHT TO SUBORBITAL: changes the gauge set, if the vessel situation changes from FLIGHT to  SUBORBITAL
   2. ORBIT TO SUBORBITAL: changes the gauge set, if the vessel situation changes from ORBIT to  SUBORBITAL
   3. OTHER TO SUBORBITAL: changes the gauge set, if the vessel situation changes from any other situation to  SUBORBITAL

This makes the SUBORBITAL profile more useful:

If it is enabled and

• you launch your vessel, it will now automatically switch to ORBIT (or whatever you choose), if the vessel situation changes to SUBORBITAL.
• you leave an ORBIT to a descending path, it will now automatically switch to LAND (or whatever you choose)

"OTHER TO SUBORBITAL" is the default for all other situation changes (e.g. if you change the vessel)

And a note: There are new hotkeys (since 1.3.5): PGUP/PGDOWN now switches between gauge sets. If you do not like those hotkeys, change or disable them in the config.