Diablo® III

enemy encounters drop my fps

Hi there,

I have been having poor performance problems in D3 since patching. Noted issues are low FPS rates when latency is at green. This fps issue is similar to the "first monster lag" in that encountering the first group is a death sentence, there screen is frozen for 1-3 seconds but will come back (and play some of the bits that i missed in a fast forward style) and i mostly come out of the freeze dead. However unlike previous threads this will continue to occur through out the game, notably on large encounters (a3 crater). In addition, i feel that i have slower map load times as evidenced in multiplayer games where Im clearly ahead of the group (30yards at least) and when i click the next zone and appear the group is now 30yards ahead of me (i estimate a 5-15sec load which is important for efficiency) . I would also like to add that a3 stonefort is not manageable, for the same screen freeze, low fps, stuttering problems.

  • Hardware Overview:

    Model Name: Mac mini
    Model Identifier: Macmini4,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.4 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 3 MB
    Memory: 2 GB
    Bus Speed: 1.07 GHz
    Boot ROM Version: MM41.0042.B00
    SMC Version (system): 1.65f2

    Hardware UUID: EAB52061-F3A1-5789-9F65-DCB0B0BBD53D

    NVIDIA GeForce 320M:

    Chipset Model: NVIDIA GeForce 320M
    Type: GPU
    Bus: PCI
    VRAM (Total): 256 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x08a4
    Revision ID: 0x00a2
    ROM Revision: 3546
    Displays:
    Display Connector:
    Status: No Display Connected
    TSB-TV:
    Resolution: 1920 x 1080 @ 60 Hz
    Pixel Depth: 32-Bit Color (ARGB8888)
    Main Display: Yes
    Mirror: Off
    Online: Yes
    Rotation: Supported
    Television: Yes

    System Software Overview:

    System Version: Mac OS X 10.6.8 (10K549)
    Kernel Version: Darwin 10.8.0
    Boot Volume: Macintosh HD
    Boot Mode: Normal

    Secure Virtual Memory: Not Enabled
    64-bit Kernel and Extensions: No
    Time since boot: 2:06


  • I have attempted to troubleshoot myself as to prevent posting here but I am at a loss. I lowered fps to 25 (i have experimented with higher and lower fps) and 1 background. Also low Fx, no shadows..ect is all set low or off and the resolution is on the lowest. I have made sure only appropriate background applications are on. I have done the SMC reset (for mac mini it said to power down, unplug, plug in wait 15sec and power on). I have reset game folder and files permissions. I did the combo update. Finally today I decided to uninstall and reinstall, and I am still getting encounter fps lag. D3 has worked great, but it is getting harder to play without the frustration of performance issues. I also wanted to mention this due to my interest in future PVP, where these performance issues would provide PVP with a poor experience.

    Thank you.
    Reply Quote
    I've had similar problems as well. The horrible FPS I get at times is not only frustrating, but sickens me while playing and I even log due to how bad it is. I don't recall having troubles to this early on in the game. I can move around at a consistent 40-50 fps, but anytime more than a few monsters appear on screen my fps is suddenly horrendous. By horrendous i mean 5-10 fps, until the monsters are clear. It's seriously frustrating and going to cause me to cease play.
    Reply Quote
    - Technical Support
    90 Human Priest
    6220
    Posts: 12,150
    The Mac Mini shares its system RAM with the GPU, so you have 256 MB RAM dedicated solely to the GPU, and the OS itself is taking up a good 700 MB on its own once you fully load to the desktop. That leaves you about 1 GB left over.

    Here are some basic tips that might help alleviate some of the problem. You can try them in any order you like:

    - Set Physics to Low. This controls only how breakable objects fly through the air and does not impact gameplay at all, other than improving framerates when set to Low.

    - Disable Anti-Aliasing. Mac Minis aren't known for powerful GPUs. The 320M isn't pathetic, but it isn't good either. Everything you can turn off helps.

    - Set Shadows to Low or Off. Off is preferrable on that system if you can live with it. Shadows above the Low setting really bring down framerates in OS X, as our OpenGL shader models just suck due to being horribly out of date (read: OLD). Poor drivers aren't helping any.

    - Set the game to a lower resolution. None of you noted your resolution, so I'll assume you are using the display's native resolution, which may be too high to be playable with the limitations that Mac Mini suffers (Low VRAM, not very powerful GPU).

    - Add some system RAM. This may be the biggest gain you can give yourself. It's also the one that costs money, but you're running with 2 GB of RAM, with only 1 GB left over for Diablo 3. The higher your resolution and graphics settings are, the more RAM the app will take, and you may well be hitting page swaps out to your disk, and the Mini's drives aren't exactly speedy beasts. More RAM ensures you never hit swap.

    If you choose to go the lower resolution route, I highly suggest using the following procedure, as the non-standard in-game resolutions don't play nicely with external monitor/TV built in scalers:

    Open the Terminal and enter the following line, followed by the Enter key:

    defaults write com.blizzard.diablo3 DesktopModeIsDefault 1

    Once entered Diablo 3 can use your current desktop resolution as if it were the native resolution. In order for this to work, you must first set your desktop resolution to the desired size, and then launch Diablo 3.

    To revert your preference file, issue the following command in Terminal:

    defaults delete com.blizzard.diablo3 DesktopModeIsDefault

    You should make a backup of this file before attempting this, just in case. The file is located here:

    ~/Library/Preferences/com.blizzard.diablo3.plist

    This will allow you to use a lower resolution for Diablo 3 like you used to without the added distortion/UI offsets caused by the non-standard resolutions that are now hard-coded into the game.

    ________________________________________________
    Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
    Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
    Caution: This cookie bites back.
    Edited by TheTias#1192 on 11/10/2012 9:10 PM PST
    Reply Quote
    thank you. I will try these suggestions with the resolution. I will add that my physics/shadows/anti-alising, were all off and i have been playing at the 800 res fullscreen. basically anything that says disable to improve performance was done. But my desktop is set to 1080p so changing that that sounds like a good try. I was more curious if there was a patch bug, because I was able to run d3 very well before the patch and now it is very frustrating to play. In browsing the forums similar mac users having issues post 1.0.5, most of them seemed to be fixed with a SMC reset, however my issues were not.

    I am also aware of the probable low ram issue. I wanted to post here before I spent money on more ram that would ultimately not effect the gameplay outcome.
    Reply Quote
    - Technical Support
    90 Human Priest
    6220
    Posts: 12,150
    Here's hoping some, or all of the items here help you out and make the game playable for you again. :)

    ________________________________________________
    Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
    Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
    Caution: This cookie bites back.
    Reply Quote
    I found that my problem is similar to https://us.battle.net/d3/en/forum/topic/7004691548.

    in my debug report i found ***sound device caps*** continuously occurring. possibly 10.6.8 is no longer fully supported?

    2012.11.11 21:47:26.148260915 Start SoundPlatform::Dispose()
    2012.11.11 21:47:26.148376023 StopOVTStream
    2012.11.11 21:47:26.323588615 - Releasing DSP effects
    2012.11.11 21:47:31.805953639 - Releasing FMOD System
    2012.11.11 21:47:31.845216937 Finish SoundPlatform::Dispose()
    2012.11.11 21:47:31.954820799 Initializing sound subsystem...
    2012.11.11 21:47:32.176405663 ****** Sound Device Caps ******
    2012.11.11 21:47:32.224862870 Found 2 sound drivers:
    2012.11.11 21:47:32.291444347 Driver 0: 'Built-in Output'
    2012.11.11 21:47:32.316243313 Min Freq: 44100, Max Freq: 44100
    2012.11.11 21:47:32.372698250 Speaker Mode: Stereo
    2012.11.11 21:47:32.372769603 Driver Capabilities:
    2012.11.11 21:47:32.373186480 Device can do multichannel output, ie greater than 2 channels.
    2012.11.11 21:47:32.373600928 Device can output to 8bit integer PCM.
    2012.11.11 21:47:32.398016399 Device can output to 16bit integer PCM.
    2012.11.11 21:47:32.442333679 Device can output to 24bit integer PCM.
    2012.11.11 21:47:32.475749265 Device can output to 32bit integer PCM.
    2012.11.11 21:47:32.476392450 Device can output to 32bit floating point PCM.
    2012.11.11 21:47:32.533357928 Driver 1: 'HDMI'
    2012.11.11 21:47:32.728384538 Min Freq: 48000, Max Freq: 48000
    2012.11.11 21:47:32.951081586 Speaker Mode: Stereo
    2012.11.11 21:47:32.951126469 Driver Capabilities:
    2012.11.11 21:47:32.951155289 Device can do multichannel output, ie greater than 2 channels.
    2012.11.11 21:47:32.951182825 Device can output to 8bit integer PCM.
    2012.11.11 21:47:32.951210609 Device can output to 16bit integer PCM.
    2012.11.11 21:47:32.951238055 Device can output to 24bit integer PCM.
    2012.11.11 21:47:32.951265403 Device can output to 32bit integer PCM.
    2012.11.11 21:47:32.951292995 Device can output to 32bit floating point PCM.
    2012.11.11 21:47:32.951322655 Selecting driver 0 (Built-in Output)
    2012.11.11 21:47:32.951366088 Speaker Mode: Stereo
    2012.11.11 21:47:32.951397146 Initializing sound with 16 channels
    2012.11.11 21:47:40.513413754 ****** SoundPlatformFModGlobals ******
    2012.11.11 21:47:40.513882870 bResetDevice: 0
    2012.11.11 21:47:40.513975773 nNumDrivers: 2
    2012.11.11 21:47:40.514223395 nDriverToUse: 0
    2012.11.11 21:47:40.514427729 ptFModSystem: 0x2905c1d8
    2012.11.11 21:47:40.514758902 pFModMemory: 0x2905c000
    2012.11.11 21:47:40.514995119 nFModMemoryAmount: 100663296
    2012.11.11 21:47:40.515223735 nNumChannels: 128
    2012.11.11 21:47:40.515434464 ptCachedSoundAllocator, used block count: 0
    2012.11.11 21:47:40.515797173 ptCachedSoundAllocator, free block count: 640
    2012.11.11 21:47:40.516313101 ptCachedSoundSampleMap, count: 0
    2012.11.11 21:47:40.516642619 ptCachedSoundStreamMap, count: 0
    2012.11.11 21:47:40.516868822 ptLRUSoundSampleList, count: 0
    2012.11.11 21:47:40.517062851 ptLRUSoundStreamList, count: 0
    2012.11.11 21:47:40.517326374 arPlayingSounds: 0x24c78c00
    2012.11.11 21:47:40.517537783 nCacheSampleSize: 0
    2012.11.11 21:47:40.517833138 nCacheStreamSize: 0
    2012.11.11 21:47:40.518045515 nFModCurrentAlloced: 48423488
    2012.11.11 21:47:40.518262860 nFModMaxAlloced: 48423488
    2012.11.11 21:47:47.939809283 Disposing sound subsystem...
    2012.11.11 21:47:47.964405970 Start SoundPlatform::Dispose()
    2012.11.11 21:47:47.964516697 StopOVTStream
    2012.11.11 21:47:47.984252848 - Releasing DSP effects
    2012.11.11 21:47:47.985771435 - Releasing FMOD System
    2012.11.11 21:47:48.022556803 Finish SoundPlatform::Dispose()
    2012.11.11 21:47:48.022693910 Initializing sound subsystem...
    2012.11.11 21:47:48.024465596 ****** Sound Device Caps ******
    2012.11.11 21:47:48.025838663 Found 2 sound drivers:
    2012.11.11 21:47:48.025924175 Driver 0: 'Built-in Output'
    2012.11.11 21:47:48.026155424 Min Freq: 44100, Max Freq: 44100
    2012.11.11 21:47:48.026411410 Speaker Mode: Stereo
    2012.11.11 21:47:48.026587079 Driver Capabilities:
    2012.11.11 21:47:48.026849732 Device can do multichannel output, ie greater than 2 channels.
    2012.11.11 21:47:48.027117388 Device can output to 8bit integer PCM.
    2012.11.11 21:47:48.027380568 Device can output to 16bit integer PCM.
    2012.11.11 21:47:48.027646861 Device can output to 24bit integer PCM.
    2012.11.11 21:47:48.027933205 Device can output to 32bit integer PCM.
    2012.11.11 21:47:48.028126114 Device can output to 32bit floating point PCM.
    2012.11.11 21:47:48.028513297 Driver 1: 'HDMI'
    Reply Quote
    - Technical Support
    90 Human Priest
    6220
    Posts: 12,150
    Dax, can you post the contents of your D3Prefs.txt file here so we can see if any particular setting might be causing (or helping to cause) this issue? Make sure to remove any perfonal info if there is any inside (there shouldn't be, but I put that there just in case).

    The file is located at the following location:

    ~/Library/Application Support/Blizzard/Diablo III/

    And since your D3Debug.txt file shows similar results to the thread you mention, if you haven't already, post your system info and the log you just posted here into that thread as well. The more reports Blizzard gets, the more likely they can home in on what is causing the error(s).

    ________________________________________________
    Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
    Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
    Caution: This cookie bites back.
    Reply Quote

    Please report any Code of Conduct violations, including:

    Threats of violence. We take these seriously and will alert the proper authorities.

    Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

    Harassing or discriminatory language. This will not be tolerated.

    Forums Code of Conduct

    Report Post # written by

    Reason
    Explain (256 characters max)

    Reported!

    [Close]