Geo-11 What is shader hunting and am I using it right?

[petermg]

So I'm desperately trying to get Star Wars Battlefront I looking better. That games looks way better than it has any right to especially for an EIGHT YEAR OLD GAME. I applied the couple fixes I found but there were still issues. So I decided to play with shader hunting and see if that does anything. It does actually. I have got a lot better results so far but I don't even really know how to use it. I am just cycling through 3 different shader options (IB/PS/VS). I don't know what they mean. I want to save the good results. Is this the basis of "fixes"? I'm using Geo-11 with an RTX 3070 and the latest Studio Drivers, going back to GRD soon, the Studio drivers thing was just something I wanted to test, which didn't change anything. So is there a place this is all explained and I can just read up on it without having to dig through tons of forum posts combing through discussions piece by piece? I didn't find much so far. Thanks.

[3DNovice]

...

[3DNovice]

...

[petermg]

some more
Utilized DarkStarSword's FOV fix in this patch
https://www.nvidia.com/en-us/geforce/fo ... his-patch/

Bo3b's School For Shaderhackers (the original thread for it)
https://forums.geforce.com/default/topi ... derhackers

DarkStarSword had a ToDoList for 3DMigoto, I'm unsure of how much bo3b and he got fixed/sorted, but perhaps the info there might be useful to someone that stumbles upon these links
DarkStarSword's TODO list
https://www.nvidia.com/en-us/geforce/fo ... todo-list/

3DMigoto also has some type of freeze frame analysis type of thing, I think/I'm pretty sure. Dunno
3DMigoto has an option to highlight a borked shader in pink, so that it can be easier to see and diagnosed, if needed.

Awesome! Getting to it now.

[3DNovice]

...

[3DNovice]

....

[3DNovice]

...

[3DNovice]

...

[3DNovice]

...

[The_Nephilim]

@petermg,

Well thing is with Geo-11 when you hunt shaders it dumps it in ASM. you could follow Bo3bs guide on the Shaderschool and possibly get a start there.. I am not familiar with ASM I prefer the HLSL but Geo-11 uses ASM for now..

I did look for the game but then realised you are using Geo-11 So I am unable to help much but if you follow some of the stuff 3D Novice posted there especailly Bo3bs school for shaderhackers lesson would be a good start..

Beasides I seen a few different Battlefronts on Steam and unsure which one you are looking at????

[3DNovice]

...

[The_Nephilim]

well yes I thought that was the one but it did not show in ssteam as a 2015 release??? but I will check into it later.. the fix by Helifax looks to be a compatibility mod fix. there is no real fix persay as it uses compatibility mode.. if the user wanted to fix Battlefront 2015 with Geo-11 they would need to do it in ASM. as that is what Geo11 dumps per shader..

I would look into it but would have to figure what game it is on Steam as there are several..

Ahh the Frostbyte engine it seems there is a universal fix for that engine here:


https://helixmod.blogspot.com/2010/12/h ... uides.html

I would highly look into that router as it should fix most of what is broke hopefully..

[3DNovice]

...

[3DNovice]

...

[3DNovice]

...

[Losti]

Btw, it's always the best to fix in ASM and ASM is not really complicated. Reasons:

10-20 % of the shaders cannot be saved in hlsl
Commute shaders are only be saved in ASM
You need a ASM based fix to write regular expressions for automatically fixing repeating things and prevent updates braking your fix due to hash name changes

[3DNovice]

...

[Rubini]

FWIW, for anyone happening upon this thread that is dumping shaders with Geo-11 and finding ASM difficult.
There is a new version of Geo-11 available that will dump HLSL, but it is not publicly available yet, so be patient.

Hi mates,
Any news about this new version of geo11? Although ASM is technically better, I still have some difficulties and prefer to make my adjustments in HLSL whenever possible. Also HLSL is great for quick & cool adjustments for fixes that are using 3DMigoto on the fly. Have options is always the best.

[3DNovice]

...

[3DNovice]

...

[3DNovice]

...

[3DNovice]

...

[3DNovice]

...

[3DNovice]

....

[john105]

Try the latest fixes made by masterataku on the blog, I looked at Dying Light, it has a June 4 2023 DLL
I'm guessing that it the newest, no idea what version number it would be called

I'm unsure of how you could tell the version number, when checking properties, it states File Version 1.3.16.0 and Product Version 1.3.16
The only thing that changes is the size of the dll and the release date

You can see the geo-11 version if you check the properties of nvapi64.dll, not d3d11.dll.

I'll say it again......

It would be nice if there was a repository of all versions on the blog, along with a chart.version history, like for the wrapper from helix

https://wiki.bo3b.net/index.php?title=H ... _available.

Yes, it would be very useful. We can look for the updated DDLs in recent fixes, but this way still doesn't give us the default d3dxdm.ini, only the one modified for the specific game the fix is for. Maybe the default d3dxdm.ini hasn't changed much since v0.6.56, but we don't really know if there are new parameters or the defaults were changed.

Another thing that might be important, is listing dependencies, like net version and MSVCRT/ VC redistributables or anything else
and have it pop up errors if dependencies are missing or currupted.

This part might be missing because there are no .NET or special VC dependencies. The only dependencies are the standard OS DLLs and some DirectX DDLs. It can be checked using Dependency Walker. For example, it looks like this for geo-11 v0.6.182.

[3DNovice]

...

[3DNovice]

...

[BazzaLB]

Nice List!

I went through my links and the only thing I can find that you maybe havent listed (unless I missed it) is this

Are there any detailed tutorials to fix some simple elements
viewtopic.php?t=23677

[3DNovice]

...

[3DNovice]

...