PCSX2 in 3d playstation 2 emulator
  8 / 16    
Thanks for the donation and testing! You got my "d3dx.ini" from github, right? I think I had solved some shader override incompatibilities simce the latest fix release. And that's the main problem. Fixing a game sometimes means breaking another. But writing about it somewhere gives you the ability to switch settings quickly. About backwards cycling, it's currently impossible to have two different keys using the same possible settings that know what is the current point of the cycle. For example, imagine that you have numbers from 1 to 10. You press the increase convergence 4 times, so you're at 4 convergence. You press the decrease convergence twice, and you're at 9. You press increase, you're at 5. You press decrease, you're at 8. That's what would happen if I made a backwards convergence hotkey with the same settings. About windows 7: do the regex hotkeys work (meaning that you have proper 3D too), and not the shader overrides? If that's what happens, then for some reason the shader hashes are different. If you enable hunting mode and search and dump the vertex shaders (numpad 4, 5, and 6), the overlay will tell you if it's regex 1, 2, or 3. Write their hashes somewhere and then delete the dumped shaders. Then use the hashes in the vertex shader overrides (back up the ini for Windows 10 if you ise the same emulator folder), replacing the old hashes. You will have to do your own individual fixes. With 3Dmigoto you have more tools than with just the emulator, although you have to learn hunting and using "d3dx.ini". You can for example disable that red shader in the forest of Valkyrie Profile 2 that appears in DX11 hardware renderer. Or whatever effect you want.
Thanks for the donation and testing!

You got my "d3dx.ini" from github, right? I think I had solved some shader override incompatibilities simce the latest fix release.

And that's the main problem. Fixing a game sometimes means breaking another. But writing about it somewhere gives you the ability to switch settings quickly.

About backwards cycling, it's currently impossible to have two different keys using the same possible settings that know what is the current point of the cycle. For example, imagine that you have numbers from 1 to 10.

You press the increase convergence 4 times, so you're at 4 convergence. You press the decrease convergence twice, and you're at 9. You press increase, you're at 5. You press decrease, you're at 8.

That's what would happen if I made a backwards convergence hotkey with the same settings.


About windows 7: do the regex hotkeys work (meaning that you have proper 3D too), and not the shader overrides? If that's what happens, then for some reason the shader hashes are different. If you enable hunting mode and search and dump the vertex shaders (numpad 4, 5, and 6), the overlay will tell you if it's regex 1, 2, or 3. Write their hashes somewhere and then delete the dumped shaders. Then use the hashes in the vertex shader overrides (back up the ini for Windows 10 if you ise the same emulator folder), replacing the old hashes. You will have to do your own individual fixes.


With 3Dmigoto you have more tools than with just the emulator, although you have to learn hunting and using "d3dx.ini". You can for example disable that red shader in the forest of Valkyrie Profile 2 that appears in DX11 hardware renderer. Or whatever effect you want.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

Posted 01/22/2018 07:40 AM   
Thank You so much for this fix! So far I have used another 3D-plugin for PCSX2 that only allowed me to play in anaglyph mode. 3DVision with full color is sooo much better now! [quote="masterotaku"]About windows 7: do the regex hotkeys work (meaning that you have proper 3D too), and not the shader overrides? If that's what happens, then for some reason the shader hashes are different. If you enable hunting mode and search and dump the vertex shaders (numpad 4, 5, and 6), the overlay will tell you if it's regex 1, 2, or 3. Write their hashes somewhere and then delete the dumped shaders. Then use the hashes in the vertex shader overrides (back up the ini for Windows 10 if you ise the same emulator folder), replacing the old hashes. You will have to do your own individual fixes.[/quote] I should have taken a look at the forum first ;) So I had to figure out by myself that the hashes for the regex shaders are different for Windows 7 and of course also for the PS. For Win 7 the hashes are: regex1 33168014181c98b9 regex2 fcb601e0cfd0c31c regex3 0bb348ba841e2646 So far I have only tested the hash for regex1 with Soul Calibur 3 with success. The other values are only copied from the overlay but not yet tested.
Thank You so much for this fix! So far I have used another 3D-plugin for PCSX2 that only allowed me to play in anaglyph mode. 3DVision with full color is sooo much better now!

