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

Since Mavericks 10.9.1 Time Machine stopped working on my Airport Timecapsule.
Now with 10.9.3 it's working again!!!
Happy camper!:)
 
Now, about those graphics drivers.

I still don't understand why graphics performance in the same game running on OS X or Windows on the very same Mac differs so much in performance (with the Windows version performing (way) better).

Is it because OS X graphics drivers are worse than the Windows versions?
Because of some other libraries or restrictions in OS X?
Because of lazy programming from game developers?
Or something else....?

I know there is a performance debate going on between DirectX and OpenGL — but would/can the same OpenGL based game run just as fast under OS X as it can under Windows?

Anyone in the know, please enlighten me.
 
I have a mid-2012 MBP and the update to 10.9.2 fixed the intermittent beach ball problem that frustrated me. I also increased my RAM to 8GB. Runs great. (This was in response to a post on Page 2 of this thread and I wasn't able to post the entire post.)
 
Now, about those graphics drivers.

I still don't understand why graphics performance in the same game running on OS X or Windows on the very same Mac differs so much in performance (with the Windows version performing (way) better).

Is it because OS X graphics drivers are worse than the Windows versions?
Because of some other libraries or restrictions in OS X?
Because of lazy programming from game developers?
Or something else....?

I know there is a performance debate going on between DirectX and OpenGL — but would/can the same OpenGL based game run just as fast under OS X as it can under Windows?

Anyone in the know, please enlighten me.
It is mostly because DirectX is more developed and generally better utilised by game developers.

OS X is not aimed at the gaming market. I think Apple would rather release a console than promote OS X gaming.
 
WiFi reconnect bug

Apple STILL needs to fix the auto WiFi reconnect bug that occurs when a Mac is brought out of sleep.

Apple should be ashamed of itself for this shoddy work, something that you'd expect from Microsoft.
 
Fix mail why don't ya! OSX is minus one app right now. You've got me using Outlook, of all apps!
 
This. It takes up to a full minute for my MBP '12 to go to sleep. When running Windows 7 in boot camp, it takes just 5 seconds. :mad:
This is not a new thing... it's actually a feature, and it's been around since at least Snow Leopard. Before going to sleep, it makes a copy of current RAM on the hard drive, so if you run out of battery power during sleep, you can recover from the hard drive copy. I believe they call it Hybrid Sleep or Safe Sleep. There's a terminal command that can disable it and bring back quick sleeping. Windows doesn't have this feature, and sleeps right away.

If you just started having this problem now, perhaps you disabled it sometime in the past and the update re-enabled it?
 
Now, about those graphics drivers.

I still don't understand why graphics performance in the same game running on OS X or Windows on the very same Mac differs so much in performance (with the Windows version performing (way) better).

Is it because OS X graphics drivers are worse than the Windows versions?
Because of some other libraries or restrictions in OS X?
Because of lazy programming from game developers?
Or something else....?

I know there is a performance debate going on between DirectX and OpenGL — but would/can the same OpenGL based game run just as fast under OS X as it can under Windows?

Anyone in the know, please enlighten me.

You'll see a lot of differences in Open GL vs Direct X, but graphic drivers also play a big role since the OSX drivers are very outdated. Currently the OSX Nvidia driver is v310 ( i don't know what it is now with 10.9.3 beta), the current Windows driver is v334.89, big difference.
 
This is not a new thing... it's actually a feature, and it's been around since at least Snow Leopard. Before going to sleep, it makes a copy of current RAM on the hard drive, so if you run out of battery power during sleep, you can recover from the hard drive copy. I believe they call it Hybrid Sleep or Safe Sleep. There's a terminal command that can disable it and bring back quick sleeping. Windows doesn't have this feature, and sleeps right away.

If you just started having this problem now, perhaps you disabled it sometime in the past and the update re-enabled it?

Windows has Hybrid Sleep, I just don't think it's enabled by default in a fresh copy of Windows. Some OEM's enable the feature in their pre-made PC's.
 
Since 10.9.2, has anyone else been having issues with Airport? It seems to randomly drop its Internet connection on both my home and work Macs. When I launch Airport Utility and click on the Internet icon, the signal returns. Then it will drop again later. (I sent feedback to Apple; hopefully a fix is on the way.)

Not only happening with airport, also happens with other routers.

After many restarts and frustrations I learned just now that it is my MBP with Mavericks.

Feels like Mavericks is getting faster updates compared to Mountain Lion.

Good stuff :)
 
Os x 10.9.3

