5.1.8 jit.qt.movie direct to screen bug

    Apr 28 2011 | 6:38 pm
    Hi guys, Here's the patch to reproduce.
    Hardware Mac OS X 10.6.7 Max 5.1.8 Macbook Pro 13.3" NVIDIA GeForce 9400M
    1. Read bball.mov 2. Start Metro 3. Go fullscreen. No Problems Direct to window works.
    Repeat 1, 2 3. Open the jit.qt.grab 4. Go fullscreen. After a second or two suddenly a giant purple artifact appears on the right hand side of the screen.
    This is more than just a little inconvenient, this breaks the functionality of an existing patch.

    • Apr 28 2011 | 9:23 pm
      We can repro. Thanks for the report
    • May 05 2011 | 5:08 pm
      This may be a weird hardware or driver issue. Can you please try the following?
      1. Download and install/run gfxCardStatus from http://codykrieger.com/gfxCardStatus 2. Switch to your integrated graphics card (intel HD graphics) 3. Launch Max and run your test
      Can you reproduce? I can't. It seems to be limited to the discrete NVIDIA card.
      It's unlikely that we'll be able to fix this immediately, but I'd be happy to know that there's some kind of workaround for users using these features until we can address it properly.
    • May 07 2011 | 3:49 pm
      Can't until May 18th. On vacation.
      Didn't think the 13" had a discrete graphics card (I know you can deity off the other in the 15" model).
    • May 09 2011 | 2:09 pm
      You're correct. Sorry about that, I missed the 13" part of your original post. Nevertheless, it does point to an issue with the NVIDIA drivers.
      When you get back, you might want to download and try this: http://www.nvidia.com/object/quadro-macosx-256.01.00f03v7-driver.html . It's officially for the quadro 4000, but apparently fixes some incompatibilities with 10.6.7 for your card (and mine as well).
      Please let us know how it goes.
      EDIT: those update drivers might only work on Mac Pros. If so, sorry for the noise.
    • May 20 2011 | 2:03 am
      No dice "This machine will not support this Nvidia Solution".
      Any other thoughts?
      Can also confirm it's not a problem with 10.5.
    • Jul 25 2011 | 6:26 pm
      Sorry to bump, but any chance this might be fixed in the potential 5.1.9 update too?