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

Home  Search Register  Login Member ListRecent Posts
Viewing User Profile for: Raff
About Contact
Joined: Jul 17, 2019 12:01 PM
Last Post: Jul 31, 2019 01:05 PM
Last Visit: Jul 31, 2019 01:09 PM
Your Age:
What Games do you play:

Send Private Message
Post Statistics
Raff has contributed to 6 posts out of 464915 total posts (0.00%) in 357 days (.02 posts per day).

20 Most recent posts:

Quote: --- Original message by: MrChromed

Don't delete anything. I hope you have a backup from that scenario (A10). If not, re-extract the .scenario from the Refined campaign without recursive mode, since you already have its dependencies in the tags folder.

Now, download this: https://drive.google.com/file/d/15VN8SO_Ic7c6sgw8majYfzGJaJpChRbt/view?usp=sharing
What is it? It's the "editor" folder. You need to place it in tags\ui (the .7z has everything set up correctly, so you will see a "tags" folder once it's extracted. Combine it with your current tags folder).

The "editor" folder contains the visual markers that are drawn in Sapien when you want to place objects. That folder is only present in the HEK install, so you'll always need that folder once you extract maps (the maps don't contain that folder when compiled).

I hope this helps you. Let me know if it worked, please.
Edited by MrChromed on Jul 30, 2019 at 01:16 PM

Hi there, that didn't work. However I decided to uninstall custom edition and to start fresh, no opensauce, no chimera just custom edition as it was before and the editing kit. Sapien now loads the scenario : )

Seems to be the same
07.29.19 23:54:38 sapien pc ----------------------------------------------
07.29.19 23:54:38 reference function: _write_to_error_file
07.29.19 23:54:38 reference address: 401b13
07.29.19 23:54:38 Couldn't read map file './sapienbeta.map'
07.29.19 23:54:39 CreateDevice succeeded with refresh rate = 0

However above it there's a new line that has

07.29.19 23:51:22 guerilla pc ----------------------------------------------
07.29.19 23:51:22 reference function: _write_to_error_file
07.29.19 23:51:22 reference address: 4011a4
07.29.19 23:51:22 Couldn't read map file './guerillabeta.map'

maybe it's from when I edited the scenario with guerilla

Quote: --- Original message by: Dabouss 15x
Try opening the scenario in Guerilla and deleting all of the script related elements near the bottom.


The options to delete the scripts, globals and references are grayed out on normal guerilla, however opening the scenario with OSguerilla doesn't have those options grayed out. Should I proceed with OSguerilla?

Edit: Alright I proceeded to delete the scripts with OSguerilla but sapien still won't open the scenario, it just closes. I tried OS_sapien as well.
Edited by Raff on Jul 29, 2019 at 05:03 PM

I extracted a10 from the refined campaign using refinery but when I try to open the scenario with sapien the program just closes. Actually it closes on every map I try to extract, even if it's just bloodgulch.

I remember seeing something about disabling "visual themes and disable desktop composition" but I'm running windows 10 and those options are gone.

This is the debug

07.29.19 23:05:09 sapien pc ----------------------------------------------
07.29.19 23:05:09 reference function: _write_to_error_file
07.29.19 23:05:09 reference address: 401b13
07.29.19 23:05:09 Couldn't read map file './sapienbeta.map'
07.29.19 23:05:10 CreateDevice succeeded with refresh rate = 0

Halo 2 Vista General Discussion » How to edit weapon damage in assembly? Jul 18, 2019 10:26 AM (Total replies: 0)

I can't find the values that change weapon damage : |

So, I've had a lot of fun messing around with Assembly and modifying Halo 2's enemy encounters. I noticed however that some enemy squads would only load if the game is set to heroic or legendary. That is the case even if I set the enemy count to a higher number in the Normal difficulty count.

Is there a way to tweak it so those squads appear in lower difficulties? Or is there a way of modifying the legendary difficulty so it has the same values as heroic/normal.

Time: Tue July 7, 2020 3:38 PM 313 ms.
A Halo Maps Website