A Community discussion forum for Halo Custom Edition, Halo 2 Vista, Portal and Halo Machinima

Home  Search Register  Login Member ListRecent Posts
   		 
»Forums Index »Halo Custom Edition (Bungie/Gearbox) »Halo CE Technical / Map Design »saphien not running on my windows 8 :/

Author Topic: saphien not running on my windows 8 :/ (8 messages, Page 1 of 1)
Moderators: Dennis

Misterbanshee
Joined: Dec 8, 2014
Posted: Dec 8, 2014 09:41 PM    Msg. 1 of 8       
ok so here is the story its kind of weird what happens. SO i install hek, saphien, and guerrilla. the problem starts when my dang sapien only runs when i use it through windows 8 compatibility trouble shooter. once i open a scenario and edit it the map looked good. once i go to open the scenario again sapien would auto close. I look at the debug list and there is a mile long list of stuff going :/ I'm hoping to have some one screen share with me to see if they can help me fix it. when i put hek folder inside the halo ce directory and extract a scenario. after that sapien would not load the scenario at all so i have a whole bunch of problems with sapien not cooperating on my pc I've tried running it as affinity and compatibility mode and every thing nothing seems to work. so would any body here be willing to try to fix my sapien at keeps corrupting my maps. I understand the basics of sapien but I have never had this much trouble with it :/

DOOM899
Joined: Jul 23, 2013

{DM} [gamesmaster] if i can ill help maybe

Posted: Dec 9, 2014 08:19 AM    Msg. 2 of 8       
Quote: --- Original message by: Misterbanshee
ok so here is the story its kind of weird what happens. SO i install hek, saphien, and guerrilla. the problem starts when my dang sapien only runs when i use it through windows 8 compatibility trouble shooter. once i open a scenario and edit it the map looked good. once i go to open the scenario again sapien would auto close. I look at the debug list and there is a mile long list of stuff going :/ I'm hoping to have some one screen share with me to see if they can help me fix it. when i put hek folder inside the halo ce directory and extract a scenario. after that sapien would not load the scenario at all so i have a whole bunch of problems with sapien not cooperating on my pc I've tried running it as affinity and compatibility mode and every thing nothing seems to work. so would any body here be willing to try to fix my sapien at keeps corrupting my maps. I understand the basics of sapien but I have never had this much trouble with it :/
maybe you added a tag that was corrupt

Super Flanker
Joined: Oct 5, 2012

The length of your life depends on my aim.

Posted: Dec 9, 2014 08:41 AM    Msg. 3 of 8       
Quote: --- Original message by: Misterbanshee
ok so here is the story its kind of weird what happens. SO i install hek, saphien, and guerrilla. the problem starts when my dang sapien only runs when i use it through windows 8 compatibility trouble shooter. once i open a scenario and edit it the map looked good. once i go to open the scenario again sapien would auto close. I look at the debug list and there is a mile long list of stuff going :/ I'm hoping to have some one screen share with me to see if they can help me fix it. when i put hek folder inside the halo ce directory and extract a scenario. after that sapien would not load the scenario at all so i have a whole bunch of problems with sapien not cooperating on my pc I've tried running it as affinity and compatibility mode and every thing nothing seems to work. so would any body here be willing to try to fix my sapien at keeps corrupting my maps. I understand the basics of sapien but I have never had this much trouble with it :/


1. Your problem could be linked to files which are missing OR most likely are using files which rely on other files which have been misplaced in some way or sort.

In very extreme cases such as: A virus or bad ripping.
Will your tags become corrupt.

2. By HEK folder what exactly do you mean?

If you MOVE either the data or tags folder located in

C:\program files (x86)\Microsoft Games\Halo Custom Edition

To any other directory within your pc you will of course encounter an incredulous amount of error ridden feedback.

Halo's engine relies on the tags folder to be specifically placed inside the directory to read and compile halo related files successfully. Moving crucial folders elsewhere in your system will not aid or satisfy your problem you are encountering.


Your best bet to get the error fixed is to either screen share with the person you spoke about or delete your debug.txt file > Open the scenerio > wait for it to fail > open the newly created debug.txt file > and copy and paste the contents in this thread.

KAD
Joined: Mar 21, 2015
Posted: Nov 22, 2015 04:49 PM    Msg. 4 of 8       
Quote: --- Original message by: SS Flanker
Quote: --- Original message by: Misterbanshee
ok so here is the story its kind of weird what happens. SO i install hek, saphien, and guerrilla. the problem starts when my dang sapien only runs when i use it through windows 8 compatibility trouble shooter. once i open a scenario and edit it the map looked good. once i go to open the scenario again sapien would auto close. I look at the debug list and there is a mile long list of stuff going :/ I'm hoping to have some one screen share with me to see if they can help me fix it. when i put hek folder inside the halo ce directory and extract a scenario. after that sapien would not load the scenario at all so i have a whole bunch of problems with sapien not cooperating on my pc I've tried running it as affinity and compatibility mode and every thing nothing seems to work. so would any body here be willing to try to fix my sapien at keeps corrupting my maps. I understand the basics of sapien but I have never had this much trouble with it :/


