Bug Report Screen remains blank

[lordxbrosiedon]

I Have done all the suggested fixes to make this work from the faq but it remains blank then an error about my gpu pops up what can I do to fix this

 

[Lain]

Hey! First, try using the "Disable Direct3D Compatibility" setting in advanced options. If that doesn't work, come back and tell me what GPU you are using.

Also, intel GPUs currently are not working correctly because intel is apparently horrible at making any fully compliant direct3d drivers.

 

[lordxbrosiedon]

it did not work and im using a nvidia GeForce GT 540M

 

[lordxbrosiedon]

it suddenly started working but not my webcam

 

[Lain]

I'm glad you got it working, does your webcam produce a red output, or black output? Also, are you using the 32bit (installer) version? or the 64bit version?

 

[lordxbrosiedon]

64 and its a red output

 

[Lain]

I will have to make a diagnostic application so I can get more information about your webcam that way. I hope you don't mind waiting a bit. In the mean time, could you show me the specific warning messages you get in your logfile with it?

 

[Lain]

Okay, I made the diagnostic app. Please run this and paste what it says for me, if you would please.

http://obsproject.com/temp/DShowDiagnostic.zip

 

[lordxbrosiedon]

this is what the app gave me

Device: CyberLink Webcam Splitter
type: YUY2, usingFourCC: false, res: 320x240 - 320x240, fps: 5-30
type: YUY2, usingFourCC: false, res: 640x480 - 640x480, fps: 5-30
type: YUY2, usingFourCC: false, res: 160x120 - 160x120, fps: 5-30
type: YUY2, usingFourCC: false, res: 800x600 - 800x600, fps: 5-15
type: YUY2, usingFourCC: false, res: 1280x960 - 1280x960, fps: 5-5
type: YUY2, usingFourCC: false, res: 1600x1200 - 1600x1200, fps: 5-5
type: RGB24, usingFourCC: false, res: 320x240 - 320x240, fps: 5-30
type: RGB24, usingFourCC: false, res: 640x480 - 640x480, fps: 5-30
type: RGB24, usingFourCC: false, res: 160x120 - 160x120, fps: 5-30
type: RGB24, usingFourCC: false, res: 800x600 - 800x600, fps: 5-15
type: RGB24, usingFourCC: false, res: 1280x960 - 1280x960, fps: 5-5
type: RGB24, usingFourCC: false, res: 1600x1200 - 1600x1200, fps: 5-5

Device: WebCam SCB-1100N
type: YUY2, usingFourCC: false, res: 640x480 - 640x480, fps: 5-30
type: YUY2, usingFourCC: false, res: 160x120 - 160x120, fps: 5-30
type: YUY2, usingFourCC: false, res: 176x144 - 176x144, fps: 5-30
type: YUY2, usingFourCC: false, res: 320x240 - 320x240, fps: 5-30
type: YUY2, usingFourCC: false, res: 352x288 - 352x288, fps: 5-30
type: YUY2, usingFourCC: false, res: 800x600 - 800x600, fps: 5-15
type: YUY2, usingFourCC: false, res: 1280x720 - 1280x720, fps: 5-7.5
type: YUY2, usingFourCC: false, res: 1280x1024 - 1280x1024, fps: 5-7.5
type: MJPG, usingFourCC: false, res: 640x480 - 640x480, fps: 5-30
type: MJPG, usingFourCC: false, res: 160x120 - 160x120, fps: 5-30
type: MJPG, usingFourCC: false, res: 176x144 - 176x144, fps: 5-30
type: MJPG, usingFourCC: false, res: 320x240 - 320x240, fps: 5-30
type: MJPG, usingFourCC: false, res: 352x288 - 352x288, fps: 5-30
type: MJPG, usingFourCC: false, res: 800x600 - 800x600, fps: 5-30
type: MJPG, usingFourCC: false, res: 1280x720 - 1280x720, fps: 5-30
type: MJPG, usingFourCC: false, res: 1280x1024 - 1280x1024, fps: 5-30

Device: Dxtory Video 1
type: RGB32, usingFourCC: false, res: 640x480 - 640x480, fps: 30-30

Device: Dxtory Video 2
type: RGB32, usingFourCC: false, res: 640x480 - 640x480, fps: 30-30

Device: Dxtory Video 3
type: RGB32, usingFourCC: false, res: 640x480 - 640x480, fps: 30-30

Device: Dxtory Video 4
type: RGB32, usingFourCC: false, res: 640x480 - 640x480, fps: 30-30

Device: XSplitBroadcaster
type: RGB32, usingFourCC: false, res: 1x1 - 320x240, fps: 1-255.004
type: YUY2, usingFourCC: false, res: 1x1 - 320x240, fps: 1-255.004

 

[Lain]

First of all, don't run xsplit while running my app if possible. If will often cause conflicts and cause the red source error with devices. WebCam SCB-1100N? If so then yea, I see the problem with your webcam now. Let me tweak some code and release a minor update soon, then your webcam should be fixed. Sorry, this is indeed my fault.

 

[lordxbrosiedon]

i was not running at the time it just picked it up but yeah and cool thank you

 

[Lain]

Your issue should be fixed in the latest daily builds and will be fixed in the next major release.