sallz0r wrote:Hmm... that's interesting. Are you guys that are seeing the problem able to zip up your entire Vixen 3 data directory (in 'My Documents') and either post it here or make a bug in the bugtracker and attach it to that?Hopefully we can reproduce it from that info. Unfortunately I don't think any developers have seen it yet, so can't quite figure out what's happening. 🙁
Also, what versions are you using, and how have you installed them?
I started with version 3.0.6.16, then tried a few in between and lastly version 3.0.6. Each time I used the installing EXE after un-installing the old version and deleting the Vixen 3 directory.
I did not really find any information on exactly how to get started or what needs to be done first but my steps are pretty much as follows:
- Configured 10 channels in "Configure Elements & Groups"
- Configured an E1.31 Controller in "Configure Controllers" told it to use 10 channels, unicast to localhost (Tried multicast and other options all the same crash in preview)
- Configured the patching in "Configure Filters & Patching" no filters used as I don't know what they do or how they work
- Tried to configure a preview in "Configure Previews" and once the name dialog returns Vixen will crash a second or two later
As far as a bit of testing, I have three monitors on this laptop, disabled two and still have the same issue. Running Windows 7 with an NVIDIA GTX 660M currently running driver version 296.01 but in progress of updating to 320.49. I will report back after I update.
Attached is the Vixen 3 directory.
dlovely wrote:Running Windows 7 with an NVIDIA GTX 660M currently running driver version 296.01 but in progress of updating to 320.49. I will report back after I update.
Using the latest driver results in the same crash.
So I must be really unlucky, or the steps I posted I use are not the correct ones to be using. I just tested a fresh install of Vixen 3 on my MacBook Pro running a fresh install of Win7 in VMWare and get the same exact crash with version 3.0.6.18. Is there a document or post that details everything you need to do when first starting out with Vixen 3 to get the preview working?
Alright I am going to have to go find some more information on what these properties are in the elements and group configuration screen. I went and added a 'Location' property to every item (For some reason selecting all and adding a property ONLY adds it to the last item selected) and then went and added a preview and it showed a black screen looking like it is going to work now. Removing 'Location' from every element/group allows me to create a new preview without a crash, so it seems you need to add a 'Location' then everything will work. I cannot find any documentation on what these properties do and do I need to add all three to every item in the list? If so a functional select all would be great!
I didn't get a chance to look into it last night, sorry -- but I'll try and reproduce it tonight to see what the cause is. (Unfortunately the autobuilds can often be not stable at all, since they're just triggered by code checkins -- so there's often many things that are broken during development until we make an 'official' release!)
sallz0r wrote:I didn't get a chance to look into it last night, sorry -- but I'll try and reproduce it tonight to see what the cause is. (Unfortunately the autobuilds can often be not stable at all, since they're just triggered by code checkins -- so there's often many things that are broken during development until we make an 'official' release!)
All my testing also included build 3.0.6 for that very reason. I only went on to test the 3.0.6.X builds to see if it might have been fixed.
Gotcha. Hmm, that's a bit more worrying then. 🙁 Not to worry, we'll find what's happening. 🙂
Just to confirm -- it's the same problem every time, throwing an exception with the following error? (as posted earlier in the thread):
System.NullReferenceException: Object reference not set to an instance of an object.
at VixenModules.Preview.VixenPreview.VixenPreviewSetu p3.VixenPreviewSetup3_Resize(Object sender, EventArgs e)
sallz0r wrote:Gotcha. Hmm, that's a bit more worrying then. 🙁 Not to worry, we'll find what's happening. 🙂Just to confirm -- it's the same problem every time, throwing an exception with the following error? (as posted earlier in the thread):
System.NullReferenceException: Object reference not set to an instance of an object.
at VixenModules.Preview.VixenPreview.VixenPreviewSetu p3.VixenPreviewSetup3_Resize(Object sender, EventArgs e)
Not really, the issue I see most is two lines in the Debug log about preview:resize (see my earlier post) and then a hard crash(windows says it stopped responding), but when I disable the execution engine the problem changes and I get that exception.
OK, gotcha. Thanks for that clarification.
While that fix of adding Location to the elements worked on my other computer, its not working on this one for versions 3.0.6 or 3.0.6.18. So something is strange.
