Support Forum

OK, either I don't understand how the basis of FS works, or something is fubar in the way it handles movements. In any case, it's REALLY difficult to understand how it works. Here's what I do, step by step:

I erased everything (scenes, buttons etc..) except my 3 fixtures (currently 2 scanners and a strobe).
Selected the 2 scanners only.
Created a scene with 1 step, transparent mode, choosing a gobo and a color and using the pan/tilt window to start a rectangle movement (bezier).
Saved the scene. (the Pan and Tilt channels remain "off" in the channels window, is this normal? but the scans do move).
Assigned the scene to a button in latch mode.
Up to there, everything fine, clicking the button on /off starts/stops the scene for the scanners as expected.

Unselected everything.
Created a new scene.
Selected the strob, set the 2 channels to 200 (not important), snap mode.
Checked again that the channels for the scans are set to "off" before saving the scene.
Set the scene to static mode, saved, assigned to another button. Button works fine too when used alone.

Now if when I click on the strob button I get this "freeze movements" described in another topic, but:
- it also blacks out the scanners
- even if I click on the scanners scene button, it lights up the gobo and the scan, but no movement until I release the strob button AND cycle once more off/on the scan scene button

I'm totally stuck.

This has currently been discussed in another thread im starting to belive this could possibley be a bug and will investigate and talk to raph about the results.

Matt

Seems I found a workaround. If I add the scene for the scanners in a cue and start it with the cue, it seems to work and does not get stopped by the strobe button. But I still get some inconsistent results from time to time, for example I opened the strobe scene (just 1 step setting the values) to check its parameters, then closed it in the scene editor. To check the button again I set manually the speed and intensity to 0 in the main windows. But then the button didn't work anymore.
I opened the scene again and saw that the speed (only the speed) had been reset to 0 in the scene. I never did this and saved it like that. Strange.