Talthos wrote:
Their drivers don't like something that dgVoodoo does that's why your driver crashes.
Which driver are you using? I tested with and am currently using Catalyst 15.10 Beta. (I'm not touching the Crimson drivers again for the time being)
I'm using nVidia, though I have a low-end AMD HD6450 for testing occassionally. But this AMD thing is an old issue, see:
Re: dgVoodoo 2 for DirectX 11
I even reported the bug to AMD twice, along with a simple repro app attached (got no any respond and saw no progression later, of course).
Since dynamic shader compiling introduced in 2.5 doesn't solve the problem (as opposed to my hopes), the only way seems to be getting such an AMD card in question, checking the problem myself and finding a workaround for the driver bug (ahh, how I hate workarounding bad codes...), if possible.
Talthos wrote:Well, D3D hw mode checks out alright. Now, for the next problem I'm just noticing: The inability for dgvoodoo to respect my 'Mai […]
Show full quote
Well, D3D hw mode checks out alright. Now, for the next problem I'm just noticing: The inability for dgvoodoo to respect my 'Maintain Aspect Ratio' setting in the Catalyst Control Center. And yes, I made sure that dgvoodoo's scaling mode is set to 'Unspecified' during all testing.
Quick searches only seem to show solutions for NVIDIA cards. Which leaves me rather stuck, seeing as I'm using an AMD card with Catalyst drivers.
I've tested with 'Enable GPU Scaling' both enabled and disabled, with the same result: dgvoodoo still forces the game to scale the entire image to the full size, which introduces that awful 'stretching' effect.
Any suggestions on possible fixes?
AMD has no 'override application scaling setting' on its control panel, so there is no soultion for the current dgVoodoo version, I think.
I'm going to address somehow this issue in the next version because it all is a disaster, a solution is sorely needed.