1. Your problem could be linked to files which are missing OR most likely are using files which rely on other files which have been misplaced in some way or sort.

In very extreme cases such as: A virus or bad ripping.
Will your tags become corrupt.

2. By HEK folder what exactly do you mean?

If you MOVE either the data or tags folder located in

C:\program files (x86)\Microsoft Games\Halo Custom Edition

To any other directory within your pc you will of course encounter an incredulous amount of error ridden feedback.

Halo's engine relies on the tags folder to be specifically placed inside the directory to read and compile halo related files successfully. Moving crucial folders elsewhere in your system will not aid or satisfy your problem you are encountering.


Your best bet to get the error fixed is to either screen share with the person you spoke about or delete your debug.txt file > Open the scenerio > wait for it to fail > open the newly created debug.txt file > and copy and paste the contents in this thread.
I'm also a Windows 8/8.1 user and Sapien crashes when I open a scenario campaign file.

KAD
Joined: Mar 21, 2015
Posted: Nov 24, 2015 07:18 PM    Msg. 5 of 8       
Quote: --- Original message by: sparky

The simplest attempt to fix this crashing problem can be to try running each HEK program in Administrator Mode. Right-click on it and look at its properties...

Does "scenario campaign file" mean that you extracted tags using the HEK+ program? You will need to check the "Rec." (Recursive) checkbox next to the .scenario tag in the extraction list in order to extract tags recursively, so that you are not missing any tags. Also note that the HEK+ has problems with some kinds of tags and so I don't think of it as a completely reliable program.

So that means it's a problem with the .scenario tags.

Sapien requires tags to be in working order before it will load a .scenario file. There is a problem with one of your tags that is somehow connected to the globals\globals.globals tag or the .scenario tag you attempted to load. This could be as simple as you missing a tag; when a tag is missing from your tags directory, the tag pathname string text will appear in red in Guerilla when you open the tag that references it.

What you can do is look at the debug.txt file in the Halo Custom Edition folder and see what error Sapien displayed there. You might want to delete the debug.txt file first so you don't have to scroll all the way through the log history to see the current log at the end of the file. So delete the debug.txt file and open the level in Sapien and go back and look at the new debug.txt file to see what Sapien said.

Alternatively, you can attempt to run Tool's build-cache-file command to compile your .scenario tag and it will tell you what problems it encounters.

Now if you can open the levels\test\tutorial\tutorial.scenario tag in Sapien, then it's those other .scenario tags that are having a problem. But if you can't even open that tag in Sapien, then you might need to try reinstalling the HEK. If you're using Open Sauce or some other hacked program, I don't have enough experience to say what to do, since your registry is probably corrupted from having installed those programs.

Edited by sparky on Nov 22, 2015 at 07:01 PM
They're V2s of the campaign files that I'm running.

