Xlights 38 wont start

[needbrew]

I installed the latest version on Windows 10 and it originally launched and I was able to use it.  Now when I start it, I see it in the windows task manager and then it just disappears.  No launch or crash.

[needbrew]

FYI,

I re-installed version 37 and it launches fine.

[keithsw1111]

Can you package logs using the menu item on the tools menu and upload them.

[needbrew]

from version 37?  I cant get 38 to launch at all

[keithsw1111]

37 is fine. They are the same logs.

[needbrew]

Here they are

[keithsw1111]

Do you get a crash log as well?

[Gilrock]

Did you rename your show directory and restart v38?

[needbrew]

I did not get a crash log as Version 38 would not start at all.  Just disappears.  I will try the rename of the show directory tonight when I get home. .  Just to be clear, I was running version 37 and it was working.  I installed version 38 and it worked once.  After I exited the app and tried to use it later, it would do nothing.  I looked in the task manager and could see an Xlights process starting, and then it would just disappear.  I uninstalled 38 and re-installed it and the result was the same.  I uninstalled it and installed 37 and it worked again.

Thanks for the assistance.

[Gilrock]

Hopefully you didn't save the xlights_rgbeffects.xml changes after starting it in v38 and then try to use it in v37.  You can't go backwards and forwards with this release.  It will screw up your show directory.

[algerdes]

I am having the same symptoms. 

Attempts to get it to work include removing xLights from the computer, downloaded a new copy from the site.  Installation appears to work.  Where it would normally start as part of the installation does not work.

Manually starting it does not work either.

It never gets to anywhere I could get logs of any kind.

Perplexed as it (version 38) used to work on this computer.  Now, dead in the water.
I checked Windows 10 update log.  No changes since the last time I worked on xLights.

[Gilrock]

I'm just gonna blame it on all the new fancy autosave mess until someone can blame it on me...lol.

[Gilrock]

By the way if you save your models file (xlights_rgbeffects.xml) in v38 and then go back and save it in v37 and then try to move forward to v38 again you can end up with duplicate tags because it will go through the upgrade process of the that file twice.  The duplicate tags can cause the xml parser to crash at startup.

[keithsw1111]

Replace your rgbeffects file with this one.

[Gilrock]

Needbrew: I'm not at home but just a quick look at what Keith changed and the problem is somehow where I save the last Layout you were looking at got out of sync.  I'm guessing you created a preview called "Testing" and then deleted it?  I've tested deleting previews and restarting so I'll need to figure out what you could have done to get that out of sync and I guess add a check so we don't try to load one that isn't defined.  I don't like putting protection code in for every possible thing that could go wrong I usually like to programmatically ensure that you can't get into a bad state.  But I guess I also need to protect against people manually altering the file.