Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Gaias on November 16, 2005, 11:15:27 pm
-
I have tried to make a search on the forums but everytime I do I get a "You are not allowed to search for posts in this forum."
Everytime I try to use the "Select MOD" function in FS2 Open Lancher 5.3, I get a window that pops up and says "mod directory name cant contain space". I was wondering what this was and the solution to may be.
It all works for me completely as long as I have all the media VP files in the main Freespace 2 directory.
-
That's...odd. Does the full path to your Freespace 2 directory have spaces? That's usually what causes the problem...don't see why having or not having the mVPs would change that.
-
What mod are you playing?
-
If you're trying to put the Media VP's in a seperate mod directory, try having the directory be named "MediaVPs" or "Media_VPs", as something with spaces, like "Media VPs" will cause that error.
-
The other problem is that the game doesn't like running a mod if you've installed to a folder that contains a space. C:\Program Files\Freespace2\Media_VPs for instance would still give you that error.
I believe that Taylor said it was possible to fix the problem but that guy has far too much on his plate to deal with this quickly no doubt :)
In the meantime simply move the folder\rename it to make sure that there are no spaces and the problem should go away.
Incidentally kudos on sticking the media.vp files in their own folder and running it as a mod. That's how everyone should do it! :)
-
I believe that Taylor said it was possible to fix the problem
Any game related issue has been worked out already. The only reason it's still a problem is because of bugs in the Launcher. I'm working on a new launcher though and it won't have this problem (or any other problem that the current Launcher suffers from) but it might be around the first of December before that's ready. This is just one of those issues that shouldn't even exist and is pretty easy to fix even in the current Launcher. It's just that no one has bothered to do so yet.
-
Thanks karajorma! It was indeed that I had installed Freespace 2 in the C:\Program Files, instead of the defalt directory C:\Games. I been pulling my hair out and beating my desk something fierce trying to get it to work the way it was intented to. Now I can sit back and enjoy the Freespace universe in all it upgraded graphical spleador!
Thanks again for helping me with my dilemma, it was much appreciated.
-
The other problem is that the game doesn't like running a mod if you've installed to a folder that contains a space. C:\Program Files\Freespace2\Media_VPs for instance would still give you that error.
Odd, it has for me.
Incidentally kudos on sticking the media.vp files in their own folder and running it as a mod. That's how everyone should do it! :)
I'm doing that too, I just forgot how to do a MOD in a MOD folder thing. :D
-
Either type -mod mod1,mod2,media_VPs into the launcher manually (Where mod1 is the mod you want to play, mod2 is the name of any supporting mods it needs and media_VPs is the name of the folder where you put the VPs) or use mod ini files to do the same sort of thing automatically. Be warned that mod.ini's are going to be replaced by something better Taylor is cooking up but for the moment they're real timesavers.
There are a whole bunch of sample ini files available here (http://homepage.ntlworld.com/karajorma/FAQ/Downloads/FS2_Launcher_Ini_Files.rar).
-
Be warned that mod.ini's are going to be replaced by something better Taylor is cooking up but for the moment they're real timesavers.
I did want to add the the new launcher I'm working on now will still be able to use mod.ini files. The ultra new version that goes with all of the updates I have coming down the line in a few months will at least be able to read the current mod.ini files and use the same settings in the newer ini code (didn't originally plan to do that but decided to recently) or still use them as is but with the newer dependency stuff and additional ini files. We (me plus everyone else ;)) will just have to see how that ends up working out. The current mod.ini files aren't cross-platform friendly and how that gets worked out will ultimately determine the final product.
Either way the current mod.ini files will be supported in some fashion for a long time to come so feel free to keep making them.
-
Ah. Fair enough. That's even better :)
-
Gee, I wonder what mod you are trying to run. I wonder.....