[quote="mrorange55"][quote="DHR"]@mrorange55
Can you try using this hooking method, search for "hook=" in the d3dx.in and copy-paste this
[code]hook=recommended skip_dxgi_factory skip_dxgi_device[/code]
If that doesn't work...try using 368.39 driver.
In the screenshot you have some models in 2D....very strange. would not surprise me if this is related to win10 + Anniversary s**t or win10 alone.[/quote]
The hooking is not working. Yes I have the anniversary update... I installed. I am an idio :(. Until know it only brought bad. Made my PC crash three times at least. Next time I willbe smarter... but now it is too late.
Okay, I guess then the only chance is to roll back the driver...
But actually Battlefront is working all fine with profile and fix, therefore I don't understand what is the difference to Battlefield 1?
Soon the Beta is over. I guess then I can wait a bit until I purchase this game.[/quote]
You have 10 days to be able to roll back the Anniversary update.
I also encourage everyone to do what is in your best interest, not what works best for Microsoft. If they were doing a great job, that would be different, but it's gotten ridiculous.
3D Vision is a trailing edge technology, it's always going to work more smoothly and easily on Win7. Win10 is as leading edge as it gets. Anniversary is bleeding edge.
You can't live on the bleeding edge and the trailing edge at the same time.
For 3D gaming, everyone will have fewer hassles with a Win7 setup. Dual boot if needed.
In the screenshot you have some models in 2D....very strange. would not surprise me if this is related to win10 + Anniversary s**t or win10 alone.
The hooking is not working. Yes I have the anniversary update... I installed. I am an idio :(. Until know it only brought bad. Made my PC crash three times at least. Next time I willbe smarter... but now it is too late.
Okay, I guess then the only chance is to roll back the driver...
But actually Battlefront is working all fine with profile and fix, therefore I don't understand what is the difference to Battlefield 1?
Soon the Beta is over. I guess then I can wait a bit until I purchase this game.
You have 10 days to be able to roll back the Anniversary update.
I also encourage everyone to do what is in your best interest, not what works best for Microsoft. If they were doing a great job, that would be different, but it's gotten ridiculous.
3D Vision is a trailing edge technology, it's always going to work more smoothly and easily on Win7. Win10 is as leading edge as it gets. Anniversary is bleeding edge.
You can't live on the bleeding edge and the trailing edge at the same time.
For 3D gaming, everyone will have fewer hassles with a Win7 setup. Dual boot if needed.
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
@mrorange55
You can try those thing. After this i don't have more ideas
1) Try with the 368.39 driver using DDU
2) Use Nvidia Inspector to assign B1 exe to Battlefront exe....if battlefront work, this game should works also.
3) Re-install the Open Beta game, maybe something is wrong with the installation.
Also for testing purpose....if you change in the d3dx.ini "hunting=0" for "hunting=1" you see the 3Dmigoto overlay? pressing F10 produce a beep sound?
You can try those thing. After this i don't have more ideas
1) Try with the 368.39 driver using DDU
2) Use Nvidia Inspector to assign B1 exe to Battlefront exe....if battlefront work, this game should works also.
3) Re-install the Open Beta game, maybe something is wrong with the installation.
Also for testing purpose....if you change in the d3dx.ini "hunting=0" for "hunting=1" you see the 3Dmigoto overlay? pressing F10 produce a beep sound?
[quote="DHR"]@mrorange55
You can try those thing. After this i don't have more ideas
1) Try with the 368.39 driver using DDU
2) Use Nvidia Inspector to assign B1 exe to Battlefront exe....if battlefront work, this game should works also.
3) Re-install the Open Beta game, maybe something is wrong with the installation.
Also for testing purpose....if you change in the d3dx.ini "hunting=0" for "hunting=1" you see the 3Dmigoto overlay? pressing F10 produce a beep sound?[/quote]
I found setting hunting=1 would make the game freak out at launch, and give a ResizeBuffers assertion dialog. Unplayable.
Try the hunting=2 to get it up and running, then Numpad 0 to show overlay.
You can try those thing. After this i don't have more ideas
1) Try with the 368.39 driver using DDU
2) Use Nvidia Inspector to assign B1 exe to Battlefront exe....if battlefront work, this game should works also.
3) Re-install the Open Beta game, maybe something is wrong with the installation.
Also for testing purpose....if you change in the d3dx.ini "hunting=0" for "hunting=1" you see the 3Dmigoto overlay? pressing F10 produce a beep sound?
I found setting hunting=1 would make the game freak out at launch, and give a ResizeBuffers assertion dialog. Unplayable.
Try the hunting=2 to get it up and running, then Numpad 0 to show overlay.
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
[quote="DHR"]@mrorange55
You can try those thing. After this i don't have more ideas
1) Try with the 368.39 driver using DDU
2) Use Nvidia Inspector to assign B1 exe to Battlefront exe....if battlefront work, this game should works also.
3) Re-install the Open Beta game, maybe something is wrong with the installation.
Also for testing purpose....if you change in the d3dx.ini "hunting=0" for "hunting=1" you see the 3Dmigoto overlay? pressing F10 produce a beep sound?[/quote]
Re-installation did not help. Did this already.
Other profile assignement is not helping either.
I don't get the beep sound.
So the next thing I have to try is to re install the old driver, I suppose.
Concerning the anniversary update. I guess I should really de-install it. Since the 16th August I have like 20 different Updates.
- EDIT: D'Oh - my updating was before more than 10 days. I can't go back. What the heck?
You can try those thing. After this i don't have more ideas
1) Try with the 368.39 driver using DDU
2) Use Nvidia Inspector to assign B1 exe to Battlefront exe....if battlefront work, this game should works also.
3) Re-install the Open Beta game, maybe something is wrong with the installation.
Also for testing purpose....if you change in the d3dx.ini "hunting=0" for "hunting=1" you see the 3Dmigoto overlay? pressing F10 produce a beep sound?
Re-installation did not help. Did this already.
Other profile assignement is not helping either.
I don't get the beep sound.
So the next thing I have to try is to re install the old driver, I suppose.
Concerning the anniversary update. I guess I should really de-install it. Since the 16th August I have like 20 different Updates.
- EDIT: D'Oh - my updating was before more than 10 days. I can't go back. What the heck?
If you use "hunting=1" or "2" and you don't get the beep sound when you press F10....that mean that the fix is not kicking in.
2 more things to try:
1) Uninstall the fix and re-install... be sure that all the files are in the same place than the EXE.
2) When you try with the 368.39 driver using DDU....also try this driver with the hooking method:
[code]hook=recommended skip_dxgi_factory skip_dxgi_device[/code]
If you use "hunting=1" or "2" and you don't get the beep sound when you press F10....that mean that the fix is not kicking in.
2 more things to try:
1) Uninstall the fix and re-install... be sure that all the files are in the same place than the EXE.
2) When you try with the 368.39 driver using DDU....also try this driver with the hooking method:
DHR said:I found the shader....is related to light reflections, BUT is not working properly in HLSL (decompiler issue?). When i dump i see some white stuff all over the screen...pressing F9 make the issue disappear. Pressing F10 i can hear the good beep.
OK, I took a look at this one, but I think the Decompiler is correct. I'm not seeing anything that seems out of the ordinary, and an ASM compare gives me pretty close results.
However, more importantly, when testing this, I had it launch without any problem a couple of times, without me doing anything.
Then to test further, I launched again with no changes whatsoever, and saw the effect come back.
So it's pretty clear this is a game bug of some form that we are making more obvious. Part of being Beta most likely.
My best guess is that it's timing related.
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
Thanks bo3b!!
I found another reflections shader with the same white issue, it's almost the same than this one...i change the values XXXXXXXe-006 for the correct numbers present in the ASM and fix the white issue in this shader...Maybe is some kind of bug of the Beta like you says.
I will test a little more with the "if (r3.w == 0)" section you mention in the PM. THANKS!
I found another reflections shader with the same white issue, it's almost the same than this one...i change the values XXXXXXXe-006 for the correct numbers present in the ASM and fix the white issue in this shader...Maybe is some kind of bug of the Beta like you says.
I will test a little more with the "if (r3.w == 0)" section you mention in the PM. THANKS!
I re-installed the fix now like 5 times and it looks every time different. One time I actually had the hope that it would now be fixed, because the earth in the beginning was for the first time looking perfect. But in-game, it was still broken. Here a picture to this.
I think we are on something here. I remember having the same problem with Battlefront, then I re-installed the fix one time and it was all fine.
What else, except the hook and the driver change might be possible to make sure the fix kicks in?
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/70135/[/img]
I re-installed the fix now like 5 times and it looks every time different. One time I actually had the hope that it would now be fixed, because the earth in the beginning was for the first time looking perfect. But in-game, it was still broken. Here a picture to this.
I think we are on something here. I remember having the same problem with Battlefront, then I re-installed the fix one time and it was all fine.
What else, except the hook and the driver change might be possible to make sure the fix kicks in?
@mrorange55
Only for testing.....remove weapon DOF and Motion Blur. Maybe the issue is related to the Motion Blur. I have both disabled.
Also try using Vsync Off in-game.
**EDIT:
You can try replacing the DLL (both) for a previous 3Dmigoto version. In this fix i'm using the last one.
Heureka, it works!!! [s]I replaced in the BF1 fix the three dll files with the ones from your Battlefront fix. And now it kicks in. :) We found the solution. Great.
[/s]
Here a picture:
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/70136/[/img]
[u][b]EDIT: TURN OFF VSYNC[/b][/u]
Heureka, it works!!! I replaced in the BF1 fix the three dll files with the ones from your Battlefront fix. And now it kicks in. :) We found the solution. Great.
Great that work now!!!
You replace with the Battlefront DLL from my fix or the helifax fix?
is to take note about the 3Dmigoto version used. In my fix i use the 1.2.39....maybe a bug is introduced in newer versions of 3Dmigoto in some configurations.
Why your sky is cut-off in the sides...i fix that cut-off issue in Battlefront and B1....very strange.
Great that work now!!!
You replace with the Battlefront DLL from my fix or the helifax fix?
is to take note about the 3Dmigoto version used. In my fix i use the 1.2.39....maybe a bug is introduced in newer versions of 3Dmigoto in some configurations.
Why your sky is cut-off in the sides...i fix that cut-off issue in Battlefront and B1....very strange.
[quote="DHR"]Thanks bo3b!!
I found another reflections shader with the same white issue, it's almost the same than this one...i change the values XXXXXXXe-006 for the correct numbers present in the ASM and fix the white issue in this shader...Maybe is some kind of bug of the Beta like you says.
I will test a little more with the "if (r3.w == 0)" section you mention in the PM. THANKS![/quote]
Yeah, this game has some funny launch for me. Sometimes it works and sometimes it does not. I even did a quit to main menu without leaving the game, and one time it was OK, one time it had whiteness.
Maybe try experimenting with cache and stereo off. When the shader is cached it seems slightly more often to startup OK. Also had it draw correctly after disabling 3D with Ctrl-T during loading, but that wasn't fully consistent.
I think it's getting in a race condition with another shader, probably a compute shader, and gets the wrong input value to start with. And our recompiled version is slightly less efficient than the original version because of conversions to float (300 instructions, vs. 291). Which might be why it shows correctly with the F9. Not 100% sure, but it is definitely inconsistent on launch.
The numbers you changed for E-6 were actually OK. I don't think it matters either way, but it created the numbers that were actually stored in the shader. It uses the binary versions nowadays, not the text output assembler.
I found another reflections shader with the same white issue, it's almost the same than this one...i change the values XXXXXXXe-006 for the correct numbers present in the ASM and fix the white issue in this shader...Maybe is some kind of bug of the Beta like you says.
I will test a little more with the "if (r3.w == 0)" section you mention in the PM. THANKS!
Yeah, this game has some funny launch for me. Sometimes it works and sometimes it does not. I even did a quit to main menu without leaving the game, and one time it was OK, one time it had whiteness.
Maybe try experimenting with cache and stereo off. When the shader is cached it seems slightly more often to startup OK. Also had it draw correctly after disabling 3D with Ctrl-T during loading, but that wasn't fully consistent.
I think it's getting in a race condition with another shader, probably a compute shader, and gets the wrong input value to start with. And our recompiled version is slightly less efficient than the original version because of conversions to float (300 instructions, vs. 291). Which might be why it shows correctly with the F9. Not 100% sure, but it is definitely inconsistent on launch.
The numbers you changed for E-6 were actually OK. I don't think it matters either way, but it created the numbers that were actually stored in the shader. It uses the binary versions nowadays, not the text output assembler.
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
@mrorange55
Thanks for the info....i normally enabled Vsync in the NVCP. I noticed that works best for most games (maybe some lame vsync implementation in games)...and in-game a normally use Vsync off and sometimes on when i have tearing (but normally is off in-game). But in this game i have normal 3D with or without vsync.
@bo3b
I will leave the Beta fix like that. Is a waste of time to dig more if the Beta have still some internal issues. I also experiment some crashes in the Beta.....with Battlefront never have a single crash.
@mrorange55
Thanks for the info....i normally enabled Vsync in the NVCP. I noticed that works best for most games (maybe some lame vsync implementation in games)...and in-game a normally use Vsync off and sometimes on when i have tearing (but normally is off in-game). But in this game i have normal 3D with or without vsync.
@bo3b
I will leave the Beta fix like that. Is a waste of time to dig more if the Beta have still some internal issues. I also experiment some crashes in the Beta.....with Battlefront never have a single crash.
You have 10 days to be able to roll back the Anniversary update.
I also encourage everyone to do what is in your best interest, not what works best for Microsoft. If they were doing a great job, that would be different, but it's gotten ridiculous.
3D Vision is a trailing edge technology, it's always going to work more smoothly and easily on Win7. Win10 is as leading edge as it gets. Anniversary is bleeding edge.
You can't live on the bleeding edge and the trailing edge at the same time.
For 3D gaming, everyone will have fewer hassles with a Win7 setup. Dual boot if needed.
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
You can try those thing. After this i don't have more ideas
1) Try with the 368.39 driver using DDU
2) Use Nvidia Inspector to assign B1 exe to Battlefront exe....if battlefront work, this game should works also.
3) Re-install the Open Beta game, maybe something is wrong with the installation.
Also for testing purpose....if you change in the d3dx.ini "hunting=0" for "hunting=1" you see the 3Dmigoto overlay? pressing F10 produce a beep sound?
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
I found setting hunting=1 would make the game freak out at launch, and give a ResizeBuffers assertion dialog. Unplayable.
Try the hunting=2 to get it up and running, then Numpad 0 to show overlay.
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
Re-installation did not help. Did this already.
Other profile assignement is not helping either.
I don't get the beep sound.
So the next thing I have to try is to re install the old driver, I suppose.
Concerning the anniversary update. I guess I should really de-install it. Since the 16th August I have like 20 different Updates.
- EDIT: D'Oh - my updating was before more than 10 days. I can't go back. What the heck?
Intel Core i7-3820, 4 X 3,60 GHz overclocked to 4,50 GHz ; EVGA Titan X 12VRAM ; 16 GB Corsair Vengeance DDR-1600 (4x 4 GB) ; Asus VG278H 27-inch incl. 3D vision 2 glasses, integrated transmitter ; Xbox One Elite wireless controller ; Windows 10HTC VIVE 2,5 m2 roomscale3D VISION GAMERS - VISIT ME ON STEAM and feel free to add me: http://steamcommunity.com/profiles/76561198064106555 YOUTUBE: https://www.youtube.com/channel/UC1UE5TPoF0HX0HVpF_E4uPQ STEAM CURATOR: https://store.steampowered.com/curator/33611530-Streaming-Deluxe/
2 more things to try:
1) Uninstall the fix and re-install... be sure that all the files are in the same place than the EXE.
2) When you try with the 368.39 driver using DDU....also try this driver with the hooking method:
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
OK, I took a look at this one, but I think the Decompiler is correct. I'm not seeing anything that seems out of the ordinary, and an ASM compare gives me pretty close results.
However, more importantly, when testing this, I had it launch without any problem a couple of times, without me doing anything.
Then to test further, I launched again with no changes whatsoever, and saw the effect come back.
So it's pretty clear this is a game bug of some form that we are making more obvious. Part of being Beta most likely.
My best guess is that it's timing related.
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
I found another reflections shader with the same white issue, it's almost the same than this one...i change the values XXXXXXXe-006 for the correct numbers present in the ASM and fix the white issue in this shader...Maybe is some kind of bug of the Beta like you says.
I will test a little more with the "if (r3.w == 0)" section you mention in the PM. THANKS!
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
I think we are on something here. I remember having the same problem with Battlefront, then I re-installed the fix one time and it was all fine.
What else, except the hook and the driver change might be possible to make sure the fix kicks in?
Intel Core i7-3820, 4 X 3,60 GHz overclocked to 4,50 GHz ; EVGA Titan X 12VRAM ; 16 GB Corsair Vengeance DDR-1600 (4x 4 GB) ; Asus VG278H 27-inch incl. 3D vision 2 glasses, integrated transmitter ; Xbox One Elite wireless controller ; Windows 10HTC VIVE 2,5 m2 roomscale3D VISION GAMERS - VISIT ME ON STEAM and feel free to add me: http://steamcommunity.com/profiles/76561198064106555 YOUTUBE: https://www.youtube.com/channel/UC1UE5TPoF0HX0HVpF_E4uPQ STEAM CURATOR: https://store.steampowered.com/curator/33611530-Streaming-Deluxe/
Only for testing.....remove weapon DOF and Motion Blur. Maybe the issue is related to the Motion Blur. I have both disabled.
Also try using Vsync Off in-game.
**EDIT:
You can try replacing the DLL (both) for a previous 3Dmigoto version. In this fix i'm using the last one.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
I replaced in the BF1 fix the three dll files with the ones from your Battlefront fix. And now it kicks in. :) We found the solution. Great.
Here a picture:
EDIT: TURN OFF VSYNC
Intel Core i7-3820, 4 X 3,60 GHz overclocked to 4,50 GHz ; EVGA Titan X 12VRAM ; 16 GB Corsair Vengeance DDR-1600 (4x 4 GB) ; Asus VG278H 27-inch incl. 3D vision 2 glasses, integrated transmitter ; Xbox One Elite wireless controller ; Windows 10HTC VIVE 2,5 m2 roomscale3D VISION GAMERS - VISIT ME ON STEAM and feel free to add me: http://steamcommunity.com/profiles/76561198064106555 YOUTUBE: https://www.youtube.com/channel/UC1UE5TPoF0HX0HVpF_E4uPQ STEAM CURATOR: https://store.steampowered.com/curator/33611530-Streaming-Deluxe/
You replace with the Battlefront DLL from my fix or the helifax fix?
is to take note about the 3Dmigoto version used. In my fix i use the 1.2.39....maybe a bug is introduced in newer versions of 3Dmigoto in some configurations.
Why your sky is cut-off in the sides...i fix that cut-off issue in Battlefront and B1....very strange.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Intel Core i7-3820, 4 X 3,60 GHz overclocked to 4,50 GHz ; EVGA Titan X 12VRAM ; 16 GB Corsair Vengeance DDR-1600 (4x 4 GB) ; Asus VG278H 27-inch incl. 3D vision 2 glasses, integrated transmitter ; Xbox One Elite wireless controller ; Windows 10HTC VIVE 2,5 m2 roomscale3D VISION GAMERS - VISIT ME ON STEAM and feel free to add me: http://steamcommunity.com/profiles/76561198064106555 YOUTUBE: https://www.youtube.com/channel/UC1UE5TPoF0HX0HVpF_E4uPQ STEAM CURATOR: https://store.steampowered.com/curator/33611530-Streaming-Deluxe/
Yeah, this game has some funny launch for me. Sometimes it works and sometimes it does not. I even did a quit to main menu without leaving the game, and one time it was OK, one time it had whiteness.
Maybe try experimenting with cache and stereo off. When the shader is cached it seems slightly more often to startup OK. Also had it draw correctly after disabling 3D with Ctrl-T during loading, but that wasn't fully consistent.
I think it's getting in a race condition with another shader, probably a compute shader, and gets the wrong input value to start with. And our recompiled version is slightly less efficient than the original version because of conversions to float (300 instructions, vs. 291). Which might be why it shows correctly with the F9. Not 100% sure, but it is definitely inconsistent on launch.
The numbers you changed for E-6 were actually OK. I don't think it matters either way, but it created the numbers that were actually stored in the shader. It uses the binary versions nowadays, not the text output assembler.
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
Thanks for the info....i normally enabled Vsync in the NVCP. I noticed that works best for most games (maybe some lame vsync implementation in games)...and in-game a normally use Vsync off and sometimes on when i have tearing (but normally is off in-game). But in this game i have normal 3D with or without vsync.
@bo3b
I will leave the Beta fix like that. Is a waste of time to dig more if the Beta have still some internal issues. I also experiment some crashes in the Beta.....with Battlefront never have a single crash.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com