I hope they fix the kernel panic system freeze & reboot that I'm experiencing with my 2012 MacBook Pro A1278, never had any problems until I downloaded and applied the 10.9.2 update and now my system's unstable; nothing else has changed in my computer to cause the system crashes.
 
As others have mentioned 10.9.2 is far far slower at restoring a wifi connection after waking from sleep on my 2013 rMBP, and it's not just 802.11n Airport (my home setup) networks either as I had the same issue at the weekend at my mums house on her no brand ISP provided router and it's 802.11g wifi.

Reconnection felt pretty much instant on 10.9.1 - certainly no longer than a second or so and any delay wasn't noticeable. Since the update to 10.9.2 I seem to be watching anywhere between 5 and 15 seconds of wifi connection animation before it is finally up and usable.
 
Honestly, I'm starting to doubt that there's a hardware fault with these Nvidia 320m GPUs. For some reason, 9400m seems to do a better job in terms of smoothness of animations.

since 10.9.2 the animations are smoother but introduced a bug when i plug/unplug my cinema display :/
 
Short lived....

the SSL fix should of be separate of 10.9.2 after they fixed it.... Whats 24 hours ? its a long time to stay vulnerable.

SSL fix one day, 10.9.2 the next..... :eek:

My guess would be 10.9.3 would bring MORE stuff from iOS....

Makes you wanna go back to Mountain Lion doesn't it ?

I think this is more of Apple changing how OS works, gone are the days mobile and desktop features were separate... Now, they are all in one..

I wonder what would have happened if Microsoft started introducing Google/Android features in their OS

This is the biggest pile of crap I've ever read!

10.9.3 will not turn OS X into iOS! Apple have stated they have no intention of merging the two!

And no it doesn't make me want to go back to the mess that was Mountain Lion! Mavericks is far superior.

----------

really? I just am not seeing those kind of issues with my mbp.

Me neither. Mavericks is far superior.
 
Hmm.

Now, about those graphics drivers.

I still don't understand why graphics performance in the same game running on OS X or Windows on the very same Mac differs so much in performance (with the Windows version performing (way) better).

Is it because OS X graphics drivers are worse than the Windows versions?
Because of some other libraries or restrictions in OS X?
Because of lazy programming from game developers?
Or something else....?

I know there is a performance debate going on between DirectX and OpenGL — but would/can the same OpenGL based game run just as fast under OS X as it can under Windows?

Anyone in the know, please enlighten me.



