3Dmigoto now open-source...
  122 / 143    
@Helifax Is: [code]hook=skip_dxgi_device allow_platform_update=1 [/code] If you can test the Frostbite3 Universal Fix ([url="https://forums.geforce.com/default/topic/1035614/3d-vision/universal-fixes/"]HERE[/url]) in Battlefront 2 will be great! (i don't have the game to test direcly)
@Helifax

Is:
hook=skip_dxgi_device
allow_platform_update=1


If you can test the Frostbite3 Universal Fix (HERE) in Battlefront 2 will be great!
(i don't have the game to test direcly)

MY WEB

Helix Mod - Making 3D Better

My 3D Screenshot Gallery

Like my fixes? you can donate to Paypal: dhr.donation@gmail.com

Posted 01/29/2018 09:56 PM   
[s][quote="DHR"]@Helifax Is: [code]hook=skip_dxgi_device allow_platform_update=1 [/code] If you can test the Frostbite3 Universal Fix ([url="https://forums.geforce.com/default/topic/1035614/3d-vision/universal-fixes/"]HERE[/url]) in Battlefront 2 will be great! (i don't have the game to test direcly)[/quote][/s] Yupp... tried that before... Nope... is not working... At least on Windows 10 ... :(
DHR said:@Helifax

Is:
hook=skip_dxgi_device
allow_platform_update=1


If you can test the Frostbite3 Universal Fix (HERE) in Battlefront 2 will be great!
(i don't have the game to test direcly)


Yupp... tried that before... Nope... is not working... At least on Windows 10 ... :(

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

Posted 01/29/2018 10:38 PM   
[quote]At least on Windows 10 ... :( [/quote]Yeah, I know what's going on: [code] Hooked IDXGIFactory2::CreateSwapChainForHwnd(00000000064D9680) called Device = 000000007A61B320 SwapChain = 0000000080B3E6B0 Description1 = 000000005D46F788 FullScreenDescription = 000000005D46F768 Windowed = 0 lookup_hacker_device(000000007A61B320) IUnknown: 000000007A61B2F0 HackerDevice: 0000000000000000 Fatal: CreateSwapChainForHwnd could not locate HackerDevice for 000000007A61B320 Checking what interfaces 000000007A61B320 supports... IUnknown: Supported: 000000007A61B2F0 ID3D12CommandQueue: Supported: 000000007A61B320 ID3D12DeviceChild: Supported: 000000007A61B320 ID3D12Object: Supported: 000000007A61B320 ID3D12Pageable: Supported: 000000007A61B320 [/code] It's using a DirectX 12 device to create the swap chain, and 3DMigoto has no idea what to do - that's why this is only showing up on Windows 10 (that interface check is only in our exp_vs2015 branch because it needs a more recent Windows SDK to know the DX12 IIDs - you won't see that in the logs of any officially released version yet). Change the DirectX version to 11 in game settings.
At least on Windows 10 ... :(
Yeah, I know what's going on:

Hooked IDXGIFactory2::CreateSwapChainForHwnd(00000000064D9680) called
Device = 000000007A61B320
SwapChain = 0000000080B3E6B0
Description1 = 000000005D46F788
FullScreenDescription = 000000005D46F768
Windowed = 0
lookup_hacker_device(000000007A61B320) IUnknown: 000000007A61B2F0 HackerDevice: 0000000000000000
Fatal: CreateSwapChainForHwnd could not locate HackerDevice for 000000007A61B320
Checking what interfaces 000000007A61B320 supports...
IUnknown: Supported: 000000007A61B2F0
ID3D12CommandQueue: Supported: 000000007A61B320
ID3D12DeviceChild: Supported: 000000007A61B320
ID3D12Object: Supported: 000000007A61B320
ID3D12Pageable: Supported: 000000007A61B320


It's using a DirectX 12 device to create the swap chain, and 3DMigoto has no idea what to do - that's why this is only showing up on Windows 10 (that interface check is only in our exp_vs2015 branch because it needs a more recent Windows SDK to know the DX12 IIDs - you won't see that in the logs of any officially released version yet).

Change the DirectX version to 11 in game settings.

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

Posted 01/30/2018 02:57 AM   
I'm noticed in FIFA 2018 DEMO there is a "Directx" option in the launcher (Automatic, DX11 and DX12), since i'm using Win7 is using DX11 in automatic, but still i mark the DX11 option when i tested. I suppose same option is present in [b]Battlefront II[/b]...so if someone can test changing to "DX11" option and use this settings in the ini: [code]hook=skip_dxgi_device allow_platform_update=1[/code]
I'm noticed in FIFA 2018 DEMO there is a "Directx" option in the launcher (Automatic, DX11 and DX12), since i'm using Win7 is using DX11 in automatic, but still i mark the DX11 option when i tested.

I suppose same option is present in Battlefront II...so if someone can test changing to "DX11" option and use this settings in the ini:
hook=skip_dxgi_device
allow_platform_update=1

MY WEB

Helix Mod - Making 3D Better

My 3D Screenshot Gallery

Like my fixes? you can donate to Paypal: dhr.donation@gmail.com

Posted 01/30/2018 11:06 AM   
[quote="DarkStarSword"][quote]At least on Windows 10 ... :( [/quote]Yeah, I know what's going on: [code] Hooked IDXGIFactory2::CreateSwapChainForHwnd(00000000064D9680) called Device = 000000007A61B320 SwapChain = 0000000080B3E6B0 Description1 = 000000005D46F788 FullScreenDescription = 000000005D46F768 Windowed = 0 lookup_hacker_device(000000007A61B320) IUnknown: 000000007A61B2F0 HackerDevice: 0000000000000000 Fatal: CreateSwapChainForHwnd could not locate HackerDevice for 000000007A61B320 Checking what interfaces 000000007A61B320 supports... IUnknown: Supported: 000000007A61B2F0 ID3D12CommandQueue: Supported: 000000007A61B320 ID3D12DeviceChild: Supported: 000000007A61B320 ID3D12Object: Supported: 000000007A61B320 ID3D12Pageable: Supported: 000000007A61B320 [/code] It's using a DirectX 12 device to create the swap chain, and 3DMigoto has no idea what to do - that's why this is only showing up on Windows 10 (that interface check is only in our exp_vs2015 branch because it needs a more recent Windows SDK to know the DX12 IIDs - you won't see that in the logs of any officially released version yet). Change the DirectX version to 11 in game settings.[/quote] That is very interesting. I set the game as DX11 in the menu and it still gets there! Something confuses the game into trying to go the DX12 route! (Or maybe it does it anyway?) But, 1.3.1 3DMigoto works flawless! :D:D:D:D:D Eternal gratitude for that! (Both for DarkStarSword and Bo3b)!
DarkStarSword said:
At least on Windows 10 ... :(
Yeah, I know what's going on:

Hooked IDXGIFactory2::CreateSwapChainForHwnd(00000000064D9680) called
Device = 000000007A61B320
SwapChain = 0000000080B3E6B0
Description1 = 000000005D46F788
FullScreenDescription = 000000005D46F768
Windowed = 0
lookup_hacker_device(000000007A61B320) IUnknown: 000000007A61B2F0 HackerDevice: 0000000000000000
Fatal: CreateSwapChainForHwnd could not locate HackerDevice for 000000007A61B320
Checking what interfaces 000000007A61B320 supports...
IUnknown: Supported: 000000007A61B2F0
ID3D12CommandQueue: Supported: 000000007A61B320
ID3D12DeviceChild: Supported: 000000007A61B320
ID3D12Object: Supported: 000000007A61B320
ID3D12Pageable: Supported: 000000007A61B320


It's using a DirectX 12 device to create the swap chain, and 3DMigoto has no idea what to do - that's why this is only showing up on Windows 10 (that interface check is only in our exp_vs2015 branch because it needs a more recent Windows SDK to know the DX12 IIDs - you won't see that in the logs of any officially released version yet).

Change the DirectX version to 11 in game settings.


That is very interesting. I set the game as DX11 in the menu and it still gets there! Something confuses the game into trying to go the DX12 route! (Or maybe it does it anyway?)

But, 1.3.1 3DMigoto works flawless! :D:D:D:D:D Eternal gratitude for that! (Both for DarkStarSword and Bo3b)!

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

Posted 01/30/2018 06:56 PM   
Just to report, Path of Exile now working again in windows 10 creators update with 3Dmigoto 1.31! Thanks very much too DarkStarSword, and B03b!!!!!! and thanks also to all you usual suspects =)
Just to report, Path of Exile now working again in windows 10 creators update with 3Dmigoto 1.31!

Thanks very much too DarkStarSword, and B03b!!!!!!
and thanks also to all you usual suspects =)

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

Posted 01/31/2018 08:37 AM   
1.31? The releases page on github shows only up to 1.30. Hey, and thanks for the update! I should check GOG Galaxy overlay compatibility. It used to crash with 3Dmigoto in most games. And maybe it can improve Dead Rising stability.
1.31? The releases page on github shows only up to 1.30.

Hey, and thanks for the update! I should check GOG Galaxy overlay compatibility. It used to crash with 3Dmigoto in most games.

And maybe it can improve Dead Rising stability.

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/31/2018 09:28 AM   
I just reported to bo3b a "possible" BUG in the [b]1.3 version[/b], related to ShaderRegex and possible other overrides not working properly in some cases. (**Note: This may or may not explain why in Battlefront II, one of the Regex is not working) Please take note that is an ***EXPERIMENTAL*** release. Do not use this version to start a fix, because may have some bugs. I'm testing with different games and fixes, so we not broke an existent fix when updating the version of the dll *upgrading*. If some other ShaderHacker want to help, try with this own fixes updating the dll and change the *allow part in the ini for the one shiped in the 1.3 Pre-release.
I just reported to bo3b a "possible" BUG in the 1.3 version, related to ShaderRegex and possible other overrides not working properly in some cases.

(**Note: This may or may not explain why in Battlefront II, one of the Regex is not working)


Please take note that is an ***EXPERIMENTAL*** release. Do not use this version to start a fix, because may have some bugs.

I'm testing with different games and fixes, so we not broke an existent fix when updating the version of the dll *upgrading*. If some other ShaderHacker want to help, try with this own fixes updating the dll and change the *allow part in the ini for the one shiped in the 1.3 Pre-release.

MY WEB

Helix Mod - Making 3D Better

My 3D Screenshot Gallery

Like my fixes? you can donate to Paypal: dhr.donation@gmail.com

Posted 01/31/2018 01:40 PM   
[quote] I just reported to bo3b a "possible" BUG in the 1.3 version, related to ShaderRegex and possible other overrides not working properly in some cases.[/quote]Given that ShaderRegex and most of the override code is my domain, can you let me know what the issue is? Have you also confirmed that this issue doesn't happen on 1.2.71? The issue tracker is a good place to report any issues you find, since both Bo3b and I look at that and can work together to find a solution: https://github.com/bo3b/3Dmigoto/issues
I just reported to bo3b a "possible" BUG in the 1.3 version, related to ShaderRegex and possible other overrides not working properly in some cases.
Given that ShaderRegex and most of the override code is my domain, can you let me know what the issue is? Have you also confirmed that this issue doesn't happen on 1.2.71?

The issue tracker is a good place to report any issues you find, since both Bo3b and I look at that and can work together to find a solution:
https://github.com/bo3b/3Dmigoto/issues

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

Posted 01/31/2018 09:19 PM   
Just send you a PM. This issue is present since 1.2.68 version of 3Dmigoto. Tested all until 1.3. Using 1.2.67 solve the issue, all work OK.
Just send you a PM.

This issue is present since 1.2.68 version of 3Dmigoto. Tested all until 1.3.
Using 1.2.67 solve the issue, all work OK.

MY WEB

Helix Mod - Making 3D Better

My 3D Screenshot Gallery

Like my fixes? you can donate to Paypal: dhr.donation@gmail.com

Posted 01/31/2018 09:50 PM   
[quote="DHR"]Just send you a PM. This issue is present since 1.2.68 version of 3Dmigoto. Tested all until 1.3. Using 1.2.67 solve the issue, all work OK.[/quote]Ok, this was just another case of a game finding a way to unbind StereoParams that I hadn't accounted for - this time by using deferred contexts (I had got one variation of this already, but missed the other). This will be fixed in 1.2.72 and 1.3.1
DHR said:Just send you a PM.

This issue is present since 1.2.68 version of 3Dmigoto. Tested all until 1.3.
Using 1.2.67 solve the issue, all work OK.
Ok, this was just another case of a game finding a way to unbind StereoParams that I hadn't accounted for - this time by using deferred contexts (I had got one variation of this already, but missed the other). This will be fixed in 1.2.72 and 1.3.1

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

Posted 02/01/2018 01:31 AM   
Thought I'd share an online RegEx tool that can take a lot of the pain out of creating regex expressions. https://regex101.com/ This has a very strong UI, and supports the pcre form of regex directly (pcre1, but not 2, which is what is in 3Dmigoto. Not sure that is necessarily significant.) Regex is great for automated tasks, but I find creating the actual expressions impossibly tedious and annoying, where single character errors in a string of nearly random gibberish make it fail silently. This makes it a lot easier, where you can see it live. You'll want to make it all one line in the regex101 input pane. If you paste it in exactly as you'd put it in the d3dx.ini it won't match because you'll have extra whitespace of line feeds. And be wary of extra line feeds in the box. As always with RegEx, start with small matches and build up to your full expression.
Thought I'd share an online RegEx tool that can take a lot of the pain out of creating regex expressions.

https://regex101.com/

This has a very strong UI, and supports the pcre form of regex directly (pcre1, but not 2, which is what is in 3Dmigoto. Not sure that is necessarily significant.)

Regex is great for automated tasks, but I find creating the actual expressions impossibly tedious and annoying, where single character errors in a string of nearly random gibberish make it fail silently. This makes it a lot easier, where you can see it live.

You'll want to make it all one line in the regex101 input pane. If you paste it in exactly as you'd put it in the d3dx.ini it won't match because you'll have extra whitespace of line feeds. And be wary of extra line feeds in the box. As always with RegEx, start with small matches and build up to your full expression.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

Posted 02/01/2018 03:16 AM   
@DarkStarSword Very nice for the fix, thanks!! About ShaderRegex, i think we can improve something....i have 2 ShaderRegex that need to fix 1 shader. If i test both independently works!, but when active boths there are not working properly because the {stereo} is defined twice (use 2 different register for the same stereoparams) so break the shader (both replace pattern are used correctly, checked in the log)....is possible that IF 2 ShaderRegex are fixing 1 shader, both ShaderRegex use only 1 stereoparams register for boths ShaderRegex (with this the shader will be fixed correctly), even if i defined in both ShaderRegex....those ShaderRegex are algo used one time per Shader in others scenarios.
@DarkStarSword
Very nice for the fix, thanks!!


About ShaderRegex, i think we can improve something....i have 2 ShaderRegex that need to fix 1 shader. If i test both independently works!, but when active boths there are not working properly because the {stereo} is defined twice (use 2 different register for the same stereoparams) so break the shader (both replace pattern are used correctly, checked in the log)....is possible that IF 2 ShaderRegex are fixing 1 shader, both ShaderRegex use only 1 stereoparams register for boths ShaderRegex (with this the shader will be fixed correctly), even if i defined in both ShaderRegex....those ShaderRegex are algo used one time per Shader in others scenarios.

MY WEB

Helix Mod - Making 3D Better

My 3D Screenshot Gallery

Like my fixes? you can donate to Paypal: dhr.donation@gmail.com

Posted 02/01/2018 10:52 AM   
[quote]If i test both independently works!, but when active boths there are not working properly because the {stereo} is defined twice (use 2 different register for the same stereoparams) so break the shader (both replace pattern are used correctly, checked in the log)....[/quote] That shouldn't matter - I specifically designed it so that should work. You'll get a second temporary register for stereoparams and it will load both from t125 separately, but that shouldn't hurt anything. t125 should only be declared once if it's the same in both InsertDeclarations sections. Can you show me exactly what it's doing that's wrong?
If i test both independently works!, but when active boths there are not working properly because the {stereo} is defined twice (use 2 different register for the same stereoparams) so break the shader (both replace pattern are used correctly, checked in the log)....


That shouldn't matter - I specifically designed it so that should work. You'll get a second temporary register for stereoparams and it will load both from t125 separately, but that shouldn't hurt anything. t125 should only be declared once if it's the same in both InsertDeclarations sections. Can you show me exactly what it's doing that's wrong?

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

Posted 02/01/2018 01:54 PM   
[center][color="orange"][size="XL"]3Dmigoto & cmd_Decompiler 1.2.72[/size][/color][/center][center][color="green"][url]https://github.com/bo3b/3Dmigoto/releases/tag/1.2.72[/url][/color][/center] [list] [.] Fixed another case where games (like Prey) could unbind StereoParams - hopefully the last one![/.] [.] Fixed bug where the very first time a [ShaderRegex] applied to a shader would not have a working command list unless there was at least one [ShaderOverride] section.[/.] [.] Assembly shaders will now have whitespace stripped from the end of each line. This is to assist when writing ShaderRegex patterns as previously the "ret ", "endif " and "else " lines had a space at the end of the line that could make it difficult to write a pattern correctly if you didn't notice it. If you already wrote a ShaderRegex pattern that explicitly matched such a space you will need to edit it to remove that, or make it optional (I don't think anyone has).[/.] [.] Removed warnings related to the except_set_shader_resource hooking workaround causing very large log files in some games[/.] [.] Upscaling now bypasses 3DMigoto's texture creation when using hooking as well[/.] [.] References to "no_view_cache" removed from d3dx.ini template - this has been enforced when accessing the back buffer for a while now, so doesn't matter if it is in the ini or not and just confusing to have it there.[/.] [/list] All of these updates will also be included in tomorrow's 1.3.1 release, and a little teaser of a new feature you can look forward to that is going to replace the beeps with something a little more informative (I will be looking for feedback on this): [url=https://forums.geforce.com/cmd/default/download-comment-attachment/74526/][img]https://forums.geforce.com/cmd/default/download-comment-attachment/74526/[/img][/url]
3Dmigoto & cmd_Decompiler 1.2.72

  • Fixed another case where games (like Prey) could unbind StereoParams - hopefully the last one!

  • Fixed bug where the very first time a [ShaderRegex] applied to a shader would not have a working command list unless there was at least one [ShaderOverride] section.

  • Assembly shaders will now have whitespace stripped from the end of each line. This is to assist when writing ShaderRegex patterns as previously the "ret ", "endif " and "else " lines had a space at the end of the line that could make it difficult to write a pattern correctly if you didn't notice it. If you already wrote a ShaderRegex pattern that explicitly matched such a space you will need to edit it to remove that, or make it optional (I don't think anyone has).

  • Removed warnings related to the except_set_shader_resource hooking workaround causing very large log files in some games

  • Upscaling now bypasses 3DMigoto's texture creation when using hooking as well

  • References to "no_view_cache" removed from d3dx.ini template - this has been enforced when accessing the back buffer for a while now, so doesn't matter if it is in the ini or not and just confusing to have it there.


All of these updates will also be included in tomorrow's 1.3.1 release, and a little teaser of a new feature you can look forward to that is going to replace the beeps with something a little more informative (I will be looking for feedback on this):

Image

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

Posted 02/01/2018 02:40 PM   
  122 / 143    
Scroll To Top