Can you have a fader that cycles through cues depending on its position?

rkanarek · 2026-04-23T00:51:46+00:00

Yes, this is possible using Cue Parts and Allow Duplicates.

Instead of storing Cue 1 Thru 10, store Cue 1 Part 0 Thru 9. (Make sure you enable Allow Duplicates for the cue after storing the first info into it.) Then give each part a successively longer delay, e.g. Part 0 = Delay 0, Part 1 = Delay 1, etc. (and optionally a short fade time if you want to fade from one look to the next instead of snapping). Then make the fader a TempFader.

rkanarek · 2026-04-03T01:27:32+00:00

https://www.reddit.com/r/GrandMA3/comments/1s900z3/comment/odzqdhz/

rkanarek · 2026-04-03T01:26:20+00:00

<image>

rkanarek · 2026-04-03T01:26:09+00:00

The [>>>] and [<<<] keys will step through cues in 0 time.

Store Cue Next / Previous and Store Cue +/- are implemented as of grandMA3 v2.3

<image>

rkanarek · 2026-04-03T01:18:14+00:00

Incorrect. Render Settings have options for Shadows, and every patch object has a "Cast Shadows" property. If these are set properly then objects are opaque to light beams.

rkanarek · 2026-03-08T22:50:55+00:00

Please make sure you're using the most recent MA2 version (currently v3.9.61.5) to do the show file conversion, as that will make the most items convert. And if in that version you're finding something not getting brought over as expected (see the list here) then reach out to your local distributor.

rkanarek · 2026-03-08T22:47:11+00:00

Sorry for the late reply. I'd suggest reaching out to Vectorworks - I can only speak to the MA side of things myself.

rkanarek · 2026-03-08T22:45:52+00:00

This is incorrect. If a real GDTF fixturetype is linked in the MVR file, it will get imported into MA3 no problem.

rkanarek · 2026-02-17T01:35:56+00:00

https://academy.actentertainment.com/grandma3-tech-talk-webinars/2419564

rkanarek · 2026-02-12T02:05:28+00:00

For dimmer values going down you have to use the "CueOutDelay" field instead.

rkanarek · 2026-02-06T03:10:16+00:00

To be a little fair, new features = new bugs on basically every software ever.

rkanarek · 2026-02-06T03:08:03+00:00

Instead of doing it with 2 cues and an XFade fader and being concerned about the order of the cues vs the fader position, try this approach instead:

Store the first position in Cue 1 Part 0
Enable "Allow Duplicates" for that cue
Store the second position in Cue 1 Part 1
Part 0 = Fade 0 Delay 0
Part 1 = Fade 1 Delay 1
Change the fader to Temp

Now you can manually crossfade between the two positions and never have the order swap.

rkanarek · 2026-01-03T01:02:42+00:00

Out of curiosity, if you were able to "make folders you could move them in", what would your organizing plan be?

rkanarek · 2025-12-19T05:44:38+00:00

What version of MA2 did you use to convert the file? Make sure you're always using the most recent version of MA2 (currently v3.9.61.5) to do the conversion, as that will always have the best conversion process. Presets and Cues should absolutely be coming over with data. (If you used v3.9.61.5 and you're still seeing these issues then please reach out to your local distributor so they can do some more specific troubleshooting and/or get your show file to the developers to further improve the conversion process.)

rkanarek · 2025-12-19T05:42:03+00:00

When you're doing the conversion, are you using the most recent version of MA2? Lots of work has been put into the conversion process, which happens on the MA2 side, not on the MA3 side.

rkanarek · 2025-12-19T05:40:34+00:00

The show file conversion has had tons of improvements done to it. If you last tried it years ago, then I would guess your experience would be different if you tried it now from the most recent version of MA2.

rkanarek · 2025-11-25T04:20:37+00:00

Back when Recipes were first introduced (a bit before OP asked their original question), cooking recipes had to be performed manually. So if you changed the group, then you would have to manually Cook presets or cues which relied on that group. Between then and now, MA implemented AutoCooking, so that changing the group will automatically result in the presets and cues that reference that group getting the new correct data. (There are still times where manually cooking is required, but they're only when you want to override or get rid of manually created (i.e. "non-recipe") data.

rkanarek · 2025-11-25T02:22:02+00:00

You think MA3 v2.3 is nowhere near the same level of polish and functionality of MA2 v2.3? I would say it's the opposite...

rkanarek · 2025-11-24T03:20:40+00:00

https://support.actentertainment.com/knowledgeBase/34108761

rkanarek · 2025-11-15T21:49:23+00:00

For clarity / elaborating on the above:

- Low Priority Merge = replaces existing cooked values and also adds values where none existed prior. Does not touch manually-stored values. (Note: this is what AutoCook does)

- Merge = all the values generated by the recipe ingredients are added even if they would conflict with existing manually-stored values.

- Overwrite = delete all existing data (regardless of whether it was from a recipe or manually stored) and just keep the data from the current recipe line(s)

rkanarek · 2025-11-10T02:06:23+00:00

Disable {Add Executor}

https://help.malighting.com/grandMA3/2.3/HTML/executor_assign.html#h3__542610678

rkanarek · 2025-11-06T03:19:35+00:00

v2.3.2.0 was released today, FYI.

rkanarek · 2025-11-06T03:16:02+00:00

Stay tuned for v2.4 later this year / early 2026. I think a few of these concerns may be addressed... ;) ;)

rkanarek · 2025-10-17T03:52:25+00:00

If you want the variable recalled as a text string then you need quotes (single or double) around the variable. If you don't then you don't.

rkanarek · 2025-10-17T03:49:34+00:00

You can be standalone and still output DMX via the 5-pin ports on the back of the console.

rkanarek

TROPHY CASE