im trying to set up the modtools again and i have the following problem that visualmunge doesnt create the _LVL_PC folder.
First vm didnt munge anything so i applied the vista munge fix (im using wondows 7). Now itis munging the individual files and even creates the addme script and the necessary folders in the addon directory. They log says that the lvl files are copied over but that cant work without the _LVL_PC folder.
the only error in the log is: "\Intel\iCLS" unexpected at this time. I searched for the term but the error seems to be normally resolved by the mungefix.
has anyone else encountered the error and know what it is about?

by the way, the link to the mungefix in the everythingyouneedthread doesnt work anymore.

Mh the link works fine for me: http://www.gametoast.com/viewtopic.php? ... 73#p295373

They where fixed the last days after the hack.

About the problem, in what directory have you installed modtools?? if you installed it to C:\Programs\... you have the problems with the write permissions. You could try to run the munge.exe as admin, or install ModTolls to C:\BF_modtools or remove the write protection from the folder.

Nice to see you back

thanks
at first i didnt have the modtools installed at the root. i reinstalled them but it didnt make a difference.
I tried running vom and the bat files as admin but nothing changes.

can you upload a new map source to see if the problem is with your pc or modtools??

alright, here are the files

There's a problem with either your tools or how your computer interacts with them. I tried using the munger and received the same error.

I also have problems with this source.

try using these munge bat in the data/build folder and make a new testmap.

https://www.dropbox.com/s/5h0lyvazflxtr94/_BUILD.rar

thanks, when i create new data folders with this build folder it actually works! o.o

A file comparison reveals an incomplete mungefix applied to Duck's files resulting in the problem.

Example:

• data\_BUILD\munge.bat (default)

  Code: Select all

  if "%MUNGE_BIN_DIR%"=="" (
  	set MUNGE_BIN_DIR=%CD%\..\..\ToolsFL\Bin
  	REM echo MUNGE_BIN_DIR=%MUNGE_BIN_DIR%
  	set PATH=%CD%\..\..\ToolsFL\Bin;%PATH%
  )
  

  data\_BUILD\munge.bat (mungefix file)

  Code: Select all

  REM if "%MUNGE_BIN_DIR%"=="" (
  	set MUNGE_BIN_DIR=%CD%\..\..\ToolsFL\Bin
  	REM echo MUNGE_BIN_DIR=%MUNGE_BIN_DIR%
  REM	set PATH=%CD%\..\..\ToolsFL\Bin;%PATH%
  REM )
  

  data\_BUILD\munge.bat (Anakin's)

  Code: Select all

  REM if "%MUNGE_BIN_DIR%"=="" (
  	set MUNGE_BIN_DIR=%CD%\..\..\ToolsFL\Bin
  	REM echo MUNGE_BIN_DIR=%MUNGE_BIN_DIR%
  REM	set PATH=%CD%\..\..\ToolsFL\Bin;%PATH%
  REM )
  

  data\_BUILD\munge.bat (Duck's)

  Code: Select all

  REM if "%MUNGE_BIN_DIR%"=="" (
  	set MUNGE_BIN_DIR=%CD%\..\..\ToolsFL\Bin
  	REM echo MUNGE_BIN_DIR=%MUNGE_BIN_DIR%
  	set PATH=%CD%\..\..\ToolsFL\Bin;%PATH%
  REM )
  

If the automated mungefix doesn't work as intended on your machine for whatever reason, you could always edit the batch files in the BF2_modtools\data folders by hand to get around the problem. You only need to do this once, unless you reinstall the modtools.

I'll mark your thread as [Solved]

thanks for the explanation! weird that the mungefix didnt work completely.