jhonipin Posted March 29, 2020 Share Posted March 29, 2020 (edited) Hello everyone I'm creating this topic to share what I discovered and try to solve the problem that I can't solve. Why do I want to compile Openparrot first? I wanted to put coin in DirtyDrivin, I analyzed the exe from the first dump and the exe from Jconfig and noticed that the one from jconfig ignores the modifications of the .ini configuration file in the RuntimeData folder so it has a path applied to it that bypasses the verification of the exe teknoparrot dump applies this path when loading the game. So here's a step by step of what I did I downloaded the openparrot source code unzipped and ran premake.bat for vs2019 (Visual Studio 2019) open openparrot.sln with Visual Studio 2019 I opened openparrot then src/Functions/Games/Other and now DirtyDrivin.cpp in the code I identified where the paths are applied in the configurations, ignoring the .ini file of the RuntimeData folder and these are I commented all of them now I have it compiled in release mode and Win32 after finishing compiling a folder called build is created I follow this path build \ bin \ release \ output and copy all the content and paste it into teknoparrot OpenParrotWin32 folder ok in theory it was just that i thought that when sending teknoparrot to run the game he would not do the verification paths and i could find out the memory address of the coin but i get it when i send it this error means that openparrot checks the CRC executable (Cyclic Redundancy Checksum) and that for some reason I don't know yet, it changed when compiling the new openparrot and that the new CRC generated is 5F4E17C3 I reopened OpenParrot.sln with Visual Studio 2019 I vaculated the code and found GameDetect.cpp I found where it links the CRC with the game id and replaced the old CRC with the new one I thought I had resolved more now by sending teknoparrot to run the game it doesn't show the error anymore it also doesn't open the game now that i don't know what i can do anymore if someone knows what i did wrong and can compile openparrot with the Dirty Drivin modification share it here I appreciate everyone's attention and I think that if we help each other and share our experiences we can evolve and make the dumps as perfect as possible Edited March 30, 2020 by 7zxkv title balise 4 Link to comment Share on other sites More sharing options...
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 account
Already have an account? Sign in here.Sign In Now