masterotaku said:About windows 7: do the regex hotkeys work (meaning that you have proper 3D too), and not the shader overrides? If that's what happens, then for some reason the shader hashes are different. If you enable hunting mode and search and dump the vertex shaders (numpad 4, 5, and 6), the overlay will tell you if it's regex 1, 2, or 3. Write their hashes somewhere and then delete the dumped shaders. Then use the hashes in the vertex shader overrides (back up the ini for Windows 10 if you ise the same emulator folder), replacing the old hashes. You will have to do your own individual fixes.

I should have taken a look at the forum first ;) So I had to figure out by myself that the hashes for the regex shaders are different for Windows 7 and of course also for the PS.
For Win 7 the hashes are:

regex1 33168014181c98b9
regex2 fcb601e0cfd0c31c
regex3 0bb348ba841e2646

So far I have only tested the hash for regex1 with Soul Calibur 3 with success. The other values are only copied from the overlay but not yet tested.

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/22/2018 05:51 PM   
Thanks for testing. In my previous comment I was on my phone, so I can post this now. What people using W7 need to replace if they want to do their own overrides for pixel shaders, are the hashes in the following "d3dx.ini" block: [code] ;Regex vertex shaders. [ShaderOverrideRegex1VS] Hash=6d64bfd710f98b05 x3=0 w3=0 [ShaderOverrideRegex2VS] Hash=0c8511661cbc3936 y3=0 [ShaderOverrideRegex3VS] Hash=a1f8cd42ceaae9e9 z3=0 [/code] What did you do with Soul Calibur 3, ddr0390? I guess one of the HUD fixes that I have there, but changing the hash of the pixel shaders. The most important part (the base for everything else that can be done) is that the three regexes and their hotkeys work in all Windows versions (testing in this thread proves that W7 and W10 work), and we'll see if future PCSX2 builds work too. For example, I have tested an old version from almost a year ago, "pcsx2-v1.5.0-dev-1740-gaf3c1fc-windows-x86", and regex 1 has a different pattern. I don't know if I should include it just in case. It was this: [code] [ShaderRegex1.Pattern] mad o0\.xyzw, r0\.xyzw, cb0\[0\]\.xyzw, -cb0\[1\]\.xyzw\n mov o1\.xy, v0\.xyxx\n [/code] And at the two last lines of "[ShaderRegex1.Pattern.Replace]" instead of what currently is there: [code] mov o0.xyzw, ${tmp3}.xyzw\n mov o1.xy, v0.xyxx [/code] I post it in case someone needs to use an old build similar to that. Also, reminder for other people: if you dump the vertex shaders, they will stop being 3D, because the regex only affects non dumped shaders. That's why I say that you have to delete them after you get their hashes.
Thanks for testing. In my previous comment I was on my phone, so I can post this now. What people using W7 need to replace if they want to do their own overrides for pixel shaders, are the hashes in the following "d3dx.ini" block:

;Regex vertex shaders.
[ShaderOverrideRegex1VS]
Hash=6d64bfd710f98b05
x3=0
w3=0
[ShaderOverrideRegex2VS]
Hash=0c8511661cbc3936
y3=0
[ShaderOverrideRegex3VS]
Hash=a1f8cd42ceaae9e9
z3=0


What did you do with Soul Calibur 3, ddr0390? I guess one of the HUD fixes that I have there, but changing the hash of the pixel shaders.

