Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: kylekatarn77 on July 12, 2017, 11:02:06 pm
-
So, I am not looking to be a mod creator, just to enjoy other people's work. I downloaded FS2 from GOG, and then downloaded the FSOpen Installer. Everything seemed to download, including things like Blue Planet. And the game seemed to load and run fine (I'm assuming that since I used the installer, the graphics are now the newer version for main game.)
However, I have no clue as to how to open any of those modded campaigns, such as Blue Planet. Anyone know what to do?
-
Assuming the installer worked and installed the mods correctly into your FS directory, it's basically a two step process. First, select the mod you want to play from the launcher and run FSOpen. Then, either with a new pilot or an old pilot, go to the campaign room from the main hall menu and select the campaign from the mod you activated. Then play the campaign like you would normal FS2.
-
First BW, wanna legitimately thank you for taking the time to help someone out.
Second, meant to ask, is there anything special I need to do to ensure the newer graphics and visuals for main game are used or should it be automatic? Was looking at picture comparisons, now no longer sure if it did it automatically lol.
But on to the main issue the post is for.
Ok, so in Blue Planet Folder in the directory, there's a bunch of files... and then I used the launcher, which if I used the right one was called Launcher and had a paw print next to it... and then clicked browse and hit Blue planet.... and the only thing in that, or any of the folders, was either blank or the text documents. I think I did something wrong.
-
Yea, IIRC the old launcher (v5.5g) did things a little bit differently - I think you need to select a FS2 Open executable - it should be in the main game directory, something like fs2_open_3_8_0_RC1_x64_SSE2.exe... But to run new FSO versions properly, you will need the wxLauncher. Just download the exe (https://github.com/scp-fs2open/wxLauncher/releases/download/0.12.0-rc.2/wxlauncher-0.12.0-rc.2.exe), install wxLauncher from it, and 90% work should be done by then. It should automatically detect Freespace Open - the only thing left for you is to select the proper options (mostly 'Advanced' tab, if you feel like tampering with cool stuff) and choose the mod you want to play via 'Mods' tab.
-
First BW, wanna legitimately thank you for taking the time to help someone out.
Second, meant to ask, is there anything special I need to do to ensure the newer graphics and visuals for main game are used or should it be automatic? Was looking at picture comparisons, now no longer sure if it did it automatically lol.
It's automatic if you want to play a fan made camapign. For example, if you choose Blue Planet, it will load the advanced graphics as a subset of its own new ships and effects and things. If you just want to play the FS2 campaign with the nicer graphics, you need to select the "MediaVPs 2014" mod and click "Activate" (like any other mod).
MitoPL has nailed it otherwise. I hope this isn;t sounding too complicated - it really isn't, especially with WX launcher. The first time you play, you need to select your downloaded FSO executable, set your initial settings once (there are presets to help with that), pick a mod, click activate and then click play. After that it's one click to play until you want to try a different mod, then you select it, click activate and away you go.
-
Wanna thank you both so far. Hmm, well Mito I did try downloading that. But, and this counts for Blackwolf's original idea too, it seems to have the same issue as the other launcher, - in that when I go to pic a MOD folder, they all seem to be empty and it claims they have no executables.
-
Yea, IIRC the old launcher (v5.5g) did things a little bit differently - I think you need to select a FS2 Open executable - it should be in the main game directory, something like fs2_open_3_8_0_RC1_x64_SSE2.exe... But to run new FSO versions properly, you will need the wxLauncher.
???
5.5g is running the new executables just fine.
-
There's one more thing - have you selected the game's main folder in the proper field? (like D:/Games/Freespace) If you didn't, that's probably why the launcher can't find any executables: it doesn't know where to look for them.
You might also consider using one of the more recent FSO builds, as the PBR render is amazing.
@Spoon: So the problems are only with wxLauncher 0.10.1? I think it was about SDL and proper mod loading, but I can't remember that for sure.
-
Right now, this is where everything is- C:\GOG Games\Freespace 2 and in freespace 2 is where all the mod folders are
-
IS that right?
-
@Spoon: So the problems are only with wxLauncher 0.10.1? I think it was about SDL and proper mod loading, but I can't remember that for sure.
I dont know about wxLauncher, as I havent used it in a very long time. But 5.5g hasn't given me any issues with mod loading or SDL or anything.
-
Yea, IIRC the old launcher (v5.5g) did things a little bit differently - I think you need to select a FS2 Open executable - it should be in the main game directory, something like fs2_open_3_8_0_RC1_x64_SSE2.exe... But to run new FSO versions properly, you will need the wxLauncher.
???
5.5g is running the new executables just fine.
It runs them, but there are definitely issues. A 3.8 executable from 5.5g can't see mod folders with spaces in the name, for example. Bloom doesn't work, and other lighting is weird. Probably other things too.
Kylekatarn77: The folder you have FSO installed into shouldn't matter. Have you chosen an executable file yet? The "Basic Settings" tab of wxLauncher will allow you to set your FS2 folder, and then it will detect all of the FSO executable files in that folder, which you can pick from a dropdown menu. Here's what mine looks like:
(http://i.imgur.com/VC4hbfk.jpg)
It doesn't matter if the installer didn't install 3.8.0 - as long as you pick an executable file. It'll probably be 3.7.4 or something like that. Do that, and then check the mods tab. They should all show up.
-
...Maybe there isn't any FSO executable to choose? It's getting a bit weird.
-
Got it to work! I think I was going too far into subfolders- choosing just freespace 2 folder worked. Thanks again guys!
One last thing- mission 3 or 4 I tried to change my selected fighter and it keeps causing the game to stop working and quit. Any thoughts?
-
Please post your fs2_open.log file. Instructions on how to do this can be found in this post.
I think that turning on '3D Weapon Selection' and '3D Ship Selection' in Advanced Settings in your launcher should help.
-
It runs them, but there are definitely issues. A 3.8 executable from 5.5g can't see mod folders with spaces in the name, for example. Bloom doesn't work, and other lighting is weird. Probably other things too.
??????????
(https://ibin.co/3TFhl5ADlQFz.jpg)
(https://ibin.co/3TFhZqIEsmzf.jpg)
Looks like bloom to me!
It can see every mod folder just fine with a build made this very month.
There seems to be some odd misinformation circling about 5.5g, because exactly zero of the things you guys are saying about it are true. And I've even put WoD on my laptop with windows 10 to make sure its not an OS problem, since my desktop is on 7.
Guys, 5.5g still works fine.
-
5.5g works for standalone game i.e. original FS2, new WoD etc., not with mods for them.
-
Okay, I'll bite, how does that (not) work?
-
5.5g works for standalone game i.e. original FS2, new WoD etc., not with mods for them.
Again, what? I have been running JAD, Mediavp's, BP etc etc with 5.5g or years, and never run into any issues.
-
5.5g works for standalone game i.e. original FS2, new WoD etc., not with mods for them.
Again, what? I have been running JAD, Mediavp's, BP etc etc with 5.5g or years, and never run into any issues.
None of the mods you just listed come in folders with spaces in them.
-
So out of curiosity I tried 5.5g with some of the recent 64 bit builds and it just didn't work at all. No matter what mod folder I selected or even when I used 'no mod' it would just launch with the last mod I played with wxlauncher.
I also tried setting some silly flags like -fov 0.1 which resulted in no change whatsoever. So I definitely wouldn't say 5.5g is fine. It might work for some machines in some circumstances but in general it just doesn't play nice with newer FSO builds.
-
@FrigkFeek: I think the underlying issue is the new settings directory. 5.5g still uses the registry, however wxLauncher automatically creates %AppData%\HardLightProductions (the new settings folder) which causes FSO to ignore the registry settings. If you delete or rename that folder, 5.5g should work until you use wxLauncher again.
-
Well, that makes sense. Still, being able to switch from 5.5g to Wxl with no issues but the reverse being a bit more annoying makes WxL the better launcher.
I'd have to do more testing with different mod folder names on 5.5g to know for sure how well it works with newer builds and I just can't be arsed to backup my HLP settings folder out of just curiosity.