-= Gametoast.com =-

Anakin wrote: ↑

Fri May 22, 2020 4:48 am

As it says, it's about sound munge. sound munge does not work the origin way. The bats need adjustments. But as long as you don't have custom sounds/music, you don't need that. And you don't even need to check sound when munging.

For a common mod you just need to select your map, sides, and check common. If you have custom weapon names, check localize, too. Everything else is not needed.

INMR wrote: ↑

Sat May 23, 2020 5:02 pm

Anakin wrote: ↑

Fri May 22, 2020 4:48 am

As it says, it's about sound munge. sound munge does not work the origin way. The bats need adjustments. But as long as you don't have custom sounds/music, you don't need that. And you don't even need to check sound when munging.

For a common mod you just need to select your map, sides, and check common. If you have custom weapon names, check localize, too. Everything else is not needed.

Thanks for the clarification. I feel like I need to go back and re-learn everything that I used to know how to do. I downloaded Marvel4's improved Munge files and put them in the data file before creating that level. Is there anything else that I would need to do to fix the sound files?

CommanderStrell wrote: ↑

Sat May 23, 2020 2:57 am

will this crash the game or what?

ERROR[PC_texturemunge msh\Crate_normal.tga]:Targa type 10 not currently supported.
ERROR[PC_texturemunge msh\Crate_normal.tga]:Targa type 10 not currently supported.
[continuing]
2 Errors 0 Warnings

Sporadia wrote: ↑

Sat May 23, 2020 6:40 pm

If you're using Marvel4's batch files, that explains every single "sound error" in the mungelog. I only started with sound modding about a month ago (probably less) and have been seeing the exact same "errors" since I installed Marvel4's batch files. Putting "errors" in speech marks because those ones specifically are completely meaningless. If you're doing sound modding, the proper place to look for real sound errors are the files configmunge.txt and levelpack.txt which appear in your sound folder after you munge (that's data_ABC/Sound/worlds/ABC). The mungelog tends to jump at nothing when it comes to sound. If you're not interested in modding sound you can ignore that stuff completely. Also your error 'Input file shell.req does not exist' is a default message. Unless you do shell modding, or are using the shell to munge user scripts, you can ignore that too.

Edit: If you want a better explanation of those sound errors: Every time you make a mod it will contain a load of template sound folders by default. Before you had Marvel4's batch files, your mungetools weren't able to munge sound so they didn't throw up any errors. Now though, you can munge sound (and do munge sound, every time you munge with visual munge). The template sound folders all get munged badly, alongside anything you want to munge. And because they're templates which are slightly broken/incomplete, the mungelog lists every irrelevant sound error that goes with them. Even when you get into sound modding, it can be more convenient to alter soundmunge.bat and stop it from copying the munged sound into the addon folder all the time, or stop it from munging the useless folders. Personally have stopped it from copying the munged sound over because that's what I prefer. Commented out the line:

Code: Select all

xcopy _LVL_%MUNGE_PLATFORM%\SOUND\* "%BF2_PATH%\addon\%WORLD_NAME%\data\_LVL_PC\SOUND\" /Y

So it became:

Code: Select all

@rem xcopy _LVL_%MUNGE_PLATFORM%\SOUND\* "%BF2_PATH%\addon\%WORLD_NAME%\data\_LVL_PC\SOUND\" /Y

And I manually move the munged sound lvls from the _LVL_PC folder as and when I need to. (This doesn't get rid of the "errors" because I'm still munging useless sounds, but if you choose to edit the batch file to disable certain sound folders from being munged, that will remove the "errors" and speed up munge time)