Is it the installer or the actual program that you can't run? And do you get a message when you try to run it? (If you do, post it here.)
Never mind, I got it to work this time. I clicked the wrong application icon last time. What is it that I do again? Put it in the Freespace 2 folder? I have a folder named GOG Games, and a folder within that called Freespace 2. However, I have a folder within the Freespace 2 folder called Games, in which I have ANOTHER Freespace 2 folder with lots of the FSO stuff.
EDIT: Okay, now it's really messed up. I managed to unzip the 11.4 file to the Freespace 2 folder (the one in the GOG Games folder), but when I put it there, it said that Windows encountered a problem and couldn't load the program. When I deleted the 7-zip file from the folder, FSO loaded, but at the sign in page, it said that it failed to save the pilot file and that I needed to free up disk space or something like that. I don't know WHAT'S going on there.
With some laptops, you need to hold the Fn key to make the F keys perform their usual functions.
Thanks, it worked now.
The strangest thing happened when I went to the ship lab and clicked on various ships. I put it on wireframe like you said, and when I clicked on a new ship, the FPS almost always dropped to 23 or 30 or something around there and went back up to 60 after a second. Once the ship was up, the FPS would stay 60 until I loaded a different ship model. The bigger ships were especially slow.
And here's the cmdline:
C:\GOG Games\Freespace 2\fs2_open_3_6_18_NO-SSE.exe -mod Games/Freespace 2/MediaVPs_3612
I believe after seeing your previous debug logs (whoops I only saw what methods you had applied, not your debug log) you actually haven't disabled GLSL rendering.
Of course I don't play on your computer so things might be different.
So once again go under the Troubleshooting list in the Flags section and CHECK the box : Disable GLSL (shader) support
(I just suggested this method because I see only -window flag line is enabled and in-built shaders are being USED. So I thought that you took disabling GLSL rendering as disabling specular, environment and normal maps. Not that I am correct always.)
Thanks Arpit. You were right--I didn't have Disable GLSL (shader) support on. I did check that box and then played, and that seemed to fix the stuttering when viewing damage lightning and engine exhaust. (It's sad, though, because the GLSL looks so pretty.
Any way that I could still use it?) However, there are still plenty of hiccups involved with other things, mainly ships warping in and some of the explosions.
I've especially noticed the slowdowns on the current level I'm playing, "The King's Gambit." A ton of ships are constantly warping in on this one, and therefore the chopiness is worse. I don't know if the audio is related, either, because the stuttering always goes on for only a few seconds when something warps in, but it's always accompanied by command or another pilot commenting on the development. Also, the music and dialogue on the mission briefings frequently have little hiccups/skipping as well.
My Avast antivirus also happened to be running a quick scan during one of the times I tried to load FSO, and it actually froze on a white screen for some reason and said it wasn't responding. Could be something to do with the antivirus, too, as some have suggested. So many variables!