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
HTPC Projects
Software
Operating System
Windows 7 & half fullscreen
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="Scythe42" data-source="post: 894021" data-attributes="member: 95833"><p>Some stuff is hard to solve if no dev can reproduce it on demand or make a connection to the code. Not every dev knows all the code. /me and tsreader? No clue...</p><p> </p><p>Identified the root cause more or less by chance and then found a way to prevent it as well as digging down more D3D issues until finally identified the root causes (yep, plural in this case). Very, very ancient parts of the code in relation to D3D no one has touched in years and no active dev attached to this part of the code.</p><p> </p><p>From general ACPI levels, over Windows messages, down to D3D and various C# parts. Now that I know what it was (patch will have complete description) it was an easy one to identify. But that's usually the case for all post mortem discussions.</p><p> </p><p>But again, has to go through Area 51 as I cannot reproduce the issue at all it there might be additional regressions for people who can reproduce it that are now left overs of the main issue and all it subparts.</p></blockquote><p></p>
[QUOTE="Scythe42, post: 894021, member: 95833"] Some stuff is hard to solve if no dev can reproduce it on demand or make a connection to the code. Not every dev knows all the code. /me and tsreader? No clue... Identified the root cause more or less by chance and then found a way to prevent it as well as digging down more D3D issues until finally identified the root causes (yep, plural in this case). Very, very ancient parts of the code in relation to D3D no one has touched in years and no active dev attached to this part of the code. From general ACPI levels, over Windows messages, down to D3D and various C# parts. Now that I know what it was (patch will have complete description) it was an easy one to identify. But that's usually the case for all post mortem discussions. But again, has to go through Area 51 as I cannot reproduce the issue at all it there might be additional regressions for people who can reproduce it that are now left overs of the main issue and all it subparts. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Software
Operating System
Windows 7 & half fullscreen
Contact us
RSS
Top
Bottom