Re: UserTool - OpenSauce command line tool
Code:
0041E0F9 LEA ECX,[LOCAL.70]
0041E0FD PUSH ECX
0041E0FE PUSH 20019
0041E103 PUSH 0
0041E105 PUSH OFFSET 004253A4 ; ASCII "SOFTWARE\Microsoft\Microsoft Games\Halo HEK"
0041E10A PUSH 80000002
0041E10F CALL DWORD PTR DS:[<&ADVAPI32.RegOpenKeyExA>]
My registry path was default: "SOFTWARE\\Wow6432Node\\Microsoft\\Microsoft Games\\Halo HEK". I am running Windows 7. Regardless of where your Halo Custom Edition directory is installed or whether it's x86 or x64, the registry entry it opens may be incorrect. Since UserTool must be placed in the Halo CE directory anyway, may I suggest using GetCurrentDirectory or GetModuleFileName to obtain the path? Otherwise you may need to check multiple registry paths.
Re: UserTool - OpenSauce command line tool
Quote:
Originally Posted by
Skarma
Code:
0041E0F9 LEA ECX,[LOCAL.70]
0041E0FD PUSH ECX
0041E0FE PUSH 20019
0041E103 PUSH 0
0041E105 PUSH OFFSET 004253A4 ; ASCII "SOFTWARE\Microsoft\Microsoft Games\Halo HEK"
0041E10A PUSH 80000002
0041E10F CALL DWORD PTR DS:[<&ADVAPI32.RegOpenKeyExA>]
My registry path was default: "SOFTWARE\\
Wow6432Node\\Microsoft\\Microsoft Games\\Halo HEK". I am running Windows 7. Regardless of where your Halo Custom Edition directory is installed or whether it's x86 or x64, the registry entry it opens may be incorrect. Since UserTool must be placed in the Halo CE directory anyway, may I suggest using GetCurrentDirectory or GetModuleFileName to obtain the path? Otherwise you may need to check multiple registry paths.
This is actually quite simple to fix, however the fix I am about to give really only changes the registry usertool tries to find: the x32 Halo HEK registry, and instead makes it look for the x64 directory.
I was going to make a small tutorial on how to do this yourself, but because of how FireSythe has his project folders and directories set up (He has the directories/folders on another hard drive of some kind, I had to use my flash drive to make it look there. I even placed all the files exactly the way he had it, and Visual C++ still told me it couldnt find the files, even though it was sitting in front of it's stupid face.) I cannot accomplish that. I did however make a successful exe a while ago, and I have no idea what caused it to not work anymore.
Anyway, enough rambling, here is the exe I promised.
http://www.codebrainshideout.net/files/usertool_x64.exe
Re: UserTool - OpenSauce command line tool
The odd thing is it was developed and tested on x64 since that's what I use. When I get the chance i'll change it to use the current working directory rather than the registry path.
Re: UserTool - OpenSauce command line tool
Yeah, the usertool_x64.exe gets the same error for me, thanks though CodeBrain. Guess I'll have to wait for Firescythe's fix.
Re: UserTool - OpenSauce command line tool
Add some more error checking so the app can spit out the exact error codes from failed functions, might help work out the kinks
Re: UserTool - OpenSauce command line tool
Oh derp I forgot to give you guys the .reg file as well. <_>
http://codebrainshideout.net/files/Halo_HEK_x64.reg
If you install the Halo Editing Kit on a x64 bit machine, I think usertool tries to look in the x32 registry instead of the x64 registry. Therefore, the solution is to copy what the x64 registry for "Halo HEK" has and import it into the x32 bit. The file above is the solution. (I think)
Re: UserTool - OpenSauce command line tool
Drat. Still gives that error. Does it work on your end?
And I'm testing it by typing in usertool_x64.exe, then seeing if it gives a list of commands, like tool does. Instead, it gives back that error. If I need to type an actual command, let me know. I couldn't figure out what exactly that command was, honestly.
Re: UserTool - OpenSauce command line tool
@Siliconmaster: Try this fix I cooked up, works great for me now. It uses a different method other than the registry to get your Halo CE working directories. Just don't forget to put it in your Halo CE folder before running it. You may need to run as admin, but it worked without that for me.
usertool with fixed paths problem:
http://www.mediafire.com/?9yjwp1i4vqqt3rc
Changed:
To:
Re: UserTool - OpenSauce command line tool
and not only that, the app is also 20 bytes faster congratz :allears:
Re: UserTool - OpenSauce command line tool
All right, Skarma fixed the issue for me, though he initially fixed the earlier version of usertool, not the most updated one. However, now the app itself is giving me crap lol. Max exports the 22 lightmaps as a single .obj file. But when the app tries to import the uvs, it says that the bsp has 295 objects. Wat. How do I fix this?
