DDraw Fix by Aqrit - Page 5

On January 14 2016 19:49 Endymion wrote:
does ddraw work on linux or would i need wine

On January 30 2016 12:29 f10eqq wrote:
I think I found a bug:
Supply count in replays turn into really long floating point numbers and there's no way to turn it off that I can find.

Also, I wasn't able to use BWAPI with this dll file in my Starcraft folder- it would kind of suck if I had to swap dll files every time I wanted to use the Replay++ plugin.

On January 30 2016 15:23 f10eqq wrote:
It's part of shitty plugin right? Does no one else see supply like that? o.O

On January 31 2016 02:48 aqrit wrote:
The FPU precision state must have indavertently gotten changed by ddraw.dll; single-precision round-to-nearest vs double-precision mode.

The Replay++ plugin looks like it draws all over the screen. It probably calls some ddraw functions that aren't yet implemented.

In the foreign plugin code, in "display.cpp" in the code

hr = d3d->CreateDevice( D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hwnd,
D3DCREATE_NOWINDOWCHANGES | D3DCREATE_HARDWARE_VERTEXPROCESSING | D3DCREATE_PUREDEVICE,
&d3dpp, &d3ddev );

add the flag "D3DCREATE_FPU_PRESERVE" so that the code is:

hr = d3d->CreateDevice( D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hwnd,
D3DCREATE_NOWINDOWCHANGES | D3DCREATE_HARDWARE_VERTEXPROCESSING | D3DCREATE_PUREDEVICE | D3DCREATE_FPU_PRESERVE,
&d3dpp, &d3ddev );

If you leave out this code, Direct 3D changes the precision used by the FPU for your process and you will see less precise values. The alternative is to use explicit formating when displaying floating point values.

See also http://blogs.msdn.com/b/tmiller/archive/2004/06/01/145596.aspx

On February 04 2016 15:40 WinterViewbot420 wrote:
Found a bug, boss!

On February 05 2016 03:18 xboi209 wrote:

Are you on Windows 7 and did this occur after alt+tabbing?

On February 05 2016 05:27 LaStScan wrote:

I thought I showed you this alt tab bug 3 weeks ago on skype?