Report, edit, etc...Posted by Staredit.Net Essence on 2004-11-11 at 13:55:52
I don't often have .wav files in my maps, so I haven't encountered this problem before. Whenever I save my map with Proedit, it doesn't save the .wav files that were imported. .mpq sounds work fine, but imported wav's aren't saved. I had this problem with SF, but I can fix that now, just takes a while. Anyways, anyone have any idea why Proedit isn't keeping the .wav files? (It is Proedit. 1,4 by the way) And I have tested the map before it's saved, and the .wav files work fine.
Report, edit, etc...Posted by SaLaCiouS(U) on 2004-11-11 at 14:28:28
StarForge screws it up so ProEdit ends up deleting the sound files. There's a way to get around it.. bah. Looks like I'll be writing the tutorial for this.. 
ProEdit Removing Sounds Glitch [Fix]
This is caused when you use StarForge in making your map. StarForge damages the sound files so that ProEdit removes them. There is a way to fix this though it is a bit complicated.
Requirements: WinMPQ
1.) Get your map ready to be protected with ProEdit.
2.) Open the map in WinMPQ
3.) Prepare to scream
- You should see that the names of the sound files have been changed into a bunch of jibberish. You can either change the names of the sounds back MANUALLY.. or you can remove them and re-add them with WinMPQ. If you take them out first, then you need to use WinMPQ to re-compress the .scx file. I'm not even sure how to do that, but I know you can.
4.) Then you're fine to protect. Hopefully.
ProEdit Removing Sounds Glitch [Fix]
This is caused when you use StarForge in making your map. StarForge damages the sound files so that ProEdit removes them. There is a way to fix this though it is a bit complicated.
Requirements: WinMPQ
1.) Get your map ready to be protected with ProEdit.
2.) Open the map in WinMPQ
3.) Prepare to scream
- You should see that the names of the sound files have been changed into a bunch of jibberish. You can either change the names of the sounds back MANUALLY.. or you can remove them and re-add them with WinMPQ. If you take them out first, then you need to use WinMPQ to re-compress the .scx file. I'm not even sure how to do that, but I know you can.
4.) Then you're fine to protect. Hopefully.
Report, edit, etc...Posted by Staredit.Net Essence on 2004-11-11 at 14:33:31
Thanks, I'll try that.
The glitch only screws up maps saved by StarForge right?
Anyways, thanks alot.
The glitch only screws up maps saved by StarForge right?
Anyways, thanks alot.
Report, edit, etc...Posted by SaLaCiouS(U) on 2004-11-11 at 14:42:50
Yes I believe so. I'm not sure if that problem is fixed in StarForge 2.2 or whichever the newest version is. I doubt it.
Report, edit, etc...Posted by Staredit.Net Essence on 2004-11-11 at 14:45:05
Nope, I used 2.2, so it isn't fixed.
Report, edit, etc...Posted by Paella on 2004-11-11 at 21:09:41
Is that glitch if u used SF at any time during the making of the map? Or only if it is a recent edit...
Report, edit, etc...Posted by SaLaCiouS(U) on 2004-11-12 at 14:00:03
I think it can happen if you use StarForge at any time, I'm not sure why it happens though so I can't tell you why it only occurs sometimes.