https://pcsx2.net/download/development/git.html
Which leads you to the buildbot that automatically compiles builds: https://buildbot.orphis.net/pcsx2/index.php
Another thing. After some tests, I have discovered that "Large Framebuffer" isn't necessary for games that have a progressive scan mode or cheat code (when the mode is enabled, of course). I say it because "Large Framebuffer" results in a MASSIVE increase in VRAM requirements when you use very high resolutions, especially after doing the necessary steps to enable 3D. The difference in games that work in 3D with and without it can be of more than 3GB of VRAM. In some games I can have over 6GB of VRAM usage at 8x native resolution with "Large Framebuffer" enabled.
There are games that have a cheat code for progressive scan included in the widescreen codes that come with the emulator, like Final Fantasy XII International.
Another thing. After some tests, I have discovered that "Large Framebuffer" isn't necessary for games that have a progressive scan mode or cheat code (when the mode is enabled, of course). I say it because "Large Framebuffer" results in a MASSIVE increase in VRAM requirements when you use very high resolutions, especially after doing the necessary steps to enable 3D. The difference in games that work in 3D with and without it can be of more than 3GB of VRAM. In some games I can have over 6GB of VRAM usage at 8x native resolution with "Large Framebuffer" enabled.
There are games that have a cheat code for progressive scan included in the widescreen codes that come with the emulator, like Final Fantasy XII International.
This is what I'm going to post on the blog soon (probably tomorrow because I have to go to bed soon and it's going to be a LONG post): https://s3.amazonaws.com/masterotaku/PCSX2/PCSX2_3D_Vision_feature.7z
If you have the fix from the previous page and update "d3dx.ini" from my github page, it's the same, except maybe for a backup folder for the SBS/TAB/etc shader.
So if you know your way around my hoykeys (check the new God of War 1-2 one) and know how to boot games, you won't need the blog post that much.
If you have the fix from the previous page and update "d3dx.ini" from my github page, it's the same, except maybe for a backup folder for the SBS/TAB/etc shader.
So if you know your way around my hoykeys (check the new God of War 1-2 one) and know how to boot games, you won't need the blog post that much.
I'm looking into making separation accurate (I have a ruler now, lol. In PC games, my max separation is 7cm). I had to change the number, and Soul Calibur 3 needs a higher value. So the previous post doesn't have the definitive fix then :). I'll try to finish everything today.
I'm looking into making separation accurate (I have a ruler now, lol. In PC games, my max separation is 7cm). I had to change the number, and Soul Calibur 3 needs a higher value. So the previous post doesn't have the definitive fix then :). I'll try to finish everything today.
The SBS/TAB workaround - have you dug into that at all to work out why it can't be enabled on launch? You shouldn't need hunting=2 to allow the d3dx.ini and custom shaders to be reloaded for that workaround - so long as reload_config is enabled F10 will still reload the d3dx.ini (this is the only [Hunting] keybinding that is still allowed when hunting is disabled*). You won't hear the beep - that beep is a confirmation that replaced shaders were successfully reloaded, and those do require hunting enabled to reload.
* In case you're thinking about it - you can use this to enable hunting on the fly if hunting was 0 on launch, but it will be severely limited and a game restart is highly recommended in this case.
The SBS/TAB workaround - have you dug into that at all to work out why it can't be enabled on launch? You shouldn't need hunting=2 to allow the d3dx.ini and custom shaders to be reloaded for that workaround - so long as reload_config is enabled F10 will still reload the d3dx.ini (this is the only [Hunting] keybinding that is still allowed when hunting is disabled*). You won't hear the beep - that beep is a confirmation that replaced shaders were successfully reloaded, and those do require hunting enabled to reload.
* In case you're thinking about it - you can use this to enable hunting on the fly if hunting was 0 on launch, but it will be severely limited and a game restart is highly recommended in this case.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
You're right about not needing hunting=2 to change the loading of the SBS/TAB shaders. I've edited the blog post to reflect that.
I know about changing the hunting setting mid game and that it's limited, that's why I thought I needed hunting=2 fot this, in fact.
Why can't the SBS shader be enabled at launch? I don't know. After the "closing the GSdx config" step and resume the game (even before trying to use fullscreen), the game screen freezes and the emulator console starts to throw theses errors:
[code]
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
[/code]
About the "get_resolution_from=depth_stencil", I still got the same hashes as before for render targets, different for each resolution.
You're right about not needing hunting=2 to change the loading of the SBS/TAB shaders. I've edited the blog post to reflect that.
I know about changing the hunting setting mid game and that it's limited, that's why I thought I needed hunting=2 fot this, in fact.
Why can't the SBS shader be enabled at launch? I don't know. After the "closing the GSdx config" step and resume the game (even before trying to use fullscreen), the game screen freezes and the emulator console starts to throw theses errors:
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSdx: Memory allocation error
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
GSDX OUT OF MEMORY
About the "get_resolution_from=depth_stencil", I still got the same hashes as before for render targets, different for each resolution.
Hi masterotaku.Thank you for this great fix.I tried but I can't get into exclusive fullscreen mode after double clicking and alt-tab.I using a passive lg 49 3d tv with Optimized for geforce(acer edid)and windows 10.
Hi masterotaku.Thank you for this great fix.I tried but I can't get into exclusive fullscreen mode after double clicking and alt-tab.I using a passive lg 49 3d tv with Optimized for geforce(acer edid)and windows 10.
It isn't alt+tab. It's alt+enter. Did you follow the SBS/TAB steps I explained in the post? What's your Windows version?
Someone that commented on the blog (with a passive display and W7) reached the point of exclusive fullscreen, because the profile green text appeared. I'm waiting for that person to answer some questions.
It isn't alt+tab. It's alt+enter. Did you follow the SBS/TAB steps I explained in the post? What's your Windows version?
Someone that commented on the blog (with a passive display and W7) reached the point of exclusive fullscreen, because the profile green text appeared. I'm waiting for that person to answer some questions.
I don't know what to suggest, if you did everything right. I don't have any passive display so I can't try it. Exclusive fullscreen depends on SpecialK, and I don't think it cares about the type of display.
Can more people with passive TVs or projectors try it?
I don't know what to suggest, if you did everything right. I don't have any passive display so I can't try it. Exclusive fullscreen depends on SpecialK, and I don't think it cares about the type of display.
Can more people with passive TVs or projectors try it?
Fix updated. No more custom resolution or "Large Framebuffer" needed to play certain games (more like a lot) in 3D. Now all of them will work without any special setting.
Fix updated. No more custom resolution or "Large Framebuffer" needed to play certain games (more like a lot) in 3D. Now all of them will work without any special setting.
@silentbrains
Thanks for the feedback.
I'm not sure if I had a space in the filepath but come to think of it I didn't try installing the patch with those quotation marks like you did. It gave me some parameter error after trying a few times and because I had no idea what this "%~dp0" does I just removed it lol.
Anywho the way I installed it was by opening the cmd-line tool with admin mode, going to the folder where I had the sdb file and simply typing the command: sdbinst d3d11_fix.sdb
It will actually give you a message saying that PCSX2 compatibility patch was successfully installed or something similar.
I'm not sure if I had a space in the filepath but come to think of it I didn't try installing the patch with those quotation marks like you did. It gave me some parameter error after trying a few times and because I had no idea what this "%~dp0" does I just removed it lol.
Anywho the way I installed it was by opening the cmd-line tool with admin mode, going to the folder where I had the sdb file and simply typing the command: sdbinst d3d11_fix.sdb
It will actually give you a message saying that PCSX2 compatibility patch was successfully installed or something similar.
Which leads you to the buildbot that automatically compiles builds: https://buildbot.orphis.net/pcsx2/index.php
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
There are games that have a cheat code for progressive scan included in the widescreen codes that come with the emulator, like Final Fantasy XII International.
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
If you have the fix from the previous page and update "d3dx.ini" from my github page, it's the same, except maybe for a backup folder for the SBS/TAB/etc shader.
So if you know your way around my hoykeys (check the new God of War 1-2 one) and know how to boot games, you won't need the blog post that much.
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
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
All the explanations and tutorials included.
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
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
* In case you're thinking about it - you can use this to enable hunting on the fly if hunting was 0 on launch, but it will be severely limited and a game restart is highly recommended in this case.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
I know about changing the hunting setting mid game and that it's limited, that's why I thought I needed hunting=2 fot this, in fact.
Why can't the SBS shader be enabled at launch? I don't know. After the "closing the GSdx config" step and resume the game (even before trying to use fullscreen), the game screen freezes and the emulator console starts to throw theses errors:
About the "get_resolution_from=depth_stencil", I still got the same hashes as before for render targets, different for each resolution.
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
Someone that commented on the blog (with a passive display and W7) reached the point of exclusive fullscreen, because the profile green text appeared. I'm waiting for that person to answer some questions.
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
Can more people with passive TVs or projectors try 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
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
Thanks for the feedback.
I'm not sure if I had a space in the filepath but come to think of it I didn't try installing the patch with those quotation marks like you did. It gave me some parameter error after trying a few times and because I had no idea what this "%~dp0" does I just removed it lol.
Anywho the way I installed it was by opening the cmd-line tool with admin mode, going to the folder where I had the sdb file and simply typing the command: sdbinst d3d11_fix.sdb
It will actually give you a message saying that PCSX2 compatibility patch was successfully installed or something similar.