![]() | i3D.net Support (email & live chat)
|
| |||||||||
| Register | Invite Your Friends | All Albums | Members List | Social Groups | Search | Today's Posts | Mark Forums Read |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
| | #1 (permalink) |
| Guest
Posts: n/a
Downloads: Uploads: | cooking maps to keep the file size down - see the quote from Matt below. Where you have 'nice' mappers only cooking where there's a good reason to do so you end up with much smaller maps which compress well. Where you have maps from people who cook them regardless of whether this is the right thing to do or not you end up with unnecessarily large maps which get even larger when compressed. The scenario you end up with is: 1. Correctly Uncooked maps which need to be on the redirect compressed 2. Correctly Cooked maps containing significant custom content which need to be on the redirect uncompressed 3. Incorrectly Cooked maps which need to which need to be on the redirect uncompressed If the mappers do the right thing the majority will end up as option 1. Originally Posted by *Matt Oelfke from Epic:* The filesize reduction most people see is primarily compression (approximately equal to what the compress commandlet would do on the uncooked package) - in general, cooked packages are larger than their uncooked counterparts because of asset duplication (i.e. if you use any Epic assets, they will have some of their data baked into the map file instead of remaining in the separate packages). *I've said several times that I think it's only worth cooking if you're using significant custom content, but it appears most aren't bothering to deal with the distinction since, among other things, cooking also automatically puts files in the right places (partially our fault for a bad interface).* Gregg Hanpeter wrote: > I remember awhile ago we compared different types of compression to a > cooked map and there was never any relevant difference most of the > time. I would say go with no compression. From what I read here and > there its not really worth the trouble since the cooked map is pretty > much optimized. > > > On Tue, Apr 22, 2008 at 4:14 PM, Stephen Piglet C-E > <stephen.christian-edwards (AT) btconnect (DOT) com > <mailto:stephen.christian-edwards (AT) btconnect (DOT) com>> wrote: > > Dear Epic, > > Please could you tweek the logic for redirect downloads when > compression is turned on such that it first looks on the redirect > server for the compressed file name and a 404 response is received > it looks for an uncompressed file name? > > Sometimes compressed files are larger than uncompressed.....and it > would be nice to be able to be able to put whichever is smaller to > the redirect. > > Thanks > > --------------------- > TO LEAVE THE LIST Read more on: : i3D.net Game Forums /unreal-tournament-3-newsletter/41690-re-ut3servers-redirect-logic-tweek-please.html > --------------------- > Write to LISTSERV (AT) LIST (DOT) EPICGAMES.COM > <mailto:LISTSERV (AT) LIST (DOT) EPICGAMES.COM> and, in the text of your > message > (not the subject line), write: SIGNOFF UT3SERVERS > > > --------------------- > TO LEAVE THE LIST > --------------------- > Write to LISTSERV (AT) LIST (DOT) EPICGAMES.COM and, in the text of your message > (not the subject line), write: SIGNOFF UT3SERVERS > --------------------- TO LEAVE THE LIST --------------------- Write to LISTSERV (AT) LIST (DOT) EPICGAMES.COM and, in the text of your message (not the subject line), write: SIGNOFF UT3SERVERS |
|
| Sponsored Links |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |
| New To Site? | Need Help? |