Version 3.2 Default Values on Startup

[dizzo007]

Has anyone had any issues with the "Default Values on Startup" feature. This doesnt seems to bee working with this latest release. This would enable all of your lighting fixtures to startup with the same DMX Values every time you start up Freestyler. Now when you click on it, it doesnt do anything any more. Your values will always start up at "0".

[LJ_krede.dk]

in the new version you can set the deafult value in the fixture file by using FixtureCreator. try and see if that helps

but yes, the "Save as Startup values" feature in freestyler dont work,,,

I will contact Raph and inform him about the issue

[dizzo007]

Thanks...

I set all my start up values to have the lamps on upon start up this way they are all preheated and ready to go.

[GaryBonaducci]

I too have just started to get problems with this late last night. On boot-up, FreeStyler started posting an error message about problems loading startup values. During shutdown, it appears FreeStyler wants to post an error messagebox too, but the program cuts it off and exits before the full message can be displayed.

Restoring FreeStyler with a previous backup from one week ago had no effect--I still got that error.

I examined the files in FreeStyler's program folder and found that one file, "pres.DAT", stopped being modified at the time when the errors started to appear. I renamed the file to "pres.DAT.temp" (effectively deleting it from FreeStyler), and the program booted and shutdown normally again. A new "pres.DAT" file appeared, but this file was only 1K in size, versus 24K for my original, defective file.

Unfortunately, not only does this file seem to store startup values, it also seems to contain values for setting up the touchscreen interface. I lost my button layout by having this file damaged....

Up until this point, version 3.2 was working fine for me. I thought this problem with my corrupt "pres.DAT" file was related to a BSOD halt I had minutes earlier, but since someone else is reporting a problem, then who knows? I am experimenting with my touchscreen and Window's "On-Screen Keyboard" utility, and they seem to have some issues working with each other. I've had to reboot On-Screen Keyboard a few times.

[remco_k]

Do you still have that press.dat.temp?

If so, please report this as a bug and save that file. Maybe Raph (the developer) contacts you to recieve the file.
[bugreporting][/bugreporting]

[lj_raph]

There is no problem of corruption, in the current release startup values specified in the fixture profile have priority. (fixture default values were applied after the startup values)
There's a patch available on request which will fix the priority issue.

And once again: TRY NOT TO POST BUGS ON THE FORUM, SEND THEM DIRECTLY TO ME SO THEY GET FIXED ASAP !!!

Raph

[GaryBonaducci]

And once again: TRY NOT TO POST BUGS ON THE FORUM, SEND THEM DIRECTLY TO ME SO THEY GET FIXED ASAP !!!

Sorry, Raph.... I should know better! I submitted a Bug Report.