home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
MePo 1.6 Final Crash on D3D.GetCapabilities()
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Bernard" data-source="post: 1052740" data-attributes="member: 120430"><p>Your welcome! It's always a pleasure to contribute to an Open Source project! In the end that is how the project succeeds, by everyone working together!</p><p></p><p>Since I have a very uncommon problem with my video drivers, is there anyway that I can help you to improve the error handling code so to give someone a better response than "Object reference not set to an instance"? And also maybe that loop you created should have a timeout, or retry count so that it does not run indefinitely. </p><p></p><p>My thinking is that maybe we can improve the error messages, so that if anyone ever gets this same issue (it can potentially be any Direct3D related issue, that cause it to not work... i'm not sure how many cases would cause this "null reference exception") the system immediately points it out, rather than showing the same "Loading DirectX..." message indefinitely and expecting the end-user to read the logs to get a hint that he has something wrong. We could say "<strong>Fatal Error: Direct3D could not load. Please try reinstalling your display drivers, or DirectX</strong>." as an example. </p><p></p><p>I'm also a C# developer, so I don't have a problem reading and contributing code, but I need an "inside man" to vet the code and help it get accepted... So from my side I will try my best to figure out where the "null object" lies in the code, and then I can try to research the Direct3D libraries to determine "why" it would be "null". And then update the code as I think, but then I will need your help to verify that the code is acceptable?</p><p></p><p>Would you be willing to help, and would you be able to point me to the source that you worked on, since the "trunk" is now outdated? I'm also more than willing to just debug the issue and write to you what is "null" and "why" and you can then write the code to improve on the error reporting? This DOES mean that you have to do more coding work...</p><p></p><p>We can continue to work on your WIP thread referenced above just so that there is not 2 threads on this topic of D3D updates.</p><p></p><p>I will also need to get Git going as I'm still on SVN.</p></blockquote><p></p>
[QUOTE="Bernard, post: 1052740, member: 120430"] Your welcome! It's always a pleasure to contribute to an Open Source project! In the end that is how the project succeeds, by everyone working together! Since I have a very uncommon problem with my video drivers, is there anyway that I can help you to improve the error handling code so to give someone a better response than "Object reference not set to an instance"? And also maybe that loop you created should have a timeout, or retry count so that it does not run indefinitely. My thinking is that maybe we can improve the error messages, so that if anyone ever gets this same issue (it can potentially be any Direct3D related issue, that cause it to not work... i'm not sure how many cases would cause this "null reference exception") the system immediately points it out, rather than showing the same "Loading DirectX..." message indefinitely and expecting the end-user to read the logs to get a hint that he has something wrong. We could say "[B]Fatal Error: Direct3D could not load. Please try reinstalling your display drivers, or DirectX[/B]." as an example. I'm also a C# developer, so I don't have a problem reading and contributing code, but I need an "inside man" to vet the code and help it get accepted... So from my side I will try my best to figure out where the "null object" lies in the code, and then I can try to research the Direct3D libraries to determine "why" it would be "null". And then update the code as I think, but then I will need your help to verify that the code is acceptable? Would you be willing to help, and would you be able to point me to the source that you worked on, since the "trunk" is now outdated? I'm also more than willing to just debug the issue and write to you what is "null" and "why" and you can then write the code to improve on the error reporting? This DOES mean that you have to do more coding work... We can continue to work on your WIP thread referenced above just so that there is not 2 threads on this topic of D3D updates. I will also need to get Git going as I'm still on SVN. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
MePo 1.6 Final Crash on D3D.GetCapabilities()
Contact us
RSS
Top
Bottom