How to fix/disable shaders in games(DLL,guide and fixes).
50 / 167
You can use nvstres from old driver(don't forget to restore 9D68E0CD.txt back).
I sent you PM with link to old nvstres.
I hope someone from Nvidia read this:
It'll be a good to have registry key which will give us ability to disable Nvidia profile(or function in NVAPi).
Because it's hard to adapt fixes for difference driver versions.
[quote name='-=HeliX=-' date='24 March 2012 - 03:54 AM' timestamp='1332579284' post='1387208']
You can use nvstres from old driver(don't forget to restore 9D68E0CD.txt back).
I sent you PM with link to old nvstres.
I hope someone from Nvidia read this:
It'll be a good to have registry key which will give us ability to disable Nvidia profile(or function in NVAPi).
Because it's hard to adapt fixes for difference driver versions.
[/quote]
Thanks for the file HeliX. I copied over my current nvstres.dll with the one you linked me too but it still had the profile in the game when I rebooted my PC. I don't know if it is an issue with having a new card that was not in the old drivers or not. I am trying to find a way to launch the game with re-directed .exe so that Origin will allow it to launch but have no luck so far. I am going to see what else I can try.
[quote name='-=HeliX=-' date='24 March 2012 - 03:54 AM' timestamp='1332579284' post='1387208']
You can use nvstres from old driver(don't forget to restore 9D68E0CD.txt back).
I sent you PM with link to old nvstres.
I hope someone from Nvidia read this:
It'll be a good to have registry key which will give us ability to disable Nvidia profile(or function in NVAPi).
Because it's hard to adapt fixes for difference driver versions.
Thanks for the file HeliX. I copied over my current nvstres.dll with the one you linked me too but it still had the profile in the game when I rebooted my PC. I don't know if it is an issue with having a new card that was not in the old drivers or not. I am trying to find a way to launch the game with re-directed .exe so that Origin will allow it to launch but have no luck so far. I am going to see what else I can try.
I finally found a way to get this game to run in 3D with HeliX's fixes and not have the 3D Vision profile break it. If you are going to do what is detailed here please follow the directions carefully and do so at your won risk. I also suggest making sure Origin is shut down first. I basically did what is detailed here with my tweaks to the naming convention:
I downloaded the supplied zipped file, extracted it, and then copied the masseffect3demo.exe and masseffect3.ini to the same folder as the Reckoning's .exe: C:\Program Files (x86)\Origin Games\Kingdoms of Amalur Reckoning\
Next you must rename the Reckoning.exe and Reckoning.par files to something that you know doesn't have a 3D Vision profile. In this case I renamed them to Amalur.exe and Amalur.par. Next you must rename those copied files, masseffect3demo.exe and masseffect3.ini, to the game's actual file names that are recognized by Origin, Amalur.exe and Amalur.ini. Next edit the .ini file and put the name of the new .exe after the part that says "program=", which in this case it will now show program=amalur.exe.
That's it - now just re-start Origin and launch the game using the new .exe you made, Amalur.exe in this case. You will now notice the in-game 3D info will show "amalur". Since the games are still launching through Origin, I see nothing illegal with doing this. I would probably advise against doing this with any online games where it may be viewed as a hack and get you banned.
I also just did the same thing for Mass Effect 3, which has the folder locations as indicated in the link I provided above. Now I can keep my drivers up to date without worrying about Nvidia profiles breaking Origin games that HeliX has went through the trouble of making the 3D awesome for all of us.
Here is a link on how to make it work on Steam games - the process is the basically the same as for Origin games. I tested it on a couple of my Steam games and confirm it works. All thanks for these tricks go to Bloody at 3D Vision Blog!
I finally found a way to get this game to run in 3D with HeliX's fixes and not have the 3D Vision profile break it. If you are going to do what is detailed here please follow the directions carefully and do so at your won risk. I also suggest making sure Origin is shut down first. I basically did what is detailed here with my tweaks to the naming convention:
I downloaded the supplied zipped file, extracted it, and then copied the masseffect3demo.exe and masseffect3.ini to the same folder as the Reckoning's .exe: C:\Program Files (x86)\Origin Games\Kingdoms of Amalur Reckoning\
Next you must rename the Reckoning.exe and Reckoning.par files to something that you know doesn't have a 3D Vision profile. In this case I renamed them to Amalur.exe and Amalur.par. Next you must rename those copied files, masseffect3demo.exe and masseffect3.ini, to the game's actual file names that are recognized by Origin, Amalur.exe and Amalur.ini. Next edit the .ini file and put the name of the new .exe after the part that says "program=", which in this case it will now show program=amalur.exe.
That's it - now just re-start Origin and launch the game using the new .exe you made, Amalur.exe in this case. You will now notice the in-game 3D info will show "amalur". Since the games are still launching through Origin, I see nothing illegal with doing this. I would probably advise against doing this with any online games where it may be viewed as a hack and get you banned.
I also just did the same thing for Mass Effect 3, which has the folder locations as indicated in the link I provided above. Now I can keep my drivers up to date without worrying about Nvidia profiles breaking Origin games that HeliX has went through the trouble of making the 3D awesome for all of us.
Here is a link on how to make it work on Steam games - the process is the basically the same as for Origin games. I tested it on a couple of my Steam games and confirm it works. All thanks for these tricks go to Bloody at 3D Vision Blog!
Oh thats why it broke, stupid late profiles. I was the one that found out about the .par renaming = ) . Bloody did the rest. Ill update the amalur page.
I'd recommend for online games(like me3). Keeping a backup old 3d vision https://s3.amazonaws.com/Helixfix/3dvision295.73%28ME3+COMPATIBLE%29.zip
Oh thats why it broke, stupid late profiles. I was the one that found out about the .par renaming = ) . Bloody did the rest. Ill update the amalur page.
OMD! works nearly flawlessly in S3D, with only one problem: the crosshair is 2D. nVidia rates the game "Good," but my fix improves its S3D performance by making the crosshair render with depth.
Unfortunately, the crosshair is part of the same vertex shader as all of the UI graphic elements. This is my first attempt to use the Helix Mod, so I have no idea if the crosshair can be isolated.
I modified two other vertex shaders to make sure the UI was fully legible. UI/Menu text now also renders with depth.
Change the shaders' depth values to whatever is comfortable for your preferred depth/convergence settings. Adjust the value underlined below in all three shaders:
There are some problems that this fix causes. Some health bars don't display properly, similar to the problem with health and shield bars in the ME3 fix. I couldn't find a vertex or pixel shader for the minimap, so that remains 2D.
OMD! works nearly flawlessly in S3D, with only one problem: the crosshair is 2D. nVidia rates the game "Good," but my fix improves its S3D performance by making the crosshair render with depth.
Unfortunately, the crosshair is part of the same vertex shader as all of the UI graphic elements. This is my first attempt to use the Helix Mod, so I have no idea if the crosshair can be isolated.
I modified two other vertex shaders to make sure the UI was fully legible. UI/Menu text now also renders with depth.
Change the shaders' depth values to whatever is comfortable for your preferred depth/convergence settings. Adjust the value underlined below in all three shaders:
def c220, 0.80, 0, 0.0625, 0
There are some problems that this fix causes. Some health bars don't display properly, similar to the problem with health and shield bars in the ME3 fix. I couldn't find a vertex or pixel shader for the minimap, so that remains 2D.
[url="http://helixmod.blogspot.com/2012/03/orcs-must-die_24.html"]Added Orcs must die! to wiki[/url]
Yeah was actually working on it as you did it lol. Saved me some time. Yea unfortunately crosshair can not be seperated. It basically needs to be seperate textures. You start game find the shader that you want to check (eight digit).txt . Then exit game. Then open up log.txt and check if that (eight digit) is repeated more then once. That means that you can seperate "pieces" of the shader.
Yeah was actually working on it as you did it lol. Saved me some time. Yea unfortunately crosshair can not be seperated. It basically needs to be seperate textures. You start game find the shader that you want to check (eight digit).txt . Then exit game. Then open up log.txt and check if that (eight digit) is repeated more then once. That means that you can seperate "pieces" of the shader.
Thanks for the tip about separating the textures. I have no idea how to make that work, but it seems useful to learn. And also, thanks for featuring the fix on your blog.
Now that I'm beginning to understand how this all works, I will be making adjustments to many games in the future. Hopefully I can eventually learn to create fixes for other rendering problems. This is a skill that will be valuable for my work.
Thanks for the tip about separating the textures. I have no idea how to make that work, but it seems useful to learn. And also, thanks for featuring the fix on your blog.
Now that I'm beginning to understand how this all works, I will be making adjustments to many games in the future. Hopefully I can eventually learn to create fixes for other rendering problems. This is a skill that will be valuable for my work.
http://helixmod.blogspot.com/2012/03/dlls-update.html
Has more in reference to what I was talking about (where if shader is used more then once in log)
Also I went through shaders and I dont think mini map is one. Same thing happened to me to dragon age(icons)
Helix, I don't have ME3 yet, but I'm one of the many who is still getting a huge benefit from your hard work. Just wanted to say, you're a genius and I don't think it's going too far to say that you've single handedly transformed 3d gaming for the better, so thank you very very much! :-)
Oh and Eqzitara, thank you too for taking so much of your time to look after the wiki and stay so active on this :-)
Helix, I don't have ME3 yet, but I'm one of the many who is still getting a huge benefit from your hard work. Just wanted to say, you're a genius and I don't think it's going too far to say that you've single handedly transformed 3d gaming for the better, so thank you very very much! :-)
Oh and Eqzitara, thank you too for taking so much of your time to look after the wiki and stay so active on this :-)
Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
Hi, I'm back after a few days away. So, I noticed something about the wrapper. When I use the debug d3d9.dll I get corrupted shaders. I didn't think much of it at first because the 2012-02-20 release version of d3d9.dll works fine, and I was able to find the shader anyway. However, any subsequent release .dll causes the same corrupted shaders issue as with debug .dll.
eqzitara I see you were kind enough to attempt sorting out my .txt. I'd be really curious to see what you did. It probably crashes after the main menu because you use the "problematic" latest wrapper .dll, I assume. The vertex shader in question happens to be used for both the main menu and the in-game HUD, so the next step will be that I isolate the textures used for the HUD and apply depth changes to these only. Thing is... the release .dll that allows such things obviously has the shader problems...
Hi, I'm back after a few days away. So, I noticed something about the wrapper. When I use the debug d3d9.dll I get corrupted shaders. I didn't think much of it at first because the 2012-02-20 release version of d3d9.dll works fine, and I was able to find the shader anyway. However, any subsequent release .dll causes the same corrupted shaders issue as with debug .dll.
eqzitara I see you were kind enough to attempt sorting out my .txt. I'd be really curious to see what you did. It probably crashes after the main menu because you use the "problematic" latest wrapper .dll, I assume. The vertex shader in question happens to be used for both the main menu and the in-game HUD, so the next step will be that I isolate the textures used for the HUD and apply depth changes to these only. Thing is... the release .dll that allows such things obviously has the shader problems...
LOL DAMN. You told me 10 seconds after I figured it out.
Yeah I am adding the release right now. Check the wiki in like 10 mins
update: http://helixmod.blogspot.com/2012/03/sonic-sega-all-stars_24.html
Game looks pretty good surprised no one ever mentions it. Yeah apparently when I gave you the 2->3 I missed a 1. Should of wrote texcoord1. Rest of it was right though. Went light on the depth value. The log.txt lets you know when you screw something up. Always check it if its not working will post all "versions of the shader"
Game looks pretty good surprised no one ever mentions it. Yeah apparently when I gave you the 2->3 I missed a 1. Should of wrote texcoord1. Rest of it was right though. Went light on the depth value. The log.txt lets you know when you screw something up. Always check it if its not working will post all "versions of the shader"
Absolutely fantastic, many thanks. Pretty sure I get it now, I see what I'd done wrong and it seems more logical. I'm now waiting for my stupid glasses to recharge (the bane of the 3d vision gamer's existence) afterwards I'll check it out and see if texture isolation could be an option in the event of a new wrapper that works with the game (hoping helix could look into that... logically if it worked before it can work again). In fact most of the HUD is quite OK, most elements would be fine with just a very slight push. What I aim to do is push the crosshair (that appears when you get missile weapons) further back than the rest, so it appears to be in front of the car. If I can do that the game would be completely flawless.
And yes, even as it is it's a very good looking game, worthy of a place in any 3d game collection I think.
Absolutely fantastic, many thanks. Pretty sure I get it now, I see what I'd done wrong and it seems more logical. I'm now waiting for my stupid glasses to recharge (the bane of the 3d vision gamer's existence) afterwards I'll check it out and see if texture isolation could be an option in the event of a new wrapper that works with the game (hoping helix could look into that... logically if it worked before it can work again). In fact most of the HUD is quite OK, most elements would be fine with just a very slight push. What I aim to do is push the crosshair (that appears when you get missile weapons) further back than the rest, so it appears to be in front of the car. If I can do that the game would be completely flawless.
And yes, even as it is it's a very good looking game, worthy of a place in any 3d game collection I think.
@anisotonic
What are we talking about? I never actually played game. I thought that was only problem. Direct me so I can see what can be done. Is this a different shader we are talking about or same?
@rustyk
Haha. Yeah its no problem. This stuff gives me something to do. I watch fighting game tourneys alot so in between matches I am doing forum/web-site stuff. I kind of owe helix (besides making games awesome) for giving me something to do between matches. People probably wonder why I edit my responses so much lol.
What are we talking about? I never actually played game. I thought that was only problem. Direct me so I can see what can be done. Is this a different shader we are talking about or same?
@rustyk
Haha. Yeah its no problem. This stuff gives me something to do. I watch fighting game tourneys alot so in between matches I am doing forum/web-site stuff. I kind of owe helix (besides making games awesome) for giving me something to do between matches. People probably wonder why I edit my responses so much lol.
I sent you PM with link to old nvstres.
I hope someone from Nvidia read this:
It'll be a good to have registry key which will give us ability to disable Nvidia profile(or function in NVAPi).
Because it's hard to adapt fixes for difference driver versions.
I sent you PM with link to old nvstres.
I hope someone from Nvidia read this:
It'll be a good to have registry key which will give us ability to disable Nvidia profile(or function in NVAPi).
Because it's hard to adapt fixes for difference driver versions.
You can use nvstres from old driver(don't forget to restore 9D68E0CD.txt back).
I sent you PM with link to old nvstres.
I hope someone from Nvidia read this:
It'll be a good to have registry key which will give us ability to disable Nvidia profile(or function in NVAPi).
Because it's hard to adapt fixes for difference driver versions.
[/quote]
Thanks for the file HeliX. I copied over my current nvstres.dll with the one you linked me too but it still had the profile in the game when I rebooted my PC. I don't know if it is an issue with having a new card that was not in the old drivers or not. I am trying to find a way to launch the game with re-directed .exe so that Origin will allow it to launch but have no luck so far. I am going to see what else I can try.
You can use nvstres from old driver(don't forget to restore 9D68E0CD.txt back).
I sent you PM with link to old nvstres.
I hope someone from Nvidia read this:
It'll be a good to have registry key which will give us ability to disable Nvidia profile(or function in NVAPi).
Because it's hard to adapt fixes for difference driver versions.
Thanks for the file HeliX. I copied over my current nvstres.dll with the one you linked me too but it still had the profile in the game when I rebooted my PC. I don't know if it is an issue with having a new card that was not in the old drivers or not. I am trying to find a way to launch the game with re-directed .exe so that Origin will allow it to launch but have no luck so far. I am going to see what else I can try.
http://3dvision-blog.com/7212-3d-vision-cheat-fix-for-mass-effect-3-demo-and-other-origin-games/
I downloaded the supplied zipped file, extracted it, and then copied the masseffect3demo.exe and masseffect3.ini to the same folder as the Reckoning's .exe: C:\Program Files (x86)\Origin Games\Kingdoms of Amalur Reckoning\
Next you must rename the Reckoning.exe and Reckoning.par files to something that you know doesn't have a 3D Vision profile. In this case I renamed them to Amalur.exe and Amalur.par. Next you must rename those copied files, masseffect3demo.exe and masseffect3.ini, to the game's actual file names that are recognized by Origin, Amalur.exe and Amalur.ini. Next edit the .ini file and put the name of the new .exe after the part that says "program=", which in this case it will now show program=amalur.exe.
That's it - now just re-start Origin and launch the game using the new .exe you made, Amalur.exe in this case. You will now notice the in-game 3D info will show "amalur". Since the games are still launching through Origin, I see nothing illegal with doing this. I would probably advise against doing this with any online games where it may be viewed as a hack and get you banned.
I also just did the same thing for Mass Effect 3, which has the folder locations as indicated in the link I provided above. Now I can keep my drivers up to date without worrying about Nvidia profiles breaking Origin games that HeliX has went through the trouble of making the 3D awesome for all of us.
Here is a link on how to make it work on Steam games - the process is the basically the same as for Origin games. I tested it on a couple of my Steam games and confirm it works. All thanks for these tricks go to Bloody at 3D Vision Blog!
http://3dvision-blog.com/1435-aliens-vs-predator-multiplayer-demo-fix-for-3d-vision-users/
http://3dvision-blog.com/7212-3d-vision-cheat-fix-for-mass-effect-3-demo-and-other-origin-games/
I downloaded the supplied zipped file, extracted it, and then copied the masseffect3demo.exe and masseffect3.ini to the same folder as the Reckoning's .exe: C:\Program Files (x86)\Origin Games\Kingdoms of Amalur Reckoning\
Next you must rename the Reckoning.exe and Reckoning.par files to something that you know doesn't have a 3D Vision profile. In this case I renamed them to Amalur.exe and Amalur.par. Next you must rename those copied files, masseffect3demo.exe and masseffect3.ini, to the game's actual file names that are recognized by Origin, Amalur.exe and Amalur.ini. Next edit the .ini file and put the name of the new .exe after the part that says "program=", which in this case it will now show program=amalur.exe.
That's it - now just re-start Origin and launch the game using the new .exe you made, Amalur.exe in this case. You will now notice the in-game 3D info will show "amalur". Since the games are still launching through Origin, I see nothing illegal with doing this. I would probably advise against doing this with any online games where it may be viewed as a hack and get you banned.
I also just did the same thing for Mass Effect 3, which has the folder locations as indicated in the link I provided above. Now I can keep my drivers up to date without worrying about Nvidia profiles breaking Origin games that HeliX has went through the trouble of making the 3D awesome for all of us.
Here is a link on how to make it work on Steam games - the process is the basically the same as for Origin games. I tested it on a couple of my Steam games and confirm it works. All thanks for these tricks go to Bloody at 3D Vision Blog!
http://3dvision-blog.com/1435-aliens-vs-predator-multiplayer-demo-fix-for-3d-vision-users/
I'd recommend for online games(like me3). Keeping a backup old 3d vision https://s3.amazonaws.com/Helixfix/3dvision295.73%28ME3+COMPATIBLE%29.zip
I'd recommend for online games(like me3). Keeping a backup old 3d vision https://s3.amazonaws.com/Helixfix/3dvision295.73%28ME3+COMPATIBLE%29.zip
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
OMD! works nearly flawlessly in S3D, with only one problem: the crosshair is 2D. nVidia rates the game "Good," but my fix improves its S3D performance by making the crosshair render with depth.
Unfortunately, the crosshair is part of the same vertex shader as all of the UI graphic elements. This is my first attempt to use the Helix Mod, so I have no idea if the crosshair can be isolated.
I modified two other vertex shaders to make sure the UI was fully legible. UI/Menu text now also renders with depth.
Change the shaders' depth values to whatever is comfortable for your preferred depth/convergence settings. Adjust the value underlined below in all three shaders:
[quote]def c220, [u][b]0.80[/b][/u], 0, 0.0625, 0[/quote]
There are some problems that this fix causes. Some health bars don't display properly, similar to the problem with health and shield bars in the ME3 fix. I couldn't find a vertex or pixel shader for the minimap, so that remains 2D.
[b]Screenshots:[/b]
[url="http://photos.3dvisionlive.com/Eincrou/image/4f6dd7343785013145000000/"]Before Fix[/url]
[url="http://photos.3dvisionlive.com/Eincrou/image/4f6dd7f8378501e446000000/"]After Fix[/url]
[b]Fixed Shaders[/b]
[url="https://www.rapidshare.com/files/3917992056/HM-OrcsMustDie_ShaderOverride_v1.zip"]HM-OrcsMustDie_ShaderOverride_v1.zip[/url]
Rapidshare isn't a permanent storage solution, so if anyone has suggestions for a better place to upload this, please let me know.
OMD! works nearly flawlessly in S3D, with only one problem: the crosshair is 2D. nVidia rates the game "Good," but my fix improves its S3D performance by making the crosshair render with depth.
Unfortunately, the crosshair is part of the same vertex shader as all of the UI graphic elements. This is my first attempt to use the Helix Mod, so I have no idea if the crosshair can be isolated.
I modified two other vertex shaders to make sure the UI was fully legible. UI/Menu text now also renders with depth.
Change the shaders' depth values to whatever is comfortable for your preferred depth/convergence settings. Adjust the value underlined below in all three shaders:
There are some problems that this fix causes. Some health bars don't display properly, similar to the problem with health and shield bars in the ME3 fix. I couldn't find a vertex or pixel shader for the minimap, so that remains 2D.
Screenshots:
Before Fix
After Fix
Fixed Shaders
HM-OrcsMustDie_ShaderOverride_v1.zip
Rapidshare isn't a permanent storage solution, so if anyone has suggestions for a better place to upload this, please let me know.
Yeah was actually working on it as you did it lol. Saved me some time. Yea unfortunately crosshair can not be seperated. It basically needs to be seperate textures. You start game find the shader that you want to check (eight digit).txt . Then exit game. Then open up log.txt and check if that (eight digit) is repeated more then once. That means that you can seperate "pieces" of the shader.
Yeah was actually working on it as you did it lol. Saved me some time. Yea unfortunately crosshair can not be seperated. It basically needs to be seperate textures. You start game find the shader that you want to check (eight digit).txt . Then exit game. Then open up log.txt and check if that (eight digit) is repeated more then once. That means that you can seperate "pieces" of the shader.
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
Thanks for the tip about separating the textures. I have no idea how to make that work, but it seems useful to learn. And also, thanks for featuring the fix on your blog.
Now that I'm beginning to understand how this all works, I will be making adjustments to many games in the future. Hopefully I can eventually learn to create fixes for other rendering problems. This is a skill that will be valuable for my work.
Thanks for the tip about separating the textures. I have no idea how to make that work, but it seems useful to learn. And also, thanks for featuring the fix on your blog.
Now that I'm beginning to understand how this all works, I will be making adjustments to many games in the future. Hopefully I can eventually learn to create fixes for other rendering problems. This is a skill that will be valuable for my work.
Has more in reference to what I was talking about (where if shader is used more then once in log)
Also I went through shaders and I dont think mini map is one. Same thing happened to me to dragon age(icons)
Has more in reference to what I was talking about (where if shader is used more then once in log)
Also I went through shaders and I dont think mini map is one. Same thing happened to me to dragon age(icons)
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
[url="http://helixmod.blogspot.com/2012/03/mass-effect-3-3d-vision-fix-update.html"]Mass Effect 3 fix updated.[/url]
[/quote]
Helix, I don't have ME3 yet, but I'm one of the many who is still getting a huge benefit from your hard work. Just wanted to say, you're a genius and I don't think it's going too far to say that you've single handedly transformed 3d gaming for the better, so thank you very very much! :-)
Oh and Eqzitara, thank you too for taking so much of your time to look after the wiki and stay so active on this :-)
Mass Effect 3 fix updated.
Helix, I don't have ME3 yet, but I'm one of the many who is still getting a huge benefit from your hard work. Just wanted to say, you're a genius and I don't think it's going too far to say that you've single handedly transformed 3d gaming for the better, so thank you very very much! :-)
Oh and Eqzitara, thank you too for taking so much of your time to look after the wiki and stay so active on this :-)
Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
eqzitara I see you were kind enough to attempt sorting out my .txt. I'd be really curious to see what you did. It probably crashes after the main menu because you use the "problematic" latest wrapper .dll, I assume. The vertex shader in question happens to be used for both the main menu and the in-game HUD, so the next step will be that I isolate the textures used for the HUD and apply depth changes to these only. Thing is... the release .dll that allows such things obviously has the shader problems...
eqzitara I see you were kind enough to attempt sorting out my .txt. I'd be really curious to see what you did. It probably crashes after the main menu because you use the "problematic" latest wrapper .dll, I assume. The vertex shader in question happens to be used for both the main menu and the in-game HUD, so the next step will be that I isolate the textures used for the HUD and apply depth changes to these only. Thing is... the release .dll that allows such things obviously has the shader problems...
Yeah I am adding the release right now. Check the wiki in like 10 mins
update: http://helixmod.blogspot.com/2012/03/sonic-sega-all-stars_24.html
Game looks pretty good surprised no one ever mentions it. Yeah apparently when I gave you the 2->3 I missed a 1. Should of wrote texcoord1. Rest of it was right though. Went light on the depth value. The log.txt lets you know when you screw something up. Always check it if its not working will post all "versions of the shader"
Yeah I am adding the release right now. Check the wiki in like 10 mins
update: http://helixmod.blogspot.com/2012/03/sonic-sega-all-stars_24.html
Game looks pretty good surprised no one ever mentions it. Yeah apparently when I gave you the 2->3 I missed a 1. Should of wrote texcoord1. Rest of it was right though. Went light on the depth value. The log.txt lets you know when you screw something up. Always check it if its not working will post all "versions of the shader"
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
And yes, even as it is it's a very good looking game, worthy of a place in any 3d game collection I think.
And yes, even as it is it's a very good looking game, worthy of a place in any 3d game collection I think.
What are we talking about? I never actually played game. I thought that was only problem. Direct me so I can see what can be done. Is this a different shader we are talking about or same?
@rustyk
Haha. Yeah its no problem. This stuff gives me something to do. I watch fighting game tourneys alot so in between matches I am doing forum/web-site stuff. I kind of owe helix (besides making games awesome) for giving me something to do between matches. People probably wonder why I edit my responses so much lol.
What are we talking about? I never actually played game. I thought that was only problem. Direct me so I can see what can be done. Is this a different shader we are talking about or same?
@rustyk
Haha. Yeah its no problem. This stuff gives me something to do. I watch fighting game tourneys alot so in between matches I am doing forum/web-site stuff. I kind of owe helix (besides making games awesome) for giving me something to do between matches. People probably wonder why I edit my responses so much lol.
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918