Page 4 of 5 FirstFirst ... 2 3 4 5 LastLast
Results 31 to 40 of 43

Thread: UserTool - OpenSauce command line tool

  1. #31
    Codesaurus Skarma's Avatar
    Join Date
    Apr 2009
    Location
    Columbus, OH
    Posts
    227

    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.
    Last edited by Skarma; August 27th, 2010 at 02:22 PM.
    Reply With Quote

  2. #32

    Re: UserTool - OpenSauce command line tool

    Quote Originally Posted by Skarma View Post
    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
    Reply With Quote

  3. #33
    Senior Member FireScythe's Avatar
    Join Date
    Sep 2006
    Location
    UK, England
    Posts
    321

    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.
    Reply With Quote

  4. #34
    Movie Maker Siliconmaster's Avatar
    Join Date
    Sep 2006
    Location
    NJ (College)
    Posts
    2,192

    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.
    Last edited by Siliconmaster; August 28th, 2010 at 09:14 AM.
    Reply With Quote

  5. #35
    Codesaurus Skarma's Avatar
    Join Date
    Apr 2009
    Location
    Columbus, OH
    Posts
    227

    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
    Reply With Quote

  6. #36

    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)
    Reply With Quote

  7. #37
    Movie Maker Siliconmaster's Avatar
    Join Date
    Sep 2006
    Location
    NJ (College)
    Posts
    2,192

    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.
    Reply With Quote

  8. #38
    Codesaurus Skarma's Avatar
    Join Date
    Apr 2009
    Location
    Columbus, OH
    Posts
    227

    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:
    Code:
    004376CF  LEA ECX,[ESP+14]
    004376D3  PUSH ECX
    004376D4  PUSH 20019
    004376D9  PUSH EBX
    004376DA  PUSH OFFSET 00449CD0                              ; ASCII "SOFTWARE\Microsoft\Microsoft Games\Halo HEK"
    004376DF  PUSH 80000002
    004376E4  CALL DWORD PTR DS:[<&ADVAPI32.RegOpenKeyExA>]
    004376EA  TEST EAX,EAX
    004376EC  JNE 0043796B
    004376F2  LEA EDX,[ESP+18]
    004376F6  PUSH EDX
    004376F7  MOV EDX,DWORD PTR SS:[ESP+18]
    004376FB  LEA EAX,[ESP+78]
    004376FF  PUSH EAX
    00437700  LEA ECX,[ESP+24]
    00437704  PUSH ECX
    00437705  PUSH EBX
    00437706  PUSH OFFSET 00449CFC                              ; ASCII "EXE Path"
    0043770B  PUSH EDX
    0043770C  MOV DWORD PTR SS:[ESP+34],1
    00437714  MOV DWORD PTR SS:[ESP+30],104
    0043771C  CALL DWORD PTR DS:[<&ADVAPI32.RegQueryValueExA>]
    00437722  MOV EAX,DWORD PTR SS:[ESP+14]
    00437726  PUSH EAX
    00437727  CALL DWORD PTR DS:[<&ADVAPI32.RegCloseKey>]

    To:
    Code:
    004376CF  PUSH EAX
    004376D0  PUSH 104
    004376D5  MOV ECX,DWORD PTR DS:[<&KERNEL32.GetCurrentDirectoryA>]
    004376DB  CALL ECX
    004376DD  TEST EAX,EAX
    004376DF  JE 0043796B
    004376E5  JMP SHORT 0043772D
    004376E7  NOP
    004376E8  NOP
    004376E9  NOP
    004376EA  NOP
    004376EB  NOP
    004376EC  NOP
    004376ED  NOP
    004376EE  NOP
    004376EF  NOP
    004376F0  NOP
    004376F1  NOP
    004376F2  NOP
    004376F3  NOP
    004376F4  NOP
    004376F5  NOP
    004376F6  NOP
    004376F7  NOP
    004376F8  NOP
    004376F9  NOP
    004376FA  NOP
    004376FB  NOP
    004376FC  NOP
    004376FD  NOP
    004376FE  NOP
    004376FF  NOP
    00437700  NOP
    00437701  NOP
    00437702  NOP
    00437703  NOP
    00437704  NOP
    00437705  NOP
    00437706  NOP
    00437707  NOP
    00437708  NOP
    00437709  NOP
    0043770A  NOP
    0043770B  NOP
    0043770C  NOP
    0043770D  NOP
    0043770E  NOP
    0043770F  NOP
    00437710  NOP
    00437711  NOP
    00437712  NOP
    00437713  NOP
    00437714  NOP
    00437715  NOP
    00437716  NOP
    00437717  NOP
    00437718  NOP
    00437719  NOP
    0043771A  NOP
    0043771B  NOP
    0043771C  NOP
    0043771D  NOP
    0043771E  NOP
    0043771F  NOP
    00437720  NOP
    00437721  NOP
    00437722  NOP
    00437723  NOP
    00437724  NOP
    00437725  NOP
    00437726  NOP
    00437727  NOP
    00437728  NOP
    00437729  NOP
    0043772A  NOP
    0043772B  NOP
    0043772C  NOP
    Last edited by Skarma; September 1st, 2010 at 10:05 AM.
    Reply With Quote

  9. #39

    Re: UserTool - OpenSauce command line tool

    and not only that, the app is also 20 bytes faster congratz
    Reply With Quote

  10. #40
    Movie Maker Siliconmaster's Avatar
    Join Date
    Sep 2006
    Location
    NJ (College)
    Posts
    2,192

    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?
    Reply With Quote

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •