Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Cross-Platform Development => Topic started by: Soulstorm on January 07, 2008, 01:23:42 pm

Title: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 07, 2008, 01:23:42 pm
DOWNLOAD HERE (http://swc.fs2downloads.com/builds/OSX/FS2_Open_Launcher_3.1.3.dmg) (edit: link updated once more, link on original site (http://oramind.com/launcher-os-x-3/) is down again)
...Still in beta, however, I find it much stable. This is what it is added:

- Custom standalone mods. By selecting the mod's application, and the mod's Library folder, you can add any standalone mod into the application.
- Many memory leaks fixed. No garbage collection used.
- Much more stable code, and many minor enhancements.

Perhaps the most notable thing of all is the new source. It's almost completely changed, and the inclusion of new things is much easier. I did that to encourage more people to download the new source and mess around with it, without having to devote much time to figure out what I've done, first. If that beta works fine, I'll release a full featured final version (with update check), and later the fully documented source, in both CVS and in my webspace as a dmg file. Oh, and... Taylor, I still have problems with it. It doesn't accept my login. Anyway, I will send you a pm requesting exact instructions, as a new version and source source is something that I think you wanted some time ago when you figured out that the project needed some modifications. I have the feeling that you wanted to get involved with it, but found it a little messy. Well, I hope this isn't the case this time.

What works:
Every basic functionality that existed in version 2.

What needs attention: Probably, for mods that are not the original FS2_Open application, you must select the folder that contains their preferences. So, you must have ran at least once that particular mod in order to have that folder created. Also, a new preferences file is used. It's called com.soulstorm.MMST2_3.plist and it is subject to change. It resides in your preferences folder in your user Library.

Specific questions I would like to have answered:
Does it work in Tiger? (done!)
Does it display the available options ok?
Does it work with the original FS2_Open as the old one (or better)?
Does it work with additional standalone mods like it should? (done!)
Does the custom command line drawer display the proper enables options, and does it save any custom options that do not exist in the main window as expected (try to give an arbitrary command and see if it's saved in the .cfg file).

EDIT: Updated the beta again. Check the link again.
EDIT2: Updated the link again.
EDIT3: Download again, please. New beta released that fixes many new things...

EDIT: March 2009
I will say it here, because I keep getting questions: As the read-me states, this is the correct order to do things in the Launcher:
1) Do whatever you want with the main window
2) Open the command line drawer (command-T)
3) Hit refresh. The drawer will be updated with all the contents of the main window.
4)Do whatever you want with the command line drawer by adding custom commands or removing some.
5) Save when done.

Link updated to new location. -- Zacam (08/24/11)
Updated link again. -- chief1983 (06/23/14)
Title: Re: FS2_Launcher OS X 3.0
Post by: jr2 on January 07, 2008, 02:27:05 pm
:yes:  :nod:  :D

Good to see more work being done...  thx!  Now if I just had a Mac, I'd test it for you... :nervous: 
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on January 07, 2008, 02:35:31 pm
[...]
Specific questions I would like to have answered:
Does it work in Tiger? (that's something I am dying to know :) )
[...]

No.
After the doubleclick it bounces 2 times in the dock an dies.

No error is reported. HTH

Jan  7 21:30:38 PowerMac-G5 crashdump[298]: Console crashed
Jan  7 21:30:38 PowerMac-G5 crashdump[298]: crash report written to: /Users/lang/Library/Logs/CrashReporter/Console.crash.log
Code: [Select]
**********

Host Name:      PowerMac-G5
Date/Time:      2008-01-07 21:30:37.360 +0100
OS Version:     10.4.11 (Build 8S165)
Report Version: 4

Command: Console
Path:    /Volumes/MacOS X 10.5/Applications/Utilities/Console.app/Contents/MacOS/Console
Parent:  WindowServer [58]

Version: 10.5 (135)

PID:    297
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0   libSystem.B.dylib    0x9012c6f0 _malloc_initialize + 56
1   libSystem.B.dylib    0x900033b8 malloc + 48
2   com.apple.Foundation 0x92bc1ef4 _NSAPDataCreate + 32
3   com.apple.Foundation 0x92bc2070 NSPushAutoreleasePool + 40
4   com.apple.AppKit      0x938907ec NSApplicationMain + 60
5   com.apple.Console    0x00001fbc 0x1000 + 4028

Thread 0 crashed with PPC Thread State 64:
  srr0: 0x000000009012c6f0 srr1: 0x100000000000d030                        vrsave: 0x0000000000000000
    cr: 0x44000202          xer: 0x0000000000000000   lr: 0x000000009012c6ec  ctr: 0x00000000900017a0
    r0: 0x000000009012c6ec   r1: 0x00000000bffffaa0   r2: 0x00000000a0001fac   r3: 0x0000000000000000
    r4: 0x0000000000000000   r5: 0x0000000094615278   r6: 0x000000000000009a   r7: 0x000000000000009a
    r8: 0x000000000000009b   r9: 0x0000000000000000  r10: 0x00000000900014f0  r11: 0x00000000a00061ec
   r12: 0x00000000900017a0  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
   r16: 0x0000000000000000  r17: 0x0000000000000000  r18: 0x0000000000000000  r19: 0x0000000000000000
   r20: 0x0000000000000000  r21: 0x0000000000000000  r22: 0x0000000000000000  r23: 0x0000000000000094
   r24: 0x000000009fffc6c0  r25: 0x0000000000000000  r26: 0x00000000bffffccc  r27: 0x00000000a37e07bc
   r28: 0x00000000a0003390  r29: 0x00000000a000c6c0  r30: 0x0000000000000000  r31: 0x000000009012c6c0

Binary Images Description:
    0x1000 -    0x1ffff com.apple.Console 10.5 (135) /Volumes/MacOS X 10.5/Applications/Utilities/Console.app/Contents/MacOS/Console
0x8fe00000 - 0x8fe52fff dyld 46.16 /usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x9021b000 - 0x90268fff com.apple.CoreText 1.0.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x90293000 - 0x90344fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x90373000 - 0x9072efff com.apple.CoreGraphics 1.258.77 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x907bb000 - 0x90895fff com.apple.CoreFoundation 6.4.9 (368.31) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x908de000 - 0x908defff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x908e0000 - 0x909e2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a3c000 - 0x90ac0fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90aea000 - 0x90b5cfff com.apple.framework.IOKit 1.4.1 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90b72000 - 0x90b84fff libauto.dylib /usr/lib/libauto.dylib
0x90b8b000 - 0x90e62fff com.apple.CoreServices.CarbonCore 681.17 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x90ec8000 - 0x90f48fff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x90f92000 - 0x90fd4fff com.apple.CFNetwork 129.22 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x90fe9000 - 0x91001fff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServicesCore.framework/Versions/A/WebServicesCore
0x91011000 - 0x91092fff com.apple.SearchKit 1.0.7 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x910d8000 - 0x91101fff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x91112000 - 0x91120fff libz.1.dylib /usr/lib/libz.1.dylib
0x91123000 - 0x912defff com.apple.security 4.6 (29770) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x913dd000 - 0x913e6fff com.apple.DiskArbitration 2.1.2 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x913ed000 - 0x913f5fff libbsm.dylib /usr/lib/libbsm.dylib
0x913f9000 - 0x91421fff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x91434000 - 0x9143ffff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x91444000 - 0x914bffff com.apple.audio.CoreAudio 3.0.5 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x914fc000 - 0x914fcfff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x914fe000 - 0x91536fff com.apple.AE 1.5 (297) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x91551000 - 0x91623fff com.apple.ColorSync 4.4.10 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x91676000 - 0x91707fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x9174e000 - 0x91805fff com.apple.QD 3.10.25 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x91842000 - 0x918a0fff com.apple.HIServices 1.5.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x918cf000 - 0x918f0fff com.apple.LangAnalysis 1.6.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x91904000 - 0x91929fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/FindByContent.framework/Versions/A/FindByContent
0x9193c000 - 0x9197efff com.apple.LaunchServices 182 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x9199a000 - 0x919aefff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x919bc000 - 0x91a02fff com.apple.ImageIO.framework 1.5.6 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x91a19000 - 0x91ae0fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x91b2e000 - 0x91b44fff libcups.2.dylib /usr/lib/libcups.2.dylib
0x91b49000 - 0x91b67fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91b6d000 - 0x91c24fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91c73000 - 0x91c77fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91c79000 - 0x91ce3fff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x91ce8000 - 0x91d25fff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x91d2c000 - 0x91d46fff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x91d4b000 - 0x91d4efff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x91d50000 - 0x91e2efff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x91e4e000 - 0x91e4efff com.apple.Accelerate 1.2.2 (Accelerate 1.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x91e50000 - 0x91f35fff com.apple.vImage 2.4 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x91f3d000 - 0x91f5cfff com.apple.Accelerate.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x91fc8000 - 0x92036fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x92041000 - 0x920d6fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x920f0000 - 0x92678fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x926ab000 - 0x929d6fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x92a06000 - 0x92af4fff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x92af7000 - 0x92b7ffff com.apple.DesktopServices 1.3.7 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x92bc0000 - 0x92debfff com.apple.Foundation 6.4.9 (567.36) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92f18000 - 0x92f36fff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x92f41000 - 0x92f9bfff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92fe7000 - 0x92ff7fff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x93250000 - 0x9326dfff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x93295000 - 0x935a3fff com.apple.HIToolbox 1.4.10 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x936f3000 - 0x936fffff com.apple.opengl 1.4.7 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x93799000 - 0x93799fff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x9379b000 - 0x93dcefff com.apple.AppKit 6.4.9 (824.44) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x9415b000 - 0x941cdfff com.apple.CoreData 91 (92.1) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x94206000 - 0x942cbfff com.apple.audio.toolbox.AudioToolbox 1.4.7 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x9431e000 - 0x9431efff com.apple.audio.units.AudioUnit 1.4 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x94320000 - 0x944e0fff com.apple.QuartzCore 1.4.12 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x9452a000 - 0x94567fff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
0x9456f000 - 0x945bffff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x945c8000 - 0x945e2fff com.apple.CoreVideo 1.4.2 /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x945f3000 - 0x94614fff libmx.A.dylib /usr/lib/libmx.A.dylib


Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 07, 2008, 04:52:10 pm
Please redownload the application. I think I fixed it...
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on January 08, 2008, 12:50:47 pm
Please redownload the application. I think I fixed it...

Nope.

Same result. Do you need the crashlog?
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 09, 2008, 02:48:56 pm
That would prove useful...
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 09, 2008, 03:08:49 pm
Actually, I got it. I changed some things and configurations, and tested the new application under Tiger and it works. Now, everyone can spot the other bugs... :)

Download the new application HERE (http://users.forthnet.gr/ath/jonmecos/Mainsite/Development/archives/limbo/multiplemodsupport%20Tiger.zip)
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on January 09, 2008, 03:17:07 pm
Actually, I got it. I changed some things and configurations, and tested the new application under Tiger and it works. Now, everyone can spot the other bugs... :)
[...]

so you resurrected your own tiger  ;)

It works. Looks good. I will test it on the weekend. Thanks for the Launcher  :yes:

Edit: Short test with WCS. Works. very nice!

Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 11, 2008, 04:12:09 am
Quote
so you resurrected your own tiger
Actually, I resurrected my old mac :)

Thanks for the information. I will make some minor changes and release the final version not long from now.
Title: Request For an Icon!
Post by: Soulstorm on January 14, 2008, 12:37:37 pm
Calling all artists or anyone who wants to be a little involved...

Can anyone make a simple Icon for the Launcher, because my own is absolutely terrible! And I have no idea on how to make a decent one! His/her name will be mentioned, of course!

Oh and as for the launcher... in one or two days the final beta will be posted in here. Memory leaks have been addressed and the UI has changed a bit.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 16, 2008, 12:24:59 pm
New beta! Check it out!

