Most aggravating munge error I ever got!

Post by **[RDH]Zerted** » Mon Jul 13, 2009 4:39 pm

Where did you install your mod tools? What is its exact path?

Havoc 526 · Post by **Havoc 526** » Mon Jul 13, 2009 4:56 pm

Well, they were on the C: drive, but apparently, they were taking up too much of the hard drive, so my Dad had them and the game moved onto an external hard drive in February. However, I haven't had any problems until recently. This is the path.

G:\Richard's Games\Star Wars Battlefront II\GameData

Xavious · Post by **Xavious** » Mon Jul 13, 2009 5:24 pm

You can't have spaces in the path.

Havoc 526 · Post by **Havoc 526** » Mon Jul 13, 2009 7:37 pm

What, you mean in "Star Wars Battlefront II"? It's been like that for years! It hasn't caused any problems that I know of...
At least, I don't think so.

Xavious · Post by **Xavious** » Mon Jul 13, 2009 10:05 pm

Your mod tools are in that directory. And the mod tools can't have a space in their location.

Frisbeetarian · Post by **Frisbeetarian** » Mon Jul 13, 2009 10:33 pm

@Xavious
It would seem as though he mentioned the path for his game, not his modtools:

Link504 wrote:moved onto an external hard drive in February.

Link504 wrote:It's been like that for years!

@Link504
You can't spaces in your modtools directory. It's fine to have them in your game's directory. What is your modtools directory?

Link504 wrote:Well, in that case, I'll try again, and this time with the gunship listed only.

If the modtools directory doesn't have spaces, what result did you get?

Xavious · Post by **Xavious** » Mon Jul 13, 2009 10:35 pm

He has his modtools in his gamedata folder.

Well, they were on the C: drive, but apparently, they were taking up too much of the hard drive, so my Dad had them and the game moved onto an external hard drive

RogueKnight · Post by **RogueKnight** » Mon Jul 13, 2009 10:37 pm

Xavious wrote:He has his modtools in his gamedata folder.

Well, they were on the C: drive, but apparently, they were taking up too much of the hard drive, so my Dad had them and the game moved onto an external hard drive

And that concludes the problem then.

Just move your modtools to a directory that doesnt have spaces in the title.

Frisbeetarian · Post by **Frisbeetarian** » Mon Jul 13, 2009 10:39 pm

Right, but he didn't say where they are on the external drive, he said where his game executable is. His modtools are probably directly in G:\ since he said they were working until recently (I assume he means this problem).

DarthRogueKnight wrote:And that concludes the problem then.

You hopped onto the topic a little early. Lets wait to see what he says first.

Havoc 526 · Post by **Havoc 526** » Wed Jul 15, 2009 2:18 pm

Oh, in the file they're located? No there's no spaces in there. It's in a different file on the external hardrive.

Code: Select all

G:\Richard's\BF2_ModTools

Xavious · Post by **Xavious** » Wed Jul 15, 2009 4:19 pm

Just to be safe, try putting them at G:\BF2_Modtools.

Havoc 526 · Post by **Havoc 526** » Wed Jul 15, 2009 4:22 pm

I already have a set of BF2 modtools right there. If I use those, my game crashes at the title screen.

Frisbeetarian · Post by **Frisbeetarian** » Wed Jul 15, 2009 5:13 pm

Xavious wrote:Just to be safe, try putting them at G:\BF2_Modtools.

There's nothing unsafe about where he has them. Batch files only fail with spaces in their names. "Richard's" doesn't have spaces in it.

Link504 wrote:Well, in that case, I'll try again, and this time with the gunship listed only.

So now that we've figured out your fine for where you modtools are installed, how about this. What was the result here?

Post by **[RDH]Zerted** » Wed Jul 15, 2009 5:33 pm

Depending on how the batch scripts were written, the ' in Richard's could also cause a problem. I don't think anyone has tried the mod tools in a path with one of those characters before.

Frisbeetarian · Post by **Frisbeetarian** » Wed Jul 15, 2009 5:40 pm

[RDH]Zerted wrote:Depending on how the batch scripts were written, the ' in Richard's could also cause a problem.

How? With what batch functions would an apostrophe conflict? Regardless, I just tested it, and it works fine. Let's move on.

Havoc 526 · Post by **Havoc 526** » Wed Jul 15, 2009 7:45 pm

Frisbeetarian wrote:
Xavious wrote:Just to be safe, try putting them at G:\BF2_Modtools.
There's nothing unsafe about where he has them. Batch files only fail with spaces in their names. "Richard's" doesn't have spaces in it.
Link504 wrote:Well, in that case, I'll try again, and this time with the gunship listed only.
So now that we've figured out your fine for where you modtools are installed, how about this. What was the result here?

Well, for some reason, it treated it the same way, and now it isn't reading the req. file for one of my backup maps in my world folder.

I think it's a bug. I already got this error before with two other vehicle reqs, and to solve that, I just deleted the req files for those, and then it happens again with this vehicle. Now it's gotten worse, effecting even one of my WLD. files!

I'm moving to the theory that it's a glitch. I may be wrong, though.

Code: Select all

ERROR[levelpack ABC2.req]:Expecting bracket, but none was found.
File : munged\pc\abc2_conquest.lvl.req(1)...

ucft <--
ERROR[levelpack ABC2.req]:Expecting bracket, but none was found.
File : munged\pc\abc2_conquest.lvl.req(1)...

ucft <--
 [continuing]
   2 Errors    0 Warnings

ERROR[levelpack ABC2.req]:Expecting bracket, but none was found.
File : munged\pc\abc2_conquest.lvl.req(1)...

ucft <--
ERROR[levelpack ABC2.req]:Expecting bracket, but none was found.
File : munged\pc\abc2_conquest.lvl.req(1)...

ucft <--
 [continuing]
   2 Errors    0 Warnings

Frisbeetarian · Post by **Frisbeetarian** » Wed Jul 15, 2009 11:10 pm

Do a manual clean and test it again.

Havoc 526 · Post by **Havoc 526** » Thu Jul 16, 2009 8:33 pm

I should really cut down on my modding.

I ran a manual clean on EVERYTHING. And now, I am back to step one. Once again, my ARC Gunship's req is having it's issues just like before. Everything else is fine. It's all beautiful. It's just that one vehicle. Nothing else. I found no errors in it's odf. I see no visible problems in the actual req file. I'm beginning to think I should scrap the vehicle altogether.

Most aggravating munge error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!

Re: Most aggravating error I ever got!