The most important part (the base for everything else that can be done) is that the three regexes and their hotkeys work in all Windows versions (testing in this thread proves that W7 and W10 work), and we'll see if future PCSX2 builds work too. For example, I have tested an old version from almost a year ago, "pcsx2-v1.5.0-dev-1740-gaf3c1fc-windows-x86", and regex 1 has a different pattern. I don't know if I should include it just in case. It was this:

[ShaderRegex1.Pattern]
mad o0\.xyzw, r0\.xyzw, cb0\[0\]\.xyzw, -cb0\[1\]\.xyzw\n
mov o1\.xy, v0\.xyxx\n


And at the two last lines of "[ShaderRegex1.Pattern.Replace]" instead of what currently is there:

mov o0.xyzw, ${tmp3}.xyzw\n
mov o1.xy, v0.xyxx


I post it in case someone needs to use an old build similar to that.


Also, reminder for other people: if you dump the vertex shaders, they will stop being 3D, because the regex only affects non dumped shaders. That's why I say that you have to delete them after you get their hashes.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

Posted 01/22/2018 06:31 PM   
[quote="masterotaku"]What did you do with Soul Calibur 3, ddr0390? I guess one of the HUD fixes that I have there, but changing the hash of the pixel shaders.[/quote] Yes, for testing I fixed one of the HUD shaders. With the hunted PS and the code for Win 7 [code];Regex vertex shaders. [ShaderOverrideRegex1VS] Hash=33168014181c98b9 x3=0 w3=0 [ShaderOverrideRegex2VS] Hash=fcb601e0cfd0c31c y3=0 [ShaderOverrideRegex3VS] Hash=0bb348ba841e2646 z3=0[/code] it worked. In SC3 also the hotkey for regex2 worked (HUD elements). When disabling regex3 (as recommended) I could not see an effect in this game yet... Do You happen to know which elements regex3 should affect in SC3? SC3 is the only game in Your PCSX2_3D_game_database I own atm.
masterotaku said:What did you do with Soul Calibur 3, ddr0390? I guess one of the HUD fixes that I have there, but changing the hash of the pixel shaders.

Yes, for testing I fixed one of the HUD shaders. With the hunted PS and the code for Win 7
;Regex vertex shaders.
[ShaderOverrideRegex1VS]
Hash=33168014181c98b9
x3=0
w3=0
[ShaderOverrideRegex2VS]
Hash=fcb601e0cfd0c31c
y3=0
[ShaderOverrideRegex3VS]
Hash=0bb348ba841e2646
z3=0

