Yeah, I tried out compatibility mode last night as well while I was trying out CMU for the first time, and it was definitely nice to get some extra FPS, and not experience the occasional effect glitch that occurs with the real 3D fix, but I found the halos a bit too distracting here (especially how it looks when flying, which you do a lot) and went back to my 3D fix.
BTW, I created a post on the Helix blog about a week ago and uploaded a newer version of the fix there, so the one in my earlier post is outdated and you might want to edit your first post to link to the blog instead. Here's the link: http://helixmod.blogspot.com/2019/02/anthem.html
Yeah, I tried out compatibility mode last night as well while I was trying out CMU for the first time, and it was definitely nice to get some extra FPS, and not experience the occasional effect glitch that occurs with the real 3D fix, but I found the halos a bit too distracting here (especially how it looks when flying, which you do a lot) and went back to my 3D fix.
BTW, I created a post on the Helix blog about a week ago and uploaded a newer version of the fix there, so the one in my earlier post is outdated and you might want to edit your first post to link to the blog instead. Here's the link: http://helixmod.blogspot.com/2019/02/anthem.html
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
The 3D glitches are fairly infrequent (and due to a bug in the FB3 engine rather than the game itself, btw), and happen only on certain effects like clouds, which although can break immersion are not super distracting to the gameplay, although sometimes can happen on fire effects during combat which can be a little more distracting but not gamebreakingly so. You can play for a whole day, maybe even a week and not experience it, or maybe come across it a couple times in the same gaming session. Darkstarsword has posted up a method he used to fix a somewhat similar issue in another game that I'll take a look at implementing in this game over the weekend... problem is with the issue being infrequent and not methodically reproducible it'll be hard for me to know if it actually worked vs the game being on good behavior, lol.
I would rate it as an 8/10 in terms of 3D fidelity alone, and because I'm spoiled with usually being able to incorporate autodepth adjustment on in game HUD items in my fixes (which I wasn't able to do with this engine) I'd dock it another half mark down to a 7.5/10 for that. It really only bugs me while in Fort Tarsis, the between mission HUB area, so not particularly crucial to have it here since it's a leisurely area, I'm just a nit picker because I know how nice it is to have in game waypoint markers at proper depth.
Overall I'd say the game is definitely worth a purchase, the core gameplay is absolutely amazing, and playing through the campaign alone makes it worth it, but there are some design philosophies (a lot of them revolving around the loot aspect of the game, as well as any concerns towards any long term endgame) that are keeping the game from being a leader in the genre, and the online/Reddit community is being extremely unforgiving due to the fact that a lot of these matters have already been experienced (and improved upon) in the games that have come before it, and with The Division 2 around the corner (which, I'm sad to report is that a proper 3D fix is not possible due to them using EasyAntiCheat) a lot of people are either holding off buying into Anthem or ready to jump ship. Anthem's devs have been as good at responding and dealing with situations accordingly, and it was always put out there that this game is in it's infancy and will develop over time, but again, almost no leeway is being given. Most people that have played the game and are honest about it's shortcomings (which I consider myself to be one of) agree that if/when the issues are all resolved the game will be one of, if not the best in the genre due to the actual gameplay.
Hope this helps you make your own, educated decision towards buying! Worst case scenario I can wholeheartedly suggest paying for a month of Origin Access to get to play the game during that period. You can easily experience everything the game currently has to offer in that timeframe for a fraction of the current cost of the game, and then maybe pick up the game in a sale later on when more improvements have come down the pipeline. That's what I did/may end up doing.
The 3D glitches are fairly infrequent (and due to a bug in the FB3 engine rather than the game itself, btw), and happen only on certain effects like clouds, which although can break immersion are not super distracting to the gameplay, although sometimes can happen on fire effects during combat which can be a little more distracting but not gamebreakingly so. You can play for a whole day, maybe even a week and not experience it, or maybe come across it a couple times in the same gaming session. Darkstarsword has posted up a method he used to fix a somewhat similar issue in another game that I'll take a look at implementing in this game over the weekend... problem is with the issue being infrequent and not methodically reproducible it'll be hard for me to know if it actually worked vs the game being on good behavior, lol.
I would rate it as an 8/10 in terms of 3D fidelity alone, and because I'm spoiled with usually being able to incorporate autodepth adjustment on in game HUD items in my fixes (which I wasn't able to do with this engine) I'd dock it another half mark down to a 7.5/10 for that. It really only bugs me while in Fort Tarsis, the between mission HUB area, so not particularly crucial to have it here since it's a leisurely area, I'm just a nit picker because I know how nice it is to have in game waypoint markers at proper depth.
Overall I'd say the game is definitely worth a purchase, the core gameplay is absolutely amazing, and playing through the campaign alone makes it worth it, but there are some design philosophies (a lot of them revolving around the loot aspect of the game, as well as any concerns towards any long term endgame) that are keeping the game from being a leader in the genre, and the online/Reddit community is being extremely unforgiving due to the fact that a lot of these matters have already been experienced (and improved upon) in the games that have come before it, and with The Division 2 around the corner (which, I'm sad to report is that a proper 3D fix is not possible due to them using EasyAntiCheat) a lot of people are either holding off buying into Anthem or ready to jump ship. Anthem's devs have been as good at responding and dealing with situations accordingly, and it was always put out there that this game is in it's infancy and will develop over time, but again, almost no leeway is being given. Most people that have played the game and are honest about it's shortcomings (which I consider myself to be one of) agree that if/when the issues are all resolved the game will be one of, if not the best in the genre due to the actual gameplay.
Hope this helps you make your own, educated decision towards buying! Worst case scenario I can wholeheartedly suggest paying for a month of Origin Access to get to play the game during that period. You can easily experience everything the game currently has to offer in that timeframe for a fraction of the current cost of the game, and then maybe pick up the game in a sale later on when more improvements have come down the pipeline. That's what I did/may end up doing.
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Great. Thank you :)
One question. For the Hub there are diffrent depths but for the crosshair just 2.
Can i manualy set the depth for the crosshair ?
Looks like its the z-variable but that affects the rest of the hub too.
One question. For the Hub there are diffrent depths but for the crosshair just 2.
Can i manualy set the depth for the crosshair ?
Looks like its the z-variable but that affects the rest of the hub too.
Win 10, SSD
i7-6700k@4,5Ghz, 16GBRam, Gigabyte G1 GTX1080 oc
Asus ROG Swift PG278QR
Oculus Rift
No, I didn't make the crosshair depth adjustable. If you want to do so you'll have to edit the shaders directly. In the shader fixes folder locate the 2 files:
272e2f3baa23cc67-vs_replace.txt
47d26e44a7bacfbe-vs_replace.txt
and locate the line in each of those files that is:
o0.x += stereo.x * (o0.w - stereo.y);
and modify it to be:
o0.x += stereo.x * (o0.w - stereo.y) * 0.xx;
where xx is the percent of depth. Alternatively you can change it to be:
o0.x += stereo.x * (o0.w - stereo.y) * params.z;
so that it will be the same depth as the rest of the HUD and adjustable via the hotkey.
Also, make sure you delete the following 2 files if you make any changes, otherwise they won't take effect:
272e2f3baa23cc67-vs_replace.bin
47d26e44a7bacfbe-vs_replace.bin
No, I didn't make the crosshair depth adjustable. If you want to do so you'll have to edit the shaders directly. In the shader fixes folder locate the 2 files:
272e2f3baa23cc67-vs_replace.txt
47d26e44a7bacfbe-vs_replace.txt
and locate the line in each of those files that is:
o0.x += stereo.x * (o0.w - stereo.y);
and modify it to be:
o0.x += stereo.x * (o0.w - stereo.y) * 0.xx;
where xx is the percent of depth. Alternatively you can change it to be:
o0.x += stereo.x * (o0.w - stereo.y) * params.z;
so that it will be the same depth as the rest of the HUD and adjustable via the hotkey.
Also, make sure you delete the following 2 files if you make any changes, otherwise they won't take effect:
272e2f3baa23cc67-vs_replace.bin
47d26e44a7bacfbe-vs_replace.bin
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Thank you very much for this fix DJ-RK!
Online games-as-a-service which can be played in 3D Vision are so rare, it's a shame. And your fix is awesome. It simply looks great (OLED TV), and plays great for a silly online game of this type. I really hope it will not be broken by updates, so that everyone can benefit from your fix.
In order to have good performance in 4K 3D the only way was to use upscaling shader (which does not work on this game) or SBS which causes insufferable tearing. So I got frustrated enough to fiddle with the options, and I found a way to use internal resolution scaling. The option is not yet incorporated in the game settings, it will probably arrive later, together with FOV and other options.
For anyone in my situation, just find the settings folder in Documents (C:\Users\USERNAME\Documents\BioWare\Anthem\settings), edit the file called ProfileOptions_profile, and add this line:
GstRender.ResolutionScale 0.500000
I'm using 50% scaling in the above example, use what you wish.
Thanks again DJ-RK! And thank you DHR, and DSS, and Bo3b and all you great people here who contributed to the Frostbyte engine fixes, and to 3D Vision in general. I know that this golden gaming age might come to an end, but you guys have contributed to my happiness as a gamer almost more than the developers themselves.
Thank you very much for this fix DJ-RK!
Online games-as-a-service which can be played in 3D Vision are so rare, it's a shame. And your fix is awesome. It simply looks great (OLED TV), and plays great for a silly online game of this type. I really hope it will not be broken by updates, so that everyone can benefit from your fix.
In order to have good performance in 4K 3D the only way was to use upscaling shader (which does not work on this game) or SBS which causes insufferable tearing. So I got frustrated enough to fiddle with the options, and I found a way to use internal resolution scaling. The option is not yet incorporated in the game settings, it will probably arrive later, together with FOV and other options.
For anyone in my situation, just find the settings folder in Documents (C:\Users\USERNAME\Documents\BioWare\Anthem\settings), edit the file called ProfileOptions_profile, and add this line:
GstRender.ResolutionScale 0.500000
I'm using 50% scaling in the above example, use what you wish.
Thanks again DJ-RK! And thank you DHR, and DSS, and Bo3b and all you great people here who contributed to the Frostbyte engine fixes, and to 3D Vision in general. I know that this golden gaming age might come to an end, but you guys have contributed to my happiness as a gamer almost more than the developers themselves.
[quote="DJ-RK"]No, I didn't make the crosshair depth adjustable. If you want to do so you'll have to edit the shaders directly. In the shader fixes folder locate the 2 files:
272e2f3baa23cc67-vs_replace.txt
47d26e44a7bacfbe-vs_replace.txt
and locate the line in each of those files that is:
o0.x += stereo.x * (o0.w - stereo.y);
and modify it to be:
o0.x += stereo.x * (o0.w - stereo.y) * 0.xx;
where xx is the percent of depth. Alternatively you can change it to be:
o0.x += stereo.x * (o0.w - stereo.y) * params.z;
so that it will be the same depth as the rest of the HUD and adjustable via the hotkey.
Also, make sure you delete the following 2 files if you make any changes, otherwise they won't take effect:
272e2f3baa23cc67-vs_replace.bin
47d26e44a7bacfbe-vs_replace.bin
[/quote]
Both methods works perfectly.
Thank you!
DJ-RK said:No, I didn't make the crosshair depth adjustable. If you want to do so you'll have to edit the shaders directly. In the shader fixes folder locate the 2 files:
272e2f3baa23cc67-vs_replace.txt
47d26e44a7bacfbe-vs_replace.txt
and locate the line in each of those files that is:
o0.x += stereo.x * (o0.w - stereo.y);
and modify it to be:
o0.x += stereo.x * (o0.w - stereo.y) * 0.xx;
where xx is the percent of depth. Alternatively you can change it to be:
o0.x += stereo.x * (o0.w - stereo.y) * params.z;
so that it will be the same depth as the rest of the HUD and adjustable via the hotkey.
Also, make sure you delete the following 2 files if you make any changes, otherwise they won't take effect:
272e2f3baa23cc67-vs_replace.bin
47d26e44a7bacfbe-vs_replace.bin
Both methods works perfectly.
Thank you!
Win 10, SSD
i7-6700k@4,5Ghz, 16GBRam, Gigabyte G1 GTX1080 oc
Asus ROG Swift PG278QR
Oculus Rift
BTW, I created a post on the Helix blog about a week ago and uploaded a newer version of the fix there, so the one in my earlier post is outdated and you might want to edit your first post to link to the blog instead. Here's the link: http://helixmod.blogspot.com/2019/02/anthem.html
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king
I would rate it as an 8/10 in terms of 3D fidelity alone, and because I'm spoiled with usually being able to incorporate autodepth adjustment on in game HUD items in my fixes (which I wasn't able to do with this engine) I'd dock it another half mark down to a 7.5/10 for that. It really only bugs me while in Fort Tarsis, the between mission HUB area, so not particularly crucial to have it here since it's a leisurely area, I'm just a nit picker because I know how nice it is to have in game waypoint markers at proper depth.
Overall I'd say the game is definitely worth a purchase, the core gameplay is absolutely amazing, and playing through the campaign alone makes it worth it, but there are some design philosophies (a lot of them revolving around the loot aspect of the game, as well as any concerns towards any long term endgame) that are keeping the game from being a leader in the genre, and the online/Reddit community is being extremely unforgiving due to the fact that a lot of these matters have already been experienced (and improved upon) in the games that have come before it, and with The Division 2 around the corner (which, I'm sad to report is that a proper 3D fix is not possible due to them using EasyAntiCheat) a lot of people are either holding off buying into Anthem or ready to jump ship. Anthem's devs have been as good at responding and dealing with situations accordingly, and it was always put out there that this game is in it's infancy and will develop over time, but again, almost no leeway is being given. Most people that have played the game and are honest about it's shortcomings (which I consider myself to be one of) agree that if/when the issues are all resolved the game will be one of, if not the best in the genre due to the actual gameplay.
Hope this helps you make your own, educated decision towards buying! Worst case scenario I can wholeheartedly suggest paying for a month of Origin Access to get to play the game during that period. You can easily experience everything the game currently has to offer in that timeframe for a fraction of the current cost of the game, and then maybe pick up the game in a sale later on when more improvements have come down the pipeline. That's what I did/may end up doing.
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king
One question. For the Hub there are diffrent depths but for the crosshair just 2.
Can i manualy set the depth for the crosshair ?
Looks like its the z-variable but that affects the rest of the hub too.
Win 10, SSD
i7-6700k@4,5Ghz, 16GBRam, Gigabyte G1 GTX1080 oc
Asus ROG Swift PG278QR
Oculus Rift
272e2f3baa23cc67-vs_replace.txt
47d26e44a7bacfbe-vs_replace.txt
and locate the line in each of those files that is:
o0.x += stereo.x * (o0.w - stereo.y);
and modify it to be:
o0.x += stereo.x * (o0.w - stereo.y) * 0.xx;
where xx is the percent of depth. Alternatively you can change it to be:
o0.x += stereo.x * (o0.w - stereo.y) * params.z;
so that it will be the same depth as the rest of the HUD and adjustable via the hotkey.
Also, make sure you delete the following 2 files if you make any changes, otherwise they won't take effect:
272e2f3baa23cc67-vs_replace.bin
47d26e44a7bacfbe-vs_replace.bin
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king
I will try it next weekend.
Win 10, SSD
i7-6700k@4,5Ghz, 16GBRam, Gigabyte G1 GTX1080 oc
Asus ROG Swift PG278QR
Oculus Rift
Online games-as-a-service which can be played in 3D Vision are so rare, it's a shame. And your fix is awesome. It simply looks great (OLED TV), and plays great for a silly online game of this type. I really hope it will not be broken by updates, so that everyone can benefit from your fix.
In order to have good performance in 4K 3D the only way was to use upscaling shader (which does not work on this game) or SBS which causes insufferable tearing. So I got frustrated enough to fiddle with the options, and I found a way to use internal resolution scaling. The option is not yet incorporated in the game settings, it will probably arrive later, together with FOV and other options.
For anyone in my situation, just find the settings folder in Documents (C:\Users\USERNAME\Documents\BioWare\Anthem\settings), edit the file called ProfileOptions_profile, and add this line:
GstRender.ResolutionScale 0.500000
I'm using 50% scaling in the above example, use what you wish.
Thanks again DJ-RK! And thank you DHR, and DSS, and Bo3b and all you great people here who contributed to the Frostbyte engine fixes, and to 3D Vision in general. I know that this golden gaming age might come to an end, but you guys have contributed to my happiness as a gamer almost more than the developers themselves.
Both methods works perfectly.
Thank you!
Win 10, SSD
i7-6700k@4,5Ghz, 16GBRam, Gigabyte G1 GTX1080 oc
Asus ROG Swift PG278QR
Oculus Rift