Vixen 3 Preview Bet...
 
Notifications
Clear all

Vixen 3 Preview Beta

64 Posts
13 Users
0 Reactions
27.8 K Views
derekbackus
Posts: 565
Topic starter
(@derekbackus)
Honorable Member
Joined: 15 years ago
MarkL wrote:Now if I select the preview, and try to "Configure Preview" a box pops up with "Unhandled exception has occurred in your application." I can post the details of the exception text if you think it would be useful.

Sure, I'd like to see it. You can post it here or PM me. I'm looking at the exception information you PMed me now and have a new DLL I'd like you to try. There's been some changes to this so hopefully it'll work for you. I'm hoping we've not added any dependencies in the last few weeks that would prevent the DLL from loading.

I'd like you to try it. If all works, great, just let me know. If not, please look at the System/Logs/Debug and send me the last few sections that start with: ----------------- Preview:VixenPreviewControl Init ---------------------

On another note. If you are not having a current issue with the preview, I would not recommend you download this. We will hopefully, in a couple days, have a new Vixen build (Bleeding Edge) that you can try. There are some new features, some performance enhancements and a new effect that you pixel lovers will not believe!


Reply
Posts: 150
(@markl)
Estimable Member
Joined: 19 years ago

No luck with the new dll. Here's the contents of the debug log.

[6/11/2013 9:39:51 PM]: ----------------- Preview:VixenPreviewControl Init ---------------------
[6/11/2013 9:39:51 PM]: Preview:Resize
[6/11/2013 9:39:51 PM]: Preview:AllocateGraphicsBuffer
[6/11/2013 9:39:51 PM]: Preview:Resize
[6/11/2013 9:39:51 PM]: Preview:AllocateGraphicsBuffer


Reply
derekbackus
Posts: 565
Topic starter
(@derekbackus)
Honorable Member
Joined: 15 years ago
MarkL wrote:No luck with the new dll. Here's the contents of the debug log.

[6/11/2013 9:39:51 PM]: ----------------- Preview:VixenPreviewControl Init ---------------------
[6/11/2013 9:39:51 PM]: Preview:Resize
[6/11/2013 9:39:51 PM]: Preview:AllocateGraphicsBuffer
[6/11/2013 9:39:51 PM]: Preview:Resize
[6/11/2013 9:39:51 PM]: Preview:AllocateGraphicsBuffer

Oh... The next line in my code is:

if (context != null)

which... it shouldn't be null... so the background is never getting allocated.


Reply
derekbackus
Posts: 565
Topic starter
(@derekbackus)
Honorable Member
Joined: 15 years ago
MarkL wrote:No luck with the new dll. Here's the contents of the debug log.

[6/11/2013 9:39:51 PM]: ----------------- Preview:VixenPreviewControl Init ---------------------
[6/11/2013 9:39:51 PM]: Preview:Resize
[6/11/2013 9:39:51 PM]: Preview:AllocateGraphicsBuffer
[6/11/2013 9:39:51 PM]: Preview:Resize
[6/11/2013 9:39:51 PM]: Preview:AllocateGraphicsBuffer

Ok, I think this helps... Try the attached and let me know.


Reply
Posts: 150
(@markl)
Estimable Member
Joined: 19 years ago

Nope. More info from the debug log below.

I'm not sure what the significance of stopping the execution engine is. If I stop it, I can add the preview without the crash. However, attempting to configure it results in the unhandled exception error.

[6/12/2013 9:32:35 PM]: ----------------- Preview:VixenPreviewControl Init ---------------------
[6/12/2013 9:32:35 PM]: Preview:Resize
[6/12/2013 9:32:35 PM]: Preview:AllocateGraphicsBuffer
[6/12/2013 9:32:35 PM]: - context != null
[6/12/2013 9:32:35 PM]: - context.MaximumBuffer.Width:225 context.MaximumBuffer.Height: 96
[6/12/2013 9:32:35 PM]: - this.Width387 this.Height: 295
[6/12/2013 9:32:35 PM]: Preview:InitializeGraphics
[6/12/2013 9:32:35 PM]: Preview:AllocateGraphicsBuffer
[6/12/2013 9:32:35 PM]: - context != null
[6/12/2013 9:32:35 PM]: - context.MaximumBuffer.Width:388 context.MaximumBuffer.Height: 296
[6/12/2013 9:32:35 PM]: - New bufferedGraphcis allocated
[6/12/2013 9:32:35 PM]: Preview:Resize
[6/12/2013 9:32:35 PM]: Preview:AllocateGraphicsBuffer
[6/12/2013 9:32:35 PM]: - context != null
[6/12/2013 9:32:35 PM]: - context.MaximumBuffer.Width:388 context.MaximumBuffer.Height: 296
[6/12/2013 9:32:35 PM]: - this.Width878 this.Height: 416
[6/12/2013 9:32:35 PM]: - Existing bufferedGraphics allocated


Reply
derekbackus
Posts: 565
Topic starter
(@derekbackus)
Honorable Member
Joined: 15 years ago
MarkL wrote:I'm not sure what the significance of stopping the execution engine is. If I stop it, I can add the preview without the crash. However, attempting to configure it results in the unhandled exception error.

When you first add it, is it enabled? Does it crash when you enable it too or just when you try to edit it?

This is very frustrating... I really want it to work on your system.


