Cocodile Posted January 28 Share Posted January 28 13 hours ago, win32 said: Find this line: 84 C0 74 0A B8 BB 00 00 C0 E9 B9 18 00 00 44 38 and change it to EB 0C 74 0A B8 BB 00 00 C0 E9 B9 18 00 00 44 38 Thnx, but these are shown in the tutorial already under no. 2. I mean I need the values at the offset 160. (No. 1 here) What do I need to change at the beginning of the file ? Cause if I change only these from no. 2 , I see the Orb is stuck. I think there is a reason for the two rows of values in this tutorial. Link to comment Share on other sites More sharing options...
win32 Posted January 28 Share Posted January 28 2 hours ago, Cocodile said: Thnx, but these are shown in the tutorial already under no. 2. I mean I need the values at the offset 160. (No. 1 here) What do I need to change at the beginning of the file ? Cause if I change only these from no. 2 , I see the Orb is stuck. I think there is a reason for the two rows of values in this tutorial. That would be the PE checksum. Tools like CFF explorer can set it automatically, but in this driver it is located at offset 170 and is this: 7B 1D 09 01 01 00 E0 01 00 00 04 00 00 00 00 00 This would be changed to: E1 69 09 01 01 00 E0 01 00 00 04 00 00 00 00 00 1 Link to comment Share on other sites More sharing options...
D.Draker Posted January 28 Author Share Posted January 28 11 hours ago, Cocodile said: Thnx, but these are shown in the tutorial already under no. 2. I mean I need the values at the offset 160. (No. 1 here) What do I need to change at the beginning of the file ? Cause if I change only these from no. 2 , I see the Orb is stuck. I think there is a reason for the two rows of values in this tutorial. You defo need to read before you post, all of that was tested by me a long time ago (including the 391.35). The NVCPL in the 39x.xx does NOT work. 1 Link to comment Share on other sites More sharing options...
D.Draker Posted January 28 Author Share Posted January 28 8 hours ago, win32 said: That would be the PE checksum. Tools like CFF explorer can set it automatically, but in this driver it is located at offset 170 and is this: 7B 1D 09 01 01 00 E0 01 00 00 04 00 00 00 00 00 This would be changed to: E1 69 09 01 01 00 E0 01 00 00 04 00 00 00 00 00 Mine doesn't . That's why I included the manual patching process with WinHex in the tutorial. Which version do you run ? I guess I was wrong when I thought it would eliminate questions like from the above. 1 Link to comment Share on other sites More sharing options...
D.Draker Posted January 28 Author Share Posted January 28 @win32, btw , you wrote you don't have that file when you install the driver , right ? So I installed 456.71 on a spare Win 7 PC with GTX780Ti, just to look what files are created, so here I made an export : 456.71 filename full.txt nvDevTools.dll nvDevToolsR.dll nvdisps.dll nvdispsr.dll nvgames.dll nvgamesr.dll nvlicensings.dll nvLicensingSR.dll nvmccss.dll nvmccssr.dll nvmobls.dll nvmoblsr.dll nvsmartmax.dll nvsmartmax64.dll nvsmartmaxapp.exe nvsmartmaxapp64.exe nvsvs.dll nvsvsr.dll nvui.dll nvuir.dll nvvitvs.dll nvvitvsr.dll nvwss.dll nvwssr.dll nvxdapix.dll nvxdbat.dll nvxdplcy.dll In reality , one can delete everything except these : nvdisps.dll nvdispsr.dll nvgames.dll nvgamesr.dll nvsmartmax.dll nvsmartmax64.dll nvsmartmaxapp.exe nvsmartmaxapp64.exe nvui.dll nvuir.dll nvvitvs.dll nvvitvsr.dll nvxdapix.dll nvxdbat.dll nvxdplcy.dll 1 Link to comment Share on other sites More sharing options...
win32 Posted January 28 Share Posted January 28 4 hours ago, D.Draker said: Mine doesn't . That's why I included the manual patching process with WinHex in the tutorial. Which version do you run ? Version 8.0.0.0 (as written in the properties of the exe) from 2012. It is listed as an option under "rebuilder". 2 Link to comment Share on other sites More sharing options...
Cocodile Posted January 30 Share Posted January 30 Everyone, thank you for the help, yes, sorry I know I had to read first. Everything was in the tutorilal. 1 Link to comment Share on other sites More sharing options...
D.Draker Posted February 3 Author Share Posted February 3 On 1/21/2023 at 4:49 AM, K4sum1 said: RDR2 ... can run with 431.36 (older than required, but modern enough to work I guess), I've done it. It's not a hard limit, unless later versions got a hard limit. How did you bypass that limit ? It constantly asks me for 446.xx driver and/or 442.xx or newer (if I remove the last patch). Link to comment Share on other sites More sharing options...
D.Draker Posted February 3 Author Share Posted February 3 On 1/20/2023 at 10:22 AM, win32 said: It is possible it checks the file versions of nvlddmkm.sys or nvd3dumx.dll. In my case the version is written as 24.21.13.9811. So it would have to be changed to 24.21.14.4229 using a resource editor or by searching for the version values in a hex editor (these are UTF-16 characters). Now it just says "please update your graphics software" and makes an attempt to launch IE (which I obviously removed from the ISO) and then quits. Link to comment Share on other sites More sharing options...
K4sum1 Posted February 3 Share Posted February 3 This was with an older version of the game, didn't think they'd make it required to update. Sucks as 431.36 gave better performance compared to latest. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now