Author Topic: Freespace 2 Open 3.7.2 Mac problems  (Read 3336 times)

0 Members and 1 Guest are viewing this topic.

Offline cstar

  • 23
Freespace 2 Open 3.7.2 Mac problems
I got FS2 from Desura and had it working two years ago on my previous computer. I recently re-downloaded the game and attempted to run it again, but the FS2_Open app crashes on startup. I realized it was an older version of FS2 Open, so I downloaded the windows FS2 installer exe, opened it in wineskin and then copied those files over and ran the FS2 open installer. I now have the latest version of FS2, 3.7.2, but it still crashes on startup. It has opened to the pilot screen once when directly opening the FS2_Open app file, but has not done so since. I have tried to get a log file, but the debug version crashes without generating a log file. I've attached the OSX crash report for the debug version instead, which I hope could be useful. Thanks for any help you guys can give me!

My error seems similar to the error described here: http://www.hard-light.net/forums/index.php?topic=71493.msg1414036#msg1414036 but that solution has not worked for me.

[attachment deleted by nobody]
« Last Edit: October 08, 2015, 12:11:48 pm by cstar »

 

Offline Cyborg17

  • 29
  • Life? Don't talk to me about life....
Re: Freespace 2 Open 3.7.2 Mac problems
You're using Wxlauncher, correct?

 

Offline cstar

  • 23
Re: Freespace 2 Open 3.7.2 Mac problems
Yep. I've tried opening the app without the launcher and it makes no difference.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Freespace 2 Open 3.7.2 Mac problems
I can see that FSO is using this video card; Intel HD Graphics 4000. They aren't that well supported in FSO, can you try adding -no_glsl to the launcher options?

Advanced Settings -> Troubleshooting -> Disable GLSL (Shader) Support


Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline cstar

  • 23
Re: Freespace 2 Open 3.7.2 Mac problems
Still crashes. My laptop has a graphics card, but I think OSX only uses it when there is high demand, which wouldn't happen when it crashes immediately.

 

Offline DahBlount

  • 29
  • Alpine ☆ Cancer Tribulation
    • Skype
    • Steam
Re: Freespace 2 Open 3.7.2 Mac problems
Mac has relatively poor driver support on Intel graphics. Disable the following: Post-Processing, FXAA, Lightshafts, Deferred Lighting, Shadows, and GLSL support.

In addition: Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.
<Axem> yet still more insightful than #hard-light

<Axem> jad2.23 will just be cat videos

<DahBlount> So
<DahBlount> JAD2.2 is like that
<Axem> maybe
<Axem> it can be whatever you like!
<DahBlount> A Chocolate Sundae?
<Axem> sure

My models: GTF Gilgamesh - GTD Nuadha [Redesigning] - Ningirama [WIP] - GTG Zephyrus

 

Offline cstar

  • 23
Re: Freespace 2 Open 3.7.2 Mac problems
I've disabled all of those that I can find. FS2_Open crashes without generating a log file, so I don't have anything other than the crash report to post. As far as I can tell, its the same issue as the one in the linked post in the OP.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Freespace 2 Open 3.7.2 Mac problems
FSO Debug should nearly always create a log, and from the OSX crash report FSO seems to have passed the point where the log will start being written. On OSX it can be found here:

~/Library/FS2_Open/data **

**NOTE FOR PEOPLE USING MAC OS X LION:
The library folder is hidden in the Finder for some excellent reason. Please see information here on how to access the folder.

I'm not very familiar with OSX, but is there a way that you can configure the more powerful GPU to always be used for FSO? On Windows this is usually found in the Nvidia or AMD control panel.
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Freespace 2 Open 3.7.2 Mac problems
If you try a more recent Nightly Build, they export special values that should make the system default to the high-performance GPU; renderer changes may also affect your ability to launch the game.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline cstar

  • 23
