New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D3DDevice_CreatePixelShader issue #794
Comments
According to some feedback, "it's not only Cold Fear and Dino Crisis 3 that have this problem, Panzer Dragoon Orta and Jet Set Radio Future also have this (actually putting the CreatePixelShader = 0 in the .ini of JSRF fix the tag problem and make the game fully playable (no more glitch, other than the character legs, everything else look fine), PDO have the same problem after pushing the start button in the mission, everything become white and impossible to play, modifying this line again, fix this issue." |
When you say to insert "CreatePixelShader = 0" in the .ini of JSRF, where does one find the .ini? Ive tried looking through the files of JSRF but couldn't find it. Thank you. |
You'll find it in the "%appdata%/Cxbx-Reloaded/HLECache" folder |
The fix for this issue would be to stop patching CreatePixelShader completely, and instead move shader conversion to the SetPixelShader functions instead. (Or better yet, at draw time) |
All PixelShader related patches are gone, except for SetPixelShader, which uses a trampoline. Commit 4637f4d resolves this issue. |
At least two games suffer from an issue with CreatePixelShader;
Cold Fear - see Cxbx-Reloaded/game-compatibility#434
and Dino Crisis 3 : see Cxbx-Reloaded/game-compatibility#114 (comment)
Cold Fear crashes due to expecting the HANDLE returned by CreatePixelShader to be a pointer to valid memory, containing the pixel shader definition. Currently, our implementation of CreatePixelShader returns a handle to the host pixel shader, which is not correct behavior.
Cold Fear crashes while executing the following code (located at 0x0004F0F0 within the .text segment)
The text was updated successfully, but these errors were encountered: