
Guilty_spark
Joined: Dec 8, 2011
enjoy my bright, blue, balls!
|
Posted: Feb 13, 2012 09:59 PM
Msg. 1 of 7
can someone tell me how to fix problem when compiling OS map.The problem is when it finishes compiling I look in my maps folder and all I get is a temporary uncompressed cache file.
Edited by Spark on Feb 15, 2012 at 04:40 PM
|
|
|

game user10
Joined: Dec 9, 2011
Who is the Overseer?
|
Posted: Feb 15, 2012 08:02 AM
Msg. 2 of 7
Type in tool 'os_tool build-cache-file-ex "" 0 0 1 <scenario>'
|
|
|

Guilty_spark
Joined: Dec 8, 2011
enjoy my bright, blue, balls!
|
Posted: Feb 15, 2012 04:34 PM
Msg. 3 of 7
when it finished compiling I look in the maps folder and all I got was a temporary uncompressed cache file.
|
|
|

game user10
Joined: Dec 9, 2011
Who is the Overseer?
|
Posted: Feb 16, 2012 05:25 AM
Msg. 4 of 7
Quote: --- Original message by: Spark when it finished compiling I look in the maps folder and all I got was a temporary uncompressed cache file. That means tool did not finish... That or you typed in build-cache-file-ex <mod-name> 1 1 1 <scenario> Here is the help from the Open Sauce wiki build-cache-file-ex Builds a cache file with extra Open Sauce arguments. Output cache file will be in .yelo format instead of .map if use-memory-updates is on. (the first "1") create-anew - Should new data-files be created before building the cache? (the second "1") store-resources - Should the scenario's bitmaps/sounds/locale data be stored in the data-files? (the third "1") use-memory-upgrades - Does the scenario require Open Sauce's memory upgrades to run? Produces .yelo file instead of .map Your error has something to do with the data-files, so you should try using 0 0 1 instead, cause that's what happened to me and doing the 0 0 1 fixed it. Edited by game user10 on Feb 16, 2012 at 05:34 AM
|
|
|

Guilty_spark
Joined: Dec 8, 2011
enjoy my bright, blue, balls!
|
Posted: Feb 16, 2012 04:34 PM
Msg. 5 of 7
I already did 0 0 1 and korman told me to get latest version of OS so I did now I get this
os_tool Invalid format in data file bitmaps ### FAILED TO OPEN DATA-CACHE FILE.
Invalid format in data file sounds ### FAILED TO OPEN DATA-CACHE FILE.
Invalid format in data file loc ### FAILED TO OPEN DATA-CACHE FILE.
WARNING: 11 clusters in structure_bsp levels\test\tutorial\tutorial have no back ground sound or sound environment. pre-processing custom tag instances... done culling uncompressed model vertices...done culling uncompressed structure bsp vertices...done culling uncompressed model animation data...done building predicted resources for structures...done processing custom tag instances...done structure bsp 'levels\test\tutorial\tutorial' is 0.26M tag headers and names are 0.18M streaming model vertex and index buffers...done streaming tagsEAX: 0x00000000 EBX: 0x00000000 ECX: 0xEB5C9CBA EDX: 0x0324E698 EDI: 0x00000000 ESI: 0x010A11C0 EBP: 0x0012A2B0 ESP: 0x0012A240 EIP: 0x004BA29B, 8B 04 18 03 ????? 5F796B73 ????? EXCEPTION_ACCESS_VIOLATION
EXCEPTION (that's all I know!)
|
|
|

OrangeJuice
Joined: Jan 29, 2009
Documentation and debug.txt
|
Posted: Feb 17, 2012 12:44 PM
Msg. 6 of 7
okay: os_tool build-cache-file-ex modname create-anew store-resources memory-upgrade path/to/scenario/scenario-name
modname: This won't affect your map unless you are planning to make a with shared tag-collection, for like.... mapseries using same tags..(A.F.A.I.K.)
create-anew: This should not be used if you have already compiled your map(you failed this one right? if so, put 1), This puts a copy of your maps "source code" into OpenSauce, so that it knows you use OpenSauce content in it. If you've already compiled it(with os_tool build-cache-file-ex) before, you just put 0 from now on. EDIT> you can put 1 or 0 afterwards, it'd only make a difference on a super-slow computer(maybe) where you'd notice the different speed of the compilation process
store-resources: This tells your map that instead of putting all of its custom sounds and bitmaps into sounds.map and bitmaps.map, it will either be referenced with OpenSauce-storage, or stored directly into your map.(ask the developer, I don't know which one is the truth :P )
memory-upgrade: Like everyone says: This makes your wanted .map into a .yelo instead, BUT it also tells your map that it will be using a higher tagspace capacity(also A.F.A.I.K., I'vent made a .yelo of my own yet.)
Basically if you want to compile a map(after installing OpenSauce) you'd have to use os_tool build-cache-file-ex modname # # # yourmap
For any generic map you'd probably just use blahblah 1 0 0 yourmap (If you've never compiled it into a map yet)
and then 0 0 0 (If you have compiled it into a .map or .yelo before)
If it still isn't working, have you upgraded your OS? Edited by OrangeJuice on Feb 17, 2012 at 12:46 PM
|
|
|

Guilty_spark
Joined: Dec 8, 2011
enjoy my bright, blue, balls!
|
Posted: Feb 17, 2012 01:25 PM
Msg. 7 of 7
nvm its working now.
|
|
|
| |
|
|
 |
|