Here's my debug error's 11.22.15 14:13:43 sapien pc 01.00.00.0609 ----------------------------------------------
11.22.15 14:13:43 reference function: _write_to_error_file
11.22.15 14:13:43 reference address: 401b13
11.22.15 14:13:43 Couldn't read map file './sapienbeta.map'
11.22.15 14:13:43 CreateDevice succeeded with refresh rate = 0
11.22.15 14:13:43 Initializing 10 button 5 axis 1 pov joystick 'Controller (XBOX One For Windows)'
11.22.15 14:13:43 Successfully initialized device axis 258 instance number 1 - Y Axis to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 2 instance number 0 - X Axis to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 1026 instance number 4 - Y Rotation to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 770 instance number 3 - X Rotation to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 514 instance number 2 - Z Axis to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device button 4 instance number 0 - Button 0
11.22.15 14:13:43 Successfully initialized device button 260 instance number 1 - Button 1
11.22.15 14:13:43 Successfully initialized device button 516 instance number 2 - Button 2
11.22.15 14:13:43 Successfully initialized device button 772 instance number 3 - Button 3
11.22.15 14:13:43 Successfully initialized device button 1028 instance number 4 - Button 4
11.22.15 14:13:43 Successfully initialized device button 1284 instance number 5 - Button 5
11.22.15 14:13:43 Successfully initialized device button 1540 instance number 6 - Button 6
11.22.15 14:13:43 Successfully initialized device button 1796 instance number 7 - Button 7
11.22.15 14:13:43 Successfully initialized device button 2052 instance number 8 - Button 8
11.22.15 14:13:43 Successfully initialized device button 2308 instance number 9 - Button 9
11.22.15 14:13:43 Successfully initialized device POV 16 instance number 0 - Hat Switch to range [-4096,4096]
11.22.15 14:13:43 Could not initialize unknown device object 192 instance number 0 - Collection 0 - Game Pad
11.22.15 14:13:43 Could not initialize unknown device object 448 instance number 1 - Collection 1
11.22.15 14:13:43 Could not initialize unknown device object 704 instance number 2 - Collection 2
11.22.15 14:13:43 Could not initialize unknown device object 960 instance number 3 - Collection 3
11.22.15 14:13:43 Sound card doesn't meet minimum hardware requirements. Disabling hardware option.
11.22.15 14:13:44 Increasing sound decompression buffer size to 1048576 bytes
11.22.15 14:13:45 file_open('tags\cinematics\scenery\shotgun\shotgun.scenery') error 0x00000003 'The system cannot find the path specified. '
11.22.15 14:13:45 couldn't open scenery tag 'shotgun.scenery'.
11.22.15 14:13:45 file_open('tags\scenery\vehicles\pelican_crashed\pelican_crashed.scenery') error 0x00000003 'The system cannot find the path specified. '
11.22.15 14:13:45 couldn't open scenery tag 'pelican_crashed.scenery'.
11.22.15 14:13:46 file_open('tags\characters\marine_armored\marine_armored.biped') error 0x00000002 'The system cannot find the file specified. '
11.22.15 14:13:46 couldn't open biped tag 'marine_armored.biped'.
11.22.15 14:13:46 file_open('tags\characters\elite\elite.biped') error 0x00000002 'The system cannot find the file specified. '
11.22.15 14:13:46 couldn't open biped tag 'elite.biped'.
11.22.15 14:13:46 file_open('tags\characters\cyborg\cyborg_unarmed.biped') error 0x00000002 'The system cannot find the file specified. '
11.22.15 14:13:46 couldn't open biped tag 'cyborg_unarmed.biped'.
11.22.15 14:13:46 file_open('tags\vehicles\warthog\warthog.vehicle') error 0x00000002 'The system cannot find the file s
Edited by KAD on Nov 24, 2015 at 08:32 PM

Super Flanker
Joined: Oct 5, 2012

The length of your life depends on my aim.

Posted: Nov 27, 2015 10:08 AM    Msg. 6 of 8       
Quote: --- Original message by: KAD

Quote: --- Original message by: sparky

The simplest attempt to fix this crashing problem can be to try running each HEK program in Administrator Mode. Right-click on it and look at its properties...

Does "scenario campaign file" mean that you extracted tags using the HEK+ program? You will need to check the "Rec." (Recursive) checkbox next to the .scenario tag in the extraction list in order to extract tags recursively, so that you are not missing any tags. Also note that the HEK+ has problems with some kinds of tags and so I don't think of it as a completely reliable program.

So that means it's a problem with the .scenario tags.

Sapien requires tags to be in working order before it will load a .scenario file. There is a problem with one of your tags that is somehow connected to the globals\globals.globals tag or the .scenario tag you attempted to load. This could be as simple as you missing a tag; when a tag is missing from your tags directory, the tag pathname string text will appear in red in Guerilla when you open the tag that references it.

What you can do is look at the debug.txt file in the Halo Custom Edition folder and see what error Sapien displayed there. You might want to delete the debug.txt file first so you don't have to scroll all the way through the log history to see the current log at the end of the file. So delete the debug.txt file and open the level in Sapien and go back and look at the new debug.txt file to see what Sapien said.

Alternatively, you can attempt to run Tool's build-cache-file command to compile your .scenario tag and it will tell you what problems it encounters.

Now if you can open the levels\test\tutorial\tutorial.scenario tag in Sapien, then it's those other .scenario tags that are having a problem. But if you can't even open that tag in Sapien, then you might need to try reinstalling the HEK. If you're using Open Sauce or some other hacked program, I don't have enough experience to say what to do, since your registry is probably corrupted from having installed those programs.

Edited by sparky on Nov 22, 2015 at 07:01 PM
They're V2s of the campaign files that I'm running.

