GPU profiler error on Mac

Hi all, i have the error "Graphics card driver returned invalid timing information. Please update to a newer version in available" in the "GPU Usage" bar of the profiler. And gpu profiling doesn't work.
Lion 10.7.3

Thanks in advance.

 

Same. Ever fixed it?

 

Ive got the same problem.

Machine Specs:
iMac 24-inch, Early 2008
OSX v 10.7.4
3.06 GHz Intel Core 2 Duo
4GB 800 MHz DDR2 SDRAM
NVIDIA GeForce 8800 GS 512 MB

 

Strange because it's only just suddenly stopped working.

 

Yeah, same issue. I hope Unity Tech. can find a fix for this

 

Same problem here, on a MBP Retina, with 10.8.2

Intel HD Graphics 4000*:

Jeu de composants: Intel HD Graphics 4000
Type: Processeur graphique (GPU)
Bus: Intégré
VRAM (totale): 512 Mo
Fournisseur: Intel (0x8086)
Identifiant du périphérique: 0x0166
Identifiant de révision: 0x0009
Version gMux: 3.2.19 [3.2.

NVIDIA GeForce GT 650M*:

Jeu de composants: NVIDIA GeForce GT 650M
Type: Processeur graphique (GPU)
Bus: PCIe
Longueur de la voie PCIe: x8
VRAM (totale): 1024 Mo
Fournisseur: NVIDIA (0x10de)
Identifiant du périphérique: 0x0fd5
Identifiant de révision: 0x00a2
Révision de la ROM: 3688
Version gMux: 3.2.19 [3.2.8]
Moniteurs:
LCD couleur*:
Type de moniteur: LCD
Résolution: 2880 X 1800
Retina: Oui
Profondeur de pixels: Couleurs 32 bits (ARGB8888)
Moniteur principal: Oui
Miroir: Désactivé
Connecté: Oui
Intégré: Oui
Type de connexion: DisplayPort

 

Same problem. Mid-2012 MacBook Pro

 

Same thing here, 10.8.2, 3-week-old Retina MBP.

Occasionally the GPU profiler displays something like this interesting graph:



But most of the time, it only displays the error message described above.

Any update on this being fixed?

 

MBP Retina, 10.8.2:

Hardware Overview:

Model Name: MacBook Pro
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 8 GB

Intel HD Graphics 4000:

Chipset Model: Intel HD Graphics 4000
Type: GPU
Bus: Built-In
VRAM (Total): 512 MB
Vendor: Intel (0x8086)
Device ID: 0x0166
Revision ID: 0x0009
gMux Version: 3.2.19 [3.2.8]

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]
Displays:
Color LCD:
Display Type: LCD
Resolution: 2880 X 1800
Retina: Yes
Pixel Depth: 32-Bit Color (ARGB8888)
Mirror: Off
Online: Yes
Built-In: Yes
Connection Type: DisplayPort
Thunderbolt Display:
Display Type: LCD
Resolution: 2560 x 1440
Pixel Depth: 32-Bit Color (ARGB8888)
Display Serial Number: C02HQ0L1F2GC
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Connection Type: DisplayPort

 

I understand the situation and appreciate the response. But as for "There's not much we can do" -- certainly there is, Kaspar said 4 months ago that you'd follow up, but there has been nothing since then. What did Apple / NVIDIA say? Is a fix coming this year? Next year? Never? This has completely halted progress on my project, since I'm trying to optimize graphics on OS X now. I can't afford to buy a different Macbook, this one is all I have!

One of the reasons I love Unity is that you devs are informative about your progress on tech issues.. so even if you can't fix it yourselves, please put some more pressure on Apple/NVIDIA to fix their timing data, and please give us some indication of how it's going, so we can plan our work around this until it's fixed.

 

This effects me, too. Same model as ShaneStevens.

 

Same thing is happening to me but the weird thing about it was that it was working before on my MacBook but once I tried adding occlusion culling to a scene that had no static gameobjects (I do not know why I was doing that lol) it somehow messed up my GPU reading.

[EDIT] This was fixed for me by restarting my MacBook. But I guess you guys are having the same problem still.

 

