Assassin's Creed 3 - real 3D game fix, beta release
1 / 10
[img]http://sg.bo3b.net/AC3SP1_dock.jpg[/img]
Today we have something very interesting, and we hope, fun! We've got a new fix for Assassin's Creed 3!
[b]That's right, a true DX11 fix, using 3Dmigoto.[/b]
[i]Please [/i]note that this is a Beta release. We know there are some problems with the shader fixes themselves, and 3Dmigoto is probably going to have some bugs as well.
We are releasing it as Beta instead of complete, because it's easily in a playable state, and we want to get feedback on how well it's working and if you see any problems. As a first fix using 3Dmigoto, we cannot be sure how well it's going to work.
Please give us feedback in this thread to let us know what you think, or detail problems you run into.
How to use it:
[u]1) Make sure you have a platform patch installed. [/u]
This is an optional graphics patch from Microsoft. You need this update to avoid having 3Dmigoto crash.
You can look in your View Installed Updates, and search for KB2670838.
If you don't have it, you can get it here:
[url]http://www.microsoft.com/en-us/download/details.aspx?id=36805[/url]
[u]2) Run the game once to make sure it's installed, resolution and refresh are like you want.[/u]
Make sure 3D kicks in.
In game settings, you'll want Environmental Quality set to Normal. Frame rates jump from 18 to 30 in Boston, with this one setting. All other settings can be at max.
[u]3) If you are running recent drivers, and Compatibility Mode is kicking in, do Ctrl-Alt-F11 to disable it.[/u]
It doesn't hurt to have it enabled, but it competes with the fix, and adds haloing around close objects.
We've tested it on older drivers like 320.49 and the most recent Beta, and think it should work in all cases.
We've tested it with SLI and single GPU.
[u]4) Get the fix as a zip file from here:[/u] [url]https://github.com/bo3b/3Dmigoto/releases/download/0.6-beta/3Dmigoto-AC3-0.6_Beta.zip[/url]
And unzip all of the files and ShaderFixes folder into the Assassin's Creed 3 exe folder.
e.g. "T:\SteamLibrary\SteamApps\common\Assassin's Creed 3\"
It's a lot of files, 500 shader files, and 16 dlls, an uninstall, and the .ini file. It's still a work in progress.
If you need to uninstall, there is an uninstall.bat that will delete the dlls.
[u]5) With all that installed, run AC3.[/u]
You should be able to see everything in 3D, and be able to change depth and convergence.
Performance should be good, very close to what you normally get with AC3 in 3D. You should see all of your CPU cores active.
First launch will be slow, like a minute, as it caches shaders.
Big, big thanks to many people. This was definitely a team effort.
Let's give a particularly big [i]Thank You[/i] to Mike_ar69 for actually making the fix. Seriously, the man is a genius, and managed to figure out how to fix shaders in the game and learn how to fix a game using the brand new 3Dmigoto approach, which has had and still has rough spots. Without Mike's work here, we would have nothing.
Let's also note that Chiri made this possible by allowing us to open-source 3Dmigoto. It simply would not have been possible without the source code.
Airion was our top voter on the wishlist for AC3 ([url]http://lists.bo3b.net/wish/[/url]), so we punished and rewarded him by giving him an early look. Huge thanks go to him for finding and reporting shader glitches in game, doing lots of testing, and giving us the final push that it really needed to be released.
I'd personally like to thank eqzitara and Airion for putting in some great effort to help me track down a crash that would only happen on their machines, not on my test machines. Finding remote crashes is one of the hardest things to debug. After 6 builds, I think we were all ready to have me fix it already.
Lastly I'd like to thank Flugan for some early help on fixing 3Dmigoto, help working out some of the Decompiler problems, and the uninstall batch file.
Today we have something very interesting, and we hope, fun! We've got a new fix for Assassin's Creed 3!
That's right, a true DX11 fix, using 3Dmigoto.
Please note that this is a Beta release. We know there are some problems with the shader fixes themselves, and 3Dmigoto is probably going to have some bugs as well.
We are releasing it as Beta instead of complete, because it's easily in a playable state, and we want to get feedback on how well it's working and if you see any problems. As a first fix using 3Dmigoto, we cannot be sure how well it's going to work.
Please give us feedback in this thread to let us know what you think, or detail problems you run into.
How to use it:
1) Make sure you have a platform patch installed.
This is an optional graphics patch from Microsoft. You need this update to avoid having 3Dmigoto crash.
You can look in your View Installed Updates, and search for KB2670838.
If you don't have it, you can get it here: http://www.microsoft.com/en-us/download/details.aspx?id=36805
2) Run the game once to make sure it's installed, resolution and refresh are like you want.
Make sure 3D kicks in.
In game settings, you'll want Environmental Quality set to Normal. Frame rates jump from 18 to 30 in Boston, with this one setting. All other settings can be at max.
3) If you are running recent drivers, and Compatibility Mode is kicking in, do Ctrl-Alt-F11 to disable it.
It doesn't hurt to have it enabled, but it competes with the fix, and adds haloing around close objects.
We've tested it on older drivers like 320.49 and the most recent Beta, and think it should work in all cases.
We've tested it with SLI and single GPU.
And unzip all of the files and ShaderFixes folder into the Assassin's Creed 3 exe folder.
e.g. "T:\SteamLibrary\SteamApps\common\Assassin's Creed 3\"
It's a lot of files, 500 shader files, and 16 dlls, an uninstall, and the .ini file. It's still a work in progress.
If you need to uninstall, there is an uninstall.bat that will delete the dlls.
5) With all that installed, run AC3.
You should be able to see everything in 3D, and be able to change depth and convergence.
Performance should be good, very close to what you normally get with AC3 in 3D. You should see all of your CPU cores active.
First launch will be slow, like a minute, as it caches shaders.
Big, big thanks to many people. This was definitely a team effort.
Let's give a particularly big Thank You to Mike_ar69 for actually making the fix. Seriously, the man is a genius, and managed to figure out how to fix shaders in the game and learn how to fix a game using the brand new 3Dmigoto approach, which has had and still has rough spots. Without Mike's work here, we would have nothing.
Let's also note that Chiri made this possible by allowing us to open-source 3Dmigoto. It simply would not have been possible without the source code.
Airion was our top voter on the wishlist for AC3 (http://lists.bo3b.net/wish/), so we punished and rewarded him by giving him an early look. Huge thanks go to him for finding and reporting shader glitches in game, doing lots of testing, and giving us the final push that it really needed to be released.
I'd personally like to thank eqzitara and Airion for putting in some great effort to help me track down a crash that would only happen on their machines, not on my test machines. Finding remote crashes is one of the hardest things to debug. After 6 builds, I think we were all ready to have me fix it already.
Lastly I'd like to thank Flugan for some early help on fixing 3Dmigoto, help working out some of the Decompiler problems, and the uninstall batch file.
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
Naturally, there are known issues that we have not quite been able to resolve, but we think they are minor enough to not hold up the Beta release. I'll add to this list as you find more.
The game has been tested using SLI and non-SLI, on 500, 600, and 700 series cards, on monitors and projectors, and at 1080p and 720p. Old 320.49 drivers, and latest Beta. Clearly there may be other configurations for which there are issues.
Please report glitches that you've find, with some idea on location in game, and include a JPS if you can.
-----------------------------
1. Triangles in the animus look wrong
2. There is an AO issue on ship sails, and some wall surfaces, if the angle of view is very narrow
3. There might still be the odd minor shadow issue in cutscenes
4. The Moon renders wrong in an early cut scene on the ship
5. The moon renders at a slightly deeper depth than stars in gameplay scenes
6. Some decals have been disabled (for now) - blood splatters on the ground, explosion marks etc. If you turn off 3D they come back again
7. This game has an Nvidia Depth Buffer profile, accessible by pressing Ctrl-Alt-F11. However, it is not completely decoupled from the 3DMigoto fix, and when toggling the depth buffer on, the shadows will be rendered incorrectly (not at 2D though, just in the wrong place). Just bear that in mind - to get the 'best' from the depth buffer approach, you need to disable/remove the 3DMigoto fix. You disable it easily using the uninstall.bat.
8. The fix does not seem to work properly if you try and use the registry depth hack - shadows render at the wrong depth.
9. Presently incompatible with Windows 8.1 64 Bit Update 1. 3Dmigoto won't run. (Edit: workaround is to delete the dxgi.dll file)
Naturally, there are known issues that we have not quite been able to resolve, but we think they are minor enough to not hold up the Beta release. I'll add to this list as you find more.
The game has been tested using SLI and non-SLI, on 500, 600, and 700 series cards, on monitors and projectors, and at 1080p and 720p. Old 320.49 drivers, and latest Beta. Clearly there may be other configurations for which there are issues.
Please report glitches that you've find, with some idea on location in game, and include a JPS if you can.
-----------------------------
1. Triangles in the animus look wrong
2. There is an AO issue on ship sails, and some wall surfaces, if the angle of view is very narrow
3. There might still be the odd minor shadow issue in cutscenes
4. The Moon renders wrong in an early cut scene on the ship
5. The moon renders at a slightly deeper depth than stars in gameplay scenes
6. Some decals have been disabled (for now) - blood splatters on the ground, explosion marks etc. If you turn off 3D they come back again
7. This game has an Nvidia Depth Buffer profile, accessible by pressing Ctrl-Alt-F11. However, it is not completely decoupled from the 3DMigoto fix, and when toggling the depth buffer on, the shadows will be rendered incorrectly (not at 2D though, just in the wrong place). Just bear that in mind - to get the 'best' from the depth buffer approach, you need to disable/remove the 3DMigoto fix. You disable it easily using the uninstall.bat.
8. The fix does not seem to work properly if you try and use the registry depth hack - shadows render at the wrong depth.
9. Presently incompatible with Windows 8.1 64 Bit Update 1. 3Dmigoto won't run. (Edit: workaround is to delete the dxgi.dll file)
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
Benq W1070/W1080ST users will probably need an EDID override to get the game to run in 720p (there are options in the 3Dmigoto ini to force it, but they didn't work for me). See this thread: [url]https://forums.geforce.com/default/topic/573000/3d-vision/benq-w-1080st-3dtv-play-help/2/[/url]
[quote="bo3b"]Airion was our top voter on the wishlist for AC3 ([url]http://lists.bo3b.net/wish/[/url]), so we punished and rewarded him by giving him an early look.[/quote]
It was like being an ice cream taste-tester! So a big thanks to both you and Mike_ar69 for all your work and talents. I thought a fix like this would probably never happen.
bo3b said:Airion was our top voter on the wishlist for AC3 (http://lists.bo3b.net/wish/), so we punished and rewarded him by giving him an early look.
It was like being an ice cream taste-tester! So a big thanks to both you and Mike_ar69 for all your work and talents. I thought a fix like this would probably never happen.
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
nvidia inspector -> Assassin's Creed III -> remove app from current profile -> ac3sp.exe
this gives me a 40 % fps boost in boston.
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
[quote="Kingping1"]nvidia inspector -> Assassin's Creed III -> remove app from current profile -> ac3sp.exe
this gives me a 40 % fps boost in boston.[/quote]
Wow, I'm gonna try me some of that...
[quote="bo3b"][img]http://sg.bo3b.net/AC3SP1_dock.jpg[/img]
Today we have something very interesting, and we hope, fun! We've got a new fix for Assassin's Creed 3!
[b]That's right, a true DX11 fix, using 3Dmigoto.[/b]
[i]Please [/i]note that this is a Beta release. We know there are some problems with the shader fixes themselves, and 3Dmigoto is probably going to have some bugs as well.
We are releasing it as Beta instead of complete, because it's easily in a playable state, and we want to get feedback on how well it's working and if you see any problems. As a first fix using 3Dmigoto, we cannot be sure how well it's going to work.
Please give us feedback in this thread to let us know what you think, or detail problems you run into.
How to use it:
[u]1) Make sure you have a platform patch installed. [/u]
This is an optional graphics patch from Microsoft. You need this update to avoid having 3Dmigoto crash.
You can look in your View Installed Updates, and search for KB2670838.
If you don't have it, you can get it here:
[url]http://www.microsoft.com/en-us/download/details.aspx?id=36805[/url]
[u]2) Run the game once to make sure it's installed, resolution and refresh are like you want.[/u]
Make sure 3D kicks in.
In game settings, you'll want Environmental Quality set to Normal. Frame rates jump from 18 to 30 in Boston, with this one setting. All other settings can be at max.
[u]3) If you are running recent drivers, and Compatibility Mode is kicking in, do Ctrl-Alt-F11 to disable it.[/u]
It doesn't hurt to have it enabled, but it competes with the fix, and adds haloing around close objects.
We've tested it on older drivers like 320.49 and the most recent Beta, and think it should work in all cases.
We've tested it with SLI and single GPU.
[u]4) Get the fix as a zip file from here:[/u] [url]https://github.com/bo3b/3Dmigoto/releases/download/0.6-beta/3Dmigoto-AC3-0.6_Beta.zip[/url]
And unzip all of the files and ShaderFixes folder into the Assassin's Creed 3 exe folder.
e.g. "T:\SteamLibrary\SteamApps\common\Assassin's Creed 3\"
It's a lot of files, 500 shader files, and 16 dlls, an uninstall, and the .ini file. It's still a work in progress.
If you need to uninstall, there is an uninstall.bat that will delete the dlls.
[u]5) With all that installed, run AC3.[/u]
You should be able to see everything in 3D, and be able to change depth and convergence.
Performance should be good, very close to what you normally get with AC3 in 3D. You should see all of your CPU cores active.
First launch will be slow, like a minute, as it caches shaders.
Big, big thanks to many people. This was definitely a team effort.
Let's give a particularly big [i]Thank You[/i] to Mike_ar69 for actually making the fix. Seriously, the man is a genius, and managed to figure out how to fix shaders in the game and learn how to fix a game using the brand new 3Dmigoto approach, which has had and still has rough spots. Without Mike's work here, we would have nothing.
Let's also note that Chiri made this possible by allowing us to open-source 3Dmigoto. It simply would not have been possible without the source code.
Airion was our top voter on the wishlist for AC3 ([url]http://lists.bo3b.net/wish/[/url]), so we punished and rewarded him by giving him an early look. Huge thanks go to him for finding and reporting shader glitches in game, doing lots of testing, and giving us the final push that it really needed to be released.
I'd personally like to thank eqzitara and Airion for putting in some great effort to help me track down a crash that would only happen on their machines, not on my test machines. Finding remote crashes is one of the hardest things to debug. After 6 builds, I think we were all ready to have me fix it already.
Lastly I'd like to thank Flugan for some early help on fixing 3Dmigoto, help working out some of the Decompiler problems, and the uninstall batch file.[/quote]
I'd like to emphasize what a fantastic job bo3b has done, and continues to do, developing the 3DMigoto wrapper - as people probably gather, this is a very complicated undertaking and bo3b has taken control of it completely, working it out and fixing some extremely tricky issues. It's been great working together on this, and we have a few more games in our pipeline to move 3DMigoto further towards becoming a general purpose DX11 wrapper. We hope and expect AC3 to be just the beginning.
Today we have something very interesting, and we hope, fun! We've got a new fix for Assassin's Creed 3!
That's right, a true DX11 fix, using 3Dmigoto.
Please note that this is a Beta release. We know there are some problems with the shader fixes themselves, and 3Dmigoto is probably going to have some bugs as well.
We are releasing it as Beta instead of complete, because it's easily in a playable state, and we want to get feedback on how well it's working and if you see any problems. As a first fix using 3Dmigoto, we cannot be sure how well it's going to work.
Please give us feedback in this thread to let us know what you think, or detail problems you run into.
How to use it:
1) Make sure you have a platform patch installed.
This is an optional graphics patch from Microsoft. You need this update to avoid having 3Dmigoto crash.
You can look in your View Installed Updates, and search for KB2670838.
If you don't have it, you can get it here: http://www.microsoft.com/en-us/download/details.aspx?id=36805
2) Run the game once to make sure it's installed, resolution and refresh are like you want.
Make sure 3D kicks in.
In game settings, you'll want Environmental Quality set to Normal. Frame rates jump from 18 to 30 in Boston, with this one setting. All other settings can be at max.
3) If you are running recent drivers, and Compatibility Mode is kicking in, do Ctrl-Alt-F11 to disable it.
It doesn't hurt to have it enabled, but it competes with the fix, and adds haloing around close objects.
We've tested it on older drivers like 320.49 and the most recent Beta, and think it should work in all cases.
We've tested it with SLI and single GPU.
And unzip all of the files and ShaderFixes folder into the Assassin's Creed 3 exe folder.
e.g. "T:\SteamLibrary\SteamApps\common\Assassin's Creed 3\"
It's a lot of files, 500 shader files, and 16 dlls, an uninstall, and the .ini file. It's still a work in progress.
If you need to uninstall, there is an uninstall.bat that will delete the dlls.
5) With all that installed, run AC3.
You should be able to see everything in 3D, and be able to change depth and convergence.
Performance should be good, very close to what you normally get with AC3 in 3D. You should see all of your CPU cores active.
First launch will be slow, like a minute, as it caches shaders.
Big, big thanks to many people. This was definitely a team effort.
Let's give a particularly big Thank You to Mike_ar69 for actually making the fix. Seriously, the man is a genius, and managed to figure out how to fix shaders in the game and learn how to fix a game using the brand new 3Dmigoto approach, which has had and still has rough spots. Without Mike's work here, we would have nothing.
Let's also note that Chiri made this possible by allowing us to open-source 3Dmigoto. It simply would not have been possible without the source code.
Airion was our top voter on the wishlist for AC3 (http://lists.bo3b.net/wish/), so we punished and rewarded him by giving him an early look. Huge thanks go to him for finding and reporting shader glitches in game, doing lots of testing, and giving us the final push that it really needed to be released.
I'd personally like to thank eqzitara and Airion for putting in some great effort to help me track down a crash that would only happen on their machines, not on my test machines. Finding remote crashes is one of the hardest things to debug. After 6 builds, I think we were all ready to have me fix it already.
Lastly I'd like to thank Flugan for some early help on fixing 3Dmigoto, help working out some of the Decompiler problems, and the uninstall batch file.
I'd like to emphasize what a fantastic job bo3b has done, and continues to do, developing the 3DMigoto wrapper - as people probably gather, this is a very complicated undertaking and bo3b has taken control of it completely, working it out and fixing some extremely tricky issues. It's been great working together on this, and we have a few more games in our pipeline to move 3DMigoto further towards becoming a general purpose DX11 wrapper. We hope and expect AC3 to be just the beginning.
[quote="bo3b"]Naturally, there are known issues that we have not quite been able to resolve, but we think they are minor enough to not hold up the Beta release. I'll add to this list as you find more.
The game has been tested using SLI and non-SLI, on 500, 600, and 700 series cards, on monitors and projectors, and at 1080p and 720p. Old 320.49 drivers, and latest Beta. Clearly there may be other configurations for which there are issues.
Please report glitches that you've find, with some idea on location in game, and include a JPS if you can.
-----------------------------
1. Triangles in the animus look wrong
2. There is an AO issue on ship sails, and some wall surfaces, if the angle of view is very narrow
3. There might still be the odd minor shadow issue in cutscenes
4. The Moon renders wrong in an early cut scene on the ship
5. The moon renders at a slightly deeper depth than stars in gameplay scenes
6. Some decals have been disabled (for now) - blood splatters on the ground, explosion marks etc. If you turn off 3D they come back again
7. This game has an Nvidia Depth Buffer profile, accessible by pressing Ctrl-Alt-F11. However, it is not completely decoupled from the 3DMigoto fix, and when toggling the depth buffer on, the shadows will be rendered incorrectly (not at 2D though, just in the wrong place). Just bear that in mind - to get the 'best' from the depth buffer approach, you need to disable/remove the 3DMigoto fix. You disable it easily using the uninstall.bat.
8. The fix does not seem to work properly if you try and use the registry depth hack - shadows render at the wrong depth.
[/quote]
One more thing I will mention is how we did the HUD. The HUD in this game is all coupled together with other things like the sun and moon, bloom, menus etc, so the solution used in this beta fix pushes the hud to a constant and uniform depth, which was a fortuitous sweet spot. The game itself gives a lot of control over what parts of the hud are visible, so an alternative that has been used in testing is to turn everything off except the minimap, and then the minimap can be at a lower depth and hence be a little less 'intrusive'. We will make this available shortly.
bo3b said:Naturally, there are known issues that we have not quite been able to resolve, but we think they are minor enough to not hold up the Beta release. I'll add to this list as you find more.
The game has been tested using SLI and non-SLI, on 500, 600, and 700 series cards, on monitors and projectors, and at 1080p and 720p. Old 320.49 drivers, and latest Beta. Clearly there may be other configurations for which there are issues.
Please report glitches that you've find, with some idea on location in game, and include a JPS if you can.
-----------------------------
1. Triangles in the animus look wrong
2. There is an AO issue on ship sails, and some wall surfaces, if the angle of view is very narrow
3. There might still be the odd minor shadow issue in cutscenes
4. The Moon renders wrong in an early cut scene on the ship
5. The moon renders at a slightly deeper depth than stars in gameplay scenes
6. Some decals have been disabled (for now) - blood splatters on the ground, explosion marks etc. If you turn off 3D they come back again
7. This game has an Nvidia Depth Buffer profile, accessible by pressing Ctrl-Alt-F11. However, it is not completely decoupled from the 3DMigoto fix, and when toggling the depth buffer on, the shadows will be rendered incorrectly (not at 2D though, just in the wrong place). Just bear that in mind - to get the 'best' from the depth buffer approach, you need to disable/remove the 3DMigoto fix. You disable it easily using the uninstall.bat.
8. The fix does not seem to work properly if you try and use the registry depth hack - shadows render at the wrong depth.
One more thing I will mention is how we did the HUD. The HUD in this game is all coupled together with other things like the sun and moon, bloom, menus etc, so the solution used in this beta fix pushes the hud to a constant and uniform depth, which was a fortuitous sweet spot. The game itself gives a lot of control over what parts of the hud are visible, so an alternative that has been used in testing is to turn everything off except the minimap, and then the minimap can be at a lower depth and hence be a little less 'intrusive'. We will make this available shortly.
THIS is GREAT news!!!
Just tested and works wonder...also remove the profile with Nvidia inspector and with 3DTV Play i have great performance....finally i can play this game (with Tridef this game have a poor performance).
Thanks to bo3b and mike for this fantastic job... i will test and report back if i found anything strange.
CHEERS!!!!
Just tested and works wonder...also remove the profile with Nvidia inspector and with 3DTV Play i have great performance....finally i can play this game (with Tridef this game have a poor performance).
Thanks to bo3b and mike for this fantastic job... i will test and report back if i found anything strange.
You guys are incredible!
I don't know what to say, i'm usually a well-spoken person but I'm speechless.
I've tested the fix for a couple of hours, mostly playing the King Washington DLC.
The game is breathtaking in true 3D!
I only played very briefly some naval combat, water seems fine, horizon line is a little fuzzy or something, nothing major.
The only thing I could spot was a minor character shadow problem, depending on the costume / auxiliary weapon, the shadow of this weapon is drawn at an offset from the main shadow. In the DLC it was the arrow bag, and in the main game it was a sword.
Will keep testing and give feedback.
Congratulations guys, and let this be the dawn of a golden age for community fixes.
Hats off to Bob, Mike, and the rest.
THANK YOU FOR YOUR GIFT!!!
You guys are incredible!
I don't know what to say, i'm usually a well-spoken person but I'm speechless.
I've tested the fix for a couple of hours, mostly playing the King Washington DLC.
The game is breathtaking in true 3D!
I only played very briefly some naval combat, water seems fine, horizon line is a little fuzzy or something, nothing major.
The only thing I could spot was a minor character shadow problem, depending on the costume / auxiliary weapon, the shadow of this weapon is drawn at an offset from the main shadow. In the DLC it was the arrow bag, and in the main game it was a sword.
Will keep testing and give feedback.
Congratulations guys, and let this be the dawn of a golden age for community fixes.
Hats off to Bob, Mike, and the rest.
THANK YOU FOR YOUR GIFT!!!
[quote="Zappologist"]You guys are incredible!
I don't know what to say, i'm usually a well-spoken person but I'm speechless.
I've tested the fix for a couple of hours, mostly playing the King Washington DLC.
The game is breathtaking in true 3D!
I only played very briefly some naval combat, water seems fine, horizon line is a little fuzzy or something, nothing major.
The only thing I could spot was a minor character shadow problem, depending on the costume / auxiliary weapon, the shadow of this weapon is drawn at an offset from the main shadow. In the DLC it was the arrow bag, and in the main game it was a sword.
Will keep testing and give feedback.
Congratulations guys, and let this be the dawn of a golden age for community fixes.
Hats off to Bob, Mike, and the rest.
THANK YOU FOR YOUR GIFT!!![/quote]
Thank you for the feedback :-) I think I might know what you are referring to with the shadow thing. If it what I think then it happens in 2D as well. I think it's the AO, which has other issues as well, even in 2D. If you see it again, toggle 3D off and see if it's still there - if not, then it is something I can look at. Thanks again.
Zappologist said:You guys are incredible!
I don't know what to say, i'm usually a well-spoken person but I'm speechless.
I've tested the fix for a couple of hours, mostly playing the King Washington DLC.
The game is breathtaking in true 3D!
I only played very briefly some naval combat, water seems fine, horizon line is a little fuzzy or something, nothing major.
The only thing I could spot was a minor character shadow problem, depending on the costume / auxiliary weapon, the shadow of this weapon is drawn at an offset from the main shadow. In the DLC it was the arrow bag, and in the main game it was a sword.
Will keep testing and give feedback.
Congratulations guys, and let this be the dawn of a golden age for community fixes.
Hats off to Bob, Mike, and the rest.
THANK YOU FOR YOUR GIFT!!!
Thank you for the feedback :-) I think I might know what you are referring to with the shadow thing. If it what I think then it happens in 2D as well. I think it's the AO, which has other issues as well, even in 2D. If you see it again, toggle 3D off and see if it's still there - if not, then it is something I can look at. Thanks again.
Today we have something very interesting, and we hope, fun! We've got a new fix for Assassin's Creed 3!
That's right, a true DX11 fix, using 3Dmigoto.
Please note that this is a Beta release. We know there are some problems with the shader fixes themselves, and 3Dmigoto is probably going to have some bugs as well.
We are releasing it as Beta instead of complete, because it's easily in a playable state, and we want to get feedback on how well it's working and if you see any problems. As a first fix using 3Dmigoto, we cannot be sure how well it's going to work.
Please give us feedback in this thread to let us know what you think, or detail problems you run into.
How to use it:
1) Make sure you have a platform patch installed.
This is an optional graphics patch from Microsoft. You need this update to avoid having 3Dmigoto crash.
You can look in your View Installed Updates, and search for KB2670838.
If you don't have it, you can get it here:
http://www.microsoft.com/en-us/download/details.aspx?id=36805
2) Run the game once to make sure it's installed, resolution and refresh are like you want.
Make sure 3D kicks in.
In game settings, you'll want Environmental Quality set to Normal. Frame rates jump from 18 to 30 in Boston, with this one setting. All other settings can be at max.
3) If you are running recent drivers, and Compatibility Mode is kicking in, do Ctrl-Alt-F11 to disable it.
It doesn't hurt to have it enabled, but it competes with the fix, and adds haloing around close objects.
We've tested it on older drivers like 320.49 and the most recent Beta, and think it should work in all cases.
We've tested it with SLI and single GPU.
4) Get the fix as a zip file from here: https://github.com/bo3b/3Dmigoto/releases/download/0.6-beta/3Dmigoto-AC3-0.6_Beta.zip
And unzip all of the files and ShaderFixes folder into the Assassin's Creed 3 exe folder.
e.g. "T:\SteamLibrary\SteamApps\common\Assassin's Creed 3\"
It's a lot of files, 500 shader files, and 16 dlls, an uninstall, and the .ini file. It's still a work in progress.
If you need to uninstall, there is an uninstall.bat that will delete the dlls.
5) With all that installed, run AC3.
You should be able to see everything in 3D, and be able to change depth and convergence.
Performance should be good, very close to what you normally get with AC3 in 3D. You should see all of your CPU cores active.
First launch will be slow, like a minute, as it caches shaders.
Big, big thanks to many people. This was definitely a team effort.
Let's give a particularly big Thank You to Mike_ar69 for actually making the fix. Seriously, the man is a genius, and managed to figure out how to fix shaders in the game and learn how to fix a game using the brand new 3Dmigoto approach, which has had and still has rough spots. Without Mike's work here, we would have nothing.
Let's also note that Chiri made this possible by allowing us to open-source 3Dmigoto. It simply would not have been possible without the source code.
Airion was our top voter on the wishlist for AC3 (http://lists.bo3b.net/wish/), so we punished and rewarded him by giving him an early look. Huge thanks go to him for finding and reporting shader glitches in game, doing lots of testing, and giving us the final push that it really needed to be released.
I'd personally like to thank eqzitara and Airion for putting in some great effort to help me track down a crash that would only happen on their machines, not on my test machines. Finding remote crashes is one of the hardest things to debug. After 6 builds, I think we were all ready to have me fix it already.
Lastly I'd like to thank Flugan for some early help on fixing 3Dmigoto, help working out some of the Decompiler problems, and the uninstall batch file.
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
The game has been tested using SLI and non-SLI, on 500, 600, and 700 series cards, on monitors and projectors, and at 1080p and 720p. Old 320.49 drivers, and latest Beta. Clearly there may be other configurations for which there are issues.
Please report glitches that you've find, with some idea on location in game, and include a JPS if you can.
-----------------------------
1. Triangles in the animus look wrong
2. There is an AO issue on ship sails, and some wall surfaces, if the angle of view is very narrow
3. There might still be the odd minor shadow issue in cutscenes
4. The Moon renders wrong in an early cut scene on the ship
5. The moon renders at a slightly deeper depth than stars in gameplay scenes
6. Some decals have been disabled (for now) - blood splatters on the ground, explosion marks etc. If you turn off 3D they come back again
7. This game has an Nvidia Depth Buffer profile, accessible by pressing Ctrl-Alt-F11. However, it is not completely decoupled from the 3DMigoto fix, and when toggling the depth buffer on, the shadows will be rendered incorrectly (not at 2D though, just in the wrong place). Just bear that in mind - to get the 'best' from the depth buffer approach, you need to disable/remove the 3DMigoto fix. You disable it easily using the uninstall.bat.
8. The fix does not seem to work properly if you try and use the registry depth hack - shadows render at the wrong depth.
9. Presently incompatible with Windows 8.1 64 Bit Update 1. 3Dmigoto won't run. (Edit: workaround is to delete the dxgi.dll file)
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
It was like being an ice cream taste-tester! So a big thanks to both you and Mike_ar69 for all your work and talents. I thought a fix like this would probably never happen.
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
this gives me a 40 % fps boost in boston.
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
But will give it a go to see how it look in 3d :)
Wow, I'm gonna try me some of that...
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
I'd like to emphasize what a fantastic job bo3b has done, and continues to do, developing the 3DMigoto wrapper - as people probably gather, this is a very complicated undertaking and bo3b has taken control of it completely, working it out and fixing some extremely tricky issues. It's been great working together on this, and we have a few more games in our pipeline to move 3DMigoto further towards becoming a general purpose DX11 wrapper. We hope and expect AC3 to be just the beginning.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
One more thing I will mention is how we did the HUD. The HUD in this game is all coupled together with other things like the sun and moon, bloom, menus etc, so the solution used in this beta fix pushes the hud to a constant and uniform depth, which was a fortuitous sweet spot. The game itself gives a lot of control over what parts of the hud are visible, so an alternative that has been used in testing is to turn everything off except the minimap, and then the minimap can be at a lower depth and hence be a little less 'intrusive'. We will make this available shortly.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
Just tested and works wonder...also remove the profile with Nvidia inspector and with 3DTV Play i have great performance....finally i can play this game (with Tridef this game have a poor performance).
Thanks to bo3b and mike for this fantastic job... i will test and report back if i found anything strange.
CHEERS!!!!
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Keep it it!
Gigabyte Z370 Gaming 7 32GB Ram i9-9900K GigaByte Aorus Extreme Gaming 2080TI (single) Game Blaster Z Windows 10 X64 build #17763.195 Define R6 Blackout Case Corsair H110i GTX Sandisk 1TB (OS) SanDisk 2TB SSD (Games) Seagate EXOs 8 and 12 TB drives Samsung UN46c7000 HD TV Samsung UN55HU9000 UHD TVCurrently using ACER PASSIVE EDID override on 3D TVs LG 55
Core i7-4700 HQ - GTX 970 - Windows 7 - VG248QE - 3Dvision 2
I don't know what to say, i'm usually a well-spoken person but I'm speechless.
I've tested the fix for a couple of hours, mostly playing the King Washington DLC.
The game is breathtaking in true 3D!
I only played very briefly some naval combat, water seems fine, horizon line is a little fuzzy or something, nothing major.
The only thing I could spot was a minor character shadow problem, depending on the costume / auxiliary weapon, the shadow of this weapon is drawn at an offset from the main shadow. In the DLC it was the arrow bag, and in the main game it was a sword.
Will keep testing and give feedback.
Congratulations guys, and let this be the dawn of a golden age for community fixes.
Hats off to Bob, Mike, and the rest.
THANK YOU FOR YOUR GIFT!!!
Thank you for the feedback :-) I think I might know what you are referring to with the shadow thing. If it what I think then it happens in 2D as well. I think it's the AO, which has other issues as well, even in 2D. If you see it again, toggle 3D off and see if it's still there - if not, then it is something I can look at. Thanks again.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278