> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark-6/actions/motor-property-action.md). # Motor Property Action

Motor Property Action allow you to change specified motor properties in your cue sequence. ## Motor Properties * Scenery Length * Scenery Width * Scenery Height * Min Jogging Percentage * Max Jogging Percentage ### Change Scenery Dimensions in the Stage Model This feature solves a common staging challenge: When multiple set pieces run on the same deck track, you may want the model to reflect the different size set pieces. Create a Motor Property Action to update the set piece's dimensions in the Stage Model without leaving the cue list during your show. You can idividually change the length, width, and height of the set piece in the Stage Model ### Jogging Percentage Adjust Maximum and Minimum Jog Percentages to control joystick sensitivity. This proves especially useful when different show segments require different motor speed ranges for safe operation when jogging from the joystick. ## Editing and Executing a Motor Property Action

### To Edit 1. Click the action inside your cue 2. Select a motor from the Motor dropdown 3. Choose a property from the Property dropdown to Update 4. Enter the new value 5. Click Save to confirm or Discard Changes to cancel ### To Execute 1. Load the Cue 2. Press Go on the Playback that has the Motor Property Action --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.creativeconners.com/docs/spikemark-6/actions/motor-property-action.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.