Even I have the same problem. Like someone said earlier - it is weird as it just popped out of no where. I had the information properly said until now. Just to fact things, I did not update Unity or my Mac before and after.

 

Can't believe nothing yet?! Maybe with mavericks, but we can only hope. Anyone been able to develop any get-around in the mean time?

 

COULD (like in many other problems i've been reading about) the HD4000 be interfering again? Is there any details you could share on how this information normally is obtained? (Like, do you ask OSX for 'a' default or active device's time, possibly causing it to return a "random" card's time in the case of a multi-gpu setup? or is this info requested more specifically?)

On a more serious note for those that expect apple to get "on top" of issues like this;
Welcome to the real world with a very clear example of where apple DOES suck.
The system is closed-down as hell, yet STILL functions break in the quite specific environment OSX has.

 

I mean, it could be NVIDIA's fault just as well as it could be apple's. And I don't think it's the HD4000 that's causing the problems as I have the same problem on my computer as well which has integrated graphics with an Intel core 2 duo. I suppose this means that the problem is directly related to OSX. Has anyone on the mavericks beta had better luck?

 

Bump. I just encountered this problem. Unity seems to be running more and more slowly and when I was doing some frame rates tests I'd notice things like my Overview window on the profiler going blank, my GPU graphs looking wonky and then getting this error message. I'm on a mid 2012 macbook pro with 16gb ram and a 1gb video card. Are there any updates to this?
thanks
-Mike

 

FWIW I found out a workaround. The problem happened for me when I was using an external monitor as well as the MacBook itself. If you close the clamshell and only use the external, or just use the macbook itself, the GPU issues go away.

 

10 stars for the workaround described above. 15" MBP, circa 2010 w/ AMD HD 6490M GPU - same problems as described through the thread. Fixed with simply using just my external. I miss the extra real estate, but the bump in overall FPS and performance (along with fixing the incorrect timing issue) is most welcome. Thanks @moproductions for posting your solution.

 

Same issue here. The card is an NVIDIA GeForce GTX 680MX 2GB.

Unfortunately I can't use the workaround above - I’m using an iMac 3.4GHz Intel Core i7 with 32GB running OS X 10.9 (Mavericks), with no external display.

 

Same issue here also...

Using newest 27" iMac with Mavericks with NVIDIA GeForce GTX 780M 4gb..

 

Same problem:

I have a AMD Radeon HD 6770M Macbook Pro 15"

 

Still no fix for this...

 

I've raised case 597347 for this issue.

 

Same problem:

I have a AMD Radeon HD 6630M 256 МБ, Mac mini, OS X 10.9.2 - Mavericks

 

Still no response to my bug report.

 

I have a MacBook Pro and and iMac and I get this problem on both machines. From this thread, it looks like this issue only occurs on newer Macs (GPUs since 2012) - is anyone using a new Mac NOT getting this problem?

 

Anyone else having this issue should probably vote for it:

http://issuetracker.unity3d.com/issues/gpu-profiling-doesnt-work-on-maveric-nvidia-gt650m

I personally purchased Unity PRO just to get the profiler, and now have, well, half a profiler ...

 

the same story...

 

i was 'going' to buy unity pro for the same reason (currently using the 30 day trial) no chance now though until this is sorted!!!

 

Pretty same here!

 

anything new?
I mean two years later its (still) not working on my Machine (MacbookPro Retina 2013- NVIDIA GT 650M - i7 2,7GhZ - Yosemite)

 

Good news - it's working in Unity 5.

 

Yiha, so I can use it in 1 Year

 

I have this regularly on my MacBook Air with an Intel HD 4000 where it would work for a short while and then break.

Now I've just noticed this happens when the profiler is open before starting playback. If the profiler is open and enter playback then I get this timing error until I reopen Unity. If I close the profiler and only open it when in play mode, the GPU profiler works fine.

This is on Unity 4.5.5 haven't tried with 4.6 or 5.

 

Im having this same problem on my late 2013 iMac running Yosemite and Unity 4.6

Graphics card is:

NVIDIA GeForce GTX 775M 2048 MB

 

Sorry for digging this up but it doesn't work on my iMac.
GPU: Intel Iris Pro 1536 MB