PDA

View Full Version : Scene issues on V3

MVSobey
01 Nov 04, 09:58 AM
I have noticed after playing with the new V3 software that it has many advantages over V2. It does however have a major disadvantage in comparison to V2 with its use of the scenes on Neo keys. With V2 software when a scene is place on a key, a group description can still be place in the block for that key and can then be assigned to one of the other keys on the unit. This is not possible on the new V3 software reducing the Unit overall functionality.
Duncan
01 Nov 04, 10:01 AM
I have noticed after playing with the new V3 software that it has many advantages over V2. It does however have a major disadvantage in comparison to V2 with its use of the scenes on Neo keys. With V2 software when a scene is place on a key, a group description can still be place in the block for that key and can then be assigned to one of the other keys on the unit. This is not possible on the new V3 software reducing the Unit overall functionality.


Great point!

I've logged it for resolution in a future build..
Duncan
01 Nov 04, 10:47 AM
Great point!

I've logged it for resolution in a future build..


MV.. just a clarification.. I thought on first reading your post that you were using the assigning of a Group Address to the Scene Key in order to 'label' what scene has been set for a key.. I now realise on re-reading that you're looking to reuse the Group assigned to that block on another key..

Regretfully, a pending update to Neo firmware to offer more enhanced scene support may in fact make that form of re-use of the relevant block no longer work. What you have done in the past was an unfortunate loophole in V2. We now reserve the block for additional future functionality.
barry dawson
01 Nov 04, 11:01 AM
Regretfully, a pending update to Neo firmware to offer more enhanced scene support may in fact make that form of re-use of the relevant block no longer work. What you have done in the past was an unfortunate loophole in V2. We now reserve the block for additional future functionality.

Shame
This was a handy feature sometimes in smaller jobs.
Even if it was a loophole.