Reply
Posts: 150
(@markl)
Estimable Member
Joined: 19 years ago
derekbackus wrote:When you first add it, is it enabled? Does it crash when you enable it too or just when you try to edit it?

When you say "is it enabled", I'm not sure what exactly you mean by enabled. Let me try better to explain what I've tried. Hopefully my terminology matches with yours, or is at least comprehensible.

When I start Vixen, the execution engine is running. If I try to add the new preview (and by add I mean clicking on "Configure Previews" from the main screen and then "Add New Preview" on the next) it will crash.

If I stop the execution engine, I can add the preview without it crashing.

Once I have it added, if I click on the checkbox (is that what you mean by it being enabled?) nothing happens.

Once it's added, if I click on "Configure Preview" from the Previews Configuration window, I get the unhandled exception error.

derekbackus wrote:This is very frustrating... I really want it to work on your system.

I appreciate you taking the time to work with me. I just wish I wasn't the only one seeing this. It's starting to feel more and more like the problem is 100% on my end. FWIW, I did put Vixen3 and the new preview on an old WinXP computer and it came up fine. Unfortunately that computer is so old and slow (installation took the better part of 20 minutes) that I can't really use it for this.


Reply
dlovely
Posts: 3167
(@dlovely)
Famed Member
Joined: 17 years ago
MarkL wrote:When you say "is it enabled", I'm not sure what exactly you mean by enabled. Let me try better to explain what I've tried. Hopefully my terminology matches with yours, or is at least comprehensible.

When I start Vixen, the execution engine is running. If I try to add the new preview (and by add I mean clicking on "Configure Previews" from the main screen and then "Add New Preview" on the next) it will crash.

If I stop the execution engine, I can add the preview without it crashing.

Once I have it added, if I click on the checkbox (is that what you mean by it being enabled?) nothing happens.

Once it's added, if I click on "Configure Preview" from the Previews Configuration window, I get the unhandled exception error.

I appreciate you taking the time to work with me. I just wish I wasn't the only one seeing this. It's starting to feel more and more like the problem is 100% on my end. FWIW, I did put Vixen3 and the new preview on an old WinXP computer and it came up fine. Unfortunately that computer is so old and slow (installation took the better part of 20 minutes) that I can't really use it for this.

I am getting the exact same error, I started with version 3.0.6.16, then tried a few in between and lastly version 3.0.6 and none would let me add a preview. My process was "Configure Previews" then "Add New Preview" Select "Vixen Display Preview" and after hitting OK Vixen will crash within 5 seconds. The Debug log shows the following:

[7/16/2013 12:27:56 PM]: Preview:Resize
[7/16/2013 12:27:56 PM]: Preview:Resize

After reading this post I turned off the Execution Engine and can add the preview without a crash, but when I click "Configure Preview" now I get the following unhandled exception:

*********** Exception Text ***********
System.NullReferenceException: Object reference not set to an instance of an object.
at VixenModules.Preview.VixenPreview.VixenPreviewSetup3.VixenPreviewSetup3_Resize(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnResize(EventArgs e)
at System.Windows.Forms.Control.OnSizeChanged(EventArgs e)
at System.Windows.Forms.Control.UpdateBounds(Int32 x, Int32 y, Int32 width, Int32 height, Int32 clientWidth, Int32 clientHeight)
at System.Windows.Forms.Control.UpdateBounds(Int32 x, Int32 y, Int32 width, Int32 height)
at System.Windows.Forms.Control.SetBoundsCore(Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified)
at System.Windows.Forms.Form.SetBoundsCore(Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified)
at System.Windows.Forms.Control.ScaleControl(SizeF factor, BoundsSpecified specified)
at System.Windows.Forms.ScrollableControl.ScaleControl(SizeF factor, BoundsSpecified specified)
at System.Windows.Forms.Form.ScaleControl(SizeF factor, BoundsSpecified specified)
at System.Windows.Forms.Control.ScaleControl(SizeF includedFactor, SizeF excludedFactor, Control requestingControl)
at System.Windows.Forms.ContainerControl.Scale(SizeF includedFactor, SizeF excludedFactor, Control requestingControl)
at System.Windows.Forms.ContainerControl.PerformAutoScale(Boolean includedBounds, Boolean excludedBounds)
at System.Windows.Forms.ContainerControl.OnLayoutResuming(Boolean performLayout)
at System.Windows.Forms.Control.ResumeLayout(Boolean performLayout)
at VixenModules.Preview.VixenPreview.VixenPreviewSetup3.InitializeComponent()
at VixenModules.Preview.VixenPreview.VixenPreviewModuleInstance.Setup()
at VixenApplication.ConfigPreviews.buttonConfigureController_Click(Object sender, EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I noted that when I restart Vixen and leave the execution engine running, when I click the check box it instantly crashes Vixen.

Also I am guilty of not reading every post in this thread on things to try ect, Mostly just confirming that Mark is not the only one seeing this. This was a fresh install of Vixen3 with clean data directories each time.


Reply
Posts: 853
(@roterhead)
Prominent Member
Joined: 15 years ago

I've seen this exact situation. I've had no luck getting vixen to show the preview screen...


Reply
Posts: 899
(@sallz0r)
Prominent Member
Joined: 18 years ago

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?


Reply
Page 4 / 7
Share: