This is a feature request. It is not implemented yet.
In a sequence with a dummy step and set timing, you can achieve this wanted "2 loops".
If you use hard values (through the fixture profile) or via the DMX tester -> does the laser keeps its steady state?
If no: I suspect a DMX hardware issue. Isolate the fixture to a separate universe... Does it stop flickering? No? Incompatible combination somewhere on the DMX line. Does it not stop flickering? DMX timing issue, but now you are using a non-DMX-compliant fixture.
In the webinar about v1.8, they pointed out that the selection grid shows a little square dot in the upper left corner of an object. This is to show you that there are objects behind the object you see. They pointed out that this behaviour might need to be changed in the future. (To make it more clearly visible that objects are stacked onto each other)
When I need a new fixture definition, I reuse existing ones as a source.
So here f.i. you have a pixel bar with sub-fixtures defined (And 3D geometrics) https://gdtf-share.com/share.p…g&fix=iBar%2015&rev=25257 in different modes. (even the use of virtual dimmers are included, so a nice example to study)
Have a look.
To my knowledge, there is no one-shot option (yet).
Workaround is a Sequence with set duration timings and a dummy Cue and Follow properties applied to the first step?
Load the cue you want to run next
This is not quite right ...
If the cue is loaded by
and it is not yet active (by Go+ f.i.), the pointer to that cue is set for that executor.
Pressing the Go+ should resume normal operation.
If the loaded Cue is activated, there is no recollection of what cue was active previously. Depending on the tracking of a Sequence, unloading a cue to a previous output state may become problematic.
I don't know how to undo this
I would start uninstalling the 1.4 version you have since it's quite old... (and unsupported since you installed 1.7.2.x)
In my other loved forum (QLC+); I wrote these general USB guidelines:
The connecting and disconnecting sound is a hint that something is wrong with your USB bus or the USB devices connected to it. I always have my laptop's sound setting maxed out, to hear those messages...
Things you can check:
* has the laptop's USB bus full power capacity? -> energy settings, full power to USB (somewhere ... depending on your make and brand of the computer and M$ Windows version.
* is power saving DISabled for the USB ports? <- quite an important setting here... you have to change values in the registry or use tuubtuub to find a way to change explained.
* laptops should be in 'full performance mode' or whatever mode it is called nowadays?
* Verify the power consumption of your USB devices; it might be that one drains the whole power out of 1 USB port, hence leaving no power to the other, hence disconnecting itself from the bus.
use a decently powered USB hub in that case. f.i. My EntTec Pro MK2 needs to be connected to my laptop directly, for it to work decently thru long production hours. It consumes 600mA on its own, hence my USB2 port is completely exhausted... All other peripherals are connected thru a powered USB hub here (Mouse, keyboard, touch, BCF2000, touchpad, ...)
* use proper cables!!! USB-C can provide 100W (now 240W?? :shock: ) with a 5 Amps source specified. Whatever tension (5V, 19, 24V, 48V) is used, this still is 5 Ampères! If you know a network cable single lead can have 600mA maximum, such a lead is not capable of transporting 5A.
* [for future reference]
I'd love you to share your experience with USB peripherals failing causes, for future reference.
Currently, I'm not able to have 3 functioning touch displays with a OnPC-Commandwing, a powered hub, and other devices connected, without having the USB-bus reset sounds sound.
- a decent enough setup IMHO: Intel NUC i7 16G with dedicated GPU, 3D is running thru GPU...
- Commandwing in direct to a USB port
- other peripherals via a powered hub (touch1, 2, and 3, keyboard, mouse, stick) 3500mA @ 5V
Use the preview or blind mode?
As far as I can read between the lines:
If checks if the assigned fadermaster (here fader 230) has a value > 90; and then lowers its value by a factor of 75%.
without recooking? Wasn't this the issue in 1.6?
Is your graphics card strong enough? Wasn't there an updated gfx setting in the 1.7 release notes? More options in the 3D view for sure, but I reccon this influences layout views also?
I saw a FB contribution of someone (I don't recall) showing a flyout on a fader (with absolute values) and a fader effect in relative mode on another fader. When single faders were actuated, they did their thing correctly. If you would combine the abs-position flyout with the relative phaser effect together it showed mayhem. So it was denoted as a bug.
If there is no 2nd monitor attached; windows should create a 2nd instance of Ma3OnPC underlying the main instance... ALT+TAB should bring it up.
If you change the hardware setup in session (you unplug the 2nd monitor while Ma3OnPC is running) you'll have to restart Ma3OnPC
Are you sure there is no relative information present in your Preset 1?
This could explain what you notice.
Did you call the Preset 2 into the programmer? Or how did you activate Preset 2? (Notice that in GMa3 there are no action buttons yet)
I noticed some hickups, where the output was interrupted for 3 seconds and then started to work again.
I did not investigate further, but I could hear a sound from the computer telling me an USB bus reset was effectuated.
I'm not sure that the wing was the cause of this bus reset or any of the touch screens... I need to dig some further...
The location of where the 3D meshes reside, changed with v1.7.2 -> Have a look at the release notes.