Talk:SDK Installation: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
I ran across the click-and-crash bug in Hammer after the last SDK update. I'm using Windows XP (Home) and have the December 2005 DX SDK installed. I demonstrated (to myself, in any case) that switching between debug and retail versions of the d3d dlls relieves the problem. The "Enable Shader Debugging" option had no apparent effect. FYI, this was not an easy one to find. | I ran across the click-and-crash bug in Hammer after the last SDK update. I'm using Windows XP (Home) and have the December 2005 DX SDK installed. I demonstrated (to myself, in any case) that switching between debug and retail versions of the d3d dlls relieves the problem. The "Enable Shader Debugging" option had no apparent effect. FYI, this was not an easy one to find. | ||
I added the bug here because something like this must apparently be verified before being added to the Known Issues page. -- [[user:BJ|BJ]] | I made an addition to the Hammer FAQ page for this problem. | ||
I added the bug here because something like this must apparently be verified before being added to the Known Issues page. How does one get this "verified?" -- [[user:BJ|BJ]] | |||
Revision as of 13:31, 23 April 2006
I ran across the click-and-crash bug in Hammer after the last SDK update. I'm using Windows XP (Home) and have the December 2005 DX SDK installed. I demonstrated (to myself, in any case) that switching between debug and retail versions of the d3d dlls relieves the problem. The "Enable Shader Debugging" option had no apparent effect. FYI, this was not an easy one to find.
I made an addition to the Hammer FAQ page for this problem.
I added the bug here because something like this must apparently be verified before being added to the Known Issues page. How does one get this "verified?" -- BJ