Severe Graphic Glitching

  • Known issues only has texture flickering and this is well beyond that. I have rebuilt game cache, uninstalled/reinstalled, and tweaked various settings on my Mac to no avail.

    Hardware Overview:

    Model Name: MacBook Pro
    Model Identifier: MacBookPro10,1
    Processor Name: Intel Core i7
    Processor Speed: 2.7 GHz
    Number of Processors: 1
    Total Number of Cores: 4
    L2 Cache (per Core): 256 KB
    L3 Cache: 8 MB
    Memory: 16 GB
    Boot ROM Version: MBP101.00EE.B02
    SMC Version (system): 2.3f36
    Serial Number (system): C02HR04SF5Y2
    Hardware UUID: D93B938F-FF50-5842-A507-012EACD249A6

    Intel HD Graphics 4000:

    Chipset Model: Intel HD Graphics 4000
    Type: GPU
    Bus: Built-In
    VRAM (Total): 1024 MB
    Vendor: Intel (0x8086)
    Device ID: 0x0166
    Revision ID: 0x0009
    gMux Version: 3.2.19 [3.2.8]
    Color LCD:
    Display Type: Retina LCD
    Resolution: 2880 x 1800
    Retina: Yes
    Pixel Depth: 32-Bit Color (ARGB8888)
    Main Display: Yes
    Mirror: Off
    Online: Yes
    Built-In: Yes

    NVIDIA GeForce GT 650M:

    Chipset Model: NVIDIA GeForce GT 650M
    Type: GPU
    Bus: PCIe
    PCIe Lane Width: x8
    VRAM (Total): 1024 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0fd5
    Revision ID: 0x00a2
    ROM Revision: 3688
    gMux Version: 3.2.19 [3.2.8]

    System Software Overview:

    System Version: OS X 10.9.2 (13C64)
    Kernel Version: Darwin 13.1.0
    Boot Volume: Macintosh HD
    Boot Mode: Normal
    Computer Name: Julian’s MacBook Pro
    User Name: Jules (Jules)
    Secure Virtual Memory: Enabled
    Time since boot: 20:51
  • We are currently looking into this issue.
    Thanks for all the screenshots.

    We can reproduce this after many hours of gameplay. If you find a better way, we would like to know.
    This issue is different from the one where some splats on the ground are flickering.

    If you experience this issue, I would like to know the following:

    What OSX version you're using?
    What's your video card?
    How many hours before this happened (starting when you launch Diablo III)?
    When it started, did you crash shortly after? If so, please provide the crash ID. (The long number in the crash reporter)

    If my theory is correct, this is related to using too much memory address space.
    You could avoid the problem by reducing your resolution to 1650x1080 or 1920x1200 and using lower graphic settings like a lower texture quality.

    This is not a solution, we are currently working on a fix for both Windows and Mac.
  • From what I understand, on Windows, you just crash. No funny textures.

    Thanks for your feedback, this will help.
  • Obviously not a workaround but do you guys know if switching between windows and fullscreen makes the issue go away(at least for a little while)?

    If anyone has a bug report ID that would really help. You get these when you crash.

    Thanks BadLlama for yours.
  • Nggalai, your issue is discussed in this thread:
  • Thanks to everybody that sent crash IDs and informations.

    All the crashes are related.

    Technical explanation:
    We are running out of memory address space. Which is causing the textures to be loading incorrectly and to show garbage data. Changing the texture quality tells the game to reload all its textures, this might avoid the problem for a short period of time.

    This bug cannot cause damage to hardware.

    The next time this happens, can you guy launch Activity Monitor and double-click on the Diablo III process, click on the Memory tab and post the Virtual Memory Size?

    In the meanwhile, we put a tentative fix for the next patch. I say "tentative" because we have no good way to verify if this really fixes the problem.

    Thanks for your help.
  • JohanJizzu, you have 2 GB of RAM. The minimum is 4 GB.

    While upgrading won't solve all your issues, it will improve the game performance by a lot.
  • Thanks for these numbers.

    Anytime, the virtual memory is above 3.70 GB you risk crashing.
    If you are at a point where you can restart the game without losing progress, you should do that.

    It should be much better when the new patch is released.
  • The patch is coming soon, this will be a minor patch before 2.1.

    The schedule can change at anytime, that why we do not give specific dates.

    Just be aware that since this an out of memory bug, we can only make it better. Which means it might still happen but less frequently. The ultimate goal is to use less memory so this never happens.

    As a note, adding more RAM would not fix the problem but could increase the performance if you have less than 8 GB.
  • 04/02/2014 10:41 PMPosted by MysticalOS
    04/02/2014 02:07 PMPosted by S4d1k
    Just be aware that since this an out of memory bug, we can only make it better. Which means it might still happen but less frequently. The ultimate goal is to use less memory so this never happens.

    Clearly D3 is reaching its' limits as a 32 bit app if it's stretching just shy of 4 gigs as is. Also considering that not a single 32 bit machine is supported, on windows or mac side, why is this app even a 32 bit binary in the first place? Isn't it time to make this a 64 bit binary to throw any current memory limitations out the window? It should also help game performance a little bit like it did for wow by adding in addition cpu registers. Unlike wow though, seems like far far less reason to support dual binaries. go 64 only and optimize it that way. :)

    We cannot stop supporting 32 bits on Windows. Too many customer have a 32 bits OS.
    64 bits support is considered but it would be a huge task. Optimizing our memory usage is most likely easier.