DfA-DoM

Hi @rockmeowstar, The stock Gigantor XL Solar Array doesn't seem to be handled for now https://imgur.com/a/kdBQlUC

My kerbals would get as much science as possible!

For the record, there's no such launcher things while using the "direct-from-the-store" version of the game (out of Steam and other similar platforms). -D-

According to https://docs.unity3d.com/Manual/PlayerCommandLineArguments.html, you should perhaps have a try starting the game from the command line using the -monitor N option.

In fact, I was used to the NavHud mod on KSP1 and would be very delighted to get some equivalent into KSP2. Controlling the size and transparency of the HUD is mainly a matter of trade-offs between visual aids and scenery. A keyboard-driven switch would also be a must.

Another nice feature would be to get some parameters/sliders to alter the size and the transparency

KSP2 Version: 0.1.1.0.21572 KSP2 Version: 0.1.2.0.22258 Operating System: Windows 1x CPU+GPU+RAM: (not relevant) + Logitech Keyboard Mods Used: None When playing KSP, the room lighting is usually dark, so I can confirm that the keyboard backlight is an invaluable feature, BUT it should be either fully or at least properly implemented. For now, we only have a few directional keycaps highlighted while flying a rocket leaving others with the least common actions bounded desperately blanked out (while perhaps being the most important ones not to miss). Workaround The only workaround is to globally disable the application's backlight handling and rely solely on the poor Logitech application features. What I expect First of all, the backlight control should be configurable. At least, a global on/off switch would be nice. When the focus is on an input field, at least the alphabetic and/or numeric keys should be highlighted to allow proper typing. If all the thrust dedicated keys are highlighted, why are some of the directional keys missing (pitch and yaw are there, but what about the roll)? The toggle keys (RCS/SAS/Brakes/...) should reflect the current state (and possibly activate the corresponding key highlighting). Keys that affect variable parameters such as the thrust increase/decrease or the time warp speed should also have their backlight intensity modulated accordingly. Once assigned the custom action groups should also highlight the selected keys, taking into account the type of action bound to them (binary toggle or increase/decrease). For the record, here's some inspiring (but outdated) stuff: https://github.com/NiamiTV/KeyShine Another tip might be to provide handles to internal game states to enable the use of external backlighting dedicated tools like Aurora (https://www.project-aurora.com/) or Artemis (https://artemis-rgb.com/).

Please, register it in CKAN!

I've resubmitted a reformulated version the bug report/feature request here:

What a great idea to have a contest like this. It's also a good way to make people want to come to the forum to entertain their readers with their future adventures. It's exciting to discover the new UI refinements !

When reaching orbital altitude in flight, the rocket sound is gradually muffed and the soundscape is becoming rather quiet, but when switching into the orbital map screen, the sound seems to be restored to the usual/stock global level, which now is sounding... quite harsh and rough now. The same kind of annoyance is appearing when choosing to revert the current launch. (my post crossed the release one, so my expectations may be met. I need to try it soon)

The @Vandest's video is very nice demo of the mod features which could surely be referenced in the OP. But the thing not shown is the odd behavior when switching from flight to orbital map and back. @ensou04, could you please have a look at this (even if lending an ear would be more appropriate)? Thanks

In the same mood, the sound intensity may get rather high when switching from flight to orbital map. It could be nice to have a softer or longer intensity transition for that, or keep the last level for the current vessel.

Don't worry, you're welcome.

IMHO, we are here at an edge between unhandled case (bug?) and misuse, but this kind of issue would be avoided if we got a way to detect such kind of structurally arguable builds. Have you considered that your (already mandatory) mod could also provide some hints and warnings on the engineering report for example to prevent unintentional relying on ill-formed ships ?

Cool, but we'll definitely need a more appropriate sounding

Wonderful! (What else to say?)

Hi @Angel-125, With this set of mods, you're very nice to give us tasteful food for BreakingGround DLC and you're even nicer to recompile the mods for 1.12.2. So, for perfect Kerbal picnics, I'm sure that most of us would greatly appreciate having these available on CKAN. Could you please remedy or perhaps ask @HebaruSan? Thanks in advance

Hi @DMagic, The difference between an enjoyable gaming experience and a truly intense moment that you will find hard to leave is relying on few things. Tracking Station Evolved is indeed one of those that make all the difference (at least for me, but according to the thread length, I shouldn't be alone). So, other than asking for your help, what could we do to have this mod working in the last release?

Hi @Morse, As far as this UI un-enclumbering life saver mod has been tested to work as-is in 1.12.1, that would be nice to have it listed accordingly in CKAN, no?

I think that you're talking of this one:

Because that would alas mean several (at least 2) different sets of code for the same feature, implying more time to write it and leading unavoidably to an even bigger set of bugs and issues...

For the record, found in v1.11 output log once installed the v2.7 mod with CKAN : The KSPedia version should be rebuild.

Hi, I was wondering if someone had already tried the toolbar in 1.10.1 ? If so, and if that works, please @linuxgurugamer, it would be nice to have the CKAN record and/or the mod itself updated.

Despite this mod may not be considered as the most useful one for all KSP players (and I suspect neither the most difficult to handle), and since I can confirm to have working flawlessly as is on latest v1.10+, it would be nice to have it updated (at least its ckan compatibility record stuck at 1.8.1) and registered as such. Thanks in advance