The drivers for Windows is slightly better performing, but it is not the primary reason here. I wouldn't call it lazy programming, but it is the programming that's to blame for the most part. The teams developing Windows versions are much bigger and better funded, and optimizing OpenGL well is harder than optimizing DirectX, as Microsoft has already done a lot of optimization work on their en of DirectX, whereas OpenGL requires more explicit instructions. Theoretically a game should be able to run equally well on both platforms (maybe like 2 percent better on Windows due to newer drivers, depending on the GPU. There's much more information on this to be found. If you want to know more about drivers specifically, let me know), but really it comes down to the programming. A lot of game engines aren't that well developed for OS X either. Take Unity for an example. If the programmers pour their soul into it, they can fix a lot of it's problems, but if you just go with the rendering pipeline offered by vanilla Unity, performance will be way worse under OS X. Another thing to consider, is that OS X is running things like dashboard and spaces in the background all the time, and while Windows is doing similar things, there's a bit more overhead on OS X. Some Mac developers like Feral, give you the option to disable the Dock(which also disables other things like Notification Center) entirely while playing their games, allowing for greater performance. Ever since Lion though, Apple has been putting a lot of effort into improving OS X's gaming and graphics performance, making more API's available, and improving the performance of existing ones. More and more game developers are starting to use these new API's, hence the fact that more and more games require at least Lion or Mountain Lion, and as a result we see games running better. You should never expect performance to be 1:1 though, as gaming is an essential part of Microsoft's business (with Xbox and Microsoft Games Studio), and (at least on the Mac) a really small part of Apple's. That being said, the huge success of games on iOS is leading development on the Mac side, and even though iOS games aren't exactly the same, the effects are positive for proper games as well.


Also, there are a lot more third party API's for Windows already developed. As an example, TresEffects aren't in the Mac version of Tomb Raider, simply because it would be too expensive to port the technology.
 
Honestly, I'm starting to doubt that there's a hardware fault with these Nvidia 320m GPUs. For some reason, 9400m seems to do a better job in terms of smoothness of animations.

Could be. My 9400m in my 2009 handles Mavericks beautifully. I might be behind the times on a C2D but 10.9.2 has easily been my best OS X experience in the last 6 years on this machine. Do wish I still had my 2011 MBA 13" though.
 
Anyone else having an issue where your MBP takes forever to go into sleep mode?

My MP used to take maybe a second with 10.6, now it takes >20 seconds in 10.9.2, so yeah. Nothing to do with safe sleep, since I never disabled it, it's just slower.

--Eric
 
I was totally bashed for mentioning audio issues in previous beta threads. So I'm glad to see apple is fixing what I class as a massive issue.

There are many other bugs some of which disappeared with 10.9.2 and some remain.

Apple is a demon at fixing things, so quick but they've been asleep on this one.
 
I hope they fix the kernel panic system freeze & reboot that I'm experiencing with my 2012 MacBook Pro A1278, never had any problems until I downloaded and applied the 10.9.2 update and now my system's unstable; nothing else has changed in my computer to cause the system crashes.

Download the combo (10.9.2) update and (re)apply it, this may resolve the problem.
 
Went back to Mountain Lion on my 2009 MBP yesterday, wish I did earlier. Couldnt even watch HD video in Mavericks because the video drivers suck so bad, and the whole thing just felt slow and laggy (Im sure all the extra apps I had to install to bring back basic common sense usability that Apple removed didnt help).

Wow, I didn't know the 2009 models were so inferior to the 2008 models seeing as my 2008 MBP plays HD video just fine in Mavericks. :cool:

Now, about those graphics drivers.

I still don't understand why graphics performance in the same game running on OS X or Windows on the very same Mac differs so much in performance (with the Windows version performing (way) better).

Is it because OS X graphics drivers are worse than the Windows versions?
Because of some other libraries or restrictions in OS X?
Because of lazy programming from game developers?

Yes, yes and yes. OS X drivers are not as optimized as Windows ones and don't often get updates as they go so even if they do get optimized, the Windows ones may keep getting more optimized as time goes on. Most major OS X games are ports of Windows games and thus are second class citizens in terms of bothering to optimize them. Some might even be Transgaming/Cider type ports and thus you are basically converting almost emulating large parts of the Windows OS on top of that. Even if they're true ports, they often have to convert DirectX/Direct3D routines to OpenGL. Then there's the fact that OpenGL always seems to be YEARS behind the current version and thus do not align well with the latest GPU hardware supported routines. Any routines not supported have to be software emulated and that means SLOOOOW performance in that category.

Finally, most Macs are woefully underpowered in terms of their GPUs to begin with when they actually need more powerful ones to make up for the above shortcomings. Apple couldn't care less about gaming level GPUs so you're just SOL there. This has nothing to do with the Windows version on the SAME hardware running much faster, of course, but it doesn't help in general.

Add all those things up and sometimes I'm amazed many games are only 15-20% slower than the Windows versions. Many are worse yet. Apple could easily do and/or have someone else do something about the driver updates, OpenGL updates and responding faster/better to developer requests to sort these issues out and make porting and gaming development in general better. Apple seems to have little to no interest in any of that.

They can't do a whole lot about developers making their games optimized for DirectX/3D, though. Developers should have ignored Microsoft when they pushed it hard over open standards and pushed to make open standards better and easier to implement. Very few game makers develop on OpenGL anymore (I think I.D. is an exception). Basically, if Apple sorted the above out and game makers did OpenGL (which is available for both platforms), the games would/should be more or less equal performing at that point. There's nothing inherent in OS X that impedes gaming other than Apple itself. Personally, if the game runs smooth in OS X, it doesn't matter much to me. I don't need more and more fps just to have them. But Apple should take more interest in the gaming market. It's not as if they're stretched for money or something to do something about it.
 
Last edited:
I hope they fix the kernel panic system freeze & reboot that I'm experiencing with my 2012 MacBook Pro A1278, never had any problems until I downloaded and applied the 10.9.2 update and now my system's unstable; nothing else has changed in my computer to cause the system crashes.

I've experienced this 3 times since the 9.2 update. Hasnt happened recently though.

----------

This is not a new thing... it's actually a feature, and it's been around since at least Snow Leopard. Before going to sleep, it makes a copy of current RAM on the hard drive, so if you run out of battery power during sleep, you can recover from the hard drive copy. I believe they call it Hybrid Sleep or Safe Sleep. There's a terminal command that can disable it and bring back quick sleeping. Windows doesn't have this feature, and sleeps right away.

If you just started having this problem now, perhaps you disabled it sometime in the past and the update re-enabled it?

:eek:I did not know this. Thanks for the information :)
 