Here's my debug error's 11.22.15 14:13:43 sapien pc 01.00.00.0609 ----------------------------------------------
11.22.15 14:13:43 reference function: _write_to_error_file
11.22.15 14:13:43 reference address: 401b13
11.22.15 14:13:43 Couldn't read map file './sapienbeta.map'
11.22.15 14:13:43 CreateDevice succeeded with refresh rate = 0
11.22.15 14:13:43 Initializing 10 button 5 axis 1 pov joystick 'Controller (XBOX One For Windows)'
11.22.15 14:13:43 Successfully initialized device axis 258 instance number 1 - Y Axis to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 2 instance number 0 - X Axis to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 1026 instance number 4 - Y Rotation to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 770 instance number 3 - X Rotation to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device axis 514 instance number 2 - Z Axis to range [-4096,4096]
11.22.15 14:13:43 Successfully initialized device button 4 instance number 0 - Button 0
11.22.15 14:13:43 Successfully initialized device button 260 instance number 1 - Button 1
11.22.15 14:13:43 Successfully initialized device button 516 instance number 2 - Button 2
11.22.15 14:13:43 Successfully initialized device button 772 instance number 3 - Button 3
11.22.15 14:13:43 Successfully initialized device button 1028 instance number 4 - Button 4
11.22.15 14:13:43 Successfully initialized device button 1284 instance number 5 - Button 5
11.22.15 14:13:43 Successfully initialized device button 1540 instance number 6 - Button 6
11.22.15 14:13:43 Successfully initialized device button 1796 instance number 7 - Button 7
11.22.15 14:13:43 Successfully initialized device button 2052 instance number 8 - Button 8
11.22.15 14:13:43 Successfully initialized device button 2308 instance number 9 - Button 9
11.22.15 14:13:43 Successfully initialized device POV 16 instance number 0 - Hat Switch to range [-4096,4096]
11.22.15 14:13:43 Could not initialize unknown device object 192 instance number 0 - Collection 0 - Game Pad
11.22.15 14:13:43 Could not initialize unknown device object 448 instance number 1 - Collection 1
11.22.15 14:13:43 Could not initialize unknown device object 704 instance number 2 - Collection 2
11.22.15 14:13:43 Could not initialize unknown device object 960 instance number 3 - Collection 3
11.22.15 14:13:43 Sound card doesn't meet minimum hardware requirements. Disabling hardware option.
11.22.15 14:13:44 Increasing sound decompression buffer size to 1048576 bytes
11.22.15 14:13:45 file_open('tags\cinematics\scenery\shotgun\shotgun.scenery') error 0x00000003 'The system cannot find the path specified. '
11.22.15 14:13:45 couldn't open scenery tag 'shotgun.scenery'.
11.22.15 14:13:45 file_open('tags\scenery\vehicles\pelican_crashed\pelican_crashed.scenery') error 0x00000003 'The system cannot find the path specified. '
11.22.15 14:13:45 couldn't open scenery tag 'pelican_crashed.scenery'.
11.22.15 14:13:46 file_open('tags\characters\marine_armored\marine_armored.biped') error 0x00000002 'The system cannot find the file specified. '
11.22.15 14:13:46 couldn't open biped tag 'marine_armored.biped'.
11.22.15 14:13:46 file_open('tags\characters\elite\elite.biped') error 0x00000002 'The system cannot find the file specified. '
11.22.15 14:13:46 couldn't open biped tag 'elite.biped'.
11.22.15 14:13:46 file_open('tags\characters\cyborg\cyborg_unarmed.biped') error 0x00000002 'The system cannot find the file specified. '
11.22.15 14:13:46 couldn't open biped tag 'cyborg_unarmed.biped'.
11.22.15 14:13:46 file_open('tags\vehicles\warthog\warthog.vehicle') error 0x00000002 'The system cannot find the file s
Edited by KAD on Nov 24, 2015 at 08:32 PM


You have missing tags (referenced files which are missing) amongst other things.

KAD
Joined: Mar 21, 2015
Posted: Nov 27, 2015 06:02 PM    Msg. 7 of 8       
What about the campaign cmt files without the missing tags?

KAD
Joined: Mar 21, 2015
Posted: Dec 1, 2015 10:07 PM    Msg. 8 of 8       
Quote: --- Original message by: sparky

With the HEK+ program, you extracted just the .scenario tag, but that tag references other tags in the .map file from which you took it. So you need to check the box for "Rec." (recursively) next to the .scenario tag in the extraction list and extract it again.

HEK+ can be problematic with overwriting tags, so you might want to change the Tags directory in Options to a separate folder in the Halo Custom Edition "tags" folder. Then you can look in the folder and take specific tags you want or need and place them into the proper sub-directory structure within the "tags" directory.
Edited by sparky on Nov 28, 2015 at 11:45 PM
Okay.
 

 
Previous Older Thread    Next newer Thread







Time: Thu January 19, 2023 1:20 AM 266 ms.
A Halo Maps Website