see attached
**EDIT: I just noticed that it's also dropping universes, and I was having trouble outputting certain universes when only outputting quantity 1, there might be something else going on here...**
**EDIT 2: How do you tell how many parameters are active in MA3? I think this might actually be an issue of parameter activation, and the fact that it was outputting artnet universes which had no fixtures patched was making me assume something else**
Hello!
So I am running into an issue where changing the Artnet local universe start is also changing the artnet universe.
MA3 onPC for windows v 1.4.2.1
local universe 01; net 0; sub-net 0; universe 0 = artnet 0x0000
local universe 11; net 0; sub-net 0; universe 0 = artnet 0x00a0
**EDIT: local universe 01; net 0; sub-net 0; universe 10 = 0x00a0**
same settings in MA2 produce 0x0000 both times.
Would like to make sure I am not missing something before generating an error report
Thanks in advance!
That was 100% my issue, thanks! That'll learn me for not reading release notes!
Hello!
I've been having trouble using the "thru" keyword with subfixture IDs.
I am able to select individual subIDs "fixture 1.2 please" and multiple subfixtures "fixture 1.2 + fixture 1.10 please" but when I try to use the thru keyword, it seems to be ignoring everything after it. "fixture 1.2 thru fixture 1.10 please" is functioning the same as "fixture 1.2 thru please" and is selecting fixture 1.2 and every subfixture following it.
Am I missing something?
EDIT: something else curious, entering "fixture 1.3 thru fixture 2.5 please" results in selecting 1.3->1.29+2.5