I made my MBP fast using Mavericks

Mavericks has been the worst upgrade experience for me. Lion was a walk in the park compared to this 10.9 sh**!

I'm on 10.9.2 and I'm fed up with the crazy beach balling, slooow as molasses Finder, audio issues, and wifi issues. Rebooting temporarily fixes the audio and wifi issues.

I've started looking into rolling back to Mountain Lion. OS X 10.9 and iOS 7 needed more time to bake. I'm not impressed with Apple at the moment.
-ITG

For months I was also plagued with a glacially slow Mavericks install on my mid-2012 MacBook Pro. I lost count of the number of fixes (easily 30+) I tried but none of them worked. Many of the fixes suggested were from here and MacInTouch. Finally I gave up and upgraded to 8 GB RAM and an SSD. The MBP immediately became lightening fast. Bottom line, Mavericks works painfully slow on stock MBPs. Apple should just admit it and change their specs.
 
sleep related terminal commands

This is not a new thing... it's actually a feature, and it's been around since at least Snow Leopard. Before going to sleep, it makes a copy of current RAM on the hard drive, so if you run out of battery power during sleep, you can recover from the hard drive copy. I believe they call it Hybrid Sleep or Safe Sleep. There's a terminal command that can disable it and bring back quick sleeping. Windows doesn't have this feature, and sleeps right away.
If you just started having this problem now, perhaps you disabled it sometime in the past and the update re-enabled it?
I cannot give credit to those it is due to, as I picked these commands up from various threads on the forum; anyway thanks to those who contributed! :D

Open a Terminal shell (in the /Applications/Utilities folder)
pmset -g
This command will list all the current power settings/device settings.

Sleep settings
Files
All changes made through pmset are saved in a persistent preferences file (per-system, not per-user) at
/Library/Preferences/SystemConfiguration/com.apple.PowerManagement.plist
System Preferences Energy Saver modifies the same file

Scheduled power on/off events are stored separately in
/Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist

Terminal commands: Copy and paste all the commands, starting with "sudo"
Enter your password when prompted, the password you type is not shown, just hit enter.
Display the current settings;

hibernatemode = 0 (binary 0000) by default on supported desktops. The system will not back memory up to persistent storage. The system must wake from the contents of memory; the system will lose context on power loss. This is, historically, plain old sleep.
hibernatemode = 3 (binary 0011) by default on supported portables. The system will store a copy of memory to persistent storage (the disk), and will power memory during sleep. The system will wake from memory, unless a power loss forces it to restore from disk image.
hibernatemode = 25 (binary 0001 1001) is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want "hibernation" - slower sleeps, slower wakes, and better battery life, you should use this setting.

1. set hibernate mode to 0
sudo pmset -a hibernatemode 0
hibernationmode 0 is normal sleep, data kept in ram, nothing written to disk
2. delete the unnecessary sleep file (since hibernate is disabled) to regain disk space equal to memory (saves the same amount of disk space as your RAM, eg. 8 GBs, valuable on an SSD),
You can use the Go to folder menu to delete the file, found in the /var/vm/ folder, and named sleepimage. Reboot and simply delete that file,. Or use this:
sudo rm /var/vm/sleepimage or sudo rm /private/var/vm/sleepimage
The sleep image file is actually in /Private/var/vm/ but /var/vm/ is a symbolic link to that location.
Optional: Create a blanked zero-byte file so the OS cannot rewrite the file:
sudo touch /private/var/vm/sleepimage
Make file immutable:
sudo chflags uchg /private/var/vm/sleepimage

If pmset -g shows: autopoweroff**1,
disable this automatic hibernation mode (happens even if hibernation mode is set to 0 on the new Mac mini 2012 and iMac)
sudo pmset -a autopoweroff 0
4. set the safe sleep timer (standbydelay) to 20 hours, default is 4200 (1.67 hr)
sudo pmset -a standbydelay 72000
5. sudo pmset -a standby 0
While researching this, I noticed that bit 3 of hibernatemode encourages the dynamic pager to page out inactive pages prior to hibernation. So this appears to be why I have swap used after sleeping (even though my hibernatemode is 0, so bit 3 is off). I disabled this new, possibly buggy behaviour by switching off standby: sudo pmset -a standby 0
View the sleep image size:
ls -lh /private/var/vm/sleepimage
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.