Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: blowfish on May 07, 2008, 08:56:58 am
-
I have never been able to get mod.ini files to work. Some mods have come with mod.ini files, and others I have downloaded, but none seem to work. I have gotten around this, partially, by placing my MediaVPs folders in my main Freespace folder, but when some campaigns require others, like FSPort, this becomes a problem. Is this because I am on a Mac? Is there a solution? Any help would be appreciated :)
-
Since it is a Mac, I can't be sure of what is supposed to work with it. But generally, if you want a mod to use the MediaVPs, the mod.ini in the mod folder should be something like this:
[launcher]
modname = modname;
[multimod]
primarylist = ;
secondarylist = mediavps;Note the word mediavps. It should be the same as the name of the folder where you have your MediaVPs. If that folder is called media_vps, you need to edit the mod.ini accordingly. Like this:
[launcher]
modname = modname;
[multimod]
primarylist = ;
secondarylist = media_vps;If a mod also recquires the FSPort, you just add the names of the other mod folders on the same line and separate them from each other with commas. Like this:
[launcher]
modname = modname;
[multimod]
primarylist = ;
secondarylist = fsport,mediavps;
Note that again, if your FSPort folder is called something else than fsport, change that bit on the mod.ini accordingly.
-
I know hot to use mod.ini files!!! :rolleyes: Even the ones that come with mods do absolutely nothing. My FS Port folder is called fsport!
-
:sigh: Fine... sorry for trying to help. Your report really sounded like there might be inconsistensies with the mod.inis and the folders. But apparently it is not the issue. As I said, I do not know that much about Macs so try 'n have some patience and maybe someone can offer assistance. Good day.
-
If the standard format mod.ini files do not work on Macs then that sounds awfully lot like a bug. Mantis it.
-
The mod.ini files do not work on a Mac, because the mod.ini is read by the Launcher. The Mac Launcher does not have a mod.ini support, yet.
You have do change your -mod flag yourself, eg. with the mac Launcher or edit the cmdline_fso.cfg.
For example fsport:
-spec -glow -env -mipmap -nomotiondebris -missile_lighting -normal -ambient_factor 87,00 -spec_exp 13 -spec_point 0.68
-spec_static 0.85 -spec_tube 0.4 -ogl_spec 77 -ship_choice_3d -3dwarp -warp_flash -no_vsync -cache_bitmaps
-dualscanlines -targetinfo -orbradar -rearm_timer -ballistic_gauge -snd_preload -fps -window -mod fsport,mediavps
and no [Space] between the mod-names only a comma !
HTH
-
Ah.. i thought the beta state OS x launcher already reads the mod.ini files (and also assumed it was in use....)