-= Gametoast.com =-

Hello guy, I've got a big problem with the sound munge, which I've never had before.
When I use the munge fix, I get this Error:

It's German so I'll translate it for you.
"\Intel\iCLS" is not in the situation to be syntactic processed at this point.

I've never had a problem like this before. When I try to bring new music or effects into my world, it works, but if I try to combinate it with missing soundeffects or just only missing soundeffects, I get this error.
I'm kind of confused I tried so many ways to solve the problem, but I had no sucess.
I've tried the soundmunge files from swbf1 and I tried other projects, but nothing did really help.
Did anyone have this issue previously?
I also tried it with my Laptop, but then I get Nvidia instead of Intel.

Are you using the fixed munge.bats??

Anakin wrote:Are you using the fixed munge.bats??

Yes, I do use the fixed munge.bat.
There to be exactly.
data_HOE\_BUILD\Sound

I think the munge bats call an name.exe, but in your enviroment path is an other program that has the same name.exe. BUt not sure about it.

Have you tried this: http://www.gametoast.com/viewtopic.php?f=64&t=30282

That's right. I'm using a different path, because my OS is running on my SSD and my Games are running on my HDD.
It might be a path problem. Thanks dude, I'll try.

EDIT
No big change at all.
It has something to do with the Path, I think.

Have you installed the BF_modtools on your ssd or hdd??

HDD and I think there is the problem. I'll try to install it on my laptop again.

EDIT
I get the same problem on my Laptop.
The only difference is that he says Nvidia.
I only have a HDD in my Laptop and the Path: C:\Program Files(x86)\LucasArts\Star Wars Battlefront II\GameData

If I remember right you mustn't have a space in your path to the Modtools. That's why you shouldn't put it into Program Files, Just C:\BF2_ModTools.

hunpeter12 wrote:If I remember right you mustn't have a space in your path to the Modtools. That's why you shouldn't put it into Program Files, Just C:\BF2_ModTools.

I know, I've them there: D:\BF2_ModTools And Battlefront II is installed there: D:\Spiele\LucasArts\Star Wars Battlefront II

When I first installed my modtools I put them in C:\BF2_ModTools\ but I had the same problem as you. I did two things to solve the problem (in addition to using the fixed munge .bats):

1. Created a new folder to contain \BF2_ModTools\ instead of just placing it in the root of my C: drive. This folder has no spaces in its name. I wasn't very creative; I called mine \SWBF2_Modtools\. So my directory now looks like this: 2. Changed the permissions of the SWBF2_Modtools folder (and all sub-folders and files) so that all users have 'Full Control' of the folder. You can change this by right-clicking on the folder, choosing 'Properties', switching to the Security tab, and going through the groups/usernames and clicking 'Edit...'. Then just check the 'Full Control' box.

Those two steps, with the fixed munge .bats, worked totally fine for me and I haven't had any trouble since. Hopefully the same will work for you.

There was a time when I played the game from an external drive, but had mod tools on C:\

If you wanna fool the system, you can install the mod tools on C:\

and then make the following fake/empty folders:

Program Files(x86)\LucasArts\Star Wars Battlefront II\Gamedata\Addon

Then just tel visualmunge to set the game directory for that fake location.
When you mod is made, you can copy it from fake addon to the addon in your real game's destination.

jedimoose32 wrote:When I first installed my modtools I put them in C:\BF2_ModTools\ but I had the same problem as you. I did two things to solve the problem (in addition to using the fixed munge .bats):

1. Created a new folder to contain \BF2_ModTools\ instead of just placing it in the root of my C: drive. This folder has no spaces in its name. I wasn't very creative; I called mine \SWBF2_Modtools\. So my directory now looks like this:

Code: Select all

C:\SWBF2_Modtools\BF2_ModTools\

2. Changed the permissions of the SWBF2_Modtools folder (and all sub-folders and files) so that all users have 'Full Control' of the folder. You can change this by right-clicking on the folder, choosing 'Properties', switching to the Security tab, and going through the groups/usernames and clicking 'Edit...'. Then just check the 'Full Control' box.

Those two steps, with the fixed munge .bats, worked totally fine for me and I haven't had any trouble since. Hopefully the same will work for you.

Thx for your tip man, but it doesn't work.
I kind of clueless.
It has always worked.

anthonybf2 wrote:There was a time when I played the game from an external drive, but had mod tools on C:\

If you wanna fool the system, you can install the mod tools on C:\

and then make the following fake/empty folders:

Program Files(x86)\LucasArts\Star Wars Battlefront II\Gamedata\Addon

Then just tel visualmunge to set the game directory for that fake location.
When you mod is made, you can copy it from fake addon to the addon in your real game's destination.

I'm happy for every solution way, but I doubt that it will work. Why? Because I've tried to munge my sound at my laptop, but I do get the same mistake. The only difference is that he says Nvidia is not in the situation to be syntactic progress at this point.
On my laptop I've just C: with Windows and my games and other programs. So the paths are like the system want the paths.
And now I'm really confused. It's a different system, but I get the same problem. That doesn't make any sense to me. I'll try to reinstall the Mod tools at my laptop.

I'm done with those nasty problems in Win 7. I'm installing Win XP on Virtual Box.

That works too I guess.

Have you tried using the SWBF1 mod tools to munge sound? :p