I've been using the internal web server to actual lights an controller.
Works fine under Windows 7
Windows 10 results in internal server error once a selection(s) chosen.
What port are you using for vixen's web server? I ran into this a few days ago when I was testing something on a different machine. It turns out that win 10 machine had IIS running on it by default and I had to use a different port for vixen. All was happy after that.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
Nothing special - running the default 8888. I can get the web pages to display and was only when I selected sequences to run that I got the error.
Clean fresh install of 10, running I believe dev version 245 or 250 (whatever was current this past weekend).
Everything else is working absolutely great for me on this pc. I only use the webserver as a convenience to keep from running up a down basement steps as I'm testing pixels, props, and controllers
Are the sequences in question up to date? There's been at least two migrations lately. one with the 3.3 release, and we're testing another in a subsequent build. If you open it in the sequence editor, it'll prompt you to do the migration if necessary. Then you need to save it. The webserver can't do the sequence upgrade migrations that are needed to bring it to the current version so it's playable.
Sequences are up to date. I'll revisit this again in the next day or two and see if I can be a bit more definite. Right now I'm chalking it up to the Windows 10 install perhaps.
I did try build 253 on a Windows 7 box and when a sequence was selected to play the sequence upgrade process and the associated dialogs come up on the host pc, answered the prompts on host for upgrade to take place and sequence plays.
