Unity Heat [v0.6.9.0] [Edef]

[ftmme56r5]

Well, thats very strange, just tested everything on vm with fresh windows, everything works fine :/ The only problem I could think of, is when you patch game more than once in "pattern" mode (Fixed it in latest version)
View attachment 1560059

I've encountered one thing.
idk why, but after patching one GameAssembly.dll patcher decides all other new copies of unpatched .dlls as already patched. It appeared when I reinstalled the game and also reinstalled patcher said me that "this file has already been patched" while it wasn't.
Fixed it by erasing "HKEY_CURRENT_USER\SOFTWARE\CHOODICK" in windows registry.
Maybe, I suppose, this also can do for those guys, who get various .dll errors.

 

[THE_CHOODICK]

I've encountered one thing.
idk why, but after patching one GameAssembly.dll patcher decides all other new copies of unpatched .dlls as already patched. It appeared when I reinstalled the game and also reinstalled patcher said me that "this file has already been patched" while it wasn't.
Fixed it by erasing "HKEY_CURRENT_USER\SOFTWARE\CHOODICK" in windows registry.
Maybe, I suppose, this also can do for those guys, who get various .dll errors.

Hmm, I am using Keccak_512 hashing algorithm to store info about pathed dlls, so it should not be a problem, but it looks like I fucked up something:/

 

[THE_CHOODICK]

I've encountered one thing.
idk why, but after patching one GameAssembly.dll patcher decides all other new copies of unpatched .dlls as already patched. It appeared when I reinstalled the game and also reinstalled patcher said me that "this file has already been patched" while it wasn't.
Fixed it by erasing "HKEY_CURRENT_USER\SOFTWARE\CHOODICK" in windows registry.
Maybe, I suppose, this also can do for those guys, who get various .dll errors.

Thanks for the report again, just fixed the problem (I have stored hash in QByteArray, and it looks like it was the problem)

 

[Caerna]

It's just me or physics is jittery in last version? Grab a boob and it jumps around.

 

[ftmme56r5]

Thanks for the report again, just fixed the problem (I have stored hash in QByteArray, and it looks like it was the problem)

Yeah, storing something somewhere... That says me nothing, lol, me dumb don't understand programming
Still glad it was useful)
And thanks YOU a lot for your patcher, you're amazing!)

 

[Lans90]

Should the patcher be in the game folder (in the same place as the exe)? Gives an error message.

 

[THE_CHOODICK]

Yeah, storing something somewhere... That says me nothing, lol, me dumb don't understand programming
Still glad it was useful)
And thanks YOU a lot for your patcher, you're amazing!)

At least you know about registries, so you ain't that dumb

 

[THE_CHOODICK]

Should the patcher be in the game folder (in the same place as the exe)? Gives an error message.

