Toolbar: Command to Set Values Directly
Proposal:
"Set X" toolbar action that replaces "Increase X" and "Decrease X". When placing the Set X To action on the toolbar, it will prompt you with a number/text field, as programmable blocks do for their Run action. If this number begins with "++", e.g. "++500.15", then it will increment the slider value by that amount. If this number begins with "--", e.g. "--0.15", then it will decrement the slider value by that amount. Otherwise, a plain number, e.g. "-100.01" will set the slider value to that exact amount. Multiplying an existing value might also be desirable.
How this addresses some existing issues:
Pressing an Increase of Decrease command multiple times to reach a desired value: Unnecessary when you can set to the desired value directly.
Fine tuning values is not possible from the toolbar: It is possible when you have control over the size of increment used by your toolbar actions.
Automation via timer blocks: Vastly easier when you set desired values directly, and/or use increments you've defined.
Reset Velocity action on rotors sets to zero, recovering velocity not possible: Again, set your desired velocity without hassle.
Long lists of actions because every variable offers Increase and Decrease and sometimes Reset actions: Each variable only needs a single multi-purpose Set action, making lists considerably shorter. (But long lists are still possible.)
I like this feedback
I came here to post this exact request. Being able to do this without relying on a programmable block would be extremely helpful, given the issues surrounding it.
This implementation would satisfy a couple of related requests I saw:
https://support.keenswh.com/spaceengineers/pc/topic/command-option-g-bar-timer-block-reset-anyall-increasedecrease-commands
https://support.keenswh.com/spaceengineers/pc/topic/command-option-g-bartimer-block-reset-gyro-override
I came here to post this exact request. Being able to do this without relying on a programmable block would be extremely helpful, given the issues surrounding it.
This implementation would satisfy a couple of related requests I saw:
https://support.keenswh.com/spaceengineers/pc/topic/command-option-g-bar-timer-block-reset-anyall-increasedecrease-commands
https://support.keenswh.com/spaceengineers/pc/topic/command-option-g-bartimer-block-reset-gyro-override
I came here for this and for Visual programming. I think that this API would fit nicely w/ a visual programming tool also.
I found several tickets that could all be combined. I chose to comment on this one because it's the oldest I found.
https://support.keenswh.com/spaceengineers/pc/topic/add-set-to-hotbar-action-for-block-parameters
https://support.keenswh.com/spaceengineers/pc/topic/toolbars-set-instead-of-increase-decrease_1
https://support.keenswh.com/spaceengineers/pc/topic/accurate-actions
https://support.keenswh.com/spaceengineers/pc/topic/allowing-timer-blocks-to-set-accurate-values-on-functional-blocks
Set Increment
In addition to "set to" for existing sliders or numeric inputs I think it would be helpful to have "set increment" which would make Increase/Decrease actions more useful.
I came here for this and for Visual programming. I think that this API would fit nicely w/ a visual programming tool also.
I found several tickets that could all be combined. I chose to comment on this one because it's the oldest I found.
https://support.keenswh.com/spaceengineers/pc/topic/add-set-to-hotbar-action-for-block-parameters
https://support.keenswh.com/spaceengineers/pc/topic/toolbars-set-instead-of-increase-decrease_1
https://support.keenswh.com/spaceengineers/pc/topic/accurate-actions
https://support.keenswh.com/spaceengineers/pc/topic/allowing-timer-blocks-to-set-accurate-values-on-functional-blocks
Set Increment
In addition to "set to" for existing sliders or numeric inputs I think it would be helpful to have "set increment" which would make Increase/Decrease actions more useful.
This is still relevant and would solve significant issues in automating processes.
A great example is pistons in a printer that have to extend slowly at maybe (0.1 m/s) but can retract at full speed (-10 m/s). The increase/decrease action is insufficient because it changes the value by 1.
This is still relevant and would solve significant issues in automating processes.
A great example is pistons in a printer that have to extend slowly at maybe (0.1 m/s) but can retract at full speed (-10 m/s). The increase/decrease action is insufficient because it changes the value by 1.
+1 for this.
I workaround the issue mentioned by fn by setting the piston to eg 0.1, then let a timer trigger 'decrease' twice. when the next print job starts, it increses it 2 times so it is back at 0.1m/s. making this consistent requires turning off and on timers.
I was hoping they did something with the Automatons Update. Maybe a block similar to the timer which is dedicated to said action - set the piston to 0.1 no matter how often 'decrease speed' is pressed before.
+1 for this.
I workaround the issue mentioned by fn by setting the piston to eg 0.1, then let a timer trigger 'decrease' twice. when the next print job starts, it increses it 2 times so it is back at 0.1m/s. making this consistent requires turning off and on timers.
I was hoping they did something with the Automatons Update. Maybe a block similar to the timer which is dedicated to said action - set the piston to 0.1 no matter how often 'decrease speed' is pressed before.
Being able to set specific values from timers is what the game is missing, adding/subtracting 0.02 to piston max distance instead of increase/decrease an annoying giant amount.
Being able to set specific values from timers is what the game is missing, adding/subtracting 0.02 to piston max distance instead of increase/decrease an annoying giant amount.
This is sorely needed, especially for making complex contraptions on servers where scripting is not enabled
This is sorely needed, especially for making complex contraptions on servers where scripting is not enabled
+1, Maybe this will get to 50 before SE2 comes out.
Non-PB interactivity is even more relevant than ever with event controllers and AI around nowadays.
+1, Maybe this will get to 50 before SE2 comes out.
Non-PB interactivity is even more relevant than ever with event controllers and AI around nowadays.
Now we have set value and e scure for pistons rotors and hinges. There need to be more. For example I just made a script less planet ascending system and to do so I need to put thrusters on override. Currently there is no set override options . Only increase decrease. So I ended up making one tuner block with all 10 slots filled with increase and another timer block filled with decrease action s . The in event controller Instill need to use 2 slots to trigger a tuner 2 times in order to have 20 increase/decrease actions executed. It can be just as simple as set 100%/0% override and execute from a single slot in event controller without any timers at all.
I think all the functional blocks should expose set and execute commands for all the values you can normally change from K menu.
Now we have set value and e scure for pistons rotors and hinges. There need to be more. For example I just made a script less planet ascending system and to do so I need to put thrusters on override. Currently there is no set override options . Only increase decrease. So I ended up making one tuner block with all 10 slots filled with increase and another timer block filled with decrease action s . The in event controller Instill need to use 2 slots to trigger a tuner 2 times in order to have 20 increase/decrease actions executed. It can be just as simple as set 100%/0% override and execute from a single slot in event controller without any timers at all.
I think all the functional blocks should expose set and execute commands for all the values you can normally change from K menu.
Hello Engineer,
We suggest revisiting the game and checking out Rotors, Hinges, Pistons, and the Action Relay. These blocks have received the so-called Set Value actions. We're currently in the process of adding a few more of these in the upcoming 206 update, as we announced a while ago.
If you have suggestions for additional Set Value actions on specific blocks, please feel free to share them with us.
Best regards,
Keen Software House: QA Department
Hello Engineer,
We suggest revisiting the game and checking out Rotors, Hinges, Pistons, and the Action Relay. These blocks have received the so-called Set Value actions. We're currently in the process of adding a few more of these in the upcoming 206 update, as we announced a while ago.
If you have suggestions for additional Set Value actions on specific blocks, please feel free to share them with us.
Best regards,
Keen Software House: QA Department
As mentioned in OP, there is also a problem with the long list of actions. Adding more will make it even worse. Consider combining actions in 1 more customizable command. For example, take something axis related, like projection control, instead of separate action for each axis and direction, you can combine all 6 into 1 command and make 2 arguments for axis and direction. So you first select the "move projection action", first prompt will ask you the axis and you can put x y z, next prompt asks you the amount, so you put 1, -1, 4 etc.. (any integer with a sign). This might break some old automations probably, but the benefit would be enormous in terms of both reduced list of commands and ability to use arbitrary "step" for increasing/decreasing commands. Think about all variety of similar commands: all the override type commands, all min max increase/decrease (like for pistons/rotors/hinges).
There can be more events:
Axis specific speed (not just grid speed), this can be useful for some advanced flight controls and automations.
As mentioned in OP, there is also a problem with the long list of actions. Adding more will make it even worse. Consider combining actions in 1 more customizable command. For example, take something axis related, like projection control, instead of separate action for each axis and direction, you can combine all 6 into 1 command and make 2 arguments for axis and direction. So you first select the "move projection action", first prompt will ask you the axis and you can put x y z, next prompt asks you the amount, so you put 1, -1, 4 etc.. (any integer with a sign). This might break some old automations probably, but the benefit would be enormous in terms of both reduced list of commands and ability to use arbitrary "step" for increasing/decreasing commands. Think about all variety of similar commands: all the override type commands, all min max increase/decrease (like for pistons/rotors/hinges).
There can be more events:
Axis specific speed (not just grid speed), this can be useful for some advanced flight controls and automations.
Don't forget about splitting those "on/off" actions to separate "on" and "off". For example, "dampeners On/Off" should be split into 2 separate actions.
Don't forget about splitting those "on/off" actions to separate "on" and "off". For example, "dampeners On/Off" should be split into 2 separate actions.
Can we have set jumpdrive distance in kilomenters and percentage? To be able to set a couple of presets: min: 5km, 10, 15, 50, Max range etc.
Can we have set jumpdrive distance in kilomenters and percentage? To be able to set a couple of presets: min: 5km, 10, 15, 50, Max range etc.
Replies have been locked on this page!