Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

OS X Aspyr's Doom III doesn't work on Mavericks

Bradamante

Bradamante

macrumors member
Original poster
Feb 12, 2013
61
23
Germany
Hi,

in 2013 I purchased Aspyr's Doom III on GameAgent and played it on OS X.8. Now on Mavericks it seizes to work. The icon opens in the Dock, but keeps blinking and seemingly crashes silently. The system.log says:

04.08.14 18:13:18,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x10a6d8000): p=502[CoreServicesUIAg] final status 0x1000a00, denying page sending SIGKILL
04.08.14 18:13:18,000 kernel[0]: CODE SIGNING: process 502[CoreServicesUIAg]: rejecting invalid page at address 0x10a6d8000 from offset 0x0 in file "/Applications/Doom 3.app/Contents/MacOS/Doom 3" (cs_mtime:1323211396.0 == mtime:1323211396.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
04.08.14 18:13:18,514 com.apple.launchd.peruser.501[167]: (com.apple.coreservices.uiagent[502]) Exited: Killed: 9
04.08.14 18:13:18,827 ReportCrash[505]: Saved crash report for CoreServicesUIAgent[502] version 101.3 (101.3) to /Users/Example/Library/Logs/DiagnosticReports/CoreServicesUIAgent_2014-08-04-181318_Example.crash
04.08.14 18:13:19,558 Console[507]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
Click to expand...

Is the NSApplicationPresentationFullScreen an indicator of what goes wrong? Am I the only one with this problem?

My setup is a CustoMac with a i5-3570K, a GTX 760 and OS X.9.3 (now 9.4).

I am aware that id Tech 4 is open source, but I haven't seen a fire&forget Mac OS X binary download "for the rest of us" yet.
 
I ended up getting a refund sadly as I never even got crashes or error messages on Mavericks. It just bounced on the dock while saying Not Responding.

No matter what info I sent back they couldn't figure out why. What a shame. I might try and MAS version if it truly works, but there's no guarantee.
 
I have Aspyr's version and it runs OK on my Mac pro which is listed below.
 
MAS version works for me as long as I have automatic graphic switching disabled before starting it.
 
DOOM 3 non-MAS not launching on Mavericks

Hey folks,

We're currently looking into the launching issue for the non-MAS digital version of Doom 3 on OSX 10.9. The MAS version does not present any problems with launching.

If you've purchased a non-MAS digital version of Doom 3 and it is not launching under Mavericks, please submit a ticket at support@aspyr.com so that we can help you out.

Our apologies for any inconvenience and we appreciate your patience while we look into this problem.
 
Yeah no problem. Hey if you can't get your own version to run, could you put some Aspyr person on compiling the open source version? I would accept that as a replacement ... Can't speak for others, though :D

What I am wondering ... This NSApplicationPresentationFullScreen thing, is that an indicator? Full screen problems? I've got two displays connected here? Problem with Intel integrated graphics + graphics card?

Or is it a NVidia vs ATI thing? It seems people here in the thread who have ATI cards report that the game works fine?
 
Last edited:
Bradamante said:
Or is it a NVidia vs ATI thing? It seems people here in the thread who have ATI cards report that the game works fine?
Click to expand...

This is what we thought at first too. So far it looks like its a weird problem with how the application deals with gatekeeper in OSX. We are digging though. Shouldnt be too long.

Please, if anyone is experiencing this issue simply give our support team a shout. They will get you up and running with a new version. :apple:
 
Hm, I hoped having GateKeeper off (my default) would help, but no :( GK off often helps with those error messages where the system claims that an older piece of software is corrupted and should be moved to the trash.

With GateKeeper high:

07.08.14 10:56:09,531 CoreServicesUIAgent[511]: Error SecAssessmentCreate: Der Vorgang konnte nicht abgeschlossen werden. (OSStatus-Fehler -67061.)
07.08.14 10:56:09,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1128f5000): p=511[CoreServicesUIAg] final status 0x1000a00, denying page sending SIGKILL
07.08.14 10:56:09,000 kernel[0]: CODE SIGNING: process 511[CoreServicesUIAg]: rejecting invalid page at address 0x1128f5000 from offset 0x0 in file "/Applications/Doom 3.app/Contents/MacOS/Doom 3" (cs_mtime:1323211396.0 == mtime:1323211396.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
07.08.14 10:56:09,756 com.apple.launchd.peruser.501[167]: (com.apple.coreservices.uiagent[511]) Exited: Killed: 9
Click to expand...

Medium:

07.08.14 10:54:52,546 CoreServicesUIAgent[491]: Error SecAssessmentCreate: Der Vorgang konnte nicht abgeschlossen werden. (OSStatus-Fehler -67061.)
07.08.14 10:54:52,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x10cf78000): p=491[CoreServicesUIAg] final status 0x1000a00, denying page sending SIGKILL
07.08.14 10:54:52,000 kernel[0]: CODE SIGNING: process 491[CoreServicesUIAg]: rejecting invalid page at address 0x10cf78000 from offset 0x0 in file "/Applications/Doom 3.app/Contents/MacOS/Doom 3" (cs_mtime:1323211396.0 == mtime:1323211396.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
07.08.14 10:54:52,963 com.apple.launchd.peruser.501[167]: (com.apple.coreservices.uiagent[491]) Exited: Killed: 9
Click to expand...

Off (my default):

07.08.14 10:56:59,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x10c93d000): p=522[CoreServicesUIAg] final status 0x1000a00, denying page sending SIGKILL
07.08.14 10:56:59,000 kernel[0]: CODE SIGNING: process 522[CoreServicesUIAg]: rejecting invalid page at address 0x10c93d000 from offset 0x0 in file "/Applications/Doom 3.app/Contents/MacOS/Doom 3" (cs_mtime:1323211396.0 == mtime:1323211396.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
07.08.14 10:57:00,094 com.apple.launchd.peruser.501[167]: (com.apple.coreservices.uiagent[522]) Exited: Killed: 9
Click to expand...
 
Aspyr-Blair said:
This is what we thought at first too. So far it looks like its a weird problem with how the application deals with gatekeeper in OSX. We are digging though. Shouldnt be too long.

Please, if anyone is experiencing this issue simply give our support team a shout. They will get you up and running with a new version. :apple:
Click to expand...

I tried that, and support didn't have a clue for a week. They ended up giving me a full refund instead. :(
 
We figured it out! Its a quarantine issue. There is a command line work-around so we are putting together a KB article on it now. I'll follow up here with the step-by-step. :apple:
 
Aspyr-Blair said:
We figured it out! Its a quarantine issue. There is a command line work-around so we are putting together a KB article on it now. I'll follow up here with the step-by-step. :apple:
Click to expand...

And where is this guide? I also wrote to your support, but after asking me for a proof of purchase and logs, then getting them in a reply, your stuff become silent :/
 
For anyone experiencing this issue, here is the fix:

The following steps must be run on an account with administrator access and not a standard or guess account. A password is required on the account.

1. Launch Terminal from /Applications/Utilities.
2. Copy and paste the following command into terminal: sudo xattr -d -r com.apple.quarantine
3. After com.apple.quarantine, add a space.
4. In Finder, locate the Doom 3 application (this is normally in /Applications).
5. Click and drag the application into the Terminal window.
6. Select the Terminal window.
7. Press enter.
8. When prompted, enter the user account password (You will not see the password in the Terminal window).
9. After Terminal displays a new command line, exit Terminal.
10. Doom 3 should now run without issue.

Notes: This command only needs to be entered once. Subsequent launches should work without issue.

Thanks to everyone for being patient (especially revanmj ;)) and again special thanks to the OP for alerting us of the issue.
 
Yes, works. Thanks for this fix.

Runs very well at 60 FPS, 1920x1200, 8x AA for me. Loading times could be better (SSD here), but obviously a lot better than the biblical loading times in 2005.

The screen seems a bit stretched. Increasing the FOV in autoexec.cfg doesnt seem to help.

Is there some other config setting I am missing? Something like aspect ratio?
 
Bradamante said:
Yes, works. Thanks for this fix.

Runs very well at 60 FPS, 1920x1200, 8x AA for me. Loading times could be better (SSD here), but obviously a lot better than the biblical loading times in 2005.

The screen seems a bit stretched. Increasing the FOV in autoexec.cfg doesnt seem to help.

Is there some other config setting I am missing? Something like aspect ratio?
Click to expand...

Since the game was originally released for Windows in 2004, although widescreen can be set which was true even with the Quake III engine, the hud is stretched at least in Windows. I haven't run this yet in OS X although I own it. You can configure the aspect ratio by editing a config file so this may help. The info here should be of use:

http://www.wsgf.org/dr/doom-3

To find the config file on OS X, my guess is that it lives in your Library/Application Support/Doom3/base folder and is probably called DoomConfig.cfg

That ought to be close at least. I'd think you can figure it out once you find the Doom3 folder in Application Support. Look for the aspect ratio line mentioned in the link above and see if it matches what they suggest or if it is missing, add it with the appropriate value for your screen.

Last but not least, if you are not familiar with how to access your Library folder, just open Finder and then open the Go menu, press the Option key and you'll see it appear in the menu, click that menu choice, etc. to go where you need to go.

If I am wrong about where the file lives, hopefully Blair or someone else from Aspyr will come along and correct me for you.

Hope that is helpful.
 
Well, I am already doing that, I was just asking for the right values.

Besides, my custom config doesn't seem to load, no matter if I name it "autoexec.cfg" or "AutoExec.cfg". Only editing the DoomConfig.cfg changes things. Problem is that you are not supposed to edit this file, since the game will often revert to the default. It also seems to revert if it encounters values that it doesn't recognize. For example, "r_mode -1" gets reverted to "r_mode 6" here.
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back