New video card problems

[BobinWV]

Lost the DVI channel on my on board video.  Machine is an HP envy 700-430qe
Replaced with a NVIDIA card MSI HD 6450.  Xlights crashes when I try anything.(2016-39) Set openGL to 1.0 and it still crashes.  No crash report generated.
Replaced with a Geforce GT 730...same problem.

Suggestions please-
BobinWV

[Gilrock]

You shouldn't need to use 1.0 for an nVidia card so I'd put that back to auto.  Can you do a Tools-> Package Log Files?  Did you make sure to download/install the latest nVidia drivers?

[BobinWV]

Followed your suggestions; however, problem still there
openGL set to auto
drivers are up to date
log file attached

BobinWV

[Gilrock]

That's crashing really early like probably during the Layout panel constructor.  I'm afraid that will be hard to troubleshoot.  We would probably have to give you special builds with extra logging info.  I'm not going to be much help till next Sunday.  Maybe Keith will be available to help.

[Gilrock]

Actually my comments were for the first couple crashes at the top of the file but that was July 1st.  When I looked near the bottom of the file you are getting further.  Can you rename your show directory and then startup so that it will start fresh?  If that works then we know something is messed up in the show directory files.

[BobinWV]

Created a new show directory and everything works as it should

BobinWV

[BobinWV]

Tried original show directory and generated a debug report.  Don't know if it is related to openGL problem.

BobinWV

[keithsw1112]

I will take a look tonight. There are some really odd looking log entries there. I was not expecting to see the same thread crashing over and over again.

[dkulp]

You have two timing elements in the sequence with the same name.   That's causing a problem.    We definitely need better error handling around that.   

[Gilrock]

I thought there was protection to prevent the same timing element name but probably not a way to handle it if someone manually edited the file.  I'd like to know how it go into that state in case we missed somewhere to prevent it.

[keithsw1111]

In v41 I implemented code to:

- detect the duplicate timing track.
- warn the user about the duplicate
- log the fact the duplicate was found
- not load the duplicate
- load everything else

This doesnt solve the problem ... it may not be the first copy you want to keep ... but at least it handles it gracefully and loads what it can.