Call of Duty 4 fails when creating the `D3DFMT_R32F` render target about dxwrapper HOT 2 OPEN

it's here any possible to modify the HRESULT of that call to SUCCESS

Technically this can be done, but this will most likely just crash the game or have no effect. The fix for this is a bit more complex.

or much better converting it into equally fix-point type instruction?

I don't think there is an equivalent fixed point substitute. However, since this is most likely used for shadowing or for lighting, the best alternative format may be D3DFMT_G16R16. I could simply just convert this one API call to use format D3DFMT_G16R16, but it would likely require more work than just that. I really need to test it with this game to see what other functions are used by this texture and how these functions can be converted to use the new texture format.

I don't really have time to look at it right now. But I will take a look at it when I get time. As @mirh, suggested this is most likely something I would add to the dxwrapper project.

from dxwrapper.

Tbh I would wholeheartedly recommend to switch to linux on such hardware (more specifically manjaro32, I don't know other 32 bit distros with hope). Wine should take care of games, and where it would be bugged or not performant enough, I'd be pretty sure some developer can get behind helping you with anything.

But by all means.. This is really the super dope kind of stuff that I always expected dxwrapper
to be able to uniquely fixing.

from dxwrapper.