Sean Meighan
Welcome => Latest xLights/Nutcracker software => Topic started by: needbrew on June 27, 2016, 05:22:21 PM
-
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.
-
FYI,
I re-installed version 37 and it launches fine.
-
Can you package logs using the menu item on the tools menu and upload them.
-
from version 37? I cant get 38 to launch at all
-
37 is fine. They are the same logs.
-
Here they are
-
Do you get a crash log as well?
-
Did you rename your show directory and restart v38?
-
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.
-
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.
-
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.
-
I'm just gonna blame it on all the new fancy autosave mess until someone can blame it on me...lol.
-
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.
-
Replace your rgbeffects file with this one.
-
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.
-
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.
Post us your rgb_effects file and we will fix it for you.
-
Since I was not able to access the program, I was not able to set the show directory.
I did, however, scan the complete drive (the system just has the one) for "rgb_effects" with no resulting entries.
I'm running a second scan using the whole name, "rgb_effects.xml".
-
It's in your show directory
-
I don't have a show directory. Never got that far. This is now a clean install.
Where would the show directory be as default?
-
So you've never run another version of xlights on that computer except v38?
Also you got the filename wrong...it's xlights_rgbeffects.xml.
-
Perplexed as it (version 38) used to work on this computer.
I don't have a show directory. Never got that far. This is now a clean install.
Where would the show directory be as default?
You're first statement says v38 used to work on that computer...that means you had a show directory. Uninstalling the program does not delete the show directory nor does it remove the registry entry that tells us where to look for your show directory. I don't know the exact registry path but its easy to find probably under LocalMachine, Software, xLights, and it will be a variable called "LastDir".
-
Just following instructions from post #15. "rgb_effects.xml"
This computer HAD version .38 on it. It was working. When it failed, I removed .38 using control panel.
Downloaded a new copy from the website and installed it.
Rescanning for the full name as I type this.
-
To the best of my ability, this one seems to be the latest in a directory. There are 14 more with the same date and time stamp - all in different "temp" directories.
-
It's the exact same problem.
If you edit that file and search/replace "Back_Gate" with either "Front_Gate", "The_Point", or "Main_Display" it will fix it.
Now can you describe what happened with the "Back_Gate" preview. Did you delete it?
-
Copied the xlights_rgbeffects.xml to a safe place and then removed it from the old show directory.
Started xlights.
The program came up. No layout (expected) but it did come up.
-
I had added it to the list of "previews" but had not added any models to it yet.
-
Ok I did a quick code inspection and I see the problem. I'm not updating the stored layout group when you delete a preview. Until you get the next release with a fix you can prevent the problem by making sure to make a preview selection in the combo drop down top middle of the screen because that latches the last selection. You only end up with this problem if you delete a preview and then save and exit without ever switching to another preview.
-
It was late. I was tired. And I didn't want to screw anything up. Go figure.
Thank you very much for tracking that one down.
-
I had added it to the list of "previews" but had not added any models to it yet.
Hmm so you don't think you deleted it. I'll have to try to reproduce it then. Maybe there are 2 ways to get into the situation.
But in any case no reason to blank your show directory out just edit the file like I said. The "storedLayoutGroup" name needs to match one of the names in the LayoutGroups section. A LayoutGroup is what I'm calling a preview.
-
:o There is a real good chance it was the "Back_Gate" that was deleted when I was trying to find out how to "clean up" unneeded previews. Like I said, tired, grumpy (happens on City Council nights) and... who knows what else.
-
So i uninstalled 37 and re-installed 38. I renamed my show directory and copied in the rbg_effects. Now I see it running in the task manager, but never see the app load. it is currently consuming 30% of my cpu even though it is not visible.
-
I've already put in a fix and added protection just in case someone manually alters the name or deletes an entry.
-
Just an FYI. After renaming the show directory and uninstalling and re-installing it still was running in the background and using 30% cpu. I went into the registry and deleted the xlights key and sub-keys under HKCU\Software\Xlights and then when it launched it asked for a show directory. I gave it a blank one and it loaded.
-
I've already put in a fix and added protection just in case someone manually alters the name or deletes an entry.
Gil, is that in the current downloadable, or will it be in the next version?
-
No you gotta wait till Sean builds another release to pick up my changes. Or get setup to Pull and build the code yourself.
-
Ill make a build tomorrow
Sent from my iPhone using Tapatalk
-
What disappoints me is that manually fixing this issue is as simple as opening up a text file and changing one word but yet I see some folks resorting to using a blank show directory and starting over or going backwards. To me this is easily corrected and easily avoided. Just don't delete any previews until after next release.
-
What disappoints me is that manually fixing this issue is as simple as opening up a text file and changing one word but yet I see some folks resorting to using a blank show directory and starting over or going backwards. To me this is easily corrected and easily avoided. Just don't delete any previews until after next release.
Gil, I have no problem doing either or both to avoid the problem. I can see where some are not at ease with changing things, even in an xml (plain text, easily edited). This software is intense! We are amazed at what you and the others have done, and keep doing. Many don't understand (for the most part) what can and cannot be done without breaking it.
I thank you for the amazing response to the problems that I have had. It is rare that I have any with it, yet when it shows up, it gets fixed.
Thanks to you and all that work on this project. You are great.