Report, edit, etc...Posted by AcidYoshi on 2005-03-31 at 21:58:21
I have a Defense game that with no sounds has a size of 9.1 something MB!
It takes forever to download. I haven't a single clue why its so big.
It's a sweet map and I really want to release it, but nobody will spend an hour downloading it!
It takes forever to download. I haven't a single clue why its so big.
It's a sweet map and I really want to release it, but nobody will spend an hour downloading it!
Report, edit, etc...Posted by LegacyWeapon on 2005-03-31 at 22:03:18
Open the archive with WinMPQ and see if there are any files other than "staredit\scenario.chk"
If there are, you can probably delete them consider the fact that you said you have no sounds in your map.
If there are, you can probably delete them consider the fact that you said you have no sounds in your map.
Report, edit, etc...Posted by Heimdal on 2005-03-31 at 22:07:16
Remember to click the "compact" button on WinMPQ too. If the CHK is ridiculously large, post the map and I'll see what I can do.
Report, edit, etc...Posted by chuiu on 2005-03-31 at 22:17:19
He wouldn't be able to post it, you can send it to me via AIM if any of those methods aren't working.
Report, edit, etc...Posted by AcidYoshi on 2005-03-31 at 22:36:47
Thanks for the directions but I dont know how to open win mpq (whatever that is).
Report, edit, etc...Posted by Red2Blue on 2005-03-31 at 22:37:13
It may be that the file of the file has added scrap files into the map itself.
What works for me for removing these are by:
Opening the file in starforge, saving it, opening it in a regular editor, saving it, then opening in the starforge again, and save it. This will forcefully delete the wav files because starforge has a wav glitch. And reduce your file size to its regular size without wavs.
If it doesn't work, import a wav first using a regular editor.
Your map size might be big because you imported wavs before, and deleted them.
What works for me for removing these are by:
Opening the file in starforge, saving it, opening it in a regular editor, saving it, then opening in the starforge again, and save it. This will forcefully delete the wav files because starforge has a wav glitch. And reduce your file size to its regular size without wavs.
If it doesn't work, import a wav first using a regular editor.
Your map size might be big because you imported wavs before, and deleted them.
Report, edit, etc...Posted by chuiu on 2005-03-31 at 22:44:03
I love how Heimdal goes around pretending like Starforge is flawless yet people point out glitches and problems with it everyday.
Report, edit, etc...Posted by Red2Blue on 2005-03-31 at 22:54:42
Ke Ke Ke, I would say that statement is true.
StarForge does have its glitches... (like location selection and resizing, changing locations on you... 'its a pain...'), but then again, its one of the revolutionary tools that have been implemented to StarCraft. Without it, many maps wouldn't have been possible.
btw,
It looks like in this situation you may have used StarForge to import that wavs. At times, the importer for StarForge gets a little glitchy, sometimes it doesn't import the wav and it always adds scratch noises to the wav if the wav is long enough...
anywhoo, StarForge is not the program to import wavs and wavs should be imported LAST...
Also, I did find a glitch with the wav imports for regular editors.
If you import a wav, say "1.wav" into the editor, and then say, changed the data on the "1.wav" to another song, and then imported it into the editor with the same name: the editor will think that they are two separate files, and import the file with the same name, but take up the same amount of space as though it had two separate files when it is really 1 file.
The "fix-it" I explained on top fixes this as well.
StarForge does have its glitches... (like location selection and resizing, changing locations on you... 'its a pain...'), but then again, its one of the revolutionary tools that have been implemented to StarCraft. Without it, many maps wouldn't have been possible.
btw,
It looks like in this situation you may have used StarForge to import that wavs. At times, the importer for StarForge gets a little glitchy, sometimes it doesn't import the wav and it always adds scratch noises to the wav if the wav is long enough...
anywhoo, StarForge is not the program to import wavs and wavs should be imported LAST...
Also, I did find a glitch with the wav imports for regular editors.
If you import a wav, say "1.wav" into the editor, and then say, changed the data on the "1.wav" to another song, and then imported it into the editor with the same name: the editor will think that they are two separate files, and import the file with the same name, but take up the same amount of space as though it had two separate files when it is really 1 file.
The "fix-it" I explained on top fixes this as well.
Report, edit, etc...Posted by AcidYoshi on 2005-03-31 at 22:56:23
I followed ur steps with the starforge thing and I don't think it worked.
I did import and delete alot of large wavs and deleted them so that could be a problem. I'm not sure how I could fix that.
I did import and delete alot of large wavs and deleted them so that could be a problem. I'm not sure how I could fix that.
Report, edit, etc...Posted by Red2Blue on 2005-03-31 at 23:00:10
Okay, heres what you do:
Make a back-up file, yea... seriously... this part could get messy really quick.
1) Import that wav. file again using a regular editor.
2) save it using the regular editor.
3) open it with starforge, and click save.
4) now, close starforge, and open the file again in the regular editor
5) save it, It should now give you an annoying message saying "this file cannot be accessed"
6) now, click okay, and open it again in starforge, it should now give you a wierd message, "ï¼◘_" followed by another wierd message. (these messages change...)
7) after these messages, save the map again.
8) open the map in the regular editor again, and it should be missing the wav, and should clear the big map size.
tell me if it doesn't work.
(this fix-it also fixes that annoying access error caused by sf...)
Go SF!...
Make a back-up file, yea... seriously... this part could get messy really quick.
1) Import that wav. file again using a regular editor.
2) save it using the regular editor.
3) open it with starforge, and click save.
4) now, close starforge, and open the file again in the regular editor
5) save it, It should now give you an annoying message saying "this file cannot be accessed"
6) now, click okay, and open it again in starforge, it should now give you a wierd message, "ï¼◘_" followed by another wierd message. (these messages change...)
7) after these messages, save the map again.
8) open the map in the regular editor again, and it should be missing the wav, and should clear the big map size.
tell me if it doesn't work.
(this fix-it also fixes that annoying access error caused by sf...)
Go SF!...
Report, edit, etc...Posted by AcidYoshi on 2005-03-31 at 23:10:41
Thank you Red2Blue 
Report, edit, etc...Posted by Red2Blue on 2005-03-31 at 23:35:34
Im guessing that it worked, you are welcome. =)
Report, edit, etc...Posted by (U)Bolt_Head on 2005-04-01 at 10:25:57
QUOTE(Red2Blue @ Mar 31 2005, 10:00 PM)
Okay, heres what you do:
Make a back-up file, yea... seriously... this part could get messy really quick.
1) Import that wav. file again using a regular editor.
2) save it using the regular editor.
3) open it with starforge, and click save.
4) now, close starforge, and open the file again in the regular editor
5) save it, It should now give you an annoying message saying "this file cannot be accessed"
6) now, click okay, and open it again in starforge, it should now give you a wierd message, "ï¼◘_" followed by another wierd message. (these messages change...)
7) after these messages, save the map again.
8) open the map in the regular editor again, and it should be missing the wav, and should clear the big map size.
tell me if it doesn't work.
(this fix-it also fixes that annoying access error caused by sf...)
Go SF!...
[right][snapback]177570[/snapback][/right]
Make a back-up file, yea... seriously... this part could get messy really quick.
1) Import that wav. file again using a regular editor.
2) save it using the regular editor.
3) open it with starforge, and click save.
4) now, close starforge, and open the file again in the regular editor
5) save it, It should now give you an annoying message saying "this file cannot be accessed"
6) now, click okay, and open it again in starforge, it should now give you a wierd message, "ï¼◘_" followed by another wierd message. (these messages change...)
7) after these messages, save the map again.
8) open the map in the regular editor again, and it should be missing the wav, and should clear the big map size.
tell me if it doesn't work.
(this fix-it also fixes that annoying access error caused by sf...)
Go SF!...
[right][snapback]177570[/snapback][/right]
All you really have to do is import the wav in staredit, then delete it. As long as you use save instead of saveas then your fine.
Report, edit, etc...Posted by RexyRex on 2005-04-01 at 16:29:34
Just so you know...
If you, um, (This is embarrasing)...
Okay...
Well I used to make breifings that I wanted to animate and would never end.
Until everyone pushed start...
(I know I know...)
So, um, holding down copy until you hit the limit adds about 3 MB.
So dont' do it.
And if it doesn't hit 3MB, dont' do it anyways.
(I was such a newbz0r back then
)
If you, um, (This is embarrasing)...
Okay...
Well I used to make breifings that I wanted to animate and would never end.
Until everyone pushed start...
(I know I know...)
So, um, holding down copy until you hit the limit adds about 3 MB.
So dont' do it.
And if it doesn't hit 3MB, dont' do it anyways.
(I was such a newbz0r back then
)Report, edit, etc...Posted by Red2Blue on 2005-04-01 at 17:47:54
QUOTE
All you really have to do is import the wav in staredit, then delete it. As long as you use save instead of saveas then your fine.
Although this may work in some cases, if you do not have the original file name that you saved it as, and if you cannot view the strings because you may not know how to, you might be unable to use this method.
Besides, I was merely showing a universal and easy way to fix a problem that many people have.
Report, edit, etc...Posted by (U)Bolt_Head on 2005-04-02 at 13:54:39
Yes i know.
You did however say
"Import that wav. file again using a regular editor."
and that does imply that you need the same wav file.
You did however say
"Import that wav. file again using a regular editor."
and that does imply that you need the same wav file.
Report, edit, etc...Posted by Red2Blue on 2005-04-07 at 02:13:52
No, I was merely talking about that specific case. This case required the wav. Then again... you could import any wav... it works all the same...