A bug that could use some fixing:
aip_<name>.autoreg files do not work for MPI AIP listings, only IA. Needs some looking in to if this was not intentional.
Note: if you're using a custom aiplist.txt file on a map, that overrides the autoreg files.
-- GSH
Im not using custom maps (stated many times before, out of the scope of SRV), and I had to resort to the aiplist.txt method AFTER I found that autoregs do not work for MPI (not specifying a custom one, I mean I made an override by copying and modifying the file for the Beta phase of testing to still work). Having no custom aiplist.txt and only having the aip_<name>.autoreg files do not work to have the custom AIPs show up in MPI, only IA. And since it was said that autoreg files were supposed to kill the need for such files as aiplist.txt, ia_aiplist.txt, recylist.txt, etc, you can see where I found a problem.
Just trying to make that a bit more clear.
so why does pb4 list aips for mpi then?
I believe it's because aiplist.txt was deleted, but resurrected by accident. (Look in the patch13.pak). If it's present, it ignored the autoreg files.
Next full build (pb4a) will fix this by deleting aiplist.txt
-- GSH
Sorry, it was my fault. I'm glad Steeveeo caught the problem. :oops:
Quote from: wug on July 13, 2008, 04:42:27 AM
Sorry, it was my fault. I'm glad Steeveeo caught the problem. :oops:
About time.
0_O, that explains why Wug's was working this entire time :lol:
This sort of links to my current point of confusion.
My 3rd race can use just about all of the stock maps, except the mpi maps for a variety of reasons, Aips/path points etc etc.
Can anyone think of a way to Not display non Legions Of skaro mpi maps in the map list, while retaining all the other strat/dm/ctf maps?
That is a good questions....... I know you can now avoid ALL maps, but each section of the maps13 folder i think cannot be selected individually......
Wait, try this in the .cfg:
AddDirRecurse("@rootdir\maps13\Missions\Multiplayer\ST");
AddDirRecurse("@rootdir\maps13\Missions\Multiplayer\DM");
AddDirRecurse("@rootdir\maps13\Missions\Multiplayer\CTF");
// AddDirRecurse("@rootdir\maps13")
That SHOULD only include the Strat, Dm, and Ctf maps from the stock selection. :-)
Warfreak - sorry, but I don't think that'll work. The logic BZ2 uses is roughly this:
ForEach AddDirRecurse entry
- Take that path, add "Missions/Mutiplayer"
- Find all .bzn files under there, add to list
Your entries have no way to specify Missions/Multiplayer to it.
-- GSH
That's actually what i was afraid of, thanks for verifying GSH.
Using mm5 I can do this to remove the mpi maps.
RenameEX("bzone.cfg", "bzoneLOS.cfg", "bzonebak.cfg");
RenameEX("maps13\Missions\Multiplayer\mpi", "Los\Missions\Multiplayer\mpi", "Los\mpi");
RenameEX("maps13\Missions\Multiplayer\3rdParty", "Los\Missions\Multiplayer\3rdParty", "Los\3rdParty");
It also removes other 3rdParty maps, attempting to go further into the dir's to renameEX just "Greenhearts Map Pack", did not work.
I wonder if it has anything to do with the spaces in the folder names?
The rename command passes things to an internal command that does not like spaces, apparently. I may be able to fix that.
Or someone could remove the spaces in pb4a
Better to fix MM5, I think, and leave more options for people in the game.
Spaces are a correct part of pathnames and if something does not accept it then that means it is broken; the broken thing should be fixed.
(http://www.overminddl1.com/image_scripts/image_sig.php?type=ODL1signitures&image/sig.gif)
Generated by OvermindDL1's Signature Auto-Add Script (http://overminddl1.com) via GreaseMonkey (http://greasemonkey.mozdev.org/)
I hale from the old dos days. spaces were used between commands and parameters, they had no place in file names or directory names, I still stick to this old convention just to avoid problems such as this.
That was with DOS, the current Windows has no affiliation with DOS, but rather NT. Actually it is because of the filesystem, FAT16 only allowed 8.3 filenames with no spaces, FAT16+ was the same as FAT16 but with names up to 256 in length, spaces are allowed (this came out with Win95). FAT32 came out later on (Win98se I think...) which allowed everything FAT16+ allowed, but with larger volume sizes. NTFS allowed even larger volume sizes, faster access, and could be set to run in two modes, the first being compatibility mode which it supported 256 characters for a full path, and supported an old 8.3 syntax for the older apps. Native mode does not have support for the old 8.3 syntax, but sllows paths with a max length of 2048 characters. Anything that has existed for at least a decade has no excuse to be broken like that due to programmer stupidity or lazyness.
(http://www.overminddl1.com/image_scripts/image_sig.php?type=ODL1signitures&image/sig.gif)
Generated by OvermindDL1's Signature Auto-Add Script (http://overminddl1.com) via GreaseMonkey (http://greasemonkey.mozdev.org/)
True.
I do find it very annoying though when somebody does actually use a file name of 2048 characters. Its a name, your supposed to be able to remember it, not a short story.
That's the full path...
I've had issues with files with long names downloading into a few sub folders and thus becoming inaccessible. I had to use a special invalid file deleter/renamer on them.
Yes, full path. I have had to access many files where they are so many folders deep that they exceed 512 chars, making them inaccessible to the compatibility mode (that windows turns on by default, mine is off), so have to shuffle around parent directories to fix them. No issue since I run it in native now.
(http://www.overminddl1.com/image_scripts/image_sig.php?type=ODL1signitures&image/sig.gif)
Generated by OvermindDL1's Signature Auto-Add Script (http://overminddl1.com) via GreaseMonkey (http://greasemonkey.mozdev.org/)
How do you turn off compatibility mode?
Some setting in the registry, set it like three years ago and still running the same XP install (I think it is going on 5 years, man I can keep windows running fast... :P ).
(http://www.overminddl1.com/image_scripts/image_sig.php?type=ODL1signitures&image/sig.gif)
Generated by OvermindDL1's Signature Auto-Add Script (http://overminddl1.com) via GreaseMonkey (http://greasemonkey.mozdev.org/)