it worked. In SC3 also the hotkey for regex2 worked (HUD elements). When disabling regex3 (as recommended) I could not see an effect in this game yet... Do You happen to know which elements regex3 should affect in SC3? SC3 is the only game in Your PCSX2_3D_game_database I own atm.

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/22/2018 07:32 PM   
Sorry, double post...
Sorry, double post...

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/22/2018 07:37 PM   
[quote="ddr0390"]Do You happen to know which elements regex3 should affect in SC3? SC3 is the only game in Your PCSX2_3D_game_database I own atm. [/quote] No idea, after trying it for a while (didn't try the "strategy" mode). Maybe I was wrong when I said to disable regex 3 for this game, or maybe I fixed whatever it was in an unrelated override. If you don't see anything wrong, you don't have to press the key :).
ddr0390 said:Do You happen to know which elements regex3 should affect in SC3? SC3 is the only game in Your PCSX2_3D_game_database I own atm.


No idea, after trying it for a while (didn't try the "strategy" mode). Maybe I was wrong when I said to disable regex 3 for this game, or maybe I fixed whatever it was in an unrelated override. If you don't see anything wrong, you don't have to press the key :).

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

Posted 01/22/2018 08:22 PM   
Was just asking about regex3 in SC3 because I wanted to verify if I could find the right hash for regex3 in Windows 7. But as the overlay said regex3 for the VS my Win 7 code in d3dx.ini should be fine. BTW Your detailed descriptions in d3dx.ini which shader fixes which issue is very helpful when You have to make a fix for Win 7 with other hashes. Unfortunately I'm very busy so I can't do a Win 7 fix for SC3 atm. But when I will make fixes in the future I will post the code for Win 7.
Was just asking about regex3 in SC3 because I wanted to verify if I could find the right hash for regex3 in Windows 7. But as the overlay said regex3 for the VS my Win 7 code in d3dx.ini should be fine.
BTW Your detailed descriptions in d3dx.ini which shader fixes which issue is very helpful when You have to make a fix for Win 7 with other hashes. Unfortunately I'm very busy so I can't do a Win 7 fix for SC3 atm. But when I will make fixes in the future I will post the code for Win 7.

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/23/2018 08:06 AM   
I was interested to see if the game "Ico" would run in 3D. I tried the settings recommended for Ico (mipmapping "Basic", Half-pixel Offset). In 2D the game runs fine, also after opening the GSdx configuration as long as the game is in windowed mode. But when I enable fullscreen mode and 3D then left eye is dark and the picture freezes. The game is still running (sound, changing position of the character) and becomes normal when switching back to 2D windowed mode. When I use hotkey "v" in 3D then the picture for the eye with the same camera angle as 2D unfreezes but the stereoized picture for the other eye is frozen. I tried the settings which worked for SC3 but have the same issue. Switching between PAL/NTSC didn't help. I also tested Shadow of the Colossus from the same developer (maybe similar engine?) and it worked (some issues but the game was stereoized). Any idea which settings I could change?
I was interested to see if the game "Ico" would run in 3D. I tried the settings recommended for Ico (mipmapping "Basic", Half-pixel Offset). In 2D the game runs fine, also after opening the GSdx configuration as long as the game is in windowed mode. But when I enable fullscreen mode and 3D then left eye is dark and the picture freezes. The game is still running (sound, changing position of the character) and becomes normal when switching back to 2D windowed mode. When I use hotkey "v" in 3D then the picture for the eye with the same camera angle as 2D unfreezes but the stereoized picture for the other eye is frozen. I tried the settings which worked for SC3 but have the same issue. Switching between PAL/NTSC didn't help. I also tested Shadow of the Colossus from the same developer (maybe similar engine?) and it worked (some issues but the game was stereoized).
Any idea which settings I could change?

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/23/2018 04:32 PM   
[quote="ddr0390"]Any idea which settings I could change?[/quote] ICO tested! Get the newest "d3dx.ini" here: https://github.com/masterotaku/shader-mods/tree/master/PS2/3D%20database%20and%20ini First of all, the language and Hz selector screen needs native resolution to see what you're selecting (not related to 3D. Emulator problem), in the PAL version at least. Second, the game needs regex 3 to be disabled. So press that key. This fixes the frozen image. Remember this for other possible games with frozen image. Third, there is an existing override to fix the bloom/fog layer of the game without breaking shadows (which would happen if you disable regex 2). It's this one: [code] [ShaderOverrideYsV_20] Hash=b965398c3c58bfd2 y3=0 [/code] Set "y3=1" for that, but you'll make some shadows in Soul Calibur 3 2D. You'll have to change it when you play one game or the other (or other possibly unknown affected games). Unfortunately, it makes weapon swinging 2D too. If you don't use the override and instead use a high enough convergence, you can send away from the screen that "bloom/fog" layer if you want. Fourth, the game has some "unfocused" blurring (not broken. It's normal for the game) that you can disable in the "[ShaderOverrideSSH_2]" override. Uncomment the whole override and the "Handling=skip" part if you want to disable the effect. The override itself isn't needed because you are making it 2D already when you disable regex 3. Fifth, the game needs a very low convergence setting. That's why I have added two new settings for the convergence hotkey (second and third settings when you press it).
ddr0390 said:Any idea which settings I could change?



ICO tested! Get the newest "d3dx.ini" here: https://github.com/masterotaku/shader-mods/tree/master/PS2/3D%20database%20and%20ini

First of all, the language and Hz selector screen needs native resolution to see what you're selecting (not related to 3D. Emulator problem), in the PAL version at least.

Second, the game needs regex 3 to be disabled. So press that key. This fixes the frozen image. Remember this for other possible games with frozen image.

Third, there is an existing override to fix the bloom/fog layer of the game without breaking shadows (which would happen if you disable regex 2). It's this one:

[ShaderOverrideYsV_20]
Hash=b965398c3c58bfd2
y3=0


Set "y3=1" for that, but you'll make some shadows in Soul Calibur 3 2D. You'll have to change it when you play one game or the other (or other possibly unknown affected games). Unfortunately, it makes weapon swinging 2D too. If you don't use the override and instead use a high enough convergence, you can send away from the screen that "bloom/fog" layer if you want.

Fourth, the game has some "unfocused" blurring (not broken. It's normal for the game) that you can disable in the "[ShaderOverrideSSH_2]" override. Uncomment the whole override and the "Handling=skip" part if you want to disable the effect. The override itself isn't needed because you are making it 2D already when you disable regex 3.

Fifth, the game needs a very low convergence setting. That's why I have added two new settings for the convergence hotkey (second and third settings when you press it).

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

Posted 01/23/2018 10:43 PM   
Thank You for fixing ICO - a game really worth to be played ;) Now that I can play it in 3D on my PC I don't have to buy the remaster for the PS3 and borrow the 3D TV from my father :) As Win 7 has different hashes the code for the third step has to be: [code][ShaderOverrideYsV_20] Hash=ba915122eb64d940 y3=1[/code] Regarding the fourth step... So far (played about 30 mins) I could not observe a blurring effect. Maybe You could poste the code of the shader (Hash=dd3640a3970938ac) and I can try to find the shader for Win 7 with (almost) the same code and test it?
Thank You for fixing ICO - a game really worth to be played ;) Now that I can play it in 3D on my PC I don't have to buy the remaster for the PS3 and borrow the 3D TV from my father :)
As Win 7 has different hashes the code for the third step has to be:
[ShaderOverrideYsV_20]
Hash=ba915122eb64d940
y3=1

Regarding the fourth step... So far (played about 30 mins) I could not observe a blurring effect. Maybe You could poste the code of the shader (Hash=dd3640a3970938ac) and I can try to find the shader for Win 7 with (almost) the same code and test it?

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/24/2018 07:29 PM   
[quote="ddr0390"] Regarding the fourth step... So far (played about 30 mins) I could not observe a blurring effect.[/quote] This is what I mean. Before disabling it: http://u.cubeupload.com/masterotaku/pcsx2037.jpg After disabling it: http://u.cubeupload.com/masterotaku/pcsx2038.jpg You know what to look for when you hunt the pixel shader now :). It should look like the "after" screenshot when you select it in hunting mode. Note: outside, the game is "unfocused" on top of that. This override will make it look cleaner but not 100% clean in those situations. By the way, a shader hash is different when the content of the shader is different. You won't find the same code as me.
ddr0390 said:
Regarding the fourth step... So far (played about 30 mins) I could not observe a blurring effect.


This is what I mean.

Before disabling it: http://u.cubeupload.com/masterotaku/pcsx2037.jpg


After disabling it: http://u.cubeupload.com/masterotaku/pcsx2038.jpg


You know what to look for when you hunt the pixel shader now :). It should look like the "after" screenshot when you select it in hunting mode. Note: outside, the game is "unfocused" on top of that. This override will make it look cleaner but not 100% clean in those situations.


