Dwood
September 26th, 2009, 09:55 AM
Okay so lately I've decided to take a dive into Open Sauce's new Hek. While some have claimed it is buggy, I will admit I have had problems as well, however most, if not all of them are quickly fixable.
The first error I've ever gotten was the (slightly) infamous "kludge" error.
09.25.09 18:12:29 sapien pc 01.00.08.0616 ----------------------------------------------
09.25.09 18:12:29 reference function: _write_to_error_file
09.25.09 18:12:29 reference address: 401b13
09.25.09 18:12:29 Couldn't read map file './sapienbeta.map'
09.25.09 18:13:31 Couldn't read map file './sapienbeta.map'
09.25.09 18:13:31 EAX: 0x00000000
09.25.09 18:13:31 EBX: 0x00000040
09.25.09 18:13:31 ECX: 0x00000000
09.25.09 18:13:31 EDX: 0x00000000
09.25.09 18:13:31 EDI: 0x0012E960
09.25.09 18:13:31 ESI: 0x0012EE8C
09.25.09 18:13:31 EBP: 0x0012ED38
09.25.09 18:13:31 ESP: 0x0012E944
09.25.09 18:13:31 EIP: 0x00417E20, 8B 01 8B 96 ?????
09.25.09 18:13:31 0012FFF0 ?????
09.25.09 18:13:31 004053C0 ?????
09.25.09 18:13:31 7FF89EB8 ?????
09.25.09 18:13:31 7FF514CE ?????
09.25.09 18:13:31 7FF5152C ?????
09.25.09 18:13:31 7FF528A2 ?????
09.25.09 18:13:31 00751B18 ?????
09.25.09 18:13:31 004F8200 ?????
09.25.09 18:13:31 EXCEPTION_ACCESS_VIOLATION
^^^^ With default Open Sauce coded .dll compiled (kludge error)
With normal d3d9.dll:
09.25.09 18:12:05 sapien pc 01.00.08.0616 ----------------------------------------------
09.25.09 18:12:05 reference function: _write_to_error_file
09.25.09 18:12:05 reference address: 401b13
09.25.09 18:12:05 Couldn't read map file './sapienbeta.map'
Just cut and paste the Opensauce/d3d9.dll to outside of HaloCE's root directory while using OS_Sapien. As far as I'm aware, Sapien is the only hek tool that has this problem.
_____
Project_Yellow tag:
There's another error, which is quite interesting, because I didn't even know of the tag's existence, was Korn's "i've got a lovely bunch of corncobs.project_yellow" tag.
-----> If you got this you did not properly set your Project_Yellow reference (that is the default tag if you save/open a map from guerilla or sapien that hasn't been used with OS_hek yet)
Open guerilla, file -> new -> project_yellow, for best results, I think that using the same name as the map would work best. (for an example, i'll use tutorial) name it tutorial. From there you will see a list of brand new fields:
http://lookpic.com/t/789/9mJ2lyh6.jpeg (http://lookpic.com/i/789/9mJ2lyh6.jpeg)
http://lookpic.com/t/184/06xgPw88.jpeg (http://lookpic.com/i/184/06xgPw88.jpeg)
For now, just save the project_yellow tag without changing anything. Next, open the scenario tag from OS_Guerilla. At the top, you will see a part called "project yellow definitions" click browse, and go to your project_yellow tag and press ok.
Was that so hard?
Old Fix:
Just create your own tag with that name and put it at the root of the Halo_CE folder, I'm not sure what references it anywhere though.
_____
Another thing is that if you have OS_guerilla open, and can't see the "project_yellow" tag type when creating new tags, cut and paste the tag_groups.map file from the original OS_folder you extracted the OS_hek from.
The first error I've ever gotten was the (slightly) infamous "kludge" error.
09.25.09 18:12:29 sapien pc 01.00.08.0616 ----------------------------------------------
09.25.09 18:12:29 reference function: _write_to_error_file
09.25.09 18:12:29 reference address: 401b13
09.25.09 18:12:29 Couldn't read map file './sapienbeta.map'
09.25.09 18:13:31 Couldn't read map file './sapienbeta.map'
09.25.09 18:13:31 EAX: 0x00000000
09.25.09 18:13:31 EBX: 0x00000040
09.25.09 18:13:31 ECX: 0x00000000
09.25.09 18:13:31 EDX: 0x00000000
09.25.09 18:13:31 EDI: 0x0012E960
09.25.09 18:13:31 ESI: 0x0012EE8C
09.25.09 18:13:31 EBP: 0x0012ED38
09.25.09 18:13:31 ESP: 0x0012E944
09.25.09 18:13:31 EIP: 0x00417E20, 8B 01 8B 96 ?????
09.25.09 18:13:31 0012FFF0 ?????
09.25.09 18:13:31 004053C0 ?????
09.25.09 18:13:31 7FF89EB8 ?????
09.25.09 18:13:31 7FF514CE ?????
09.25.09 18:13:31 7FF5152C ?????
09.25.09 18:13:31 7FF528A2 ?????
09.25.09 18:13:31 00751B18 ?????
09.25.09 18:13:31 004F8200 ?????
09.25.09 18:13:31 EXCEPTION_ACCESS_VIOLATION
^^^^ With default Open Sauce coded .dll compiled (kludge error)
With normal d3d9.dll:
09.25.09 18:12:05 sapien pc 01.00.08.0616 ----------------------------------------------
09.25.09 18:12:05 reference function: _write_to_error_file
09.25.09 18:12:05 reference address: 401b13
09.25.09 18:12:05 Couldn't read map file './sapienbeta.map'
Just cut and paste the Opensauce/d3d9.dll to outside of HaloCE's root directory while using OS_Sapien. As far as I'm aware, Sapien is the only hek tool that has this problem.
_____
Project_Yellow tag:
There's another error, which is quite interesting, because I didn't even know of the tag's existence, was Korn's "i've got a lovely bunch of corncobs.project_yellow" tag.
-----> If you got this you did not properly set your Project_Yellow reference (that is the default tag if you save/open a map from guerilla or sapien that hasn't been used with OS_hek yet)
Open guerilla, file -> new -> project_yellow, for best results, I think that using the same name as the map would work best. (for an example, i'll use tutorial) name it tutorial. From there you will see a list of brand new fields:
http://lookpic.com/t/789/9mJ2lyh6.jpeg (http://lookpic.com/i/789/9mJ2lyh6.jpeg)
http://lookpic.com/t/184/06xgPw88.jpeg (http://lookpic.com/i/184/06xgPw88.jpeg)
For now, just save the project_yellow tag without changing anything. Next, open the scenario tag from OS_Guerilla. At the top, you will see a part called "project yellow definitions" click browse, and go to your project_yellow tag and press ok.
Was that so hard?
Old Fix:
Just create your own tag with that name and put it at the root of the Halo_CE folder, I'm not sure what references it anywhere though.
_____
Another thing is that if you have OS_guerilla open, and can't see the "project_yellow" tag type when creating new tags, cut and paste the tag_groups.map file from the original OS_folder you extracted the OS_hek from.