PDA

View Full Version : Cooked / Unpublished / Etc



VerteX
11-24-2007, 09:17 PM
i just have a simpel question:

why add all this complexity? by cooking, etc. in 2k4, i'd save my map and play, i wouldn't have to cook etc...

MaDaStar
11-30-2007, 06:54 AM
It's not really all that complex. All you have to do is click on the publish button after you've finished you're build. Cooking the map optimizes it for play. It may not be all that important for a simple DM level, but in the more complex maps with many rooms with movers, triggers, etc, it'll probably make the difference in FPS. I used to get better performance out of my UT 2004 maps when I split it into zones. If cooking tweaks the performance of maps, I'm all for it.

CVROY
11-30-2007, 09:57 AM
is it possible to edit/change a cooked map and then re-cook it or is that not possible?

ExTerminat0r
11-30-2007, 01:14 PM
is it possible to edit/change a cooked map and then re-cook it or is that not possible?

Yes, it's possible.

Solace
11-30-2007, 02:11 PM
I re-cooked Torlan and it tripled it's filesize... what's up with that?

CVROY
11-30-2007, 03:33 PM
whoa! What is that crap???

nomadicus
11-30-2007, 04:25 PM
Cooking a map optimizes for several reasons, one is to cut down on the time it takes to load while in game. It may make it larger but now it can be read sequentially. All things being equal, even a small file read randomly takes longer.

Defrag your harddrive!

Tranzcoder
11-30-2007, 07:14 PM
That doesn't make sense, why would Epic ship a map that was not already optimised? Obviously, something is missing here. I would think that re-cooking a cooked map would produce basically the same sized file, not a much bigger one!

Explanation needed. Epic?

Tranz

karmatized
11-30-2007, 07:18 PM
wrong, cooked maps compress things based on there settings in the map, depending on the flags you set for textures and music. IT wont make anything bigger or smaller that isnt set to be that way.

by default no compression is used on anything till you cook the map

Wormbo
11-30-2007, 07:30 PM
I re-cooked Torlan and it tripled it's filesize... what's up with that?

Consider it this way: If your meal is already cooked, it will be perfect for eating. However, if you decide to cook it again, you might end up with some yucky, inedible stuff. This is what happened when you tried to cook Torlan again.

Tranzcoder
11-30-2007, 07:51 PM
cooked maps compress things based on there settings in the map, depending on the flags you set for textures and music. IT wont make anything bigger or smaller that isnt set to be that way.

Any place were we can get some info on what these settings are and how they effect compression?

Tranz

karmatized
11-30-2007, 08:11 PM
heres a example
inport a custom audio file, and make the cue for it. You can select its compression in its settings.

It wont actually compress till you cook it, thats why some maps for example are 30 megs and when you cook there like 4 or 5.

epic maps im guessing are prob less cooked then user maps due to faster load times since everyone already has them when they install

CVROY
12-03-2007, 01:08 PM
If I edited torlan to my liking and added or minus a thing or two and I re-cook it why would there any yucky inedible stuff?

Era
12-03-2007, 01:41 PM
Whoa, whoa. What is all the cooked, recook stuff you are all throwing around? Am I missing something, you have to publish the map in some way, or what is it, cook it, before you stick it in the published folder to play?

Someone explain to me or give me a link explaining the concept of this cook/publish thing, and how to go about doing it.

RealF4lcon
01-07-2008, 10:45 AM
Can a map/mod/file be cooked indefinetely?