No, you should be able to patch the game almost anywhere, can you give me some more info? (if it is "GameAssembly.dll has changed too much ...", than it might occure if you didn't close the game (cause I forgot to fix this bug))

 

[Lans90]

No, you should be able to patch the game almost anywhere, can you give me some more info? (if it is "GameAssembly.dll has changed too much ...", than it might occure if you didn't close the game (cause I forgot to fix this bug))

CreateEventW , DLL api-ms-win-core-synch-l1-2-0.dll

sorry, and thank you for reply

 

[THE_CHOODICK]

CreateEventW , DLL api-ms-win-core-synch-l1-2-0.dll

sorry, and thank you for reply

Yeah, I know about this problem, but unfortunately I don't think I can do much about it :/
If you are on Window 7 or 8, you can try to download this

You must be registered to see the links

If you are on Windows 10, you can try

You must be registered to see the links

If nothing helps, you can try older version of my pather or you could try

You must be registered to see the links

(same thing, but all of the dlls are not inside exe file) - here is

You must be registered to see the links

 

[Lans90]

Yeah, I know about this problem, but unfortunately I don't think I can do much about it :/
If you are on Window 7 or 8, you can try to download this

You must be registered to see the links

If you are on Windows 10, you can try

You must be registered to see the links

If nothing helps, you can try older version of my pather or you could try dynamic build (same thing, but all of the dlls are not inside exe file) - here is

You must be registered to see the links

Unfortunately, I didn't succeed, but in any case, thanks for your responsiveness.

 

[THE_CHOODICK]

Unfortunately, I didn't succeed, but in any case, thanks for your responsiveness.

Sorry for that, also, you can try to replace GameAssembly.dll with one, I have linked

You must be registered to see the links

 

[sexyb83]

I find this patcher still works just fine

 

[Alex9107]

Unfortunately, I didn't succeed, but in any case, thanks for your responsiveness.

This is a problem with the version of the api-ms-win-core-synch-l1-2-0.dll for 64-bit Windows 7.

Your computer most likely has a version of api-ms-win-core-synch-l1-2-0.dll between 10.0.10240.16384 - 10.0.17134.12, and HeatPatcher requires an older version of api-ms-win-core- synch-l1-2-0.dll 6.3.9600.16384.

If you replace api-ms-win-core-synch-l1-2-0.dll in the path C: \ Windows \ System32, then other applications on your computer may stop working, so the actions should be as follows:

• Copy HeatPatcher.exe and api-ms-win-core-synch-l1-2-0.dll (6.3.9600.16384) to the Heat_0.3.3.1 game folder (where the Heat.exe launching file is located)
• Run HeatPatcher.exe and do everything it asks
• Without starting the game, close HeatPatcher.exe and delete HeatPatcher.exe and api-ms-win-core-synch-l1-2-0.dll (6.3.9600.16384)
• Run the game Heat.exe and click the Authenticate button ... Enjoy...

Attachment: api-ms-win-core-synch-l1-2-0.zip Size: 1607 bytes

In the archive

Name: api-ms-win-core-synch-l1-2-0.dll Size: 4096 bytes (4 KiB)
CRC32: BB765D6E
CRC64: 3CB8E01CF0B2A0DC
SHA256: 7F840E721C8CD073631F03159565219D24128EACA905668CFC7394889B908B9E
SHA1: 56659C88000FF70422E818AD827FDCB01F036DE2
BLAKE2sp: 1D917A3D03C2392F2AC688C0A4DF660F9EABB6DD6880F8EB5B99D35C803DFF15

 

[THE_CHOODICK]

I find this patcher still works just fine

Well, thats my old one, I created new, cause some people have no idea how to work with it

 

[Novasigma109]

I’m trying to connect my quest to my lap to play this any tips or instructions on how I can make this easy for myself

 

[Shy Pirate]

Sorry for that, also, you can try to replace GameAssembly.dll with one, I have linked here

When I try do download your new patcher, Windows Defender say there is a trojan in it. Do you have any comment?

 

[SoftDeerBoi]

When I try do download your new patcher, Windows Defender say there is a trojan in it. Do you have any comment?

Same problem

 

[haunt3r]

When I try do download your new patcher, Windows Defender say there is a trojan in it. Do you have any comment?

Same problem

It's likely one of two things, you're Edge browser is set up to warn you about .exe files (seen plenty of exe files be flagged as "potentially" malicious because Microlimp Microsoft doesn't have them on file.

If it is in fact Windows Defender, I'd put it in the same boat/potential paranoid heurystics in place to catch PUP. My Malwarebytes doesn't alert as a virus, and he's posted several virustotal scan links. here's one I ran for shits and giggles because your posts made me curious.

You must be registered to see the links

 

[Shy Pirate]

It's likely one of two things, you're Edge browser is set up to warn you about .exe files (seen plenty of exe files be flagged as "potentially" malicious because Microlimp Microsoft doesn't have them on file.

If it is in fact Windows Defender, I'd put it in the same boat/potential paranoid heurystics in place to catch PUP. My Malwarebytes doesn't alert as a virus, and he's posted several virustotal scan links. here's one I ran for shits and giggles because your posts made me curious.

You must be registered to see the links

That's what I thought, just wanted to make sure that it was Windows being weird again, and not an actual problem.