By the way, a shader hash is different when the content of the shader is different. You won't find the same code as me.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

Posted 01/24/2018 09:53 PM   
Strange. On my system the game already looks like Your "after disabling" screenshot. Maybe it is removed by my emulator settings? As suggested in the Wiki https://wiki.pcsx2.net/ICO I set mipmapping to basic and half-pixel offset to normal (Vertex). Or my hardware is just so bad that it can't produce the blurring effect ;) [quote="masterotaku"]By the way, a shader hash is different when the content of the shader is different. You won't find the same code as me.[/quote] I know that the code is not [b]exactly [/b]the same but at least it should be very similar...? As far as I have seen the games only have one or two dozen PS. So even comparing the shaders for Win 10 and Win 7 manually should be quite simple. At least easier than running the game itself, looking for the issues in different situations and hunting all the connected PS. So maybe just comparing the shader is the best way to convert the elaborate fixes You have made for Win 10 to Win 7... If You happen to run Soul Calibur 3 could You please just dump all the PS You got in Win 10 and upload them? You dont have to filter out the PS needed for the fix. I can find them by the d3dx.ini.
Strange. On my system the game already looks like Your "after disabling" screenshot. Maybe it is removed by my emulator settings? As suggested in the Wiki https://wiki.pcsx2.net/ICO I set mipmapping to basic and half-pixel offset to normal (Vertex). Or my hardware is just so bad that it can't produce the blurring effect ;)

