I'm new to open sauce and i have a number of questions.

1. I want to make a map that's only around 180mb (its all i need really). I understand the problems accociated with going over 128mb, but regardless i REALLY need the extra 50mb to fit in all I want. Since the creators kept claiming how it was boosted from 128 (to over 500?!?!), I assumed there ought to be some easy way to utilise that single element. I noticed that using:
OS_tool build-cache-file
still gets the 128mb limit error. So, how would I go about making my .map file thats larger than the normal limit, considering I have done all of it up to this point without OS?

2. I heard that you can make these OS maps work with people who don't have OS by giving them like 2 or so files to put in their halo root directory to make features like multiteam vehicles and stuff work. Is this true? If so, then what files are needed? And if so, will it also work with the portable version of Halo custom edition that I used to play at school off the USB with, and was v1.09?

3. What is a .project_yellow? Is that the OS version of .scenerio or is that a project by someone? I assume scenerio because of .yelo, but I'm unsure.

4. Is OS_tool build-cache-file even the right command to make a OS map?

I feel like, despite all the hype, there has been a serious lack of actual explaining as to what can be done and HOW.

i never made os maps but i know you need different command to compile map.

from what I have figured out
os_tool build-cache-file <scenario location>
is the same as
os_tool build-cache-file-ex <map name> false false false <scenario location>

is the third 'false' is made true, than the size limit is lifted, but its now a dirty .yelo >=(
i hope i can get this sorted soon, this is really bugging me.

yes, that''s hhow it works. .yelos get no size limit,, really comes in handy.

actually If I remember correctly .yelo does have a 512mb cap limit.

The fact is that people have made huge 300 mb .MAP files, and I want to be able to likewise. I doubt THAT large, but the ability ought to be there.

if there is a mp map that is over 128 mb and is a .map then they used tool pro (dont use it its bad). and mootjuh when compiling a map over 128 mb with os tool it will be compiled into a .yelo therefor only OS users can play the map.
Edited by Spark on Feb 12, 2013 at 06:14 PM

SP maps have a larger limit than MP maps

that's why I said any mp .map that is over 128 mb was compiled with tool_pro
Edited by Spark on Feb 12, 2013 at 08:20 PM

Its truly a shame that tool pro is like virus ridden and such, but i wish that someone would make a -legit- one. I only really wanted to stay with .map because this whole data_files thing i don't understand. and people keep talking about taggroups.map... do i need to do a command to make that? then what do i do if i want another person with OS to run my map without crashing upon attempting to open it. Im not having much success finding out how to use these things...

I don't really think you need to use taggroups.map and the other data_files thing to make a map that can be played normally, is bigger than the 128MB limit and is .yelo.

It consists pretty much of you doing the following:
1. Using os_tool.exe instead of the normal tool.exe to compile your map.
2. Switch on the flag for use-memory-upgrades when you compile, ie.
cmd > "C:\Program Files\Microsoft Games\Halo Custom Edition" os_tool build-cache-file-ex "" 0 0 1 path-to-your-scenario
where - "" is the mod_name, which you don't need
- 0 0 1 is to set the relevant flags, since all you need is the memory upgrades (which change the map file to .yelo instead)

Yes, the other person would need OS to play it, but at the very least your map should be reliable and less crash-prone than maps compiled with tool pro.
Edited by sargejohnson on Feb 13, 2013 at 04:18 AM

Fair enough, I'll give it a shot =)