(http://www.hard-light.net/forums/index.php?action=dlattach;topic=51391.0;attach=4593)

download it here (http://users.forthnet.gr/ath/jonmecos/Mainsite/Development/archives/limbo/FS2_Launcherbeta.zip)... (I also altered my first post's link)
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on January 16, 2008, 01:27:37 pm
it looks weird in X 10.4.11

[attachment deleted by ninja]
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 16, 2008, 05:02:50 pm
Indeed. It could be because 10.4 handles images and draws buttons differently... anyway I will release a new beta this weekend. I would do this tomorrow, but I have 2 lessons to write exams for, so these two days are going to be a little messy for me :)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 25, 2008, 08:58:55 am
OK, I think I fixed the UI problems, and ensured compatibility with 10.4.

Chect the new beta!
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on January 25, 2008, 06:41:44 pm
This launcher seems to do weird things to the cmdline_fso.cfg file.  After opening Freespace once with SomeMod (a folder I use to test stuff) and again with Derelict, this is what came out:

Code: [Select]
-spec -glow -env -jpgtga -missile_lighting -ship_choice_3d -3dwarp -fov 0.39 -rearm_timer -mod derelict -fov 0.39 -mod SomeMod
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 26, 2008, 03:06:25 am
OK... but why is this weird? All I see is some options to the command line file. Can you be more describable? I need a detailed explanation of the problem.

And I would also like to know what does this test folder contain...
Title: Re: FS2_Launcher OS X 3.0
Post by: kmunoz on January 26, 2008, 07:48:27 am
OK... but why is this weird? All I see is some options to the command line file. Can you be more describable? I need a detailed explanation of the problem.

And I would also like to know what does this test folder contain...

Some of the options repeat. I have the same problem. Notice the -fov option. If I run the Launcher twice and select that option both times, it writes it a second time in the config file.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 26, 2008, 10:46:02 am
You are right, guys. Thanks for pointing this out. Actually, it is a problem that is happening only with the options that require values for the Launcher. That is a problem with the custom command line drawer, actually. The drawer does not update itself whenever an option has been changed in the main window. But the main window, is updated of the changes in the drawer.

Because of that, you can have an option like "-mod derelict" in the drawer, but the mod "fsport" selected in the main window. When the Launcher closes, it writes both commands in the command line. I had missed that point. Probably, this problem was less notable (but not eliminated) in version 2 of the Launcher. I will definitely look at it. That's why I am releasing betas before the actual product! :)

Problem will be rectified in the next beta, whenever that is (I have my exams now)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 26, 2008, 01:29:56 pm
Quick patch!

That should correct the problem described above...

You should note, however, that the custom command line drawer allows FULL flexibility to the user. That means that there is a chance that in the command line drawer, you write an option twice, or more, and each time with different values. In that case, the values that will be saved will be the last ones, while the rest will be stripped from the command line.

Download <<ref deleted>>
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on January 26, 2008, 01:43:56 pm
THANKS.  That seems to have fixed the problem.

I have a feature request.  Could we have an option to select which tab (Graphics, Gameplay + Speed, etc) to automatically select on startup?

[offtopic]Yay!  I finally reached 27!.  LOL I'm such a noob.[/offtopic]
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 26, 2008, 04:48:20 pm
Feature Added!

Download the new beta, and check the preferences to find what you are looking for! If it doesn't work for you, you may need to delete the preferences...

DOWNLOAD HERE (http://www.hard-light.net/forums/index.php?action=dlattach;topic=51391.0;attach=4704)

EDIT: Rectified a small problem with it, and added a new function in the "special" menu that will allow you to change the selected mod's Library folder location. Previously, this wasn't possible, after you have set it when you created it in the Available Mods dialog.

[attachment deleted by ninja]
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on January 26, 2008, 08:09:50 pm
Thanks.  Now go study!
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 27, 2008, 10:49:13 am
Yes, sir!
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on May 01, 2008, 06:25:50 am
the new 3.03 is listed at http://www.macupdate.com/info.php/id/27391/fs2_open-launcher  :yes:
Title: Re: FS2_Launcher OS X 3.0
Post by: meego on May 01, 2008, 11:20:13 am
Hi,

I think the "Refresh" button is a bit confusing. If i understood right, it rebuilds the flag list based on the options selected in main window. However, this erases all custom flags.

Maybe you should look into another way to input custom flags. Something that ensures that custom flags remain even after the user changes options and refreshes the drawer. Something that would also separate them from regular flags, for the sake of visibility and clarity.

I think the Win32 launcher got it right with a special box for custom flags.
(http://homepage.ntlworld.com/karajorma/FAQ/FAQ-Images/Installing/Launcher02.jpg)

IMO, the best would be to have an editable field for custom flags, and non-editable field to display all active flags.

Just my 2cts. Still very nice job on the launcher.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 01, 2008, 05:33:42 pm
I agree that there should be a place for custom flags.  Possibly en entire section where you can add/remove custom flags (like the drawer right now but in the main window and it doesn't delete everything when you click refresh).
Title: Re: FS2_Launcher OS X 3.0
Post by: meego on May 02, 2008, 06:39:37 am
With 1208-Xt, I'm not getting the "no_emissive_light" option and have to input it as a custom flag. Shouldn't it be available? Is this a bug?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 02, 2008, 09:51:15 am
I never got that option.  No matter what build.
Title: Re: FS2_Launcher OS X 3.0
Post by: Jeff Vader on May 02, 2008, 11:03:42 am
Neither did I (even though I'm a Windork person). I guess it counts as a "custom" option.
Title: Re: FS2_Launcher OS X 3.0
Post by: karajorma on May 03, 2008, 04:12:36 am
http://homepage.ntlworld.com/karajorma/FAQ/FAQ-Images/Installing/Launcher02.jpg

I was about to point out how ridiculously out of date 3.6.7 builds are but then I realised why I should shut my mouth. :p
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 04, 2008, 02:41:30 am
I will change the command line drawer to something you might like more, then. However, I should remind you that the the refresh button was added as an additional facility and not something that should confuse you. Even if you don't hit refresh, and just use the command line drawer to give custom flags, these options will be merged with the options in the main window anyway. The refresh button exists to avoid confusion. You hit refresh, and every option you have enabled in the main window will be displayed there. Any custom options will be removed. I don't know, it seemed like a good idea at the time, as I wanted a function that would clear the drawer. of unwanted functions.

Things to add to the next build:
- Use the tooltips as the name of the options. No more options with names such as -spec
- Imrove the custom commands functionality
- Automatic searching for standalone mods in the computer (I am actually getting used to spotlight searching right now... I don't know if this will happen in this build or the next)
- Some error correction. Trashing of the preferences file if something goes wrong.

I am actually glad to see that it works for most users here who use Leopard and Tiger. I had some major incompatibilities with version 3.0 of the Launcher in Tiger (I build it using Xcode 3.0) and I was forced to take guesses as far as the code is concerned.

Just a question though. Do you think I should leave the command line drawer intact and just add the custom commands section or should I completely get rid of the drawer?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 04, 2008, 07:10:58 am
The Drawer can be useful for troubleshooting, but if you fix the system so that it updates system so that it refreshes every time you check or uncheck a box and add a custom flags system, it might not be necessary.
Title: Re: FS2_Launcher OS X 3.0
Post by: meego on May 04, 2008, 08:31:05 am
Quote
I don't know, it seemed like a good idea at the time, as I wanted a function that would clear the drawer. of unwanted functions.

This is true, but only because the drawer makes it hard to clearly see the difference between custom and standard flags.

Quote
Just a question though. Do you think I should leave the command line drawer intact and just add the custom commands section or should I completely get rid of the drawer?

I agree with blowfish. Plus it's still nice to have all flags displayed in one place.

The drawer could benefit from being uneditable - what's the point of changing -spec values if it can be done in its dedicated field? - and, with the addition of a custom flags box, the drawer could auto-refresh to mirror the changes.

Or you could get rid of the drawer and go for a box instead. I made a mock-up (forgive my awful GUI skills :p):

[attachment deleted by admin]
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 04, 2008, 08:43:42 am
No box.  Not everything fits in it.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 06, 2008, 04:56:37 am
I see. OK, then. I will not get rid of the drawer. I will make it uneditable. I will add a field for custom arguments. The drawer will reflect the unified contents of the main window and the field for custom arguments.

However, my exams start in 4 days. It may be a while before I make those changes.

Quote
No box.  Not everything fits in it.

What would you recommend, if not a text field?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 06, 2008, 08:49:03 am
Something like this.  Except less sloppy.

[attachment deleted by admin]
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 06, 2008, 04:15:08 pm
I don't believe that the way you have designed it would be better than the command line drawer as it is now. This is why:

-Firstly, you won't be able to see what custom flags you have enabled and at the same time look at the main window and make configurations. You will need to constantly change tabs to do that. I added the drawer to give the user the opportunity to have the custom flags enabled and at the same time consulting the main window.
-Secondly, the table view is just too large. It occupies all this space just to write commands that take too little space.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 06, 2008, 04:17:58 pm
Well, truth be told, I'm fine with the drawer system, except that all custom flags get erased when you refresh, which is necessary at times.
Title: Re: FS2_Launcher OS X 3.0
Post by: meego on May 06, 2008, 07:08:28 pm
Quote
OK, then. I will not get rid of the drawer. I will make it uneditable. I will add a field for custom arguments. The drawer will reflect the unified contents of the main window and the field for custom arguments.

Sounds good. Good luck with your exams.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 08, 2008, 11:11:51 am
OK, here's a big feature request (of course after your exams).  Mod.ini support.  This would take a fair amount of code, but I know it can be done.  If you wanted help with this, I know Objective-C and am familiar with the Cocoa APIs.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 11, 2008, 04:55:04 am
Quote
OK, here's a big feature request (of course after your exams).  Mod.ini support.  This would take a fair amount of code, but I know it can be done.  If you wanted help with this, I know Objective-C and am familiar with the Cocoa APIs.

Actually, I would firstly need a tutorial on mod.ini. Where can I find one?

PS. Everything can be done, don't worry. I just need to know how FS2_Open handles things.

EDIT:
I've been reading the documentation on mod.ini (http://www.hard-light.net/wiki/index.php/Command-Line_Reference#-mod) but I must admit I don't quite understand that feature request.

The way I see it, mod.ini is a file which is handled by FS2_Open (or is it the Launcher?), if it exists in the same folder as the mod. It may contain:

- a set of custom flags specific for the mod
- a set of custom mods that may be used in conjunction with this one

I already have a small parser ready that can probably handle this file (wow, I never thought that stuff I was implementing in frameworks long ago would come useful now) but I need a reference as to what types of data may be found there. So, it can be done with some effort.

However, I assume you are aware that the Launcher as it is now contains a feature that allows the user to put multiple mods in a text field and load them all? So what more can the mod.ini file offer? (of course I will implement it since there are more people asking for this thing but I need to know its use :)) I remember people telling me about mod.ini long before I released version 3.0, but I didn't pay attention because I thought they missed an already-existing feature. Seems this is not the case.

Please, enlighten me :)
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 11, 2008, 10:48:00 am
Mod.ini is supposed to be handled by the launcher.  Basically it makes things easier for the user, so that if the mod.ini file points to other mods, they will be selected automatically.  Lets take the example of Into the Depths of Hell chapter 3.  This requires chapter 2 to work, and I'm sure you want the MediaVPs with it too.  So instead of having to remember to type in "ITDOH3,ITDOH2,mediavps" every time you want to select it as a mod, you can just type "ITDOH3" and the launcher will read the Mod.ini file and automatically select ITDOH2 and mediavps.

I have found no official documentation on what a mod.ini file should contain, but from looking through a few of them, it might look something like this:

Code: [Select]
[launcher]
image255x112 = BannerImage.bmp;
infotext     = Insert Mod Description Here.;
website      = http://mywebsite.com/mymod/;
forum        = http://mywebsite.com/forum/;

[multimod]
primarylist  = ;
SecondryList = mediavps, nebulae;

[settings]
flags = -flag1, -flag2;

I'm not quite sure what the difference between primarylist and secondarylist are, as I have never seen primarylist used at all, but from what the wiki says, it should come before secondarylist.
Title: Re: FS2_Launcher OS X 3.0
Post by: karajorma on May 11, 2008, 04:23:03 pm
Mod.inis don't replace multimod. They simply act as an interface for it so that the end user never has to worry about it. They also have a few neat minor effects.

The main feature is the secondarylist option. The reason for having that (in the Windows launcher at least) is because of the Select Mod button we have to choose which mod we want to play. The advantage of having a mod.ini is that as soon as you select a mod (say FSPort) the launcher checks the mod.ini and appends any folders mentioned therein to the command line. The user no longer has to know which mods are required for the selected one to work any more.

Primarylist works similarly but anything on that list is placed in front of the selected mod so the commandline reads -mod primarylist, mod name, secondarylist. Thus far there's never been much call for the primarylist option. I can only think of a couple of times I've ever used it and both have been in fairly odd situations.

The other useful features are all in the [launcher] section and are fairly self explanatory. They allow the mod.ini to provide a bitmap image for each mod, a few paragraphs of text explaining what it's about and links to the mods forum and website.

Ignore the setting custom flags option as this is deprecated and was never implemented properly in the first place anyway.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 16, 2008, 12:34:47 pm
...Mod.ini support.  This would take a fair amount of code, but I know it can be done.  If you wanted help with this, I know Objective-C and am familiar with the Cocoa APIs.

It's allright, thank you, but I have already made a decent parser for mod.ini, and it seems to be able to also handle arbitrary arguments. All I need to do is to implement the parser inside a user interface.

I have thought of this so far:
I could provide a function in the top menu that would say "mods..." or something like that. By enabling this button, I could display a window with a table view, an image view and a text field. The tableView will display all available mod folders (folders that contain custom non-standalone mods and exist in the same folder as the selected application). The imageView will display the custom image for the selected mod (taken directly from mod.ini file) and the textfield will display the additional info for the mod (if any).

The user will also be able to select one non-standalone mod to run, and by selecting that, the Launcher will read the mod.ini file (if any) and will process any additional data accordingly.

Side Note: I will also release a framework that will accompany the source. It contains hundreds of additional functions for ObjectiveC/C++, and will provide functionality to the Launcher (among my other projects). However, it's not documented, so I am thinking about just implementing its source into the Launcher, forcing compilation of the entire framework each time. That would also result into a more bloated source. I don't know... the idea of a framework package seems more appealing to me, but writing a documentation about this framework will require an enormous amount of work.
Title: Re: FS2_Launcher OS X 3.0
Post by: karajorma on May 16, 2008, 01:23:39 pm
That's functionality that the Windows launcher doesn't have (not really enough space in the tiny launcher anyway) but which would look really cool in the Mac version. Go for it. :yes:
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 16, 2008, 06:45:52 pm
Side Note: I will also release a framework that will accompany the source. It contains hundreds of additional functions for ObjectiveC/C++, and will provide functionality to the Launcher (among my other projects). However, it's not documented, so I am thinking about just implementing its source into the Launcher, forcing compilation of the entire framework each time. That would also result into a more bloated source. I don't know... the idea of a framework package seems more appealing to me, but writing a documentation about this framework will require an enormous amount of work.

Patchy/incomplete documentation would be all right, if people had specific questions, they could just ask you or something ;)

Besides, I really don't know many people here who actually know ObjC (besides you, of course)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 17, 2008, 02:48:26 am
That's functionality that the Windows launcher doesn't have (not really enough space in the tiny launcher anyway) but which would look really cool in the Mac version. Go for it. :yes:

Remember, development is somewhat delaying because of my exams (and they last one month... grrr). Actually, I must admit I've never used the Windows Launcher. I initially made the Launcher long ago for personal use.

Quote
Besides, I really don't know many people here who actually know ObjC (besides you, of course)
So that's why no one noticed that the source for the latest version is missing from the CVS... ;)
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 17, 2008, 12:26:31 pm
So that's why no one noticed that the source for the latest version is missing from the CVS... ;)

The source is available?  Where?
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 18, 2008, 04:36:19 am
It was always available, only that it is not available in the CVS. I had a lot of problems with it, so I was always distributing the source in a .dmg in my server. I had made a promise to give the source to SCP developers, but I just couldn't do it the CVS way. Seems, however, no one saw my posts about the source... :)

The latest available source is here (http://soulstorm-creations.com/SOULSTORM_CUSTOM_FILES/FS2_Launcher_3_0_source_05022008.dmg). I have made a lot of changes since then, but it should give an idea of how things work. It is the OS X Launcher v.3.0.2.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 18, 2008, 12:33:21 pm
Thanks.  But that DMG is password protected.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 19, 2008, 11:21:40 am
damn. try "gimmethesource" (without the quotes). I am not sure if it's that.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 19, 2008, 04:02:27 pm
That seems to be the password, but the disk image still refuses to mount :(
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 20, 2008, 03:51:40 pm
Mod.ini support has been implemented. However, I didn't release it yet, since I haven't been able to test it on various machines yet. I didn't use the approach I mentioned previously. I think that what I have done now is more comprehensive and easy. I tested it on my machine with the Transcend mod. Seems to work just fine.

See the screenshot for details.

Download the latest beta here (http://www.soulstorm-creations.com/SOULSTORM_CUSTOM_FILES/FS2_Launcher_test.zip).

I am waiting for feedback on this one.

[attachment deleted by admin]
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 20, 2008, 03:54:49 pm
It won't even start for me.

BTW, what exactly is "dependencies"?  Is it updated based on mod.ini?
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 21, 2008, 01:52:03 am
Try it again. I reuploaded it.

I had failed to link the Launcher against some frameworks. Seems I must optimize my frameworks for other builds. I included the files that the application needs separately from the framework, and I got rid of it. I ran the application on an old G4 with 10.4, and it worked.

As far as dependencies goes... yes. The dependencies are the extra mods that are required in order for the mod to run properly.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 21, 2008, 08:36:12 am
It still crashes ... but it gets farther through the launch sequence than it did before :(
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 22, 2008, 11:05:20 am
OK. Let's see what's wrong. Delete the preferences of the application. This should be the file named "com.soulstorm.MMST2_3.plist" in your user preferences folder inside your library.

If that fails, please go to the console and post the results of your crash log. That should give me an idea of what's wrong. What exact system version are you using?

Does anyone else have the same problem?
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on May 22, 2008, 12:03:32 pm
Does anyone else have the same problem?

yes, after deleting the prefs it launches - but it writes new prefs and with the second launch -> crash
after deleting the prefs it launches again

Code: [Select]
Identifier:      com.soulstorm.MMST2_3
Version:         ??? (3.0.5b)
Code Type:       X86 (Native)
Parent Process:  launchd [70]

Date/Time:       2008-05-22 18:58:40.948 +0200
OS Version:      Mac OS X 10.5.2 (9C7010)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: aString != nil'

Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 23, 2008, 03:44:30 am
Damn. Seems I cannot reproduce this bug. I ran the application into 10.5.2 and 10.4.11 and it just works. I will try to spot the bug and fix it in the next few days. If anyone can help (blowfish, tinman, you think you are up to it if I give you the latest source?) tell me so, because it's very difficult to spot a bug I cannot even reproduce!
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 23, 2008, 12:05:20 pm
Seems other people (in other forums) don't have any problem with this file (http://www.soulstorm-creations.com/SOULSTORM_CUSTOM_FILES/FS2_Launcher_test_2.zip). Actually, they said everything was working fine. This is a slightly altered version. Can anyone verify this?

I have tested it into many machines (heck, I own 4!) and it runs on every one of them. Also, I saw you posted the crash log. That was helpful, but I think it would also be helpful if you posted the system log, after you have ran the application.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 23, 2008, 12:19:24 pm
It launches fine now, but the mod.ini code seems to be screwy.  When you select a mod with a mod.ini file, either the "Info..." button doesn't work, or it just crashes as soon as you select the mod.  Here is a portion of the crash log:

Code: [Select]
Process:         FS2_Launcher [6167]
Path:            /Applications/Freespace/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
Identifier:      com.soulstorm.MMST2_3
Version:         ??? (3.0.5b)
Code Type:       X86 (Native)
Parent Process:  launchd [102]

Date/Time:       2008-05-23 10:15:33.538 -0700
OS Version:      Mac OS X 10.5.2 (9C7010)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread:  0

Thread 0 Crashed:
0   libSystem.B.dylib              0x93527690 strlen + 16
1   AGRegex                        0x00900d20 -[AGRegex findInString:] + 88
2   com.soulstorm.MMST2_3          0x0000c932 -[ModIniParser imageFileLocation] + 66
3   com.soulstorm.MMST2_3          0x000078b1 -[GeneralHandler handleNonStandaloneMods:] + 335
4   com.apple.Foundation          0x96af2cdc _nsnote_callback + 364
5   com.apple.CoreFoundation      0x95db59da __CFXNotificationPost + 362
6   com.apple.CoreFoundation      0x95db5cb3 _CFXNotificationPostNotification + 179
7   com.apple.Foundation          0x96aeffd0 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
8   com.apple.Foundation          0x96af9668 -[NSNotificationCenter postNotificationName:object:] + 56
9   com.apple.AppKit              0x9158a205 -[NSComboBox(NSComboBoxCellNotifications) comboBoxCellSelectionDidChange:] + 74
10  com.apple.Foundation          0x96af2cdc _nsnote_callback + 364
11  com.apple.CoreFoundation      0x95db59da __CFXNotificationPost + 362
12  com.apple.CoreFoundation      0x95db5cb3 _CFXNotificationPostNotification + 179
13  com.apple.Foundation          0x96aeffd0 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
14  com.apple.Foundation          0x96af9668 -[NSNotificationCenter postNotificationName:object:] + 56
15  com.apple.AppKit              0x9158a1b3 -[NSComboBoxCell(NSTableViewNotifications) tableViewSelectionDidChange:] + 85
16  com.apple.Foundation          0x96af2cdc _nsnote_callback + 364
17  com.apple.CoreFoundation      0x95db59da __CFXNotificationPost + 362
18  com.apple.CoreFoundation      0x95db5cb3 _CFXNotificationPostNotification + 179
19  com.apple.Foundation          0x96aeffd0 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
20  com.apple.Foundation          0x96af9668 -[NSNotificationCenter postNotificationName:object:] + 56
21  com.apple.AppKit              0x913d3655 -[NSTableView _enableSelectionPostingAndPost] + 561
22  com.apple.AppKit              0x9140cad8 -[NSTableView mouseDown:] + 6867
23  com.apple.AppKit              0x913c3ac3 -[NSWindow sendEvent:] + 5381
24  com.apple.AppKit              0x91390714 -[NSApplication sendEvent:] + 2780
25  com.apple.AppKit              0x917074e1 -[NSComboBoxCell filterEvents:] + 2846
26  com.apple.AppKit              0x91704169 -[NSComboBoxCell popUp:] + 639
27  com.apple.AppKit              0x913c6e56 -[NSApplication sendAction:to:from:] + 112
28  com.apple.AppKit              0x913c6d94 -[NSControl sendAction:to:] + 108
29  com.apple.AppKit              0x913c6c1a -[NSCell _sendActionFrom:] + 169
30  com.apple.AppKit              0x913c5ec0 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 880
31  com.apple.AppKit              0x913c5ac6 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 541
32  com.apple.AppKit              0x91703a2e -[NSComboBoxCell trackMouse:inRect:ofView:untilMouseUp:] + 652
33  com.apple.AppKit              0x9170151a -[NSComboBox mouseDown:] + 456
34  com.apple.AppKit              0x913c3ac3 -[NSWindow sendEvent:] + 5381
35  com.apple.AppKit              0x91390714 -[NSApplication sendEvent:] + 2780
36  com.apple.AppKit              0x912ee0f9 -[NSApplication run] + 847
37  com.apple.AppKit              0x912bb30a NSApplicationMain + 574
38  com.soulstorm.MMST2_3          0x00002df2 _start + 216
39  com.soulstorm.MMST2_3          0x00002d19 start + 41

Also, it doesn't appear to be saving the build you select anymore.
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on May 24, 2008, 03:44:54 am
ok, the new one is working here...   :yes:

but:
 - it crashed the first time, when my "cmdline_fso.cfg" had the "-mod warzone,mediavps" in it (after deleting this, it worked)
 - the Launcher finds all the mods and I can choose one, but it does not find "Warzone" (the 3.03 also does not see it) I renamed it to "BWarzone" but the launcher does not find the directory  :confused:

Code: [Select]
24.05.08 09:28:38 FS2_Launcher[6608] /Applications/Spiele/Freespace2/FS2_Open_rev4622_0518.app
24.05.08 09:28:39 FS2_Launcher[6608] Making User Interface...
24.05.08 09:28:39 FS2_Launcher[6608] loading preferences from the command line...
24.05.08 09:28:39 FS2_Launcher[6608] -spec -glow -env -mipmap -nomotiondebris -missile_lighting -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 -tbp -no_vsync -cache_bitmaps -dualscanlines -targetinfo -orbradar -rearm_timer -ballistic_gauge -snd_preload -fps -window -mod FSport
24.05.08 09:28:39 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/FSport/mod.ini
24.05.08 09:28:39 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/FSport/mod.ini
24.05.08 09:28:39 FS2_Launcher[6608] mod folder located: /Applications/Spiele/Freespace2/FSport
24.05.08 09:28:39 FS2_Launcher[6608] mod folder located: /Applications/Spiele/Freespace2/mediavps
24.05.08 09:28:39 FS2_Launcher[6608] mod folder located: /Applications/Spiele/Freespace2/StormFront12
24.05.08 09:28:39 FS2_Launcher[6608] adsasdasdasFS2_Open
24.05.08 09:28:39 FS2_Launcher[6608] found mod folder: /Users/lang/Library/Beyond the Red Line
24.05.08 09:28:39 FS2_Launcher[6608] found mod folder: /Users/lang/Library/FS2_Open
24.05.08 09:28:39 FS2_Launcher[6608] found mod folder: /Users/lang/Library/WCS Prologue
24.05.08 09:28:39 FS2_Launcher[6608] 3
24.05.08 09:28:39 FS2_Launcher[6608] parsing file at: /Users/lang/Library/FS2_Open/fs2_open.ini for screen properties...
24.05.08 09:29:02 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/W/mod.ini
24.05.08 09:29:02 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/W/mod.ini
24.05.08 09:29:02 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/Wa/mod.ini
24.05.08 09:29:02 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/Wa/mod.ini
24.05.08 09:29:02 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/War/mod.ini
24.05.08 09:29:02 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/War/mod.ini
24.05.08 09:29:03 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/Warz/mod.ini
24.05.08 09:29:03 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/Warz/mod.ini
24.05.08 09:29:03 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/Warzo/mod.ini
24.05.08 09:29:03 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/Warzo/mod.ini
24.05.08 09:29:04 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/Warzon/mod.ini
24.05.08 09:29:04 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/Warzon/mod.ini
24.05.08 09:29:04 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/Warzone/mod.ini
24.05.08 09:29:04 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/Warzone/mod.ini
24.05.08 09:29:09 FS2_Launcher[6608] searching for mod.ini in: /Applications/Spiele/Freespace2/Warzone/mod.ini
24.05.08 09:29:09 FS2_Launcher[6608] trying to find mod.ini in: /Applications/Spiele/Freespace2/Warzone/mod.ini
24.05.08 09:29:16 FS2_Launcher[6608] entered, ambient_factor, ambient_factor
24.05.08 09:29:16 FS2_Launcher[6608] entered, spec_exp, spec_exp
24.05.08 09:29:16 FS2_Launcher[6608] entered, spec_point, spec_point
24.05.08 09:29:16 FS2_Launcher[6608] entered, spec_static, spec_static
24.05.08 09:29:16 FS2_Launcher[6608] entered, spec_tube, spec_tube
24.05.08 09:29:16 FS2_Launcher[6608] entered, ogl_spec, ogl_spec
24.05.08 09:29:16 FS2_Launcher[6608] entered, mod, mod
24.05.08 09:29:16 FS2_Launcher[6608] Preparing to save the current command line:
 -spec -glow -env -mipmap -nomotiondebris -missile_lighting -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 -tbp -no_vsync -cache_bitmaps -dualscanlines -targetinfo -orbradar -rearm_timer -ballistic_gauge -snd_preload -fps -window -mod Warzone
 to file in location: /Users/lang/Library/FS2_Open/data/cmdline_fso.cfg
24.05.08 09:29:16 FS2_Launcher[6608] Application Terminating...

Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on May 24, 2008, 08:01:52 am
Soulstorm, can you add a custom pref for "The Babylon Project"?

the folder is in "[home folder]/library/TheBabylonProject"

TNNX  :)

(for more info see my sig)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 26, 2008, 09:05:50 am
Tinman:

Quote from: Tinman
the Launcher finds all the mods and I can choose one, but it does not find "Warzone" (the 3.03 also does not see it) I renamed it to "BWarzone" but the launcher does not find the directory
The Launcher has some criteria when searching for folders that contain mods. The Launcher searches the FS2_Open application directory and it finds all directories in it. It only searches one level. It doesn't search subfolders. If those folders contain even one file which has the .vp suffix, then this folder is considered a folder that contains a mod.

Seems that Warzone has another directory structure. I will look at it. It would be helpful if you provided me with a link to download the mod.

Quote from: Tinman
Soulstorm, can you add a custom pref for "The Babylon Project"?
the folder is in "[home folder]/library/TheBabylonProject"
TNNX

Hm... I didn't fully understand the request. You mean if I should make the Launcher create a custom folder for this mod automatically? Or to set the Launcher use this folder when Babylon Project is selected? i 'm afraid that's not how things work. The way the Launcher is set up, in order to add an standalone mod, you need to firstly select the application, and then select its preference folder which obviously exists in the Library.

That is not automatically handled by the Launcher! The way it is now, you are prompted with a little dialog that asks you which is the appropriate folder for this application, and it shows some possible folders. Those are actually folders that contain preferences for any mod that is based on FS2_Open. But that means that in order for this folder to exist in the Library, you must have ran an least once the standalone mod!

So, in order to add a standalone mod:
- Run the mod once. That will create its own folder in the Library
- Open the Launcher. Add a mod, and, when asked, select the application for the mod, and its own preferences folder. You will not need to search the finder to do so. You will be shown every folder that contains preferences compatible with FS2_Open. select the folder named "TheBabylonProject" and there you are!

Why this is done?
It would be easy for me to just add some predefined mod Locations, but that would result in a lot of problems because some standalone mods may change the name of the preferences folder during a major update. Then, I should release an update, too. But I cannot keep track of every mod out there.

I wanted to make the Launcher as open as I could. That way, I would cover as many future standalone mods as possible without forcing the user to download an update each time something changes.
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on May 26, 2008, 12:43:59 pm
Tinman:

Quote from: Tinman
the Launcher finds all the mods and I can choose one, but it does not find "Warzone" (the 3.03 also does not see it) I renamed it to "BWarzone" but the launcher does not find the directory
The Launcher has some criteria when searching for folders [...] If those folders contain even one file which has the .vp suffix, then this folder is considered a folder that contains a mod.

Seems that Warzone has another directory structure. I will look at it. It would be helpful if you provided me with a link to download the mod.


Warzone  is a WIP, so not packed in a .VP file, but it contains a data folder with the necessary subfolders
now I know why some mods are not found by the launcher  :)

Quote from: Tinman
Tinman:
Soulstorm, can you add a custom pref for "The Babylon Project"?
the folder is in "[home folder]/library/TheBabylonProject"
TNNX

Hm... I didn't fully understand the request. You mean if I should make the Launcher create a custom folder for this mod automatically? Or to set the Launcher use this folder when Babylon Project is selected? i 'm afraid that's not how things work. The way the Launcher is set up, in order to add an standalone mod, you need to firstly select the application, and then select its preference folder which obviously exists in the Library.

[...]

oh my god, I'm such a nOOb   :mad:

you're right, it is a long time ago since I configured the launcher...
and in the custom standalone mods are "WCS","FS2_open" and "BtRl" available and I thought the wrong way how the launcher works

ok, then you can add the custom name "The Babylon Project"  :D
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 26, 2008, 01:24:08 pm
Warzone  is a WIP, so not packed in a .VP file, but it contains a data folder with the necessary subfolders
now I know why some mods are not found by the launcher  :)

Can you give me an example of those mods? I want to fix the Launcher in order to recognize them. And please, tell me where I can find Warzone! A google search came up with nothing!
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on May 26, 2008, 02:35:51 pm
Can you give me an example of those mods? I want to fix the Launcher in order to recognize them. And please, tell me where I can find Warzone! A google search came up with nothing!

here

http://www.hard-light.net/forums/index.php/topic,46147.msg1082022.html#msg1082022 (http://www.hard-light.net/forums/index.php/topic,46147.msg1082022.html#msg1082022)

Title: Re: FS2_Launcher OS X 3.0
Post by: neoterran on May 26, 2008, 04:49:45 pm
I think you really need to focus on the mods / loading mods / loading mods with other mods referenced in the .ini
aspect of the application. It's not set up so that it can work well atm.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 26, 2008, 11:13:04 pm
I think you really need to focus on the mods / loading mods / loading mods with other mods referenced in the .ini
aspect of the application. It's not set up so that it can work well atm.

Apart from the problem Tinman has, what would you like to see fixed?
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 26, 2008, 11:34:45 pm
New test build!

I added support for more mods (mods like Warzone are working now). Also, some problems with the mod loading have been rectified. Lastly, I was finally able to reproduce that bug you guys told me a few days ago. It should work fine now.

Get the latest beta here (http://www.soulstorm-creations.com/SOULSTORM_CUSTOM_FILES/FS2_Launcher_test3.zip).
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 26, 2008, 11:48:55 pm
Everything works now.  Except it crashes when I select JAD because of a weird character in the mod.ini file (i tested and this is the problem).
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 27, 2008, 05:31:02 am
I want that mod.ini file. Yes, with the weird character in it. I may be able to convert the encoding of the mod.ini on the fly and avoid the crash. Can you attach it?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 27, 2008, 08:39:20 am
OK.  I'll attach the file.  But now I'm getting preference-related crashes like before :mad: Which is odd because the new launcher worked fine for a little while.

[attachment deleted by admin]
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on May 27, 2008, 12:30:54 pm
please post your console log!
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on May 27, 2008, 12:52:28 pm
the new build works great  :yes:
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on May 30, 2008, 11:17:50 pm
please post your console log!

OK.  Relevant part of crash log:

Code: [Select]
Process:         FS2_Launcher [288]
Path:            /Applications/Freespace/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
Identifier:      com.soulstorm.MMST2_3
Version:         ??? (3.0.5b)
Code Type:       X86 (Native)
Parent Process:  launchd [129]

Date/Time:       2008-05-30 21:15:17.264 -0700
OS Version:      Mac OS X 10.5.3 (9D34)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Application Specific Information:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSCFString deleteCharactersInRange:]: Range or index out of bounds'

Thread 0 Crashed:
0   com.apple.CoreFoundation      0x9360eff4 ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ + 4
1   libobjc.A.dylib                0x9344c0fb objc_exception_throw + 40
2   com.apple.CoreFoundation      0x9360ef2b +[NSException raise:format:arguments:] + 155
3   com.apple.CoreFoundation      0x9360ef6a +[NSException raise:format:] + 58
4   com.apple.Foundation          0x912be052 mutateError + 322
5   com.soulstorm.MMST2_3          0x0000c89e -[ModIniParser secondaryListArgumentsAsString] + 207
6   com.soulstorm.MMST2_3          0x00007914 -[GeneralHandler handleNonStandaloneMods:] + 506
7   com.soulstorm.MMST2_3          0x00008e25 -[GeneralHandler showInfoForSelectedNonStandaloneMod:] + 161
8   com.soulstorm.MMST2_3          0x00006f5d -[GeneralHandler reloadAll] + 209
9   com.soulstorm.MMST2_3          0x00005bde -[GeneralHandler awakeFromNib] + 28
10  com.apple.CoreFoundation      0x9361d955 -[NSSet makeObjectsPerformSelector:] + 181
11  com.apple.AppKit              0x923dbbe6 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1533
12  com.apple.AppKit              0x923d1e12 loadNib + 264
13  com.apple.AppKit              0x923d1774 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 946
14  com.apple.AppKit              0x923d13b7 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 171
15  com.apple.AppKit              0x923d12f5 +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 391
16  com.apple.AppKit              0x923d0fa4 NSApplicationMain + 434
17  com.soulstorm.MMST2_3          0x00002d76 _start + 216
18  com.soulstorm.MMST2_3          0x00002c9d start + 41

and Console log:

Code: [Select]
5/30/08 9:15:15 PM FS2_Launcher[288] 1
5/30/08 9:15:15 PM FS2_Launcher[288] parsing file at: /Users/joeydwong/Library/FS2_Open/fs2_open.ini for screen properties...
5/30/08 9:15:15 PM FS2_Launcher[288] found mod folder: /Users/joeydwong/Library/Beyond the Red Line
5/30/08 9:15:15 PM FS2_Launcher[288] found mod folder: /Users/joeydwong/Library/FS2_Open
5/30/08 9:15:15 PM FS2_Launcher[288] found mod folder: /Users/joeydwong/Library/WCS Prologue
5/30/08 9:15:15 PM FS2_Launcher[288] 3
5/30/08 9:15:15 PM FS2_Launcher[288] /Applications/Freespace/Freespace/FS2_Open-latest.app
5/30/08 9:15:17 PM FS2_Launcher[288] Making User Interface...
5/30/08 9:15:17 PM FS2_Launcher[288] loading preferences from the command line...
5/30/08 9:15:17 PM FS2_Launcher[288] -spec -glow -env -mipmap -missile_lighting -ambient_factor 0.75 -spec_exp 11 -spec_static 0.8 -ogl_spec 60 -ship_choice_3d -3dwarp -fov 0.25 -rearm_timer -mod blueplanet
5/30/08 9:15:17 PM FS2_Launcher[288] searching for mod.ini in: /Applications/Freespace/Freespace/blueplanet/mod.ini
5/30/08 9:15:17 PM FS2_Launcher[288] trying to find mod.ini in: /Applications/Freespace/Freespace/blueplanet/mod.ini
5/30/08 9:15:17 PM FS2_Launcher[288] image file for current mod found: bplogo.bmp
5/30/08 9:15:17 PM FS2_Launcher[288] An uncaught exception was raised
 
5/30/08 9:15:17 PM FS2_Launcher[288] *** -[NSCFString deleteCharactersInRange:]: Range or index out of bounds
5/30/08 9:15:17 PM FS2_Launcher[288] *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSCFString deleteCharactersInRange:]: Range or index out of bounds'
5/30/08 9:15:17 PM FS2_Launcher[288] Stack: (
    2472603979,
    2470756603,
    2472603435,
    2472603498,
    2435571794,
    51358,
    30996,
    36389,
    28509,
    23518,
    2472663381,
    2453519334,
    2453478930,
    2453477236,
    2453476279,
    2453476085,
    2453475236,
    11638,
    11421
)
5/30/08 9:15:25 PM com.apple.launchd[129] ([0x0-0x28028].com.soulstorm.MMST2_3[288]) Exited abnormally: Trace/BPT trap
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on June 01, 2008, 04:55:49 pm
Again, I downloaded the BluePlanet mod but I cannot reproduce this bug. Have you tried deleting the Launcher preferences?

I will get involved with it in the next days. I am extremely ill at the moment, and my headache makes it hard for me to even stare at the computer screen.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on June 01, 2008, 05:34:42 pm
It seems to be fixed now.  Dunno what was up...
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on June 02, 2008, 12:47:49 am
Please post back if you have problems later. If I figure out what triggers the crash, I may be able to avoid future errors, even if they are user-related.
Title: Re: FS2_Launcher OS X 3.0
Post by: 134th Barracudas on July 06, 2008, 12:46:08 pm
Last build crashes when launched... Here's the log
My config:
Code: [Select]
Model: PowerMac10,1, BootROM 4.8.9f4, 1 processor, PowerPC G4  (1.2), 1.42 GHz, 512 MB
Graphics: kHW_ATIrv280Item, ATY,RV280, spdisplays_agp_device, 32 MB
Memory Module: DIMM0/J11, 512 MB, DDR SDRAM, PC3200U-30330
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x4E), Broadcom BCM43xx 1.0 (4.170.25.8)
Bluetooth: Version 2.1.0f17, 2 service, 1 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Parallel ATA Device: ST9808210A, 74,53 GB
Parallel ATA Device: MAT****ACD-RW  CW-8124, 352,9 MB
USB Device: LaCie Desktop Hard Drive, LaCie, high_speed, 500 mA
USB Device: Hub in Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 500 mA
USB Device: Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 250 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA

Crash Log:
Code: [Select]
Process:         FS2_Launcher [1088]
Path:            /Volumes/Backup di Time Machine/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
Identifier:      com.soulstorm.MMST2_3
Version:         ??? (3.0.5b)
Code Type:       PPC (Native)
Parent Process:  launchd [83]

Date/Time:       2008-07-06 19:29:13.699 +0200
OS Version:      Mac OS X 10.5.4 (9E17)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000095d78d94
Crashed Thread:  0

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFString setString:]: nil argument'

Thread 0 Crashed:
0   com.apple.CoreFoundation      0x95d78d94 ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ + 0
1   libobjc.A.dylib                0x96d1c768 objc_exception_throw + 68
2   com.apple.CoreFoundation      0x95d78cf8 +[NSException raise:format:arguments:] + 136
3   com.apple.CoreFoundation      0x95d78d30 +[NSException raise:format:] + 52
4   com.apple.Foundation          0x9611cbec mutateError + 184
5   com.soulstorm.MMST2_3          0x00004f34 identifyExe(NSString*) + 452
6   com.soulstorm.MMST2_3          0x00006c20 -[GeneralHandler getFlagFile] + 64
7   com.soulstorm.MMST2_3          0x00007828 -[GeneralHandler reloadAll] + 144
8   com.soulstorm.MMST2_3          0x000066cc -[GeneralHandler awakeFromNib] + 56
9   com.apple.CoreFoundation      0x95d869f0 -[NSSet makeObjectsPerformSelector:] + 200
10  com.apple.AppKit              0x954587f8 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1264
11  com.apple.AppKit              0x9544fdfc loadNib + 224
12  com.apple.AppKit              0x9544f7a0 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 840
13  com.apple.AppKit              0x9544f37c +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 336
14  com.apple.AppKit              0x9544f064 NSApplicationMain + 332
15  com.soulstorm.MMST2_3          0x00002c24 _start + 756
16  com.soulstorm.MMST2_3          0x00002928 start + 44
17  ???                            0xbffffad8 0 + 3221224152

Thread 0 crashed with PPC Thread State 32:
  srr0: 0x95d78d94  srr1: 0x0202f030   dar: 0xe0024000 dsisr: 0x42000000
    r0: 0x96d1c76c    r1: 0xbffff200    r2: 0xa0ab95f8    r3: 0x00065000
    r4: 0x001fc080    r5: 0x001fc080    r6: 0x00000000    r7: 0x001fe005
    r8: 0x000011dc    r9: 0x0008ea40   r10: 0x001fe005   r11: 0x24044442
   r12: 0x914fbf70   r13: 0x00114920   r14: 0x00000000   r15: 0xa0a1251c
   r16: 0xa09e8308   r17: 0x001501f0   r18: 0xa09e8308   r19: 0x001623c0
   r20: 0xa09e8308   r21: 0xbffff64c   r22: 0x00010000   r23: 0xa0b4cb40
   r24: 0xa0b5cb40   r25: 0xa0b5cb40   r26: 0x96dcd6e4   r27: 0xa0ace95c
   r28: 0xa0acc460   r29: 0x0018e710   r30: 0xa0cdadc0   r31: 0x96d1c734
    cr: 0x24044442   xer: 0x00000004    lr: 0x96d1c76c   ctr: 0x914fbf70
vrsave: 0x00000000

Binary Images:
    0x1000 -    0x12fff +com.soulstorm.MMST2_3 ??? (3.0.5b) <afffd6398b0373d535c1d14557b2b414> /Volumes/Backup di Time Machine/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
   0x22000 -    0x2ffe7 +org.andymatuschak.Sparkle ??? (1.1) /Volumes/Backup di Time Machine/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
   0x3b000 -    0x5cff1  libmx.A.dylib ??? (???) /usr/lib/libmx.A.dylib
  0x900000 -   0x910fff +AGRegex ??? (0.1) /Volumes/Backup di Time Machine/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/Frameworks/AGRegex.framework/Versions/A/AGRegex
  0xb1b000 -   0xc14ff3  com.apple.RawCamera.bundle 2.0.7 (2.0.7) /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x8fe00000 - 0x8fe30b23  dyld 96.2 (???) <ef2061020a88c4fe1f40b8d9cb1a6101> /usr/lib/dyld
0x903d3000 - 0x903d3ffa  com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x903fe000 - 0x90437fff  com.apple.SystemConfiguration 1.9.2 (1.9.2) <1a39075165bf7447fe8be1e93db49346> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x904a1000 - 0x90a18fff  com.apple.CoreGraphics 1.351.31 (???) <1d6f8c59da420b7b6105cf0f0dcc8f8e> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x90a22000 - 0x90ad2fff  edu.mit.Kerberos 6.0.12 (6.0.12) <5cf1a9c1d7e526bb9b084013a1722d08> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x90b3e000 - 0x90bd2ff7  com.apple.framework.IOKit 1.5.1 (???) <c1d6fa5eb7372b90ca4fea8910170152> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90bd3000 - 0x90bdefff  com.apple.speech.recognition.framework 3.7.24 (3.7.24) <ae3dc890a43a9269388301f6b59d3091> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x90bdf000 - 0x90c14fff  com.apple.AE 402.2 (402.2) <0b15a08da8ec38b74fb9dd6e579ed25f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x90c15000 - 0x90c16ff8  com.apple.ApplicationServices 34 (34) <6aa5ee485bb2e656531b3505932b845f> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x90c17000 - 0x90c92fff  com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x90c93000 - 0x90ca0fff  libCSync.A.dylib ??? (???) <c42bb98d8afc1f2f8ff764d6553dd670> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x90ca1000 - 0x90cb9ffb  com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x90cba000 - 0x90cc2fff  libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x90cc3000 - 0x910f8ffa  libGLProgrammability.dylib ??? (???) <f032e07d587794af4d4ba1b7dc7b4fd2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x91109000 - 0x91109fff  com.apple.Accelerate 1.4.2 (Accelerate 1.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x9110a000 - 0x91129fff  com.apple.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x9112a000 - 0x91136ff3  com.apple.audio.SoundManager 3.9.2 (3.9.2) <79588842bcaf6c747a95b2120304397a> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x91137000 - 0x911bbffd  com.apple.CFNetwork 330.4 (330.4) <6e1a01b50c14cf720e067ea018c4e4ad> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x911c3000 - 0x911deffb  libPng.dylib ??? (???) <a0a5ce98fa9fe98fe190c99a3dbbdfa0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x911df000 - 0x91279ffb  com.apple.ApplicationServices.ATS 3.3 (???) <5c97f539ba68e1143929cd89db390d20> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x9127a000 - 0x91283fff  com.apple.DiskArbitration 2.2.1 (2.2.1) <a389b4c2badce39540f24402f7df35e7> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x91425000 - 0x914f4fff  com.apple.ColorSync 4.5.0 (4.5.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x914f5000 - 0x9168efe3  libSystem.B.dylib ??? (???) <79cf3ef34f92361dc6263d884c723c24> /usr/lib/libSystem.B.dylib
0x9168f000 - 0x919edff2  com.apple.QuartzCore 1.5.3 (1.5.3) <c410b1f89e67d41c3d06eac1790b500c> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x919ee000 - 0x919f0ffd  libRadiance.dylib ??? (???) <3d70fcb7557347829c96c9753074b3f1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x919f1000 - 0x91a1cff7  libauto.dylib ??? (???) <b3a3a4b0f09653bd6d58f1847922b533> /usr/lib/libauto.dylib
0x91a1d000 - 0x91ae2ffb  com.apple.CoreData 100.1 (186) <9cf54cb19b18e53ee22edb7ababa6e6c> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x91d61000 - 0x9208afe7  libLAPACK.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x92105000 - 0x92113fff  libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x92114000 - 0x9215fffb  com.apple.Metadata 10.5.2 (398.18) <0899c93992af8d2e36e4dd2ad21ba475> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x92166000 - 0x92284ff7  com.apple.audio.toolbox.AudioToolbox 1.5.1 (1.5.1) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x92285000 - 0x922a4fff  libresolv.9.dylib ??? (???) <ea4013600c24f794dff0013de3db4bf4> /usr/lib/libresolv.9.dylib
0x922a5000 - 0x925a6ffb  com.apple.CoreServices.CarbonCore 786.4 (786.4) <07a9bff6abb5dabf362dd2f14d016d36> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x925a7000 - 0x925a7ffb  com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallServer
0x925a8000 - 0x9266afff  com.apple.WebKit 5525.18 (5525.18) <465f23fde0c38d87fd0e0103a3393772> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x9266b000 - 0x9268bff7  libJPEG.dylib ??? (???) <92341083256fbcd28888a179ebf941ef> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x926f2000 - 0x9270bffb  com.apple.CoreVideo 1.5.1 (1.5.1) <9b726d9ba75efbaccaed1d34e2f71ea0> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x9270c000 - 0x92dedff3  com.apple.WebCore 5525.18.1 (5525.18.1) <c339884f32c81b029105d8a0243db0ff> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
0x92ebd000 - 0x92f3efff  com.apple.print.framework.PrintCore 5.5.3 (245.3) <032f772f8169945c1d1b524d96edcef6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x92f45000 - 0x92f58fff  com.apple.LangAnalysis 1.6.4 (1.6.4) <f12db38b92cbf96b024206698434d14d> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x92f60000 - 0x92f60fff  com.apple.Carbon 136 (136) <6a6a209ec9179368db7ead8382b8ee63> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92f61000 - 0x9301bfff  libcrypto.0.9.7.dylib ??? (???) <4ea3d7e9a1c28ac7b17ed80873fe6598> /usr/lib/libcrypto.0.9.7.dylib
0x9301c000 - 0x9301dfff  libffi.dylib ??? (???) <11b77dbce4aa0f0b66d40014230abd1d> /usr/lib/libffi.dylib
0x93e98000 - 0x93effffb  libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0x93f0b000 - 0x93f26ffb  com.apple.openscripting 1.2.6 (???) <12270fbb14905644f78975f227328a98> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x93f27000 - 0x93faeffb  com.apple.audio.CoreAudio 3.1.0 (3.1) <880a5a35ef1c5158271ee4b305b35626> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x93faf000 - 0x940c3ffa  com.apple.vImage 3.0 (3.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x940c4000 - 0x941abfff  com.apple.JavaScriptCore 5525.18 (5525.18) <d94ee2a4a7aa244335a4a2a49a5aaeec> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x941ee000 - 0x94215fff  libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
0x94216000 - 0x9422dffb  com.apple.ImageCapture 4.0 (5.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x942c6000 - 0x9435ffc3  libvDSP.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x944cd000 - 0x94523fff  libGLU.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x94524000 - 0x94524fff  com.apple.audio.units.AudioUnit 1.5 (1.5) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x94533000 - 0x94582ff7  libGLImage.dylib ??? (???) <dba44404ea3684df4f23df5e8e5430c3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x94597000 - 0x9459effb  com.apple.print.framework.Print 218.0.2 (220.1) <c7e0e618d5867ae227403ae385aacd82> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x945ea000 - 0x9469afff  com.apple.QD 3.11.52 (???) <f33191c288897dd4d2e2c4b87bcc09b4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x947b6000 - 0x947beffb  libCGATS.A.dylib ??? (???) <f08869e380cd4b55e14714fe723cbc66> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x947bf000 - 0x94806fff  com.apple.NavigationServices 3.5.2 (163) <cb063c95a55ba12994a64c7e47f5706a> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x94807000 - 0x948dafff  com.apple.CoreServices.OSServices 226.5 (226.5) <50a4f7fe2d6078971f9ef6fc88cc5d2b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x948db000 - 0x948e6ffb  libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x948e7000 - 0x9490dfff  libcups.2.dylib ??? (???) <faed280b72f625b591ae0506cb142367> /usr/lib/libcups.2.dylib
0x94951000 - 0x949b1fff  com.apple.CoreText 2.0.2 (???) <e5940fddbca517f29b8865c9b02ddff0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x94b4b000 - 0x94be1fff  com.apple.LaunchServices 289.2 (289.2) <67191ba4de2d3d14be9b4bbddd4fe0a6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x94be2000 - 0x94be2ff8  com.apple.Cocoa 6.5 (???) <e9a4f1c636d00893db0494c4040176ba> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x94c2d000 - 0x94c30ffb  com.apple.securityhi 3.0 (30817) <e50c0cac9048f8923b95797753d50b5c> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x94c7f000 - 0x95239fff  libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x95386000 - 0x953a5fff  com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x953a6000 - 0x953abff6  libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x953ac000 - 0x95431fff  libsqlite3.0.dylib ??? (???) <f2a33fe2663eab9c7f4806d2cf05b4ee> /usr/lib/libsqlite3.0.dylib
0x95449000 - 0x95bbefff  com.apple.AppKit 6.5.3 (949.33) <1144a07dd55895f89e44adf80cc151d9> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x95c3f000 - 0x95ca1ffb  com.apple.htmlrendering 68 (1.1.3) <e852db1c007de975fae2f0c2769c88ef> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x95ca2000 - 0x95dc7ffb  com.apple.CoreFoundation 6.5.3 (476.14) <56add4656a227fa699f8aa1427b369d9> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x95dc8000 - 0x95dd5ffb  com.apple.opengl 1.5.6 (1.5.6) <9f2c6a226837dae46ced8b28e195210c> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x95e1d000 - 0x95f06fff  libxml2.2.dylib ??? (???) <6bf1a24e68615e0edf843988f5a0a1f4> /usr/lib/libxml2.2.dylib
0x95f07000 - 0x95f1affb  com.apple.speech.synthesis.framework 3.7.1 (3.7.1) <dc8dac074f4d19175c5613b35aa529b3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x95f1b000 - 0x95f77ffb  com.apple.HIServices 1.7.0 (???) <48d200891cc9dd795ee547d526c6a45b> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x95f78000 - 0x95fb9ffb  libTIFF.dylib ??? (???) <0d0a3107d26786c3708e6a511d5acec9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x95fba000 - 0x96042fff  com.apple.ink.framework 101.3 (86) <66a99ad6bc695390a66dd24789e23dcc> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x96043000 - 0x96288ffb  com.apple.Foundation 6.5.5 (677.19) <1667218c075b6e69728c5c2dd9ff6065> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x96289000 - 0x9628cfff  com.apple.help 1.1 (36) <7106d6e074a3b9835ebf1e6cc6c822ce> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x9628d000 - 0x963d5ffb  libicucore.A.dylib ??? (???) <dd2fd169aa328f6e97a1d700e5846866> /usr/lib/libicucore.A.dylib
0x96405000 - 0x965ebffb  com.apple.security 5.0.4 (34102) <9a5739b5b522f963b320fd71581b9cf5> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x965ec000 - 0x9661dfff  com.apple.coreui 1.1 (61) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x9661e000 - 0x96768ffb  com.apple.ImageIO.framework 2.0.2 (2.0.2) <20c50c4b4d09a4cf69fb8732e3d79081> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x96769000 - 0x96aa2feb  com.apple.HIToolbox 1.5.3 (???) <1f08f0263f6037c253e6cfbe69cfc5a0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x96ae1000 - 0x96ae8fff  com.apple.CommonPanels 1.2.4 (85) <0d1256175c5512c911ede094d767acfe> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x96afa000 - 0x96b89ffb  com.apple.DesktopServices 1.4.6 (1.4.6) <3b1ac6c5643f1858e86ec52554c4b408> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x96c35000 - 0x96c59ffb  libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x96c5a000 - 0x96ce4fff  libvMisc.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x96d12000 - 0x96df5feb  libobjc.A.dylib ??? (???) <23a407d7dac6090562827e97bac3cb86> /usr/lib/libobjc.A.dylib
0x96eed000 - 0x96ef1ffe  libGIF.dylib ??? (???) <d6e2a570359313a39c6783c2ecfee608> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0xfffec000 - 0xfffeffff  libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703  libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib


Title: Re: FS2_Launcher OS X 3.0
Post by: Admiral LSD on July 09, 2008, 01:40:40 pm
Would it be possible to rig it so it remembers the last directory it was in when you select a new build? I was messing around with several different builds the other day (more on that later) and it became extremely annoying having to navigate out of my home dir into where I keep my FS2 data.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on July 25, 2008, 08:12:48 am
First page link redirects to an error. Please fix it.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on August 07, 2008, 04:46:47 pm
Sorry I couldn't post back earlier... I was on vacation. I am back now, and starting developing on .NET (yay!).

Quote
Would it be possible to rig it so it remembers the last directory it was in when you select a new build?

Yes it is. I will do it in the next two or three days.

Quote
First page link redirects to an error. Please fix it.

What "first page"? My website is http://www.soulstorm-creations.com/ .
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on August 07, 2008, 07:43:27 pm
He's probably talking about the link in the very first post, which currently goes to an error stating that "you are not allowed to access this section".
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on August 07, 2008, 10:37:04 pm
He's probably talking about the link in the very first post, which currently goes to an error stating that "you are not allowed to access this section".

Yes, that.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on August 08, 2008, 02:16:44 pm
done ;)
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on August 08, 2008, 02:23:47 pm
Much better.  Also, I'm confused by this question:

Quote
Does it work with the original FS2_Open as the old one (or better)?

What does that mean?  I'm assuming you mean as well as the older launcher, probably your older version?  But what do you mean original FS2_open?
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on August 12, 2008, 10:23:42 am
The Launcher is designed to work with any build from 3.6.9 and up. It will probably work with 3.6.7 also, but I haven't tested it yet.

PS. A new update is released.
Title: Re: FS2_Launcher OS X 3.0
Post by: neoterran on September 26, 2008, 09:40:52 am
we need antialiasing support
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on September 26, 2008, 11:37:52 am
Isn't that configurable in the driver control panel itself?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on September 26, 2008, 06:18:39 pm
we need antialiasing support

Antialiasing really has nothing to do with the launcher.  The Windows launcher just has it there as a placeholder since the engine doesn't have antialiasing implemented.

Isn't that configurable in the driver control panel itself?

There is no graphics driver control panel on Mac OS X.

Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on September 27, 2008, 03:20:54 am
What you get on the OS X Launcher is basically this:

- A drop-down box to select a folder;
- Checkboxes to select and de-select features in FS2_Open;
- A drawer showing all standard command-line parameters, separated into the usual categories (gameplay, music, multi, etc.);
- A field to enter the filepath to FS2_Open.app;
- Three fields to set the screen width, height and colour depth, in that order.

As OpenAL is not a Mac program, there is no option to enable voices, even though Mac has its own VoiceOver Utility. In addition, since all Macs are more or less configured to the same specifications and only differ in terms of processor, RAM and graphics card, there are no hardware or software options to change.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on September 29, 2008, 10:02:29 am
Isn't that configurable in the driver control panel itself?

There is no graphics driver control panel on Mac OS X.

I'm pretty sure that when I installed the Ati drivers on my G3 for the Radeon 7000, it added a new menu option to the system preferences.  I thought that Ati Driver Utility or whatever it is would have those types of options.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on October 03, 2008, 02:58:31 am
Quote
we need antialiasing support
If the game implements it, I will, too.

Anti aliasing from the drivers is specific to the ATI cards, and is provided by ATI. I don't know if they still support it. If they do you can use that.

I hate .NET.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on October 03, 2008, 08:32:40 am
Didn't they move away from .NET in the Catalyst suite? (Edit:  I guess not).  Also, I think you can get the NGO or Omega drivers with the original control panel, or at least Ati Tray Tools.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on October 11, 2008, 01:27:19 pm
I was talking about OS X. My comment about .NET was irrelevant to the thread, I just wanted to share my anger with .NET :)
Title: Re: FS2_Launcher OS X 3.0
Post by: nuone on November 17, 2008, 08:22:47 am
I have just downloaded and installed the 3.0.8 Launcher. When I launch app I get a warning saying that "Unrecognized command line parameter, "-", continue?"

I also get that the flags are not found.

Some help would be very much appreciated.
Title: Re: FS2_Launcher OS X 3.0
Post by: Jeff Vader on November 17, 2008, 08:34:51 am
If the screenshot on Soulstorm's site is accurate, there should be a list of command-line flags on the right side of the Launcher. Remove the one that says "-" and any that seem to cause errors.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on November 22, 2008, 03:50:46 am
I have just downloaded and installed the 3.0.8 Launcher. When I launch app I get a warning saying that "Unrecognized command line parameter, "-", continue?"

I also get that the flags are not found.

Some help would be very much appreciated.

The message about the flags that are not found means that the FS2_Open application you have chosen cannot produce a necessary file for the Launcher to read the flags for this version. I imagine that the main drawer is nearly empty (it doesn't show any options)?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on November 22, 2008, 02:00:34 pm
Hey Soulstorm - a bug I found with the mod.ini parser: It does not seem to interpret characters like underscores and slashes correctly.  So if you had a mod.ini that had something like inferno_r1 that would come out as inferno,r1.  Commas should be the only separating character.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on November 25, 2008, 08:18:25 am
Hm... strange. I hadn't had any problems with it. I will check it out. Could you be kind enough to upload a mod.ini file that has problems so that I better know what am I dealing with?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on November 25, 2008, 10:01:41 am
Sure

Code: [Select]
[launcher]
image255x112 = FSU-MVP.bmp;
infotext     = Freespace II - SVN MediaVPs;
website      = http://www.hard-light.net/;
forum        = http://www.hard-light.net/forums;

[multimod]
primarylist  = ;
secondrylist = FSU/MV_Advanced,FSU/MV_Assets,FSU/MV_Effects,FSU/MV_Core;

This mod.ini was for testing the new mediavps.  The game works with the subfolders just fine, but the launcher doesn't seem to recognize the slashes or underscores.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on November 25, 2008, 10:03:40 am
Just out of curiosity, did you try the slashes the other way?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on November 25, 2008, 10:06:51 am
Just out of curiosity, did you try the slashes the other way?

I changed the slashes to forward slashes, since OSX uses forward slashes rather than backslashes.  I know it works with the engine because I modified cmdline_fso.cfg directly.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on November 25, 2008, 12:41:18 pm
I think that the bug is fixed in 3.0.10. Try it and please post back to tell me if that is the case...
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on November 25, 2008, 02:25:26 pm
By the way, that whole 'Unrecognized command line parameter, "-", continue?' bug.  It happens to me too, and I can't find a '-' option to get rid of to make it stop.  Just thought I'd throw that out there.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on November 25, 2008, 06:47:44 pm
I think that the bug is fixed in 3.0.10. Try it and please post back to tell me if that is the case...

It's fix0red now, thanks :)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on November 30, 2008, 05:18:19 am
By the way, that whole 'Unrecognized command line parameter, "-", continue?' bug.  It happens to me too, and I can't find a '-' option to get rid of to make it stop.  Just thought I'd throw that out there.

I intend to fix that. it's just a minor problem, don't worry. Although you may not found that '-' in the options, you can find it in the command line drawer. It's the box with no letters in it. Just search for an option that has no letters in it (sometimes it's the first or the last, that's why you may miss it) and delete that option. Then save the file.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on November 30, 2008, 11:21:19 am
I did glance in the drawer for it, but yeah I might have missed it anyway.  I'll doublecheck again.  Where's the configuration file saved to by default?  (that may be a really stupid question but I'm not a heavy Mac user or anything)
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on November 30, 2008, 06:52:27 pm
I did glance in the drawer for it, but yeah I might have missed it anyway.  I'll doublecheck again.  Where's the configuration file saved to by default?  (that may be a really stupid question but I'm not a heavy Mac user or anything)

Eh, don't worry. I had problems finding it the first time too. ;)

All the configuration files should be at Macintosh HD -> Users -> [your user name] -> Library -> FS2_Open
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 06, 2008, 04:06:56 pm
Where is the Launcher's own config saved?  It fired up once for me, updated to 3.0.10, that fired up ok, I saved some settings, and then when I tried to run it again to see if everything had saved ok, it no longer runs.  I deleted the FS2_Open config directory, and tried to reinstall it, but even the 3.0.7 version doesn't work now, so something was left behind it seems, or something else was changed on the system outside of itself.  It seems to be having trouble running FS2 from the location I told it to find it.  FS2 is being run, but the launcher crashes shortly after running it.
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on December 07, 2008, 04:33:36 am
deleting the plist-files in [your user name] -> Library -> Preferences -> com.soulstorm.fs2_* may help
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on December 07, 2008, 09:10:00 am
In order to delete the preferences, delete the file named "com.soulstorm.MMST2_3.plist" in your user preferences folder in your Library.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 07, 2008, 12:18:06 pm
Yeah, ok so I don't know what the problem is.  As soon as I point the launcher to the 3.6.9 exe, it doesn't actually load the valid arguments at that point.  So I close the program, and when I reopen it, it crashes.  The config file looks ok when I open it in the Property List Editor.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on December 09, 2008, 03:09:34 am
What system version do you have? The version of the Launcher is 3.0.10? Do you remember what settings have you used? Please post your command line configuration (can be seen in ~/Library/FS2_Open.ini and ~/Library/data/cmdline_fso.cfg).

That sounds as a problem with some preferences, that's why I am asking you to post the contents of those files.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 09, 2008, 02:43:52 pm
I've deleted all the configs and started over.  Both the freespace configs and the launcher configs, and it still crashes.  I have a 10.5.5 up to date Leopard install.  I was using 3.6.9 builds of Freespace and your 3.0.10 version.  So I'm relatively sure it's not the preferences since I keep deleting them.  Mine are actually in ~/Library/FS2_Open, I'm guessing you goofed and left that out unless there's something wrong with that.  I put the Freespace data in /Applications/Freespace2/, and I also put the binaries inside that folder.  I have tried deleting both the ~/Library/FS2_Open folder, and the launcher config you pointed out previously, and it still crashes on the second load.  On the first load, after I tell it where my 3.6.9 binary is, it does not update itself at that point with the available command line options and most of the tabs are empty.  I hit save anyway, close it, and restart and it crashes.  I never see the Freespace icon load in the dock, but I do end up with a new FS2_Open folder with config files in the Library folder again.  Just so you can see what it's crashing with though, here's the files it creates (I changed the res to 1024 so I could run FS directly, it crashed with it unchanged as well.  Also added -window to the command line file and got rid of the lone '-' it starts with).

~/Library/FS2_Open/fs2_open.ini
Code: [Select]
[Default]
VideocardFs2open=OGL -(1024x768)x32 bit

~/Library/FS2_Open/data/cmdline_fso.cfg
Code: [Select]
-window

The ini has a trailing newline but the cmdline file does not.  I also selected the FS2 app and then closed without hitting save, not sure what changes when I hit save but it still crashed the same.

For giggles, here's the crash report:

Code: [Select]
Process:         FS2_Launcher [40425]
Path:            /Applications/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
Identifier:      com.soulstorm.MMST2_3
Version:         ??? (3.0.10)
Code Type:       PPC (Native)
Parent Process:  launchd [117]

Date/Time:       2008-12-09 14:36:36.422 -0600
OS Version:      Mac OS X 10.5.5 (9F33)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000096837d94
Crashed Thread:  0

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFString setString:]: nil argument'

Thread 0 Crashed:
0   com.apple.CoreFoundation      0x96837d94 ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ + 0
1   libobjc.A.dylib                0x969e04e8 objc_exception_throw + 68
2   com.apple.CoreFoundation      0x96837cf8 +[NSException raise:format:arguments:] + 136
3   com.apple.CoreFoundation      0x96837d30 +[NSException raise:format:] + 52
4   com.apple.Foundation          0x93de5a64 mutateError + 184
5   com.soulstorm.MMST2_3          0x00004dfc identifyExe(NSString*) + 452
6   com.soulstorm.MMST2_3          0x00006bd4 -[GeneralHandler getFlagFile] + 64
7   com.soulstorm.MMST2_3          0x000077dc -[GeneralHandler reloadAll] + 144
8   com.soulstorm.MMST2_3          0x0000661c -[GeneralHandler awakeFromNib] + 56
9   com.apple.CoreFoundation      0x968459f0 -[NSSet makeObjectsPerformSelector:] + 200
10  com.apple.AppKit              0x921075b8 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1264
11  com.apple.AppKit              0x920febbc loadNib + 224
12  com.apple.AppKit              0x920fe560 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 840
13  com.apple.AppKit              0x920fe13c +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 336
14  com.apple.AppKit              0x920fde24 NSApplicationMain + 332
15  com.soulstorm.MMST2_3          0x00002aec _start + 756
16  com.soulstorm.MMST2_3          0x000027f0 start + 44

Thread 0 crashed with PPC Thread State 32:
  srr0: 0x96837d94  srr1: 0x0202f030   dar: 0xe0024000 dsisr: 0x42000000
    r0: 0x969e04ec    r1: 0xbffff360    r2: 0xa0a885f8    r3: 0x00065000
    r4: 0x005fc080    r5: 0x005fc080    r6: 0x00000006    r7: 0x005fe005
    r8: 0x00000f66    r9: 0x0007af30   r10: 0x005fe005   r11: 0x24044442
   r12: 0x96ae4f70   r13: 0x00512700   r14: 0x00000000   r15: 0xa03e1514
   r16: 0xa03b70c8   r17: 0x0055c880   r18: 0xa03b70c8   r19: 0x005642e0
   r20: 0xa03b70c8   r21: 0xbffff7ac   r22: 0x00010000   r23: 0xa06459b8
   r24: 0xa06559b8   r25: 0xa06559b8   r26: 0x96a916a4   r27: 0xa0a9d95c
   r28: 0xa0a9b460   r29: 0x0057a8e0   r30: 0xa0b1edc0   r31: 0x969e04b4
    cr: 0x24044442   xer: 0x00000004    lr: 0x969e04ec   ctr: 0x96ae4f70
vrsave: 0x00000000

Binary Images:
    0x1000 -    0x12fff +com.soulstorm.MMST2_3 ??? (3.0.10) <465ce2d97761bca9102326ff7d1c5912> /Applications/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
   0x22000 -    0x2ffe7 +org.andymatuschak.Sparkle ??? (1.1) /Applications/FS2_Launcher.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
   0x3b000 -    0x5cff1  libmx.A.dylib ??? (???) /usr/lib/libmx.A.dylib
  0x114000 -   0x1fdfff  libxml2.2.dylib ??? (???) <dedfda117e78db04f0b86c59923b3794> /usr/lib/libxml2.2.dylib
  0x228000 -   0x2eafff  com.apple.WebKit 5525.27 (5525.27.1) <7de8ed23795391f9d81127e9b639a3c3> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
  0x387000 -   0x46ffff  com.apple.JavaScriptCore 5525.26 (5525.26.2) <3a03d36ac807322bc73ed78c515e32be> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
  0x900000 -   0x910fff +AGRegex ??? (0.1) /Applications/FS2_Launcher.app/Contents/Frameworks/AGRegex.framework/Versions/A/AGRegex
  0x91b000 -   0xffdff3  com.apple.WebCore 5525.26 (5525.26.6) <77f5e6579cb4a8496df8d644ca7fa12d> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
 0x4370000 -  0x4469ff3  com.apple.RawCamera.bundle 2.0.7 (2.0.7) /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x8fe00000 - 0x8fe30b23  dyld 96.2 (???) <49af061b557801944d2207b1673af094> /usr/lib/dyld
0x90003000 - 0x90065ffb  com.apple.htmlrendering 68 (1.1.3) <e852db1c007de975fae2f0c2769c88ef> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x90395000 - 0x904dfffb  com.apple.ImageIO.framework 2.0.4 (2.0.4) <cbe744146e1f0e77cca0edce92bea0f7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x90535000 - 0x9056efff  com.apple.SystemConfiguration 1.9.2 (1.9.2) <1a39075165bf7447fe8be1e93db49346> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x9056f000 - 0x9061ffff  com.apple.QD 3.11.54 (???) <cd7bef6f156b82851cfb164ccd9f3986> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x90620000 - 0x90638ffb  com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x90639000 - 0x906d3ff7  com.apple.ApplicationServices.ATS 3.4 (???) <77bbf58ddc32846bdfdea2bd30ab6fb9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x906d4000 - 0x9073bffb  libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0x9073c000 - 0x907c4fff  com.apple.ink.framework 101.3 (86) <66a99ad6bc695390a66dd24789e23dcc> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x907c5000 - 0x908d9ffa  com.apple.vImage 3.0 (3.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x908da000 - 0x908edfff  com.apple.LangAnalysis 1.6.4 (1.6.4) <f12db38b92cbf96b024206698434d14d> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x908ee000 - 0x9093dfff  libGLImage.dylib ??? (???) <274f96cdf247e29c74dc476d166928ca> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x9093e000 - 0x90994fff  libGLU.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x909ab000 - 0x90a7afff  com.apple.ColorSync 4.5.1 (4.5.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x90ba1000 - 0x90be8fff  com.apple.NavigationServices 3.5.2 (163) <cb063c95a55ba12994a64c7e47f5706a> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x90c34000 - 0x90c3bffb  com.apple.print.framework.Print 218.0.2 (220.1) <c7e0e618d5867ae227403ae385aacd82> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x90c3c000 - 0x90c3cfff  com.apple.Carbon 136 (136) <f8fdb172887f2d6a374aed2d2a13b319> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x90c3d000 - 0x90c58ffb  libPng.dylib ??? (???) <248297ff5b022c274d5dcfa0de3b37b2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x90c59000 - 0x90c59ffb  com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallServer
0x90c5a000 - 0x90c65fff  com.apple.speech.recognition.framework 3.7.24 (3.7.24) <ae3dc890a43a9269388301f6b59d3091> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x90c66000 - 0x90cfafff  com.apple.framework.IOKit 1.5.1 (???) <9bd6b9e0f0a9a25c3a1d379da04dd8be> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90cfb000 - 0x90dabfff  edu.mit.Kerberos 6.0.12 (6.0.12) <c72d937eebc3e56ea636d332e2bb18cf> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x90dac000 - 0x90dacfff  com.apple.Accelerate 1.4.2 (Accelerate 1.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x90f41000 - 0x91127ffb  com.apple.security 5.0.4 (34102) <2954de63dbda688b09f2d75b834c89fa> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x91128000 - 0x9115dfff  com.apple.AE 402.2 (402.2) <0b15a08da8ec38b74fb9dd6e579ed25f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x9116a000 - 0x911f4fff  libvMisc.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x911f5000 - 0x9128efc3  libvDSP.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x913ef000 - 0x913f4ff6  libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x9169d000 - 0x919c6fe7  libLAPACK.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x91b80000 - 0x920f7ff3  com.apple.CoreGraphics 1.351.33 (???) <83d4f302053d3fe5f69c8e20b3a0c34f> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x920f8000 - 0x9286dfff  com.apple.AppKit 6.5.3 (949.34) <5a94250c410980eb9047e9a5f0f9b558> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x928c3000 - 0x92988ffb  com.apple.CoreData 100.1 (186) <9cf54cb19b18e53ee22edb7ababa6e6c> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x92989000 - 0x92989ffa  com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x9310e000 - 0x9312affb  com.apple.openscripting 1.2.8 (???) <eb961ce3c1b1e564c2eefe3682ee0555> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x93139000 - 0x9316afff  com.apple.coreui 1.2 (62) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x9316b000 - 0x93179fff  libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x931ba000 - 0x934f3feb  com.apple.HIToolbox 1.5.4 (???) <ffe389390ecc05cf8770c81db6511bd1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x934f4000 - 0x934fcfff  libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x93661000 - 0x93962ffb  com.apple.CoreServices.CarbonCore 786.6 (786.6) <94736308a0b44830c732ebb1bebd78f8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x93963000 - 0x93971ffb  com.apple.opengl 1.5.7 (1.5.7) <0f5ac86573f9bb828dfa1864d85a4162> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x93972000 - 0x93991fff  com.apple.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x93b33000 - 0x93bc2ffb  com.apple.DesktopServices 1.4.7 (1.4.7) <5792e9dc03f76544c71dedd802a1fa36> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x93bc3000 - 0x93d0bffb  libicucore.A.dylib ??? (???) <2d1f8cb81754c6b68809a4aa6c7b94a3> /usr/lib/libicucore.A.dylib
0x93d0c000 - 0x93f51ffb  com.apple.Foundation 6.5.6 (677.21) <8350383f1c44d18e471451ce92a1572c> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x94cba000 - 0x94cdaff7  libJPEG.dylib ??? (???) <f92878fdf02ffb1474b8bc60c47bb72d> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x94ce1000 - 0x94d62fff  com.apple.print.framework.PrintCore 5.5.3 (245.3) <032f772f8169945c1d1b524d96edcef6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x94d63000 - 0x94deaffb  com.apple.audio.CoreAudio 3.1.0 (3.1) <3baa0645ba65ef3c69c975ac989b2caf> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x94e15000 - 0x94e9bff9  com.apple.CFNetwork 339.5 (339.5) <b401902ddbf0d923e7b584e579ce0b4c> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x94e9c000 - 0x94ec4fff  libxslt.1.dylib ??? (???) <a69bf3978edd9dd905726660011bb6e6> /usr/lib/libxslt.1.dylib
0x94ec5000 - 0x94ec5fff  com.apple.audio.units.AudioUnit 1.5 (1.5) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x94ec6000 - 0x95480fff  libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x95481000 - 0x954a0fff  libresolv.9.dylib ??? (???) <d4538f370cadea5d74d3ac86c610e570> /usr/lib/libresolv.9.dylib
0x954a1000 - 0x954a4fff  com.apple.help 1.1 (36) <7106d6e074a3b9835ebf1e6cc6c822ce> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x954ab000 - 0x95565fff  libcrypto.0.9.7.dylib ??? (???) <335916b82e302fec637432caf7c9e8e5> /usr/lib/libcrypto.0.9.7.dylib
0x95566000 - 0x9557dffb  com.apple.ImageCapture 4.0 (5.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x9557e000 - 0x9557fff8  com.apple.ApplicationServices 34 (34) <6aa5ee485bb2e656531b3505932b845f> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x956bb000 - 0x957d9ff7  com.apple.audio.toolbox.AudioToolbox 1.5.1 (1.5.1) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x958d7000 - 0x95d05ffa  libGLProgrammability.dylib ??? (???) <603a9704539c585a35801c2452930cb2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x95d06000 - 0x95dd9fff  com.apple.CoreServices.OSServices 226.5 (226.5) <e50f547a3d8d316885b424e282bd80fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x95dda000 - 0x95df3ffb  com.apple.CoreVideo 1.5.1 (1.5.1) <43996b088c16cd1fb1223bcfabc3c366> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x95df4000 - 0x96159ff2  com.apple.QuartzCore 1.5.5 (1.5.5) <e5fa65979d5e0bb75ec19aea053ce83d> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x96187000 - 0x961e7fff  com.apple.CoreText 2.0.3 (???) <4ce8460abbfca7c9bd655ae0173976df> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x961fc000 - 0x961fcff8  com.apple.Cocoa 6.5 (???) <e9a4f1c636d00893db0494c4040176ba> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x961fd000 - 0x96205ffb  libCGATS.A.dylib ??? (???) <3c50a1f1f03470a8baadd22a17a4b547> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x96316000 - 0x96372ffb  com.apple.HIServices 1.7.0 (???) <48d200891cc9dd795ee547d526c6a45b> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x9637a000 - 0x9637cffd  libRadiance.dylib ??? (???) <34cc3c24f4be3a4372275400b6e05b85> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x963aa000 - 0x963ebffb  libTIFF.dylib ??? (???) <4c1422124af245485d6ceee207f4d735> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x963ec000 - 0x9643bfff  com.apple.Metadata 10.5.2 (398.22) <7063f883d9d901fea72151597ccd4e6a> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x9643c000 - 0x9644fffb  com.apple.speech.synthesis.framework 3.7.1 (3.7.1) <dc8dac074f4d19175c5613b35aa529b3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x96450000 - 0x96476fff  libcups.2.dylib ??? (???) <0baa8f1a940b5d8c4d8e4e63fffef410> /usr/lib/libcups.2.dylib
0x96477000 - 0x96480fff  com.apple.DiskArbitration 2.2.1 (2.2.1) <a389b4c2badce39540f24402f7df35e7> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x96481000 - 0x964aefff  libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x96761000 - 0x96886ffb  com.apple.CoreFoundation 6.5.4 (476.15) <cad7eb450d1f930417aeeca9eb00dbcd> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x968f9000 - 0x9697efff  libsqlite3.0.dylib ??? (???) <f2a33fe2663eab9c7f4806d2cf05b4ee> /usr/lib/libsqlite3.0.dylib
0x9697f000 - 0x9698cfff  libCSync.A.dylib ??? (???) <e0395a40546c6c8b244962512e74c35e> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x969d1000 - 0x969d5ffe  libGIF.dylib ??? (???) <491b205a6b8bb0c0c6ee6aaeea19a671> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x969d6000 - 0x96ab9fff  libobjc.A.dylib ??? (???) <39035ba996e55c617e20595dcd89c063> /usr/lib/libobjc.A.dylib
0x96aba000 - 0x96ad9fff  com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x96ade000 - 0x96c77fe3  libSystem.B.dylib ??? (???) <2ecfb9e8a8f2f72021bf1ee8f4c8e3fb> /usr/lib/libSystem.B.dylib
0x96c7b000 - 0x96c86ffb  libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x96d6f000 - 0x96deafff  com.apple.SearchKit 1.2.1 (1.2.1) <23c2c93a7ec832505d5c7b67fee89a6d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x96deb000 - 0x96deeffb  com.apple.securityhi 3.0 (30817) <ad843393cafb2193fd716df88d8136bf> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x96def000 - 0x96df6fff  com.apple.CommonPanels 1.2.4 (85) <0d1256175c5512c911ede094d767acfe> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x96df7000 - 0x96df8fff  libffi.dylib ??? (???) <11b77dbce4aa0f0b66d40014230abd1d> /usr/lib/libffi.dylib
0x96e52000 - 0x96e5eff3  com.apple.audio.SoundManager 3.9.2 (3.9.2) <79588842bcaf6c747a95b2120304397a> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x96e5f000 - 0x96e8aff7  libauto.dylib ??? (???) <b3a3a4b0f09653bd6d58f1847922b533> /usr/lib/libauto.dylib
0x96ebd000 - 0x96f53fff  com.apple.LaunchServices 290 (290) <fd3ffed6d3e33d356610d5eac6c7088a> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0xfffec000 - 0xfffeffff  libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703  libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on December 10, 2008, 10:26:18 pm
Hmm ... the Derelict mod.ini still seems to crash the launcher.  Not sure what causes it...

Code: [Select]
[launcher]
image255x112 = Derelict.bmp;
infotext     = Five years have passed since the jump node to the Capella system was collapsed, sealing off a massive wave of Shivan Juggernaughts from pushing further into GTVA space. The supernova and subsequent nebula hang like a growing scar throughout the GTVA as light from that event continues to spread across our worlds. You are to take a new tour of duty with the 212th Silver Scythes squadron in the Tau Sigma cluster, a remote group of systems beyond the Altair Jump Node. These are mining colonies, and while the GTVA presence is small, it is nontheless important.;
website      = http://www.3dap.com/hlp/hosted/ce/;
forum        = http://dynamic.gamespy.com/~freespace/forums/forumdisplay.php?s=83686deb4fd49b5f670f6d92203b257d&forumid=89;

[multimod]
primarylist  = ;
SecondryList = mediavps, nebulae;

[settings]
flags = -spec;
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 10, 2008, 11:55:54 pm
I would guess the infotext is longer than the launcher can handle, everything else looks about normal to me.
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on December 11, 2008, 02:01:28 pm
and

SecondryList = mediavps, nebulae;

should be

SecondryList = mediavps,nebulae;

so no space between
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 11, 2008, 05:13:24 pm
Man I wondered about that too, but I wasn't sure if you could have a space or not.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on December 11, 2008, 06:51:14 pm
I don't think you can. Leave the space out and it should work fine.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on December 16, 2008, 09:33:51 am
Af far as the problem that blowfish mentioned, I think I have found the source of the problem. I will release an update in the next few days that rectifies the problem. Chief, I would like the output of the system.log in the Console application, not the output of the crash reporter. The system.log output also displays text output from the application itself, that's why I need it, in case I am able to reproduce the problem on my machine.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 16, 2008, 10:53:45 am
Well, I can't be certain but I think it was related to the use of a case-sensitive HFS+ install instead of the default case-folding filesystem.  I reformatted over the weekend and started over, and I haven't had a single issue yet.  Launcher has been working fine.  So the only thing I can suggest is watch out for case issues.
Title: Re: FS2_Launcher OS X 3.0
Post by: neoterran on December 16, 2008, 10:56:36 am
There is a subtle bug with the launcher and mods at the moment. There is some way you can get it where the mod that has been applied "sticks" and when you move around and pick another mod, although it chooses it, it doesn't update the list you can see in the drawer. It's rare, but It happened to me with the Freespace Port where I had the mod.ini wrong and I was trying to fix it to no avail.  I worked around it by using the drawer to delete the 'stuck' mod line. When i tried to repeat the behavior it seemed to be working normally.

*this was on 3.0.10, I haven't seen it on 3.0.11 yet*
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on December 18, 2008, 02:22:12 pm
Ι have already released the update, which should fix a number of problems. Along with the encoding, I should also take into consideration differences in the ways text files are handled by developers when writting a mod.ini file. The reason why you get so many bugs with the mod.ini parser is because I built that feature on demand. That means that I took some example mod.ini files and built my parser to handle those. Occasionally, I stumble upon a mod.ini file not being handles correctly.

If someone notices it and reports it, I will fix it. If not, then I probably leave it as is. I am not playing freespace 2 anymore, but I do offer support for the Launcher. That's why I always mention that anyone should report any bugs in here, or e-mail me about a problem, since I won't notice it by myself.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 18, 2008, 04:00:35 pm
Well, the requirements are pretty lax it seems, as far as the Windows launcher is concerned.  The layout should be something like:

Code: [Select]
[launcher]
modname      = Mod Title;
image255x112 = image.bmp;
infotext     = Mod description text.;
website      = http://website/;
forum        = http://forumssite/;

[multimod]
primarylist  = ;
secondarylist = ;

[settings]
flags = ;

But as you've probably noticed, almost everything in that is optional.  settings can be completely ommitted, as I'm sure multimod can, and probably launcher too, if for some reason you just wanted multimod and/or settings.  So really, you can define anything you want.  Most lines don't even seem to need to end in semicolons as far as I can tell, secondary can be spelled secondry, the mods list can start with a comma or not, probably any number of commas, etc.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on December 18, 2008, 09:49:09 pm
Soulstorm, does the OS X Launcher now recognise "-" in the mod folder? Two releases ago, I had a problem because FSPort released their mediavps folder called fsport-mediavps, and the launcher couldn't recognise the "-", so it used the previously run mod instead.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on December 20, 2008, 02:51:28 am
Most lines don't even seem to need to end in semicolons as far as I can tell, secondary can be spelled secondry, the mods list can start with a comma or not, probably any number of commas, etc.

That doesn't mean that it's easier to parse. On the contrary, you must take into consideration differences between mod.ini files, and that may lead to problems. That's why I rely on the testers and users to tell me if I have omitted a parameter.

Androgeos Exeunt, I don't think it does. I will check it out and post back to be sure. If it doesn't, I will certainly include that parameter in the next version...

EDIT:I tested it and it works. You can do the test yourself. Rename a valid mod folder to something that contains the '-' character, and launch the Launcher to see what happens.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on December 20, 2008, 02:20:10 pm
I never said it was easy, I said the requirements are lax.  I didn't mean to imply that made it easier to parse.  I'm aware that kind of inane flexibility makes it all the more difficult to parse.
Title: Re: FS2_Launcher OS X 3.0
Post by: azile0 on February 15, 2009, 12:20:18 am
So, how do I run campaigns on this? I can't load a .vp file into the Standalone menu.. Can I run campaigns at all on a Mac?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on February 15, 2009, 12:45:25 am
So, how do I run campaigns on this? I can't load a .vp file into the Standalone menu.. Can I run campaigns at all on a Mac?

Yes.  You don't run specific vp files, but rather campaign folders.  So selecting a mod from the mod menu will use all of the VPs within that mod's folder.  Just to note, these things usually behave pretty much the same on OSX and Windows...
Title: Re: FS2_Launcher OS X 3.0
Post by: Sololop on February 18, 2009, 08:32:30 pm
I can't turn anything off.

Like in the Graphics tab, I want to disable stuff like normal and glowmaps, to try and see the effects on performance, but as soon as I close the launcher or run FS, if I re-check, they are enabled again.

I don't know why its doing that...
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on February 18, 2009, 09:25:41 pm
In such cases, I usually go to [your username] -> Library -> FS2_Open -> data and open cmdline_fso.cfg with TextEdit. I add the command lines I want, save, quit TextEdit, then lock the file.

It's very complicated and inconvenient, but a stopgap solution nonetheless.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on February 18, 2009, 09:34:37 pm
When you uncheck a box, try showing the drawer and refreshing it.  That usually works.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on March 06, 2009, 04:18:33 am
Sorry for taking so long to reply, but I have my semester exams!

This is a normal behavior, and it is documented! Please, before posting questions, read the online read me. Open your FS2_Launcher application, and go into the help menu.

The command line drawer is not automatically refreshed, but the main window with the checkboxes is! That means that when you check or uncheck a box, you must hit "refresh" on the command line drawer!. But when you change anything in the command line drawer, the main window is automatically updated.

Once again, the correct order to do things is:
1) Check or Uncheck boxes in the main window.
2) Hit refresh on the command line drawer
3) (Optional) Add any custom (maybe undocumented) commands in the command line drawer that are not visible in the main window
4) Run FS2_Open.

I have done it this way in order to facilitate giving custom command line options. If you press a button in the main window, the command line drawer is not refreshed according to the change, because if it did, it would remove every other custom command line option.

Do you think I should change that? How would YOU like it to be done?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on March 06, 2009, 10:06:30 am
Rather than adding custom flags to the list of regular ones, I think there should be a separate place to input them.  The launcher would store somewhere what custom flags had been enabled so that it could know to keep them every time the command line options are refreshed.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on March 06, 2009, 11:35:24 pm
Hmm ... would it be possible to have an option to automatically set the resolution to your display's native resolution?  I think you would use something like:

Code: [Select]
[[NSScreen mainScreen] frame].size.width

and

[[NSScreen mainScreen] frame].size.height
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on March 30, 2009, 12:34:39 pm
I will listen to all recommendations. But I won't do anything before some time has passed. I have accepted to work on a project that requires a lot of effort, and looking into FS2_Launcher is the last thing I need now.

However, bugs are a priority for me. If you spot a bug, I will look into it right away. I usually release a new version with fixes for bugs described in e-mails one or two days after I receive the e-mails, so don't hesitate to send me bug reports.
Title: Re: FS2_Launcher OS X 3.0
Post by: louiswuenator on April 06, 2009, 07:39:00 pm
Hey Soulstorm, I'm having a problem with the Launcher.  When I open it, it does nothing except bounce in the dock a few times and then quits.  I does open every once and a while, but I haven't figured out what causes the difference.  Here's the console log:

4/6/09 8:29:07 PM FS2_Launcher[574] Stack: (
    2417762571,
    2493644347,
    2417762027,
    2417762090,
    2502867634,
    51358,
    30996,
    36389,
    28509,
    23518,
    2417821973,
    2505438298,
    2505397894,
    2505396200,
    2505395243,
    2505395049,
    2505394200,
    11638,
    11421
)

4/6/09 8:29:09 PM com.apple.launchd[95] ([0x0-0x73073].com.soulstorm.MMST2_3[574]) Exited abnormally: Trace/BPT trap

Any help would be greatly appreciated, thank you!
Title: Re: FS2_Launcher OS X 3.0
Post by: noobdy on April 18, 2009, 11:18:35 pm
Hello, first time i'm using the launcher, and I just noticed that primarylist line from mod.ini files isn't recognized by the launcher, only secondarylist is.

Example: I tried to play "fsport_str" with "fsport_mediavps" using FSOpen 3.6.9 (3.6.10 is too buggy under Tiger for me) and mediavps 3.6.10.
Here's the [multimod] section of "fsport_str" mod:
Code: [Select]
[multimod]
primarylist = fsport_mediavps;
secondarylist = fsport,mediavps;
So, the command line must be:
Code: [Select]
-mod fsport_mediapvs,fsport_str,fsport,mediavps
If i select "fsport_str" mod, its secondary list of mods are recognized, but "fsport_mediavps" isn't.
Question: is it possible to add the recognition of "primarylist" line in the launcher?

There's a manual solution to resolve the problem though, which is to change the [multimod] section in mod.ini file from "fsport_mediavps" to:
Code: [Select]
[multimod]
secondarylist = fsport_str,fsport,mediavps;
Then select directly "fsport_mediavps" in the launcher... Ok, but it means that we'll loose the intuition feeling of the launcher... Not so easy for someone who doesn't check the forum everytime ^^

(hum, hope it was understandable, my english language still sucks a bit, sorry again)
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 25, 2009, 09:02:21 am
I just got FreeSpace Open and I can't seem to get my FS2_Open-20090321_r5112 to recognise any mods. Same for 3.6.9 or 3.6.10.rc2

I am on a unibody MacBook running OSX 10.5.6

First, when I used the JAR installer, the http://game-warden.com/fs2open_pxo.cfg file was missing.

Second, when I first used the launcher, it complained that it would not find a flag file.
Then when I use the 'Customize..' button, I get the file selection dialog windows, but none of the mod folders will let me use the 'open' button.

Now when I start FS_Open, I don't get any of the lovely mods that I downloaded :sigh:.

I have no idea how I may include the mods manually. I tried google, but nobody seems to have had this problem..

Best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Tinman on April 25, 2009, 09:09:06 am
in the launcher, choose "Gameplay + Speed" and select your mod
Title: Re: FS2_Launcher OS X 3.0
Post by: Jeff Vader on April 25, 2009, 09:29:37 am
And do use 3.6.10 RC2. Newer is (usually) better.
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 25, 2009, 09:42:53 am
in the launcher, choose "Gameplay + Speed" and select your mod

I see. I thought a list of mods would appear in the campaign screen inside FS2O.

Thanks,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Jeff Vader on April 25, 2009, 09:46:15 am
You must select a mod outside the game. After that, if the mod has a campaign/campaigns, they'll appear in the in-game campaign room, where you must then select the desired campaign.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 25, 2009, 10:34:44 am
Hello, first time i'm using the launcher, and I just noticed that primarylist line from mod.ini files isn't recognized by the launcher, only secondarylist is.

Example: I tried to play "fsport_str" with "fsport_mediavps" using FSOpen 3.6.9 (3.6.10 is too buggy under Tiger for me) and mediavps 3.6.10.
Here's the [multimod] section of "fsport_str" mod:
Code: [Select]
[multimod]
primarylist = fsport_mediavps;
secondarylist = fsport,mediavps;
So, the command line must be:
Code: [Select]
-mod fsport_mediapvs,fsport_str,fsport,mediavps
If i select "fsport_str" mod, its secondary list of mods are recognized, but "fsport_mediavps" isn't.
Question: is it possible to add the recognition of "primarylist" line in the launcher?

There's a manual solution to resolve the problem though, which is to change the [multimod] section in mod.ini file from "fsport_mediavps" to:
Code: [Select]
[multimod]
secondarylist = fsport_str,fsport,mediavps;
Then select directly "fsport_mediavps" in the launcher... Ok, but it means that we'll loose the intuition feeling of the launcher... Not so easy for someone who doesn't check the forum everytime ^^

(hum, hope it was understandable, my english language still sucks a bit, sorry again)

I built the Launcher some years ago... I haven't seen a mod.ini file with a Primary list that matters for a long time. I remember asking people about the importance of "primary list" and they said to me that the secondary list was of importance. Anyway, I didn't implement support for it, but I will do it. Give me some time. I will figure something out, although it has been so long since I have been involved with the project that it will take some time to remember what I have done.

EDIT: Why have 2 lists of mods? What is the difference between primarylist and secondarylist?
Title: Re: FS2_Launcher OS X 3.0
Post by: Mongoose on April 25, 2009, 10:47:47 am
EDIT: Why have 2 lists of mods? What is the difference between primarylist and secondarylist?
Mods placed in primarylist will be loaded before the mod whose folder you're selecting, while those in secondarylist will be loaded after it.  The only time I've ever seen it used myself is in Silent Threat: Reborn, since some of the files in the FSPort MediaVPs overwrite those in the ST:R release and so need to be loaded into FS2 before it.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on April 25, 2009, 10:57:05 am
I see. I thought a list of mods would appear in the campaign screen inside FS2O.

Thanks,
 Oscar
/me fires a BABeam.

(http://v4belg.blu.livefilestore.com/y1pqOjIDNsngwY22ryH_7-QV839ByEgyO2QczUt3U0lK5J3zmG5-fcAr6T3btKwie3rcufT5urFnbWm5UFWIHslVg/WelcomeAncient.png)
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 25, 2009, 11:14:25 am
You must select a mod outside the game. After that, if the mod has a campaign/campaigns, they'll appear in the in-game campaign room, where you must then select the desired campaign.

Hmm. In that case things are not working. I reinstalled 3.6.10 RC2. I start the launcher,  I enter the settings I found in the mediavps readme, and set it to fsport_mediavps. I hit launch. Then I get only the FS2 campaign, and it duly starts on Vega  :confused:.

Also, I noticed that when I reloaded the launcher (v3.0.11, I think), the '-spec_tube' field contained the following:
1.5 ogl_spec 20 mod fsport-mediavps,fsport,mediavps mod fsport-mediavps,fsport,mediavps

Can't be right, of course., and it looks like the launcher didn't properly parse my settings file. Also, I wonder why it does the mod bit twice.. In fact, from the exported version (see attached), it seems like there is a lot of pointless duplication going on.

I quite the launcher, thrashed the plist file in ~/library/preferences and then it does the same damn things again, not having junked the earlier settings. This is getting less and less intuitive..

Best wishes,
 Oscar

[attachment deleted by evil Tolwyn]
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 25, 2009, 12:07:05 pm
Quote
I quite the launcher, thrashed the plist file in ~/library/preferences and then it does the same damn things again, not having junked the earlier settings. This is getting less and less intuitive..

The settings you need to trash are the ones described in your command line file. Try that and see what happens. Do you also follow the following procedure?
Code: [Select]
1) Do whatever you want with the main window
2) Open the command line drawer (command-T)
3) Hit refresh. The drawer will be updated with all the contents of the main window.
4) Do whatever you want with the command line drawer by adding custom commands or removing some.
5) Save when done.

And, of course the controls are not intuitive. I made this program years ago, where custom mods and command line arguments were different. Years have passed, and I can't go back and rewrite the launcher for those. Back then, I wasn't even near in programming skills as I am now. For me, the Launcher need a complete overhaul. But I have undertaken a big project, and I have stated many times that I have abandoned the project, and I only fix bugs, not improve the way things work. The only thing I can do is to give the source to whoever wants to help with the development and fix the problems with the Launcher.

I have released an update that will partially fix the primarylist mod.ini issue. Not all things are ready, though. If I have the time, I will sit tomorrow and try to improve the Launcher. However, I haven't played FS2_Open for many months, and I don't know to what extent the Launcher will cover its new features, if any.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on April 25, 2009, 01:25:59 pm
It would be much appreciated, with 3.6.10 right around the corner, having any serious bugs and annoyances knocked out would be a blessing.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 25, 2009, 01:36:31 pm
As far as I understand, the most serious annoyance with the Launcher is the custom command line drawer, and the way it handles custom command line arguments. So, I will try to change that. I will release a new version in the next few days, which will use the command line drawer for inserting additional arguments. The drawer will behave independently from the main window, and when the application quits, everything will be unified and written to the configuration file of FS2_Open.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on April 25, 2009, 02:26:10 pm
I'm not sure if I like auto-save, even in Windows you have to hit OK or Apply, Cancel will let you close the launcher without committing anything you modified.
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 25, 2009, 04:31:57 pm
The settings you need to trash are the ones described in your command line file. Try that and see what happens.

Where can I find that file? I am sorry, but I am entirely unfamiliar with this platform, so I do not know in what places the files are kept.

And, of course the controls are not intuitive. I made this program years ago, where custom mods and command line arguments were different. Years have passed, and I can't go back and rewrite the launcher for those. Back then, I wasn't even near in programming skills as I am now. For me, the Launcher need a complete overhaul. But I have undertaken a big project, and I have stated many times that I have abandoned the project, and I only fix bugs, not improve the way things work. The only thing I can do is to give the source to whoever wants to help with the development and fix the problems with the Launcher.

I didn't mean this as a snipe, I quite understand programming isn't easy. I was merely hoping that someone would help me diagnose the problem. You way exceeded that be setting up a new version already  :yes:.

Best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 25, 2009, 05:15:47 pm
The settings you need to trash are the ones described in your command line file. Try that and see what happens.

Where can I find that file? I am sorry, but I am entirely unfamiliar with this platform, so I do not know in what places the files are kept.

And, of course the controls are not intuitive. I made this program years ago, where custom mods and command line arguments were different. Years have passed, and I can't go back and rewrite the launcher for those. Back then, I wasn't even near in programming skills as I am now. For me, the Launcher need a complete overhaul. But I have undertaken a big project, and I have stated many times that I have abandoned the project, and I only fix bugs, not improve the way things work. The only thing I can do is to give the source to whoever wants to help with the development and fix the problems with the Launcher.

I didn't mean this as a snipe, I quite understand programming isn't easy. I was merely hoping that someone would help me diagnose the problem. You way exceeded that be setting up a new version already  :yes:.

Best wishes,
 Oscar

First of all, you can find that file at ~/Library/FS2_Open/data/cmdline_fso.cfg. When the Launcher changes something, it changes that file. So if you delete that, you actually delete all command line arguments on FS2_Open. FS2_Open reads this file for command line arguments at startup.

In addition, you will find that a small bug remains concerning the mod.ini parser and the non-standalone mods when you start the application. Should annoy you little, though. I will do what best I can to eliminate that problem.

Also, what I meant to say is that I haven't been involved in the project for a long time. Now, I want to be able to change something in the Launcher, like the way the command line drawer behaves, and I find that in order to do so I must rewrite so many parts of the application that I find it best and less bug-prone to rewrite the whole application from scratch.

By looking at my code now, I think: "What the heck was I thinking...?". Those years since the initial release taught me so much that I really want to upgrade the Launcher to even do things that the PC version doesn't have. I will do this, as I stated in a previews post, however, I looked the code today, and I saw that it may require more time that I originally thought. Since I have undertaken a project from someone that actually pays, I must concentrate my efforts to finish that job, and then get involved in FS2_Launcher 4.

I know I stated that I abandoned the project, but today I was so pissed off when I saw how many things could be done better, that I really want to rewrite the whole application.  Heck, I am building an OpenGL game now, and I can't make a simple Launcher?

So, on to FS2_Launcher 4.0 with features:

Features that will surely be added:
- New command line drawer. I know, I have made many people angry. I just thought it would be good to make it work this way back then.
- Better mod.ini parsers.
- Renewed static menus
- New User Interface
- Helpful Developer additions (extraction of the flag files, intervene in the flag files, alter game data, etc)

Features I will try to implement:
- Automatic searching for standalone mods
- Automatic finding of FS2_Open folder and automatic configuration using hardware capabilities

When?
Well, that's the difficult part. I will try to do it as soon as I can. However, I have other projects, as I mentioned and I have my semester exams. I think that I must be honest and say that I will have something ready in the summer. Maybe I find some time sooner, but I don't want to give anyone false hopes.

Please bear with the Launcher as it is now, and I will return to active development on this after 2 months or so to give you a new version.
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 25, 2009, 05:46:04 pm
First of all, you can find that file at ~/Library/FS2_Open/data/cmdline_fso.cfg. When the Launcher changes something, it changes that file. So if you delete that, you actually delete all command line arguments on FS2_Open. FS2_Open reads this file for command line arguments at startup.

Well, no luck so far. I just cannot seem to get mods to show up in FS2O :(. I may resort to command line work when I feel like it.

Please bear with the Launcher as it is now, and I will return to active development on this after 2 months or so to give you a new version.

No worries. I have a Ph.D. thesis to finish, so it is not like I have a lot of extra time at the moment..

Best wishes and good luck with the exams,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 25, 2009, 07:03:55 pm
Hm... that is odd. I am using the Launcher with the newest version of FS2_Open and I can't seem to reproduce this problem. Let me tell you how things work, that may help you.

FS2_Launcher recognizes as mods the following:
- Folders that contain .vp files on their top level.
- Folders that contain mod.ini files on their top level.
Those folders must be in the same folder that contains the application.

If a mod folder does not match that criteria, it does not show up on the mod list. However, if you want to load a mod that doesn't show on the list, you can type the name of the corresponding folder in the field that asks for the mod name. Try that. If that doesn't work, then that means that FS2_Open itself cannot recognize the mod for some reason, so the Launcher won't help you.

I hope I helped.
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on April 25, 2009, 10:37:38 pm
Okay ... I just updated to the latest version, and I encountered a major bug.  It seems that the launcher is no longer actually putting the active mod into the command line (and replacing it with "mod "), as well as adding a weird (null) thing.  So if I have a mod that calls for the mediavps I get:

Code: [Select]
-mod mod ,(null),mediavps
When I should be getting something like:

Code: [Select]
-mod Derelict,mediavps
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 26, 2009, 02:41:22 am
Try that. If that doesn't work, then that means that FS2_Open itself cannot recognize the mod for some reason, so the Launcher won't help you.

I hope I helped.

You certainly did. The thing is that the launcher sees the mods (Awakenings, Cardinal Spear, Derelict, Destiny of Peace, DEM, FSport) but somehow FS2_Open refuses to load it :(. I will have to wait for a new RC or something..

The only things that surprises me with the current version is that the launcher still appends some options twice (which may not hurt) and appends the mods as follows: mod ,fsport-mediavps,fsport,mediavps I do not get a (null), but I do get a comma, which may be quite right.

Best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Jeff Vader on April 26, 2009, 03:05:45 am
In those terms, there should be nothing wrong with the game engine itself. FSO will use mod folders if it has a valid -mod parameter given by a command-line flag/Launcher setting/mod.ini. A new RC (or final 3.6.10) wouldn't change things. It is most likely something with the Launcher. Perchance the best option would be to input the command-line flags manually.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 26, 2009, 04:26:08 am
Okay ... I just updated to the latest version, and I encountered a major bug.  It seems that the launcher is no longer actually putting the active mod into the command line (and replacing it with "mod "), as well as adding a weird (null) thing.  So if I have a mod that calls for the mediavps I get:

Code: [Select]
-mod mod ,(null),mediavps
When I should be getting something like:

Code: [Select]
-mod Derelict,mediavps

Please post your entire mod.ini file. I am trying to reproduce the bug. Just tried warzone, and seems like FS2_Open r5020 rosebay loads all necessary mods and dependencies. Did you delete your preferences file AND your FS2_Open configuration file?
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 26, 2009, 08:02:03 am
I made some changes to the launcher, and I have made a new version ready (http://www.hard-light.net/forums/index.php?action=dlattach;topic=51391.0;attach=9873). I have changed to following:

- The custom command line drawer changes. It does not need refresh. It will ONLY hold custom command line arguments that don't exist in the main window (as requested by many people).
- The mod.ini parser is changed a bit.

Before using this, please delete both the FS2_Launcher preferences and the FS2_Open command line file. In order to simplify this process, I have created a small automator script that will do that, here (http://www.hard-light.net/forums/index.php?action=dlattach;topic=51391.0;attach=9876).

Please test the application and post back with reports asap. I want to see if it works before releasing a new version and forcing anyone to upgrade...

EDIT: Please redownload (http://www.hard-light.net/forums/index.php?action=dlattach;topic=51391.0;attach=9873). I have made a small update to the small update I did before the small update I made today  :lol:

[attachment deleted by evil Tolwyn]
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 26, 2009, 09:38:46 am
For the record, my mod.ini file (in the root FS2_Open folder) is as follows, and I think it always has been:

Code: [Select]
[launcher]
image255x112 = FS2.bmp;
infotext     = Freespace II. No mods. No new effects. No new graphics. Freespace II Classic if you will. Select mediavps as your mod to activate the new graphics. Select fs1port to play FS1 or Silent Threat with SCP enhancements.  ;
website      = http://www.hard-light.net/;
forum        = http://www.hard-light.net/forums;

I also downloaded you automator script, which compains about a growl notification that it cannot give. :).

Best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 26, 2009, 09:44:50 am
OK I fixed the small application. How about the new beta of the Launcher? Still the same problem?

Anyone else tested it?
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 26, 2009, 10:36:08 am
Yes, same thing. I do notice that when I start the application anew, it still complains about a missing flag file. Then I tell it where my FS2_Open installation is, and that complaint goes away. BTW, the install is quite hidden in
~/Library/Application Support/CrossOver Games/Bottles/FreeSpace 2/drive_c/Games/FreeSpace2/FS2_Open 3.6.10 RC2.app

When I do select that app, the launcher gives the following message:

Code: [Select]
Unknown Command

Unrecognized command line parameter, "-", continue?

<quit> <OK>

Also I noticed that parsing seems to broken on the last command line last before 'mod':

As described in the mediavps readme.txt, I fill in
-ambient_factor 35
-spec_exp 15
-spec_point 1.2
-spec_static 1.5
-spec_tube 1.5
-ogl_spec 20


I hit save and reload, and all is well. Then I select mod fsport-mediavs. In the dependencies field, I get the following:
,fsport-mediavps,fsport,mediavps

Then I hit save and reload again, and not the dependencies show ,(null),, while in the other tab, I find '-spec tube' now says: 1.5 ogl_spec 20 mod ,fsport-mediavps,fsport,mediavps.

If I clear that line to say only 1.5, hit save and reload again, I get in '-spec static' 1.5 spec_tube 1.5 mod ,fsport-mediavps,fsport,mediavps

My cmdline_fso.cfg is now the following:
Code: [Select]
-ambient_factor 35,00 -spec_exp 15 -spec_point 1.2 -spec_static 1.5 spec_tube 1.5 mod ,fsport-mediavps,fsport,mediavps -
My guess is that the trailing dash is wrong, and that it should be in front of 'spec tube' here. It see the same problem when I do not select anything with numbers, that the last command line option loses a dash, and there is a dash at the very end.

My next thought was that it might be the fact that I live in NL, and we have a comma instead of a period for decimals. So changed the config for -ambient_factor 35,00 to -ambient_factor 35.00. Still no love regarding the fsport mod :ick:..

Then I added a dash in front of the mod option, so that my config looks like this:
Code: [Select]
-spec -glow -env -missile_lighting -normal -3dshockwave -ambient_factor 35.00 -spec_exp 15 spec_point 1.2 -spec_static 1.5 -spec_tube 1.5 -ogl_spec 20 -mod fsport-mediavps,fsport,mediavps
And it works. I got the very pretty fsport-mediavs intro bit  :cool:.

So to summarise: put the dashes in the right place, in front of every command line option.

Thanks for helping my get to the bottom,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 26, 2009, 04:29:21 pm
Hm... thanks to your detailed walkthrough I figured out what was wrong. So here is a new beta:

-- The complain about the unknown command was expected and it involved a workaround in Cocoa. See, if the Launcher can't find a file in the command line file location, it will create an empty file. However, empty files in Cocoa mean a zero KByte file, which is impossible to read with standard Cocoa procedures, so it would result in a crash. So I created a file with a " " in it and that was mistakenly taken as an argument by the FS2_Open application. If you opened the command line drawer, the first line (the empty one) could be selected. If you deleted that line, you would have no problem. Of course, you shouldn't know that. I corrected it, though. Now, the Launcher will create a file with the "-spec" command in it. You can remove it later, when the app starts.
-- As far as the mod loading is concerned, I believe that your mod.ini file contained commas in some locations the Launcher didn't like. I made a workaround. Can you test it to see what works?
-- And as far as the Save and Reload procedure is concerned, I corrected that problem, but I think there's a bug on Cocoa and NSCombobox (which is the dropdown menu that selects the mod). Although you see that the dependencies mod isn't filled, if you reload again, the dependencies text field will be correct. That means that this will not affect your game. It's only a visual issue.
-- The dashes problem should be fixed now

Thanks for taking the time to provide me with information on improving the application. If you like, you can download the improved application (http://www.hard-light.net/forums/index.php?action=dlattach;topic=51391.0;attach=9878) attached below. Although I don't expect it to work flawlessly (due to heavy changes under the hood) I hope it helps you with your mods.

Can you please post the mod.ini file of the mod you want to load? The one you posted was the one of the FS2_Open Application. I need the one that is located inside the folder whose mod you want to load with FS2_Open.

[attachment deleted by evil Tolwyn]
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on April 26, 2009, 04:33:00 pm
Looks like the mod parsing is working now.  At least in cases where it worked before.  Haven't tested the primarylist thing though.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 26, 2009, 04:35:55 pm
Thank goodness, that is great to hear (read). Now oovldc remains...

What do you think of the new way the custom command line works?
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on April 26, 2009, 04:38:20 pm
Just discovered something ... when you select a mod that isn't recognized as an active mod, it doesn't even seem to add the -mod flag to the command line.
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 26, 2009, 05:10:35 pm
Still no dice with the launcher  :(.  Here's my resulting cmdline_fso.cfg:

Code: [Select]
-spec -glow -env -missile_lighting -normal -3dshockwave -ambient_factor 35,00 -spec_exp 15 -spec_point 1,2 -spec_static 1,5 -spec_tube 1,5 ogl_spec 20 mod ,fsport-mediavps,fsport,mediavps
It still lacks a dash in front of the 'mod' flag, and still loses the dash in front of 'ogl_spec'. And the first comma after 'mod' needs to go as well.

Here's the mod.ini for fsport-mediavps (I just used the JAR installer to download it, and did not change anything):
Code: [Select]
[launcher]
modname      = FSPort MediaVPs v3.1.1;
image255x112 = fsport-mediavps.bmp;
infotext     = Freespace Port Media VPs.  Requires FSPort 3.1.1 and standard Media VPs 3.6.10.;
website      = http://fsport.hard-light.net/;
forum        = http://www.hard-light.net/forums/index.php/board,170.0.html;

[multimod]
secondarylist = fsport,mediavps;

Actually, at the moment in FS2_Open, it is somewhat hit or miss for a newbie to find what goes where  :nervous:..

I think it would help if there were a section on the wiki, linked from the install pages, that explains where the FS2 files are (in your FS2_Open game folder, the config files in ~/library/FS2_Open, and a plist for the OSX launcher). Obviously different for win/Lin.

And also a page that explains the cmdline_fso.cfg file: where it lives, that you can use a launcher but also that it can be edited by hand, and that the options that you can put in it are found on this page (http://www.hard-light.net/wiki/index.php/Command-Line_Reference).

Best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 26, 2009, 06:56:39 pm
I believe this will fix your problem... ;) (Hopefully)

It may also solve some other problems. I tested it with your exact mod and it worked for me. Remember to delete your preferences...

EDIT: Please redownload. I believe I have also fixed the problem blowfish discovered a while ago...

[attachment deleted by evil Tolwyn]
Title: Re: FS2_Launcher OS X 3.0
Post by: blowfish on April 26, 2009, 07:26:32 pm
The problem I encountered is fixed now, only thing is unrecognized mods don't show up in the full mod field.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on April 27, 2009, 04:45:15 am
Thanks for the feedback. I will check into it when i get back. I hope oovldc is also fine with the changes so that I can release the new version...
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 27, 2009, 06:53:25 am
I think that's done it  :cool:.

Best wishes, and thanks for the perseverance,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on April 29, 2009, 03:09:36 am
FYI, I noticed launcher 3.1 was released yesterday.

-Oz
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on May 01, 2009, 05:29:56 pm
FYI, I drafted a Mac Installation Guide (http://www.hard-light.net/wiki/index.php/Mac_Installation_Guide) page on the wiki.

best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on May 01, 2009, 05:38:07 pm
Nice, but I probably would have just expanded on Installing FS2 Open (http://www.hard-light.net/wiki/index.php/Installing_fs2_open), and by extension, Installing FreeSpace 2 (http://www.hard-light.net/wiki/index.php/Installing_FreeSpace_2).  There doesn't seem to be a lot of Mac specific info there, and it could probably be wedged into the existing articles.  That actually probably needs to be linked to the FS2 Open on Linux guide too, as it's a very fleshed out detailed description for running on Linux.
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on May 03, 2009, 12:23:26 pm
I considered that, but there is so much implicit assumption  in the wiki that the reader uses windows that I felt a bit overwhelmed. I didn't want to go and restructure all of these.

As for the linux guide, there are two difference: one is that there is an cmdline_fso.cfg file that takes the place of command-line arguments. The other is that mac users as a rule do not compile software. They get the disk image and copy the application over.

Anyway, feel free to take it away, put content elsewhere, rewrite, etc. I just wanted to put an overview for beginners on what steps to take and link to other useful pages. To illustrate the need: when I first got here, it took me an hour of digging before I had clear that FS2O works on Mac, WIndows and Linux, FS2 only works on Windows, and that I needed a Windows machine to get the files from FS2 without a big fuss...

Best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on May 03, 2009, 01:39:23 pm
I've gone over those two articles I pointed to and done quite a lot of work to make sure they cover OS X and Linux as best as I know how.  The first one is fairly platform-agnostic until you get to the part about the Launcher, which is where your new information would have been well placed.  At least perhaps a link should go to your article at that point now.  The article about installing retail FS2 files is about as platform-agnostic as it could be, there's even two sections just for non-Windows users.  I know a lot of the wiki doesn't a lot of non-Windows info but those two articles I thought do a fairly decent job (they still need work I'll admit).
Title: Re: FS2_Launcher OS X 3.0
Post by: ovvldc on May 03, 2009, 05:50:29 pm
Looking at the Installing FS2 Open (http://www.hard-light.net/wiki/index.php/Installing_fs2_open) page, I got confused at step 2, which only lists a windows launcher (my text for soulstorms launcher may fit nicely here, as you said), and at step 5, because it seems to assume the windows launcher (without saying so)..

Looking at the Installing FreeSpace 2 (http://www.hard-light.net/wiki/index.php/Installing_FreeSpace_2) page, that is very neat. It might be good to move the details in the FS2-related parts of the install procedure (http://www.hard-light.net/wiki/index.php/FreeSpace_Open_Installer#Install_procedure) here.

The main problem with the two pages you mentioned is that they are not easily found - I couldn't really get to them from the main page.
I get into the wiki and click on Getting Started (http://www.hard-light.net/wiki/index.php/Getting_Started_(FreeSpace_Open)).

From Getting Started, you can get to a page describing the  FreeSpace Open Installer (http://www.hard-light.net/wiki/index.php/FreeSpace_Open_Installer), which tries to do two things: explain the installers and explain how to use them. Both are done too fast and are unclear. This link on the Getting Started page should be changed to your Installing FS2 Open page, which is much clearer. The article about the installer can then be properly focussed. And your Installing FreeSpace 2 page should be inserted before your Installing FS2 Open page, as the new number 3 on the Getting Started page.

I hope this is useful feeedback. No offense intended in my blunt phrasing. I can do the changes, but being a newbie here I am also reluctant to start cutting into experienced people's work, for fear that I might overlook or misstate something.

Best wishes,
 Oscar
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on May 03, 2009, 08:21:15 pm
No you're right, there's a bit of a disconnect with a lot of that information, and I totally missed that Step 2 only mentioned Windows launcher for some reason.  I need to fix that.  I'm not sure what to do about the rest of the disconnects though.
Title: Re: FS2_Launcher OS X 3.0
Post by: 134th Barracudas on June 20, 2009, 11:52:53 am
Can't open the launcher at all.
This is the extended crash report

Code: [Select]
Date/Time:      2009-06-20 18:49:54.117 +0200
OS Version:     10.4.11 (Build 8S165)
Report Version: 4

Command: FS2_Launcher
Path:    /Volumes/500K/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
Parent:  WindowServer [67]

Version: ??? (3.1)

PID:    312
Thread: 0

Exception:  EXC_BREAKPOINT (0x0006)
Code[0]:    0x00000001
Code[1]:    0x92c10490


Thread 0 Crashed:
0   com.apple.Foundation  0x92c10490 _NSRaiseError + 264
1   com.apple.Foundation  0x92c101cc +[NSException raise:format:] + 40
2   com.apple.Foundation  0x92cd86a0 mutateError + 172
3   com.apple.Foundation  0x92c05820 -[NSCFString setString:] + 100
4   com.soulstorm.MMST2_3 0x000044e8 identifyExe(NSString*) + 456
5   com.soulstorm.MMST2_3 0x000062dc -[GeneralHandler getFlagFile] + 68
6   com.soulstorm.MMST2_3 0x00006e58 -[GeneralHandler reloadAll] + 148
7   com.soulstorm.MMST2_3 0x00005d24 -[GeneralHandler awakeFromNib] + 60
8   com.apple.Foundation  0x92bff9a8 -[NSSet makeObjectsPerformSelector:] + 164
9   com.apple.AppKit      0x938006c0 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 864
10  com.apple.AppKit      0x937ec8ec loadNib + 240
11  com.apple.AppKit      0x937ec344 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 716
12  com.apple.AppKit      0x93843814 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 156
13  com.apple.AppKit      0x938d364c +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 344
14  com.apple.AppKit      0x938d33ec NSApplicationMain + 344
15  com.soulstorm.MMST2_3 0x000021d8 _start + 760
16  com.soulstorm.MMST2_3 0x00001edc start + 48

Thread 0 crashed with PPC Thread State 64:
  srr0: 0x0000000092c10490 srr1: 0x000000000202f030                        vrsave: 0x0000000000000000
    cr: 0x24000442          xer: 0x0000000000000007   lr: 0x0000000092c10468  ctr: 0x0000000092bd221c
    r0: 0x0000000000000000   r1: 0x00000000bffff560   r2: 0x00000000a2bcf508   r3: 0x00000000bffff110
    r4: 0x0000000000000000   r5: 0x0000000092bd1b44   r6: 0x00000000bffff194   r7: 0x00000000000000ff
    r8: 0x00000000bffff180   r9: 0x000000000051e9d0  r10: 0x0000000090a3f628  r11: 0x0000000024000442
   r12: 0x0000000092bd221c  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
   r16: 0x0000000000000002  r17: 0x00000000a381c078  r18: 0x00000000a381c078  r19: 0x00000000a381c078
   r20: 0x00000000a381c078  r21: 0x0000000000000000  r22: 0x0000000000010000  r23: 0x00000000005542c0
   r24: 0x0000000000010000  r25: 0x0000000000010000  r26: 0x00000000000137f8  r27: 0x0000000090ab4f74
   r28: 0x0000000000589a60  r29: 0x00000000a2bd71c8  r30: 0x00000000005542c0  r31: 0x0000000092c10398

Binary Images Description:
    0x1000 -    0x12fff com.soulstorm.MMST2_3 ??? (3.1) /Volumes/500K/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
   0x23000 -    0x30fff org.andymatuschak.Sparkle ??? (1.1) /Volumes/500K/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
   0x3c000 -    0x4cfff AGRegex ??? (0.1) /Volumes/500K/Giochi 500K/Freespace 2/FS2_Launcher.app/Contents/Frameworks/AGRegex.framework/Versions/A/AGRegex
  0x205000 -   0x2e7fff com.apple.WebKit 4530 (4530.17) /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
  0x37b000 -   0x493fff com.apple.JavaScriptCore 4530 (4530.17) /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
 0x1008000 -  0x19cdfff com.apple.WebCore 4530 (4530.17) /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
0x8fe00000 - 0x8fe52fff dyld 46.16 /usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x9021b000 - 0x90268fff com.apple.CoreText 1.0.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x90293000 - 0x90344fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x90373000 - 0x9072efff com.apple.CoreGraphics 1.258.84 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x907bb000 - 0x90895fff com.apple.CoreFoundation 6.4.11 (368.35) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x908de000 - 0x908defff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x908e0000 - 0x909e2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a3c000 - 0x90ac0fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90aea000 - 0x90b5cfff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90b72000 - 0x90b84fff libauto.dylib /usr/lib/libauto.dylib
0x90b8b000 - 0x90e62fff com.apple.CoreServices.CarbonCore 681.19 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x90ec8000 - 0x90f48fff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x90f92000 - 0x90fd4fff com.apple.CFNetwork 4.0 (129.24) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x90fe9000 - 0x91001fff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServicesCore.framework/Versions/A/WebServicesCore
0x91011000 - 0x91092fff com.apple.SearchKit 1.0.8 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x910d8000 - 0x91101fff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x91112000 - 0x91120fff libz.1.dylib /usr/lib/libz.1.dylib
0x91123000 - 0x912defff com.apple.security 4.6 (29770) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x913dd000 - 0x913e6fff com.apple.DiskArbitration 2.1.2 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x913ed000 - 0x913f5fff libbsm.dylib /usr/lib/libbsm.dylib
0x913f9000 - 0x91421fff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x91434000 - 0x9143ffff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x91444000 - 0x914bffff com.apple.audio.CoreAudio 3.0.5 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x914fc000 - 0x914fcfff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x914fe000 - 0x91536fff com.apple.AE 312.2 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x91551000 - 0x91623fff com.apple.ColorSync 4.4.11 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x91676000 - 0x91707fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x9174e000 - 0x91805fff com.apple.QD 3.10.28 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x91842000 - 0x918a0fff com.apple.HIServices 1.5.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x918cf000 - 0x918f0fff com.apple.LangAnalysis 1.6.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x91904000 - 0x91929fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/FindByContent.framework/Versions/A/FindByContent
0x9193c000 - 0x9197efff com.apple.LaunchServices 183.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x9199a000 - 0x919aefff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x919bc000 - 0x91a02fff com.apple.ImageIO.framework 1.5.8 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x91a19000 - 0x91ae0fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x91b2e000 - 0x91b43fff libcups.2.dylib /usr/lib/libcups.2.dylib
0x91b48000 - 0x91b66fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91b6c000 - 0x91c23fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91c72000 - 0x91c76fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91c78000 - 0x91ce2fff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x91ce7000 - 0x91d01fff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x91d06000 - 0x91d09fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x91d0b000 - 0x91df9fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x91e18000 - 0x91e56fff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x91e5d000 - 0x91e5dfff com.apple.Accelerate 1.2.2 (Accelerate 1.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x91e5f000 - 0x91f44fff com.apple.vImage 2.4 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x91f4c000 - 0x91f6bfff com.apple.Accelerate.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x91fd7000 - 0x92045fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x92050000 - 0x920e5fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x920ff000 - 0x92687fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x926ba000 - 0x929e5fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x92a15000 - 0x92b03fff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x92b06000 - 0x92b8efff com.apple.DesktopServices 1.3.7 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x92bcf000 - 0x92e02fff com.apple.Foundation 6.4.12 (567.42) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92f35000 - 0x92f53fff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x92f5e000 - 0x92fb8fff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92fd6000 - 0x92fd6fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92fd8000 - 0x92fecfff com.apple.ImageCapture 3.0 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x93004000 - 0x93014fff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x93020000 - 0x93035fff com.apple.securityhi 2.0 (203) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x93047000 - 0x930cefff com.apple.ink.framework 101.2 (69) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x930e2000 - 0x930edfff com.apple.help 1.0.3 (32) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x930f7000 - 0x93125fff com.apple.openscripting 1.2.7 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x9313f000 - 0x9314efff com.apple.print.framework.Print 5.2 (192.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x9315a000 - 0x931c0fff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x931f1000 - 0x93240fff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x9326e000 - 0x9328bfff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x9329d000 - 0x932aafff com.apple.CommonPanels 1.2.2 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x932b3000 - 0x935c1fff com.apple.HIToolbox 1.4.10 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x93711000 - 0x9371dfff com.apple.opengl 1.4.7 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x937b6000 - 0x937d6fff libmx.A.dylib /usr/lib/libmx.A.dylib
0x937dc000 - 0x937dcfff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x937de000 - 0x93e11fff com.apple.AppKit 6.4.10 (824.48) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x9419e000 - 0x94210fff com.apple.CoreData 91 (92.1) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x94249000 - 0x9430efff com.apple.audio.toolbox.AudioToolbox 1.4.7 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x94361000 - 0x94361fff com.apple.audio.units.AudioUnit 1.4 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x94363000 - 0x94523fff com.apple.QuartzCore 1.4.12 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x9456d000 - 0x945aafff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
0x945b2000 - 0x94602fff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x9460b000 - 0x94624fff com.apple.CoreVideo 1.4.2 /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x947dd000 - 0x947ecfff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x947f4000 - 0x94801fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x94c82000 - 0x94cf3fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib

Model: PowerMac10,1, BootROM 4.8.9f4, 1 processors, PowerPC G4  (1.2), 1.42 GHz, 512 MB
Graphics: ATI Radeon 9200, ATY,RV280, AGP, 32 MB
Memory Module: DIMM0/J11, 512 MB, DDR SDRAM, PC3200U-30330
AirPort: AirPort Extreme, 405.1 (3.90.34.0.p18)
Bluetooth: Version 1.9.5f4, 2 service, 1 devices, 1 incoming serial ports
Network Service: Ethernet integrata, Ethernet, en0
Parallel ATA Device: ST9808210A, 74.53 GB
Parallel ATA Device: MAT****ACD-RW  CW-8124
USB Device: USB2.0 Hub, Up to 480 Mb/sec, 500 mA
USB Device: LaCie Desktop Hard Drive, LaCie, Up to 480 Mb/sec, 500 mA
USB Device: Logitech USB Headset, Logitech, Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on June 25, 2009, 02:30:12 am
 Try deleting the preferences, and deleting the FS2_Open Folder inside your library as well. Does it still have the same problem? Was it working before, and suddenly stopped?

Also, the report you have submitted, will not help me, as the real report I want resides in the console application, in the file called system.log and also in the file called "console messages". That's where the Launcher writes its output.
Title: Re: FS2_Launcher OS X 3.0
Post by: 134th Barracudas on June 27, 2009, 10:05:52 am
Try deleting the preferences, and deleting the FS2_Open Folder inside your library as well. Does it still have the same problem? Was it working before, and suddenly stopped?

Also, the report you have submitted, will not help me, as the real report I want resides in the console application, in the file called system.log and also in the file called "console messages". That's where the Launcher writes its output.
I fixed it, just deleted command_line.pxo. I'll post you the console message as soon as I get back home
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on June 28, 2009, 03:45:58 pm
Please let me know if that problem appears again. If that happens, then please post the EXACT (even if a file appears to be empty, there might be spaces in it ;) ) contents of the file, even its size (in the Finder's get info window).
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on June 28, 2009, 05:23:21 pm
I've had this happen before, and another thread in cross platform development was just started that I think is the same problem.  I think it has something to do with the existence or lack of a hanging new line or space at the end of the file, but I haven't run the launcher recently myself to double check.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on July 04, 2009, 08:38:18 am
There might be such a problem, although I think I have fixed that in one of the latest versions. If that problem still exists, I think I will have to look into the code once again, and release a patch.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on July 06, 2009, 12:39:37 am
I seemed to recall it being fixed as well, so I was surprised to see it cropping up, unless it's just because a non-updated version was used.  Could be, since I don't believe the version I last downloaded from the website was the latest version at the time.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on July 07, 2009, 03:30:44 am
I seemed to recall it being fixed as well, so I was surprised to see it cropping up, unless it's just because a non-updated version was used.  Could be, since I don't believe the version I last downloaded from the website was the latest version at the time.

It isn't. To get the most updated version, you must hit the "check for updates" button.
Title: Re: FS2_Launcher OS X 3.0
Post by: Galemp on July 08, 2009, 11:03:21 pm
Can anyone point me in the direction of the LATEST version of the launcher? Soulstorm's website isn't current, and the only links I've found are ones to deleted attachments.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on July 08, 2009, 11:18:29 pm
That's what he was just talking about, get the website version, and then do an update from within the program.  I'm not aware of any direct link to the latest version.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on July 09, 2009, 09:01:50 am
Can anyone point me in the direction of the LATEST version of the launcher? Soulstorm's website isn't current, and the only links I've found are ones to deleted attachments.

Wait ... you use a Mac? :eek:
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on July 09, 2009, 10:21:35 am
He seems to be asking a few mac related questions recently, my guess is he just stumbled across one recently.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on July 09, 2009, 06:30:59 pm
Can anyone point me in the direction of the LATEST version of the launcher? Soulstorm's website isn't current, and the only links I've found are ones to deleted attachments.

As I posted previously, if you use an outdated version of the Launcher, and hit the "Check for Updates" button in the application's "File" menu, you will be able to download the newest version without having to search anywhere.

But, since you still have problems, and since I imagine that many people are in the same situation as you, I have updated the link in my website. No need to visit it, though. Click here (http://www.soulstorm-creations.com/PROJECT_SOULSTORM_2_0/SOULSTORM_CUSTOM_FILES/FS2_Launcher_3_1.zip).

Next time, though, hit the Check For Updates button. Chances are that I release a new version, while having my website link unchanged.
Title: Re: FS2_Launcher OS X 3.0
Post by: Galemp on July 09, 2009, 06:37:40 pm
Oh there we go. I was asking because the bloody thing wouldn't even launch--I had to delete the command line cfg file, then it would launch, and then I could update.

And I've been asking Mac and Linux questions because I'm switching over to Ubuntu, while my friend here has a Mac and we're trying to play local multi.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on July 10, 2009, 02:28:27 am
All of you who are using the Launcher for OS X and check in this thread often, please go here. It is important to read (http://www.hard-light.net/forums/index.php/topic,64302.0.html).
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on July 10, 2009, 04:35:39 am
Well, the Launcher gets hosted elsewhere now, and the check for Updates button will stop working, unless you read this post (http://www.hard-light.net/forums/index.php/topic,64302.msg1267708.html#msg1267708).

I have also updated the read me which is also hosted into a new location (http://soulstorm-creations.com/support/fs2_launcher/readme.html) with clarifications and how-to regarding the support of additional standalone mods, and some other things.
Title: Re: FS2_Launcher OS X 3.0
Post by: wolf123450 on July 27, 2009, 12:42:35 pm
When I try to start the launcher, it just quits.  It was working before, but after I changed the application path, it stopped working.  Even after successive redownloads, reinstallation of FS2 itself, and removal of the FS2_Open folder in my Library.  I found the console messages log and it is here:
Code: [Select]
7/27/09 11:27:38 AM FS2_Launcher[1500] 1
7/27/09 11:27:38 AM FS2_Launcher[1500] adsasdasdasFS2_Open
7/27/09 11:27:38 AM FS2_Launcher[1500] parsing file at: /Users/clint/Library/FS2_Open/fs2_open.ini for screen properties...
7/27/09 11:27:38 AM FS2_Launcher[1500] found mod folder: /Users/clint/Library/FS2_Open
7/27/09 11:27:38 AM FS2_Launcher[1500] 1
7/27/09 11:27:38 AM FS2_Launcher[1500] /Applications/FS2_Launcher.app
7/27/09 11:27:38 AM FS2_Launcher[1500] Unable to identify Exe at the given location
7/27/09 11:27:38 AM FS2_Launcher[1500] Making User Interface...
7/27/09 11:27:38 AM [0x0-0xc20c2].com.soulstorm.MMST2_3[1500] sh: /Applications/FS2_Launcher.app/Contents/MacOS/: No such file or directory
7/27/09 11:27:38 AM [0x0-0xc20c2].com.soulstorm.MMST2_3[1500] FS2_Launcher(1500) malloc: *** mmap(size=2684354560) failed (error code=12)
7/27/09 11:27:38 AM [0x0-0xc20c2].com.soulstorm.MMST2_3[1500] *** error: can't allocate region
7/27/09 11:27:38 AM [0x0-0xc20c2].com.soulstorm.MMST2_3[1500] *** set a breakpoint in malloc_error_break to debug
7/27/09 11:27:40 AM com.apple.launchd[85] ([0x0-0xc20c2].com.soulstorm.MMST2_3[1500]) Exited abnormally: Bus error

The location of my freespace folder is /Applications/Freespace2
I'm using Max OS X Version 10.5.7
Any ideas?

EDIT: When looking back over the command line to when I first started the launcher, I realize I made some stupid mistakes. Anyway, I started fiddling with the launcher before I had FS2 installed.  This was a problem, since I directed it to look for itself in my /Applications folder.  Which also explains why it opens up 300 of itself when I open it from the Applications folder.  Silly me.  I know just enough about computers to get me into trouble and then figure out why.  Getting back out again? Not so easy.  

Anyway, how do I fix that, when it won't open anymore?

EDIT2:
I'm using the FS2_launcher version 3.1.1

Further attempts to fix the problem include: I removed the com.soulstorm.MMST2_3.plist file, reinserted it, edited said file to not point at itself, and reremoved it and now the only change is that It tells me it is going to select default preferences before it crashes/quits.

new console message log:
Code: [Select]
7/27/09 2:19:10 PM FS2_Launcher[2211] 1
7/27/09 2:19:11 PM FS2_Launcher[2211] found mod folder: /Users/clint/Library/FS2_Open
7/27/09 2:19:11 PM FS2_Launcher[2211] 1
7/27/09 2:19:11 PM FS2_Launcher[2211] adsasdasdasFS2_Open
7/27/09 2:19:11 PM FS2_Launcher[2211] parsing file at: /Users/clint/Library/FS2_Open/fs2_open.ini for screen properties...
7/27/09 2:19:11 PM FS2_Launcher[2211] /Users/clint/Applications/FS2_Open.app
7/27/09 2:19:11 PM FS2_Launcher[2211] Unable to identify Exe at the given location
7/27/09 2:19:11 PM FS2_Launcher[2211] Making User Interface...
7/27/09 2:19:11 PM [0x0-0x12b12b].com.soulstorm.MMST2_3[2211] sh: /Users/clint/Applications/FS2_Open.app/Contents/MacOS/: No such file or directory
7/27/09 2:19:11 PM [0x0-0x12b12b].com.soulstorm.MMST2_3[2211] FS2_Launcher(2211,0xa05e2720) malloc: *** mmap(size=2684354560) failed (error code=12)
7/27/09 2:19:11 PM [0x0-0x12b12b].com.soulstorm.MMST2_3[2211] *** error: can't allocate region
7/27/09 2:19:11 PM [0x0-0x12b12b].com.soulstorm.MMST2_3[2211] *** set a breakpoint in malloc_error_break to debug
7/27/09 2:19:13 PM com.apple.launchd[85] ([0x0-0x12b12b].com.soulstorm.MMST2_3[2211]) Exited abnormally: Bus error
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on July 27, 2009, 02:05:19 pm
There are solution(s) for the launcher won't start bug in this thread, you might have to look for a little while.  I can't remember them off the top of my head.  If you've found a new cause (and are running the most up to date version) I'm sure Soulstorm will be around shortly to help you out.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on August 04, 2009, 05:59:44 pm
Sorry for not replying earlier, I was on vacation. So, let's see, one thing at a time.

From the looks of your bug report, seems there is a major problem with the Launcher trying to find the actual executable inside the FS2_Open Application. Normally, the Launcher would complain, and it would start up with no menus being displayed whatsoever. I am trying to reproduce the behavior you mention, with no luck. Of course, pointing the Launcher into itself resulting in 300 copies of the launcher being launched, which will be surely fixed.

First of all, I recommend you use the latest version of the Launcher. You said you had 3.1 version, but the latest version is 3.1.1. Due to server changes, the latest one will not be shown via the "Check for Updates" button. You must head over to my site to download version 3.1.1. From then on, you will be able to update properly.

Now, on to your problem. I must admit, that this is strange, because I can't reproduce the bug no matter what I do. So, since you seem a bit disoriented, we will do it one step at a time.

First, delete the file named com.soulstorm.MMST2_3.plist in your user's preferences folder. Do not alter it, do not put it back. just delete it. Start up the application.

If that does not work, then delete the preferences file again, but this time, also delete the folder named "FS2_Open" inside your user's Library.

That should do it. If not, post back the crash log again, as you did before, and also post a screenshot with the entire contents of your Freespace2 folder (only the first level). The Launcher had some problems with mod.ini parsing in the past, and maybe not all of those problems were eliminated. Perhaps it is a filename issue? We'll see.

If I am able to reproduce the bug, I will be able to fix it in a day or two.
Title: Re: FS2_Launcher OS X 3.0
Post by: neoterran on September 04, 2009, 02:21:27 pm
Just wanted to thank you for your work SoulStorm. Although you may not realize it, your work and time here helping people helps thousands of people on macs play Freespace 2 in their spare time. For that, we salute you.

Three Cheers for SoulStorm....

Hip Hip ....
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on September 11, 2009, 06:27:33 pm
Thanks a lot for your good words..! It's always good to see satisfied users! The work behind Fs2_Open is admirable, and I am really happy to even handle some basic aspects of this big project such as the Launcher for OS X.

I had my semester exams, and I didn't notice that anti-aliasing has been implemented into FS2_Open (thanks, blowfish). Expect a new version of the Launcher with anti-aliasing support to be released pretty soon!
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on September 13, 2009, 01:15:49 pm
A new patch is out, but I haven't commit the change yet. I need someone to test this new version before I release it.

You can download the new version (in beta) here: http://www.soulstorm-creations.com/tests/FS2_Launcher-beta.zip
Title: Re: FS2_Launcher OS X 3.0
Post by: GreyKat on January 14, 2010, 08:42:13 pm
Hello Soulstorm, I have the same problem people have mentionned before when starting your launcher after
I changed the app path.

I get this from the console:
2010-01-14 11:59:18.621 FS2_Launcher[53778:903] 1
2010-01-14 11:59:18.641 FS2_Launcher[53778:903] found mod folder: /Users/ddouvill/Library/FS2_Open
2010-01-14 11:59:18.645 FS2_Launcher[53778:903] 1
2010-01-14 11:59:18.646 FS2_Launcher[53778:903] /Users/ddouvill/Freespace2/FS2_Open-3.6.10.app
2010-01-14 11:59:18.647 FS2_Launcher[53778:903] An uncaught exception was raised
2010-01-14 11:59:18.648 FS2_Launcher[53778:903] *** -[NSCFString setString:]: nil argument
2010-01-14 11:59:18.649 FS2_Launcher[53778:903] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFString setString:]: nil argument'
*** Call stack at first throw:
(
   0   CoreFoundation                      0x95da740a __raiseError + 410
   1   libobjc.A.dylib                     0x9480e509 objc_exception_throw + 56
   2   CoreFoundation                      0x95da7138 +[NSException raise:format:arguments:] + 136
   3   CoreFoundation                      0x95da70aa +[NSException raise:format:] + 58
   4   Foundation                          0x962304a2 mutateError + 156
   5   FS2_Launcher                        0x00003bec _Z11identifyExeP8NSString + 386
   6   FS2_Launcher                        0x00005955 -[GeneralHandler getFlagFile] + 47
   7   FS2_Launcher                        0x0000663e -[GeneralHandler reloadAll] + 124
   8   FS2_Launcher                        0x0000532c -[GeneralHandler awakeFromNib] + 28
   9   CoreFoundation                      0x95d40b34 -[NSSet makeObjectsPerformSelector:] + 196
   10  AppKit                              0x90a01478 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1566
   11  AppKit                              0x909ff450 loadNib + 257
   12  AppKit                              0x909feaa3 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 831
   13  AppKit                              0x909fe759 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 158
   14  AppKit                              0x909fe6a4 +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 383
   15  AppKit                              0x909fb4a9 NSApplicationMain + 434
   16  FS2_Launcher                        0x000023fe _start + 216
   17  FS2_Launcher                        0x00002325 start + 41
)
Trace/BPT trap

The weird thing is, it worked flawlessly on my home computer but not on my work laptop.
My guess is (as a fellow Mac developer) that at work I use the case sensitive HFS filesystem, and your code
that locates the binary inside the .app must have a lower/upper case typo that doesn't create any problem on a case insensitive filesystem (which I have at home).

Hope that helps.

GreyKat
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 15, 2010, 02:47:59 am
Thanks for the heads up. From the console, it seems not to be related to letter case sensitivity.

The problem that people have mentioned before is the symptom, not the cause, as each one of them couldn't start the launcher for different reasons. Anyway, I will look into the matter today. Don't know what time is it in your country, but here is early morning, so, I will look at it in the evening, when I get back from work.

Thing is, the Launcher needs a rewrite, but I don't have the time to do it. And in an early thread for the next major upgrade (http://www.hard-light.net/forums/index.php?topic=65808.0) (a complete rewrite), people didn't seem much acceptance for a new version for OS X- only, so I decided not to do it at the time.

I was away from the forums for a while because I have a real work now as a freelancer, and I imagined that my little launcher would have been replaced. Seems this is not the case, as I still see many users and I may need to reconsider making FS2_Launcher 4. Time will tell.

Until I see what's wrong, I need you to delete the Launcher's preferences and your command line file. Refer to this page (http://www.soulstorm-creations.com/support/fs2_launcher/readme.html) to see how you will do that. If the problem persists, please post back here, with the console crash report.
Title: Re: FS2_Launcher OS X 3.0
Post by: GreyKat on January 15, 2010, 03:33:32 pm
I already deleted the preference file and the command line file over 10 times.
There really is something up with the path to the FreeSpace application cause your launcher boots up fine as long as I don't
change it to my installation directory.

I can look at the code if you want, but I completely understand if you don't want to show it to a pure stranger which is at his 2nd post on the forum.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 16, 2010, 05:02:28 am
I may do that, as a last solution. Give me some time to see what the problem is. I haven't looked at anything yet, due to my loaded schedule. I will look at it soon, after I create a case sensitive Journaled file system to experiment with. I have an external HDD that may do the trick.

As for the code, I may give it to you, if I fail to find the problem, or if I don't manage to reproduce it, but be warned: the code is a MESS. I wrote it some years ago, during my first steps in programming for Mac. I would surely do things much different now, that's why I am trying to find the time to rewrite it.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on January 16, 2010, 05:20:50 pm
You can also just use the Disk Utility tool to shrink your main partition a bit and create a new HFS+ with Case sensitivity partition on your main drive.  We do that at work for our local dev server environment.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 17, 2010, 03:44:39 am
My primary disk has suffered so much after I tried to install Linux in it, that I want to leave it intact at the moment... :)
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on January 17, 2010, 01:35:02 pm
Ah yeah.  Mine is so buttraped after putting Ubuntu on it that I can't even use Disk Utility on it anymore.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on January 28, 2010, 04:39:14 pm
Just wanted to let you know, guys that I haven't been able to reproduce the problem. However, I have an idea about that. I will test it in the weekend, and will post back the results.

Sorry for taking so long, but I really don't have the time to test it more at the time...
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on January 29, 2010, 05:21:55 am
At least you still give updates more frequently than most of the FreeSpace mods here. :p

:warp:
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on February 03, 2010, 04:41:52 am
Good news, people (sort of).

I managed to reproduce the problem. And I have found the exact line that crashes the problem. I haven't got a clue as to why it crashes. But at least I managed to see the circumstances which produce the fault.

More info in short time...

EDIT: Success! The new version will be uploaded later today.
PS. The Launcher really needs a rewrite. I have XCode complaining about deprecated frameworks... :)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on February 03, 2010, 07:05:08 am
Done. those of you who can't download the update from inside the application (since it doesn't open), you can download it here:

http://www.soulstorm-creations.com/support/fs2_launcher/FS2_Open_Launcher_3.1.3.dmg (http://www.soulstorm-creations.com/support/fs2_launcher/FS2_Open_Launcher_3.1.3.dmg)
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on February 03, 2010, 09:42:57 am
(http://lh3.ggpht.com/_MsZb8mYFoCs/SX6Euq2GxbI/AAAAAAAAEtI/5jur3Ejf9hA/s800/28aki86.jpg)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on February 04, 2010, 02:28:36 am
I wish I knew what that meant... :)
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on February 05, 2010, 02:10:41 am
It seems my site is down, due to server mishaps. They should renew my domain instantly after expiration, but they didn't. I expect my site to be back online within short time. I just resolved the matter.

Sorry for the inconvenience.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on February 06, 2010, 12:13:34 am
Was it down? I just updated the Launcher successfully.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on February 06, 2010, 07:15:30 am
It was, but the problem has been fixed.
Title: Re: FS2_Launcher OS X 3.0
Post by: clay_9 on July 07, 2010, 03:56:32 pm
Greetings people, first post and with a problem!
I have just downloaded FS2_open, 3.6.10 and the most recent version of Soulstorms v3 launcher. The launcher worked the first time, I directed it to where FS2_Open was located, I didn't do too much else, not even touched the mod options as was still reading up about the mediavps. I can't remember if it was on the first time it was loaded up, it may have been the second time, it crashed out.

And I haven't been able to boot it up since, trying to launch it brings an immediate FS2_Launcher quit unexpectedly dialog box. I have deleted the FS2_open folder under library and the com.soulstorm file in preferences, but still no luck (after deleteing these files it does first state it will create new preference files, it created the FS2 folder but interestingly the com.soulstorm file is not created again, it doesn't get that far before crashing.

The error log it generates is very long, would it help to post or is there something painfully obvious that I'm missing here?

Please help!!
Title: Re: FS2_Launcher OS X 3.0
Post by: clay_9 on July 07, 2010, 04:47:54 pm
Very strange, I've managed to fix this issue by copying all of the files onto an external drive and running the launcher from a different mac, then copying the FS2_Open and com.soulstorm files the new mac generated back to mac 1. And it now works!

I'm still getting a horrible graphical issue however which I'll probably post a new thread about.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on July 07, 2010, 10:17:25 pm
What version of OS X are you running on?  10.6.3 fixed a lot of Snow Leopard issues, and 10.6.4 was supposed to fix some more but incrementally updating seems to have broken a lot of people's OpenGL.
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on July 08, 2010, 04:47:52 pm
Very strange, I've managed to fix this issue by copying all of the files onto an external drive and running the launcher from a different mac, then copying the FS2_Open and com.soulstorm files the new mac generated back to mac 1. And it now works!

I'm still getting a horrible graphical issue however which I'll probably post a new thread about.

Glad to see that worked for you. Just for being sure this won't happen again, is it too much to ask to post your crash log if this happens again? I'm not looking for the console's crash reporter log, or the one that is being shown after the application crashes in the Finder.

What I want is to open your Console.app immediately when that happens, and under "DATABASE SEARCHES", please post the last lines of "All Messages" (specifically, from the one that refers to the FS2_Open startup and below, until the line that crashes).

I find your case rather strange, because I can't think of a reason the application doesn't work after deleting the preferences files, especially since it has worked before. I know you mentioned that you use the latest version of the Launcher, but can you post the exact version here (just to be sure)? It's in the "About" option when you open the Launcher.
Title: Re: FS2_Launcher OS X 3.0
Post by: clay_9 on July 09, 2010, 05:10:44 am
I'm running OS X 10.6.3 (haven't updated as I've heard bad things about .4 messing up a lot of stuff, including steam games so I've avoided that for now).

I have been running 3.1.3 of the launcher. But interestingly, during the period of time where it kept crashing I found an older version (3.0.3) I think it was, and that wouldn't open either, same immediate crash problem.

If it happens again I'll try to get the log you requested, but for the time being it's running along without any more problems.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on October 07, 2010, 06:20:54 pm
So just thought I'd see if Soulstorm is still checking in on this little baby of his.  I seem to have an issue where I cannot run the program without -no_glsl and -window, possibly others didn't look too close.  I would like to test out GLSL on my mac, and -window is probably overriding my -fullscreen_window setting too.  I've deleted the cmdline_fso.cfg, the launcher preferences file, etc, and I cannot get -no_glsl out of the log file.  Any tips?
Title: Re: FS2_Launcher OS X 3.0
Post by: Iss Mneur on October 08, 2010, 12:58:12 am
So just thought I'd see if Soulstorm is still checking in on this little baby of his.  I seem to have an issue where I cannot run the program without -no_glsl and -window, possibly others didn't look too close.  I would like to test out GLSL on my mac, and -window is probably overriding my -fullscreen_window setting too.  I've deleted the cmdline_fso.cfg, the launcher preferences file, etc, and I cannot get -no_glsl out of the log file.  Any tips?

Umm, as far as I can tell, -window and -fullscreen_window have no effect on SCP_UNIX builds.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on October 08, 2010, 09:59:43 am
Then how do you make it run in a window vs full screen?  I know I've managed to do both before.  One or the other of those works, and since -window worked before -fullscreen_window existed I'm guessing that's the one that still works.  It's also the one I can't turn off.
Title: Re: FS2_Launcher OS X 3.0
Post by: Iss Mneur on October 08, 2010, 10:25:26 am
Then how do you make it run in a window vs full screen?  I know I've managed to do both before.  One or the other of those works, and since -window worked before -fullscreen_window existed I'm guessing that's the one that still works.  It's also the one I can't turn off.

I have looked again and it seems I missed an important part, so as it stands now, -window should work on SCP_UNIX, though -no_grab may be needed as well for it to actually be useful.  -fullscreen_window definiatly will not work because:
Code: (cmdline.cpp, line 1066-1072) [Select]
if ( fullscreen_window_arg.found( ) )
{
#ifdef WIN32
Cmdline_fullscreen_window = 1;
Cmdline_window = 0; /* Make sure no-one sets both */
#endif
}

Obviously, both flags work fine on windows.

 As for the flags that won't die, make sure that you have removed the cmdline_fso.cfg files in both the game data dir, and in ~/.fs2_open/data.  That being said, the launcher may be forcing those flags without your input anyway, but unfortunately that is only something that only Soulstorm would be able to tell us.
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on October 08, 2010, 10:43:19 am
Gah!  The cmdline_fso.cfg in the root data folder.  That one seems to have been the culprit.  Dunno why it's even there, it wasn't recreated but it was definitely causing the problem.  Wonder if some changes to the Launcher could help that issue somehow.
Title: Re: FS2_Launcher OS X 3.0
Post by: Iss Mneur on October 08, 2010, 10:53:16 am
Gah!  The cmdline_fso.cfg in the root data folder.  That one seems to have been the culprit.  Dunno why it's even there, it wasn't recreated but it was definitely causing the problem.  Wonder if some changes to the Launcher could help that issue somehow.
Possibly left over from when you copied the TC directory from windows or from when you were testing wxLauncher (as it currently writes the cmdline_fso.cfg to the TC data folder).
Title: Re: FS2_Launcher OS X 3.0
Post by: Soulstorm on October 10, 2010, 08:33:00 am
So just thought I'd see if Soulstorm is still checking in on this little baby of his.  I seem to have an issue where I cannot run the program without -no_glsl and -window, possibly others didn't look too close.  I would like to test out GLSL on my mac, and -window is probably overriding my -fullscreen_window setting too.  I've deleted the cmdline_fso.cfg, the launcher preferences file, etc, and I cannot get -no_glsl out of the log file.  Any tips?

Yes, I am checking my little baby, though this baby is an old man now.

I can't do modifications as often as I could, nor will I be able to respond to messages as fast as before. This is due to the fulfillment of my army duties. Unfortunately, in Greece joining the army for 9 months is obligatory, and I had reached to a point where I  could not continue my work if I wasn't done with the army yet.

7 months are left. Due to this time, I will look into the Launcher as much as I can, but I can't promise anything, since our free time and our hours outside the camp are very limited.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on October 11, 2010, 09:45:37 am
Nine months isn't too long. I've got to do 24 next year.
Title: Re: FS2_Launcher OS X 3.0
Post by: bananaboy on October 19, 2010, 01:15:49 am
I'm having problems running FS2 Open using this launcher on a mac, but I think the problem lies with the binaries i'm using...

Still, I thought I'd chime in here to see if any of you had any ideas. Selecting the binary in the launcher yields:

"It appears that the application you have selected is not valid, the flag file that it produces in order to make the UI and other things cannot be found."

The reason I think the problem lies elsewhere, is because running the binary on its own generates a posix_spawn access denied error in the console and crashes instantly, so I suppose if the launcher queries the binaries for settings, I should at least get the binary to run first.

Still, any help would be greatly appreciated.
Title: Re: FS2_Launcher OS X 3.0
Post by: Iss Mneur on October 19, 2010, 09:40:47 am
I'm having problems running FS2 Open using this launcher on a mac, but I think the problem lies with the binaries i'm using...

Still, I thought I'd chime in here to see if any of you had any ideas. Selecting the binary in the launcher yields:

"It appears that the application you have selected is not valid, the flag file that it produces in order to make the UI and other things cannot be found."

The reason I think the problem lies elsewhere, is because running the binary on its own generates a posix_spawn access denied error in the console and crashes instantly, so I suppose if the launcher queries the binaries for settings, I should at least get the binary to run first.

Still, any help would be greatly appreciated.
What is the exact text of the posix_spawn error?
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on October 19, 2010, 09:51:08 am
This (http://www.hard-light.net/forums/index.php?topic=72141.0) is the other thread he posted in for help.
Title: Re: FS2_Launcher OS X 3.0
Post by: bananaboy on October 20, 2010, 02:11:05 am
I'm having problems running FS2 Open using this launcher on a mac, but I think the problem lies with the binaries i'm using...

Still, I thought I'd chime in here to see if any of you had any ideas. Selecting the binary in the launcher yields:

"It appears that the application you have selected is not valid, the flag file that it produces in order to make the UI and other things cannot be found."

The reason I think the problem lies elsewhere, is because running the binary on its own generates a posix_spawn access denied error in the console and crashes instantly, so I suppose if the launcher queries the binaries for settings, I should at least get the binary to run first.

Still, any help would be greatly appreciated.

Just to let you guys know, the problem has been resolved with the rev6627 nightly. It had nothing to do with the launcher.

Many thanks to chief1983 for the solution, and to Iss Mneur for taking the time to explore this issue. Oh, and soulstorm for the launcher =)
Title: Re: FS2_Launcher OS X 3.0
Post by: drummingasm on March 19, 2011, 01:54:41 pm
I can't get the launcher to open. It bounces on the dock a few times before giving me an unexpected error. I tried downloading previous version of the launcher which errored in the same way.

I have the latest versions of everything, including the 3.6.12 media vps from the turey installer, do they work with the launcher? I also have the inferno build v 3.6.12, is this compatible?
I can run fs2 open from the inferno build without any error whatsoever, but i can never get the launcher to work.

my specs:
mac  os x x 10.5.8
4GB DDR3
NVIDIA GeForce 9400M
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on March 20, 2011, 09:07:44 am
What's the error? Can you take a screenshot of it and attach it (CMD + SHIFT + 3)?
Title: Re: FS2_Launcher OS X 3.0
Post by: drummingasm on March 20, 2011, 03:13:10 pm
i don't know how to post pictures, but this is what it looks like:
http://gadgets.boingboing.net/gimages/comedy_crash.jpg
replace MDCrashReportTool with FS2_Launcher and it's the exact same.

this is the report, i don't know if it will help.


Code: [Select]
Process:         FS2_Launcher [438]
Path:            /Applications/Whatnot/Freespace/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
Identifier:      com.soulstorm.MMST2_3
Version:         ??? (3.1.3)
Code Type:       X86 (Native)
Parent Process:  launchd [69]

Interval Since Last Report:          67490 sec
Crashes Since Last Report:           18
Per-App Interval Since Last Report:  27 sec
Per-App Crashes Since Last Report:   10

Date/Time:       2011-03-20 13:10:17.147 -0700
OS Version:      Mac OS X 10.5.8 (9L31a)
Report Version:  6
Anonymous UUID:  95BDC2D4-1CE7-4B06-AFB3-093D138CAF0A

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread:  0

Thread 0 Crashed:
0   libSystem.B.dylib              0xffff0d3f __memcpy + 1439 (cpu_capabilities.h:246)
1   libSystem.B.dylib              0x95f473ad fread + 143
2   com.soulstorm.MMST2_3          0x00003882 fillVectorsWithParametersFromFile(char const*, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) + 424
3   com.soulstorm.MMST2_3          0x000095e2 -[GeneralHandler makeUI] + 314
4   com.soulstorm.MMST2_3          0x00007339 -[GeneralHandler reloadAll] + 141
5   com.soulstorm.MMST2_3          0x00005fe8 -[GeneralHandler awakeFromNib] + 28
6   com.apple.CoreFoundation      0x91c697f5 -[NSSet makeObjectsPerformSelector:] + 181
7   com.apple.AppKit              0x91d0ad8e -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1533
8   com.apple.AppKit              0x91d00fba loadNib + 264
9   com.apple.AppKit              0x91d0091c +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 946
10  com.apple.AppKit              0x91d0055f +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 171
11  com.apple.AppKit              0x91d0049d +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 391
12  com.apple.AppKit              0x91d0014c NSApplicationMain + 434
13  com.soulstorm.MMST2_3          0x0000349a _start + 216
14  com.soulstorm.MMST2_3          0x000033c1 start + 41

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0xffff0cfe  ebx: 0x95f47333  ecx: 0x00000034  edx: 0xfffff040
  edi: 0x00000fc0  esi: 0x010483cc  ebp: 0xbffff4e8  esp: 0xbffff4e0
   ss: 0x0000001f  efl: 0x00010283  eip: 0xffff0d3f   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x00000000

Binary Images:
    0x1000 -    0x12ff7 +com.soulstorm.MMST2_3 ??? (3.1.3) <1d614fc92a23428fbb526650b3e67be6> /Applications/Whatnot/Freespace/FS2_Launcher.app/Contents/MacOS/FS2_Launcher
   0x24000 -    0x30ff7 +org.andymatuschak.Sparkle ??? (1.1) /Applications/Whatnot/Freespace/FS2_Launcher.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
  0x900000 -   0x911fff +AGRegex ??? (0.1) /Applications/Whatnot/Freespace/FS2_Launcher.app/Contents/Frameworks/AGRegex.framework/Versions/A/AGRegex
0x14146000 - 0x144c5ff3  com.apple.RawCamera.bundle 3.0.2 (527) <981ab8346c346fa5f88601df06c56609> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x8fe00000 - 0x8fe2db43  dyld 97.1 (???) <458eed38a009e5658a79579e7bc26603> /usr/lib/dyld
0x90003000 - 0x900ebff3  com.apple.CoreData 100.2 (186.2) <44df326fea0236718f5ed64084e82270> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x900ec000 - 0x900f8ffe  libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x90160000 - 0x904fdfef  com.apple.QuartzCore 1.5.8 (1.5.8) <8dc9ad0616bf56ebba60d6353737ac4e> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x904fe000 - 0x9054fff7  com.apple.HIServices 1.7.1 (???) <ba7fd0ede540a0da08db027f87efbd60> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x9059f000 - 0x905a9feb  com.apple.audio.SoundManager 3.9.2 (3.9.2) <df077a8048afc3075c6f2d9e7780e78e> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x905aa000 - 0x90627feb  com.apple.audio.CoreAudio 3.1.2 (3.1.2) <782a08c44be4698597f4bbd79cac21c6> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x90628000 - 0x90902ff3  com.apple.CoreServices.CarbonCore 786.16 (786.16) <60b518e4ad02b91826240199a6311286> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x90953000 - 0x90d11fea  libLAPACK.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x90d12000 - 0x90d12ff8  com.apple.ApplicationServices 34 (34) <ee7bdf593da050bb30c7a1fc446eb8a6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x90d86000 - 0x90eceff7  com.apple.ImageIO.framework 2.0.7 (2.0.7) <acf821a3c418fdc86ef02b654366f5f6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x90ecf000 - 0x91021ff3  com.apple.audio.toolbox.AudioToolbox 1.5.3 (1.5.3) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x91022000 - 0x91032fff  com.apple.speech.synthesis.framework 3.7.1 (3.7.1) <273d96ff861dc68be659c07ef56f599a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x91033000 - 0x9104bfff  com.apple.openscripting 1.2.8 (???) <a6b446eb8ec7844096df5fb9002f5c7b> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x9104c000 - 0x91054fff  com.apple.DiskArbitration 2.2.1 (2.2.1) <2664eeb3a4d0c95a21c089892a0ae8d0> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x91055000 - 0x9105afff  com.apple.CommonPanels 1.2.4 (85) <c135f02edd6b2e2864311e0b9d08a98d> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x91103000 - 0x91132fe3  com.apple.AE 402.3 (402.3) <aee412511c8725cd1a2cfb6501316bd5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x9113f000 - 0x9120afef  com.apple.ColorSync 4.5.3 (4.5.3) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x9120b000 - 0x91265ff7  com.apple.CoreText 2.0.5 (???) <5483518a613464d043455ac661a9dcbe> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x9129d000 - 0x91330ff3  com.apple.ApplicationServices.ATS 3.8 (???) <e61b0945da6ab368348a927f7428ad67> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x91331000 - 0x91346ffb  com.apple.ImageCapture 5.0.2 (5.0.2) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x91347000 - 0x919e7fef  com.apple.CoreGraphics 1.409.7 (???) <7b65edcce394f39b6a1954d5e30bc34c> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x91a9d000 - 0x91a9dff8  com.apple.Cocoa 6.5 (???) <a1bc9247cf65c20f1a44d0973cbe649c> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x91a9e000 - 0x91aacffd  libz.1.dylib ??? (???) <a98b3b221a72b54faf73ded3dd7000e5> /usr/lib/libz.1.dylib
0x91aad000 - 0x91ab4fe9  libgcc_s.1.dylib ??? (???) <e280ddf3f5fb3049e674edcb109f389a> /usr/lib/libgcc_s.1.dylib
0x91ab5000 - 0x91b48fff  com.apple.ink.framework 101.3 (86) <d4c85b5cafa8027fff042b84a8be71dc> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x91b49000 - 0x91b6dfff  libxslt.1.dylib ??? (???) <f0872c9ba3c17861fba8c45a3647cee1> /usr/lib/libxslt.1.dylib
0x91b6e000 - 0x91ca1fe7  com.apple.CoreFoundation 6.5.7 (476.19) <a332c8f45529ee26d2e9c36d0c723bad> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x91ca2000 - 0x91cd9fff  com.apple.SystemConfiguration 1.9.2 (1.9.2) <eab546255ac099b9616df999c9359d0e> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x91cda000 - 0x91cf9ffa  libJPEG.dylib ??? (???) <d23f3f3b9d168bf32f89449f83fa07f7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91cfa000 - 0x924f8fef  com.apple.AppKit 6.5.9 (949.54) <4df5d2e2271175452103f789b4f4d8a8> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x924f9000 - 0x925a0feb  com.apple.QD 3.11.57 (???) <35f058678972d42b88ebdf652df79956> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x925a1000 - 0x925fdff7  com.apple.htmlrendering 68 (1.1.3) <1c5c0c417891b920dfe139385fc6c155> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x925fe000 - 0x925feffc  com.apple.audio.units.AudioUnit 1.5 (1.5) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x925ff000 - 0x92606ffe  libbsm.dylib ??? (???) <fa7ae5f1a621d9b69e7e18747c9405fb> /usr/lib/libbsm.dylib
0x92956000 - 0x92a37ff7  libxml2.2.dylib ??? (???) <b3bc0b280c36aa17ac477b4da56cd038> /usr/lib/libxml2.2.dylib
0x92a38000 - 0x92a3fff7  libCGATS.A.dylib ??? (???) <29154398dbefc2a1a97715e5af1e3552> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x92aa9000 - 0x92b02ff7  libGLU.dylib ??? (???) <a08a753efc35f8a27f9c8f938fa01101> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92b03000 - 0x92baafec  com.apple.CFNetwork 438.16 (438.16) <dbf00ca36a09edfae60ec44f9d7a9ef9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x92bab000 - 0x92beafef  libTIFF.dylib ??? (???) <a5991d757f0c17a9bb8b1bcb14ab9ec0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x92beb000 - 0x92bebffd  com.apple.Accelerate 1.4.2 (Accelerate 1.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x92c29000 - 0x92c32fff  com.apple.speech.recognition.framework 3.7.24 (3.7.24) <da2d8411921a3fd8bc898dc753b7f3ee> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x92c33000 - 0x92d13fff  libobjc.A.dylib ??? (???) <d1469bf9fe852864d4fff185c72768e8> /usr/lib/libobjc.A.dylib
0x92d14000 - 0x92da1ff7  com.apple.framework.IOKit 1.5.2 (???) <7a3cc24f78f93931731203854ae0d891> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x92da2000 - 0x92e2fff7  com.apple.LaunchServices 292 (292) <a41286c7c1eb20ffd5cc796f791070f0> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x92f7b000 - 0x93082ff7  com.apple.WebKit 5533.19 (5533.19.4) <9299024ba5d2d796781e6d7312fae16a> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x93083000 - 0x930aefe7  libauto.dylib ??? (???) <2e44c523b851e8e25f05d13a48070a58> /usr/lib/libauto.dylib
0x930af000 - 0x930cdfff  libresolv.9.dylib ??? (???) <39f6d8651f3dca7a1534fa04322e6763> /usr/lib/libresolv.9.dylib
0x930ce000 - 0x930cefff  com.apple.Carbon 136 (136) <2ea8decb44f41c4f2fc6fe93e0a53174> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x9310a000 - 0x9310efff  libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x932df000 - 0x93391ffb  libcrypto.0.9.7.dylib ??? (???) <d02f7e5b8a68813bb7a77f5edb34ff9d> /usr/lib/libcrypto.0.9.7.dylib
0x93517000 - 0x9352dfff  com.apple.DictionaryServices 1.0.0 (1.0.0) <7d20b8d1fb238c3e71d0fa6fda18c4f7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x9352e000 - 0x9352effd  com.apple.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x9352f000 - 0x9355cfeb  libvDSP.dylib ??? (???) <4daafed78a471133ec30b3ae634b6d3e> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x93582000 - 0x93a53f76  libGLProgrammability.dylib ??? (???) <bf7fb226cbb412edfa377537c3e35877> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x93b8d000 - 0x93ba8ff3  libPng.dylib ??? (???) <c0791798fb92acc136c250a373449359> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x93ba9000 - 0x93ba9ffd  com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x93baa000 - 0x93c71ff2  com.apple.vImage 3.0 (3.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x93c72000 - 0x93c7ffe7  com.apple.opengl 1.5.10 (1.5.10) <95c3d857570a137d0e8285c9eafa1112> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x93c80000 - 0x93efcfe7  com.apple.Foundation 6.5.9 (677.26) <c68b3cff7864959becfc7fd1a384f925> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x93efd000 - 0x93f87ff7  com.apple.DesktopServices 1.4.9 (1.4.9) <f5e51a76d315798371b3dd35a4d46d6c> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x93fcc000 - 0x94049fef  libvMisc.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x9404a000 - 0x940fafff  edu.mit.Kerberos 6.0.14 (6.0.14) <673f107cdae80c084774a27bc7bc46c1> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x941de000 - 0x943d6fff  com.apple.JavaScriptCore 5533.19 (5533.19.1) <a099821bc9203b1bba37aee855280e28> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x943d7000 - 0x94451ff8  com.apple.print.framework.PrintCore 5.5.4 (245.6) <3839795086b6857d3c60064dce8702b5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x948d9000 - 0x948d9ffa  com.apple.CoreServices 32 (32) <373d6a888f9204641f313bc6070ae065> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x94924000 - 0x94940ff3  com.apple.CoreVideo 1.6.1 (48.6) <186cb311c17ea8714e918273c86d3c13> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x94941000 - 0x9499effb  libstdc++.6.dylib ??? (???) <7d389389a99ce696726cf4c8980cc505> /usr/lib/libstdc++.6.dylib
0x9499f000 - 0x949a1fff  com.apple.securityhi 3.0 (30817) <db23f4bad9f63a606468a4047a69b945> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x949f4000 - 0x94e04fef  libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x94e39000 - 0x94ec0ff7  libsqlite3.0.dylib ??? (???) <7d1fcfae937da95c7d2b9bdea57e6dc0> /usr/lib/libsqlite3.0.dylib
0x95edb000 - 0x95edefff  com.apple.help 1.1 (36) <1a25a8fbb49a830efb31d5c0a52939cd> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x95edf000 - 0x95f08fff  libcups.2.dylib ??? (???) <2b0ab6b9fa1957ee940835d0cfd42894> /usr/lib/libcups.2.dylib
0x95f09000 - 0x96070ff3  libSystem.B.dylib ??? (???) <c8f52e158bf540cc000146ca8a705958> /usr/lib/libSystem.B.dylib
0x96090000 - 0x96090ffb  com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallServer
0x9624e000 - 0x96297fef  com.apple.Metadata 10.5.8 (398.26) <e4d268ea45379200f03cdc7c8bedae6f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x962a0000 - 0x9631fff5  com.apple.SearchKit 1.2.2 (1.2.2) <3b5f3ab6a363a4d8a2bbbf74213ab0e5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x9636f000 - 0x96371ff5  libRadiance.dylib ??? (???) <276f13ab6429e05b093a8dda251e3b53> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x96372000 - 0x96373ffc  libffi.dylib ??? (???) <eaf10b99a3fbc4920b175809407466c0> /usr/lib/libffi.dylib
0x96374000 - 0x9667cfe7  com.apple.HIToolbox 1.5.6 (???) <eece3cb8aa0a4e6843fcc1500aca61c5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x96683000 - 0x9673efe3  com.apple.CoreServices.OSServices 228.1 (228.1) <76fdc146b4d9937f9c5cbaa1512e0023> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x9673f000 - 0x9677dfff  libGLImage.dylib ??? (???) <b154e14c351ddc950d5228819201435e> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x9677e000 - 0x97278fff  com.apple.WebCore 5533.19 (5533.19.4) <9b91bb00c553ec746fdbe51abca306af> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
0x97279000 - 0x97284fe7  libCSync.A.dylib ??? (???) <06652e36188190ec04d294f49c68f28a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x97295000 - 0x97466ff3  com.apple.security 5.0.6 (37592) <0b25e1e4cc34431630f01edb3fdf54d1> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x974ee000 - 0x974f2fff  libGIF.dylib ??? (???) <36f7b0255a81d97c7b360c3b11b4e462> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x97503000 - 0x97513ffc  com.apple.LangAnalysis 1.6.5 (1.6.5) <d057feb38163121ffd871c564c692804> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x97514000 - 0x9764dff7  libicucore.A.dylib ??? (???) <f2819243b278259b9a622ea111ea5fd6> /usr/lib/libicucore.A.dylib
0x979ad000 - 0x979e7fe7  com.apple.coreui 1.2 (62) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x97dc0000 - 0x97e02fef  com.apple.NavigationServices 3.5.2 (163) <72cdc9d21f6690837870923e7b8ca358> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x97e6a000 - 0x97e70fff  com.apple.print.framework.Print 218.0.3 (220.2) <0b70ba17cbbe4d62a00bec91c8cc675e> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0xfffe8000 - 0xfffebfff  libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

[attachment deleted by ninja]
Title: Re: FS2_Launcher OS X 3.0
Post by: Tracer on April 26, 2011, 08:29:21 pm
I think I'm missing something here...how can I select the mediavps_3612 folder as my mod in this launcher? The box on the top left is only letting me choose FS2_Open.
Title: Re: FS2_Launcher OS X 3.0
Post by: Androgeos Exeunt on April 27, 2011, 12:47:49 am
You do not change mods from that list. You need to go to the Gameplay + Speed tab and click on the drop-down list in the Selected Mod field. A picture has been attached to this post for your reference.

The drop-down list at the top of the window applies only to standalone mods, i.e. mods that do not require any component of FS2_Open, such as the mediavps, to run. However, all standalone mods can still be run normally from the Selected Mods list. For instance, The Babylon Project, despite being standalone, can still be run as a mod if you place the relevant vps into a new subfolder and use the Selected Mods list to choose that folder.

On an additional note, if you want to run FS2 with retail eye-candy, all you need to do is select the text in the Selected Mods field and delete it. This disables all mods and runs only the vps stored in the root folder.

[attachment deleted by ninja]
Title: Re: FS2_Launcher OS X 3.0
Post by: Tracer on April 27, 2011, 08:10:39 pm
Yay!
Title: Re: FS2_Launcher OS X 3.0
Post by: Hoot on April 04, 2013, 10:57:01 am
Just a note on maybe confusing behaviour I had encoundered here (http://www.hard-light.net/forums/index.php?topic=80146.msg1682557#msg1682557):

If you play using wx_launcher and set a mod, but then switch to FS2_Launcher later, the command line options of wx_launcher stay in the command line (so you have mod and mediavps commands twice, which may lead to strange behaviour like in my case).

Solution was to start a game using wx_launcher set to "no mod", then quit the game and wx_launcher. After that I had a clean command line.
Title: Re: FS2_Launcher OS X 3.0
Post by: jg18 on April 04, 2013, 11:04:49 am
Unfortunately, that solution won't work in all cases, such as when there are flags checked in wxLauncher's advanced settings. The wiki (http://www.hard-light.net/wiki/index.php/Soulstorm%27s_OS_X_Launcher)'s article on FS2_Launcher has a section "If you have problems when you use one launcher and then the other one" that explains the issue.

Also, FS2_Launcher is no longer supported, because Soulstorm has said (http://www.hard-light.net/forums/index.php?topic=77552.0) that he's no longer maintaining or developing it.

wxLauncher (http://www.hard-light.net/forums/index.php?topic=67950.0) is now the standard launcher on OS X.
Title: Re: FS2_Launcher OS X 3.0
Post by: ptesone on October 26, 2013, 09:35:55 am
Trying the wxlauncher in OSX Mavericks 10.9
when browsing for game folder I Browse to /Applications/Freespace2 and it just keeps asking me to choose a FS2 root game folder over and over again. .  .trying windows version now with crossover. . .

EDIT: it says in the bttom status: "Folder Freespace2 does not have any supported executables"
I'm using GoG version
Title: Re: FS2_Launcher OS X 3.0
Post by: Iss Mneur on October 26, 2013, 09:53:52 am
Trying the wxlauncher in OSX Mavericks 10.9
when browsing for game folder I Browse to /Applications/Freespace2 and it just keeps asking me to choose a FS2 root game folder over and over again. .  .trying windows version now with crossover. . .
Please post in the offical wxLauncher thread (http://www.hard-light.net/forums/index.php?topic=67950.0) and follow the troubleshooting steps from the official thread. Thanks.
Title: Re: FS2_Launcher OS X 3.0
Post by: danslb on June 19, 2014, 06:28:45 pm
Hello all,
I am, unfortunately still o a PPC G5 and need the launcher for it. Any change of someone updating the broken download link ?
Thanks a lot
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on June 19, 2014, 06:48:36 pm
Is wxLauncher not in a PPC/x86 universal app format?  It's the preferred solution at this point where usable.  If not I have soulstorm's launcher somewhere and can get you a link if nothing turns up.
Title: Re: FS2_Launcher OS X 3.0
Post by: danslb on June 19, 2014, 07:20:30 pm
Quote
Is wxLauncher not in a PPC/x86 universal app format?  It's the preferred solution at this point where usable.

No it says its Intel only.

Quote
IIf not I have soulstorm's launcher somewhere and can get you a link if nothing turns up.
That would be really great!
Thanks
Title: Re: FS2_Launcher OS X 3.0
Post by: chief1983 on March 11, 2017, 10:57:03 am
Unstickied as we should probably be using wxLauncher exclusively on Mac for now.