masterotaku said:By the way, a shader hash is different when the content of the shader is different. You won't find the same code as me.

I know that the code is not exactly the same but at least it should be very similar...? As far as I have seen the games only have one or two dozen PS. So even comparing the shaders for Win 10 and Win 7 manually should be quite simple. At least easier than running the game itself, looking for the issues in different situations and hunting all the connected PS. So maybe just comparing the shader is the best way to convert the elaborate fixes You have made for Win 10 to Win 7...
If You happen to run Soul Calibur 3 could You please just dump all the PS You got in Win 10 and upload them? You dont have to filter out the PS needed for the fix. I can find them by the d3dx.ini.

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/25/2018 08:20 AM   
[quote="ddr0390"] I know that the code is not [b]exactly [/b]the same but at least it should be very similar...?[/quote] Yeah, differences should be very small. OK, I'll post my "ShaderCache" with all the shaders that appear after playing Soul Calibur 3 for a while. You'll have to wait a few hours still.
ddr0390 said:
I know that the code is not exactly the same but at least it should be very similar...?


Yeah, differences should be very small. OK, I'll post my "ShaderCache" with all the shaders that appear after playing Soul Calibur 3 for a while. You'll have to wait a few hours still.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

Posted 01/25/2018 12:11 PM   
No need to hurry ;) Just enjoying Your dgVoodoo based fix for Tomb Raider 4 - many thanks for making these classic games playable in 3D!!!
No need to hurry ;) Just enjoying Your dgVoodoo based fix for Tomb Raider 4 - many thanks for making these classic games playable in 3D!!!

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 01/25/2018 04:07 PM   
[quote="ddr0390"]No need to hurry ;) Just enjoying Your dgVoodoo based fix for Tomb Raider 4 - many thanks for making these classic games playable in 3D!!![/quote] Glad you like it :). By the way, there's some trouble about fixes I did for dgVoodoo games on Windows 7 too. Different shader hashes according to bo3b (at least for the Hitman games). I did them on Windows 10. About Soul Calibur 3 shaders, here they are, as promised: https://s3.amazonaws.com/masterotaku/PCSX2/ShaderCache_Soul_Calibur_3.7z
ddr0390 said:No need to hurry ;) Just enjoying Your dgVoodoo based fix for Tomb Raider 4 - many thanks for making these classic games playable in 3D!!!


Glad you like it :). By the way, there's some trouble about fixes I did for dgVoodoo games on Windows 7 too. Different shader hashes according to bo3b (at least for the Hitman games). I did them on Windows 10.

About Soul Calibur 3 shaders, here they are, as promised: https://s3.amazonaws.com/masterotaku/PCSX2/ShaderCache_Soul_Calibur_3.7z

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

Posted 01/25/2018 09:30 PM   
  8 / 16    
Scroll To Top