Re: Freespace 2 Open 3.7.2 Mac problems
I've tried the nightly build and had the same issue. I can attach the crash report for that if it would help. I have attached screenshots of my Freespace 2 folder and the folder that should contain the log file, which I still can't find  :(

[attachment deleted by nobody]

 

Offline DahBlount

  • 29
  • Alpine ☆ Cancer Tribulation
    • Skype
    • Steam
Re: Freespace 2 Open 3.7.2 Mac problems
Have you tried running a debug build instead of the normal build? They will generally have "debug" or "DEBUG" at the end of the file name.
<Axem> yet still more insightful than #hard-light

<Axem> jad2.23 will just be cat videos

<DahBlount> So
<DahBlount> JAD2.2 is like that
<Axem> maybe
<Axem> it can be whatever you like!
<DahBlount> A Chocolate Sundae?
<Axem> sure

My models: GTF Gilgamesh - GTD Nuadha [Redesigning] - Ningirama [WIP] - GTG Zephyrus

 

Offline cstar

  • 23
Re: Freespace 2 Open 3.7.2 Mac problems
Yep, the crash report in the op is from a debug version.

 

Offline Cyborg17

  • 29
  • Life? Don't talk to me about life....
Re: Freespace 2 Open 3.7.2 Mac problems
It's hard to figure out problems without the log, but let's try going back instead of forward.  We can try a really old but really stable build.  It's unlikely to work, but maybe an edge case broke somewhere along the way. :)

3.6.12 http://www.hard-light.net/forums/index.php?topic=70692.0

In addition try: Software Rendering mode.

Also do you have any mods activated?  Have you tried running vanilla (no mods)?

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Freespace 2 Open 3.7.2 Mac problems
Could you also try creating the "data" directory in Library/FS2_Open? (FSO is *supposed* to create that if it doesn't exist, so I'm not sure what's going on there). Then run another debug build & see if fs2_open.log appears there?
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline cstar

  • 23
Re: Freespace 2 Open 3.7.2 Mac problems
I created the data directory, and a file showed up, I've attached it below!!!! My original download came with 3.6.12 and that had the same issue as 3.7.2, which is why I tried to upgrade.

[attachment deleted by nobody]

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Freespace 2 Open 3.7.2 Mac problems
It looks like FSO has crashed while trying to initialise OpenGL. Try removing these command line options.

Code: [Select]
  -soft_particles
  -post_process
  -fb_explosions
  -nohtl

If that doesn't work, please run debug again and post another log.

Also, did you have any luck finding out if you can manually force OSX to use your more powerful GPU?
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline cstar

  • 23
Re: Freespace 2 Open 3.7.2 Mac problems
So I disabled those settings, but have no change, I've attached the new .log file below. I've set my computer to only use the discrete card, but it seems to not have made a difference.

Thanks for the help!

[attachment deleted by nobody]

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Freespace 2 Open 3.7.2 Mac problems
Urgh, the log isn't very helpful. As a last resort, can you try running in 1024x768... but I'm really starting to feel that we've got a fatal bug with 3.7.2 on OSX, and we're going to need the OSX coders to have a look at it.
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

  

Offline Echelon9

  • 210
Re: Freespace 2 Open 3.7.2 Mac problems
Cutting right through the testing here (thanks though), this is a known problem with OS X 10.x and one of the middleware layers the FS2Open engine uses, specifically SDL.

Apple made some changes behind the scenes to their OpenGL implementation, and the way our engine uses SDL to initialise the OpenGL renderer hits this bug every time. We directly package our SDL middleware with the FS2Open binary, so its not possible for users to simply rip and replace. Unfortunately, I'm not aware of any known workaround that you can use. i.e. FS2Open is completely broken on OS X 10.x at the moment.

Importantly, there is a fix - which is to use the latest 2.x version of the SDL middleware in a new release of the FS2Open engine. We have a testing branch called "antipodes" that has the SDL2.x middleware in use, but it is not yet in any of the nightlies builds. You can also follow along high-level development in this thread, but it doesn't include every change.

The project is aiming to get out a final SDL1.x based release of FS2Open shortly, before we pull over the antipodes testing branch to nightlies. A build based on that SDL2.x middleware code will resolve this issue for OS X.