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
Quality Assurance
Bugreports
Archive
MediaPortal Invisible on Resume from Hibernate
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="Sebastiii" data-source="post: 1197485" data-attributes="member: 60104"><p>Thanks <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> </p><p></p><p>That could be a nice idea for ex when with switch from full-screen to windowed or reverse, this will avoid to call reset which is slow <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /></p><p>But i think it will not correct the issue when the driver is recovered from windows because when it happen, it's like the GPU card doesn't exist anymore.</p><p></p><p>From my POV (while debugging) The manager (Microsoft.DirectX.Direct3D.Manager.Adapters) seems to be filled with all correct information when the windows form is created but when the driver crash and recovered (that seems to happen for [USER=49299]@rmeredit[/USER]) the Microsoft.DirectX.Direct3D.Manager.Adapters along with Screen.... call are filled with 0 value for the new recovered GPU card and i have try different thing the only way was to restart MP (because a new windows form is created).</p><p></p><p>So effectively , we missed surely something because dvbviewer handle it correctly and i think it works with DX9 but Kodi for ex directly crash.</p><p></p><p>Yes me too backbuffer stuff and co and not easy for me but still it will surely possible to make it works, maybe we need to test other open source C# and find one that can handle it and understand why lol.</p></blockquote><p></p>
[QUOTE="Sebastiii, post: 1197485, member: 60104"] Thanks :) That could be a nice idea for ex when with switch from full-screen to windowed or reverse, this will avoid to call reset which is slow :P But i think it will not correct the issue when the driver is recovered from windows because when it happen, it's like the GPU card doesn't exist anymore. From my POV (while debugging) The manager (Microsoft.DirectX.Direct3D.Manager.Adapters) seems to be filled with all correct information when the windows form is created but when the driver crash and recovered (that seems to happen for [USER=49299]@rmeredit[/USER]) the Microsoft.DirectX.Direct3D.Manager.Adapters along with Screen.... call are filled with 0 value for the new recovered GPU card and i have try different thing the only way was to restart MP (because a new windows form is created). So effectively , we missed surely something because dvbviewer handle it correctly and i think it works with DX9 but Kodi for ex directly crash. Yes me too backbuffer stuff and co and not easy for me but still it will surely possible to make it works, maybe we need to test other open source C# and find one that can handle it and understand why lol. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
MediaPortal Invisible on Resume from Hibernate
Contact us
RSS
Top
Bottom