Bug with movement limits not getting saved in DL5 project

[markov]

I have a moveable fixture with only a pan channel defined, but no tilt channel. Any pan movement limits that I set for that fixture work correctly in DL5 after I set them, but they are not saved properly in the project. The next time I reopen the project, the movement limits on that fixture are reset to default.

I also have a different moveable fixture with only a tilt channel defined (no pan channel), and it behaves the same way: tilt movement limits work correctly after I set them, but they are not saved in the project and get reset to defaults the next time I open the project.

So it appears that with fixtures that have a pan channel or a tilt channel (but not both), DL5 either doesn't save movement limit settings in the project file correctly, or doesn't reload them correctly when opening a project file. Either way, upon reopening a project file with such fixtures, all of their movement limits are reset to their default values.

Please confirm and fix this in the next release. Thanks.

[willm]

Hello,

What version of Daslight 5 are you using, and also what operating system version is your computer running? On my side- I have not been able to reproduce this (version 5.0.4.2, MacOS Sonoma). Perhaps it would also be useful to know the exact fixture profile(s) that you are using so that we can create a more accurate test?

Kind regards,
Will

[markov]

Hi willm.

I am using Daslight 5.0.4.2 running on Windows 11. The profiles I am using are:

a customized version of the official Rockville MotionStrip profile (mode 1, only has tilt channel, no pan):

MotionStrip (custom).zip

Only has tilt channel, no pan. Use mode 1.

(136.51 KiB) Downloaded 73 times

and

a customized version of the official Mini Dekker profile that maps the motor control channel as a pan channel (no tilt, mode 2):

Mini Dekker (my copy).zip

Only has pan channel, no tilt. Use mode 2.

(57.76 KiB) Downloaded 54 times

If you are still unable to replicate the issue, I can try to create a simple test project that replicates it. If for some reason that doesn't work, perhaps there is something specific to my project file that is causing the problem.

[markov]

Were you able to replicate this bug using the fixture profiles I provided willm, or do you need me to attempt to create a demonstration project? Thanks.

[willm]

Hey Markov,

Apologies for missing your last message- I have just checked this and I believe I have figured out what the issue here is. The issue here is actually to do with the Physical component of the fixture profile. As you will notice, both fixtures are set to an LED type- which I believe to be the cause of the issue. If you switch this to a Head format (I would recommend Head 26 for the MotionStrip fixture for example)- this should then work fine.

Nevertheless, it should still be the case that the limitations are stored correctly regardless of the fixture's physical settings- so I will report this as a bug to be fixed in an future version.

Kind regards,
Will

[markov]

Hi willm. I tried your suggested workaround and it worked. Thank you.

[Qwertis]

I experience something similar with settings not being saved.

viewtopic.php?p=26139#p26139