Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ShellMacros - Running batch minimized #449

Closed
Romainrob opened this issue Nov 30, 2019 · 10 comments
Closed

ShellMacros - Running batch minimized #449

Romainrob opened this issue Nov 30, 2019 · 10 comments

Comments

@Romainrob
Copy link

Bonjour!
I'm playing with the CLI to send inputs to SimHub. I'm thinking of using a dash/overlay as a virtual button box dedicated to SimHub controls, including the new Shake It controls.

So i have "C:\Program Files (x86)\SimHub\SimHubWPF.exe" -triggerinputpress MyInput commands inside .bat files in my C:\Program Files (x86)\SimHub\ShellMacros folder.

When I map these to tactile buttons it works, but I'd like the bat file to run hidden or minimized.
I found a working tricks but it involve having calling the batch via a shortcut which is a bit cluncky.

Maybe I'm going at it wrong. I wonder if there is a cleaner/easier way. If so please let me know.
If not, could SimHub launch .bat file minimized either by default or as an option?
Thanks in advance et bon dimanche!

@Romainrob
Copy link
Author

Hi! I'm not done but it's getting there. :)

Button test

This gave me a couple of suggestions ideas regarding the controls.

  1. A ShakeIt calibration reset control mapping would be a nice addition.
  2. The low fuel alert trigger value controls would make more sense to me with 0.1 lap steps than the current 1 lap.
    Bonne journée! :)

@SHWotever
Copy link
Owner

Ha that's a huge loop indeed :D, i think the best solution is the one i used for SimDeck, simply give a name to the input in dash studio and be able to map it directly on any controls in simhub,
I will look for it :) (and additional controls too ;) )

@Romainrob
Copy link
Author

That would be perfect! Thank you! :)

@Romainrob
Copy link
Author

Romainrob commented Dec 1, 2019

Re. I've done a bit more testing with the controls and here are some additional thoughts/suggestions.

These extra controls would be sweet :

  1. Mute control for the global gain of ShakeIt Motors
  2. Mute control for ShakeIt Bass Shakers
  3. Thrustmaster wheel angle +/- controls

Back to the stepping of the increase/decrease controls, some of them are not adapted to this use case. Either, too much clicking or not fine enough control to my taste. To give a couple more examples, I wish the TM wheel FFB was 5 instead of 1 and the game volume 5 instead of 10. Je sais, je chipotte...
Idk what would be best. Having the option to change any of these may be too much clutter.
If the dash studio buttons could be long pressed and the steps set at 1, that would solve this.

In any case, thanks for considering these ideas.

Game volume controls are a really handy btw. I wish I noticed them earlier. Good bye windows mixer!:)

Oh and for a final nitpicking touch i noticed this small layout issue :
image

@Romainrob
Copy link
Author

Romainrob commented Dec 2, 2019

Hi! Guess who's back for another round ;)
I've worked a bit more on my "control center" overlay today and I have yet a couple more suggestions/request.

  1. Could we have multiple inputs binded to the new ShakeIT controls. I miss the "add" button.

  2. Could the value (% and "Muted")in the overlay message be available as a property, as a flexible way to get the gain value of groups and effects when using the controls.

Button test2

  1. I doubt this is possible, but I'll ask anyway. I'd like to make the overlay "collapse" as you can see in the giant gif from a couple days ago. Visually, it works great but the whole overlay area stays "unclickable" (as in no click through possible) even when collapsed. Idk if there is a possible solution to this. I'm thinking of some a click through object we could place in the dash layout, and make active or not (using visibility binding maybe ?)

The more I mess with this, the more I think that having an overlay/dash of this kind by default would make sense. Especially if you keep adding more controls. It would be hard the decide what to include in it, since users have widely different setups. Maybe it could be splitted into screens/pages, so people could easily go in and disable what what they don"t need. I'll PM you mine if you want to check it or even reuse part of it if you like. Or not. No pressure.

Once again, thanks for considering these ideas. Hopefully some of them you'll like and be doable.
Bonne fin de soirée à toi!

PS:Maybe we should rename the Ticket, I'm afraid I've completely derailed it. sry.

@SHWotever
Copy link
Owner

Just to resume the related action :
Already available :

  • Overlay message as a property, already available :
    image

Possible :

  • Make possible to assign an input name to a dashstudio button so it can be used directly as a simhub input. -> Done
  • Global mute control for both ShakeIt -> Todo
  • Fix layout issue in TM plugin -> Todo
  • Multiple inputs for "dynamic actions" (shakeit) -> todo
  • Settings for FFB controls steps -> todo
  • Settings for game volume steps -> todo

Impossible :

  • Thrustmaster wheel angle +/- controls -> I won't do it, unlike gain, changing rotation kills ffb on most games when done with game running :(
  • Dynamic click trough : really too complex and glitchy :(

@Romainrob
Copy link
Author

Hi! Thanks for your answer and pointing me to the notification properties. I'll make good use of these :)

@Romainrob
Copy link
Author

Hi!
I remapped all my controls with the new custom buttons. It's much better. :)
Thanks you very much for that addition.

I have a couple more request/suggestions :

  1. Would it be possible to affect these custom name inputs to control the widgets as well? I'm running out of action ABCD as I run more and more dashes/overlays.

  2. I think it would make sense for the increment/decrement controls of Shake It to also unmute the effect/group/global when used. Especially since you're most likely adjusting levels "blindly" when using mapped controls.

Thanks once more for considering thees ideas.

@Romainrob
Copy link
Author

One more detail. I just noticed the notification titles (thanks for adding it btw :)) say "Shakers" and "Motors" instead of "Shakers Power" and "Motors Power" when using the new shake It mute controls.

@Romainrob
Copy link
Author

Hi again. This is a messy one.
You covered most it though. Thank you again for for all of that!
I think I'll close this one and reopen a cleaner one focused one the minor missing bits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants