MacPro model late 2013 problems with Blender #40725

New Issue

Henk Vostermans · 2014-06-20T08:32:22+02:00

Henk Vostermans commented

2014-06-20 08:32:22 +02:00

Blender Version 2.70a

Blender does not work well on a MacPro model Late 2013. I bought this computer to facilitate working with Blender. Working in the viewports is not smooth. The objects are turning in steps. Also making adjustment in material settings is not smooth. The settings are jumping so its difficult to move toward the needed settings.
If I make changes in the Image Draw Method between GLSL and Draw Pixels till I make changes in the object it works better. Its extremely frustrating.

Processor 2,7 GHz 12-Core Intel Xeon E5
Memory 32 GB 1867 MHz DDR3 ECC
Graphics AMD FirePro D700 6144 MB

Before I also used a MacPro model 2010. This combination worked much better.

Hope somebody can give me some workable advice.

Blender Version 2.70a Blender does not work well on a MacPro model Late 2013. I bought this computer to facilitate working with Blender. Working in the viewports is not smooth. The objects are turning in steps. Also making adjustment in material settings is not smooth. The settings are jumping so its difficult to move toward the needed settings. If I make changes in the Image Draw Method between GLSL and Draw Pixels till I make changes in the object it works better. Its extremely frustrating. Processor 2,7 GHz 12-Core Intel Xeon E5 Memory 32 GB 1867 MHz DDR3 ECC Graphics AMD FirePro [D700](https://archive.blender.org/developer/D700) 6144 MB Before I also used a MacPro model 2010. This combination worked much better. Hope somebody can give me some workable advice.

Henk Vostermans commented

2014-06-20 08:32:22 +02:00

Changed status to: 'Open'

Henk Vostermans commented

2014-06-20 08:32:22 +02:00

Added subscriber: @HenkVostermans

Thomas Dinges commented

2014-06-20 08:39:46 +02:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2014-06-20 08:39:46 +02:00

That is not a real bug (in terms of reproducible for us). Maybe its an issue with the GPU (Driver).

Try to change the Window Draw Method (User Preferences -> System) to something else, maybe it gets better? Do you use heavy scenes or does in also happen in simple (default) ones?

That is not a real bug (in terms of reproducible for us). Maybe its an issue with the GPU (Driver). Try to change the Window Draw Method (User Preferences -> System) to something else, maybe it gets better? Do you use heavy scenes or does in also happen in simple (default) ones?

Henk Vostermans commented

2014-06-20 08:56:57 +02:00

When I make changes in GLSL into DrawPixels (and save user setting) it works fine. When I change something however I am back into trouble. Also setting made by sliders is not doable because it moves in fragments. All other programs on the MacPro are working fine.

Henk Vostermans commented

2014-06-20 11:40:00 +02:00

What can I do to make the priority higher? The computer configuration in combination with Blender is not workable.

Thomas Dinges commented

2014-06-20 11:54:19 +02:00

Did you try my suggestion with the Window Draw Method?

I am afraid this is a issue with the GPU driver, we cannot fix a bug, that we cannot reproduce. I have no issues on my Late 2013 Macbook Pro.

Did you try my suggestion with the Window Draw Method? I am afraid this is a issue with the GPU driver, we cannot fix a bug, that we cannot reproduce. I have no issues on my Late 2013 Macbook Pro.

Henk Vostermans commented

2014-06-20 13:09:22 +02:00

I did try all 3 options. If I make a change in the Window Draw settings, (whatever the choice is) it works. Afterwards if I make a change in a setting (fi material) or make adjustment to the object it bad again. So what setting did you made on you MacPro? Perhaps I can try those?

Henk Vostermans commented

2014-06-20 13:30:54 +02:00

I think its the AMD FirePro D700 6144 MB which is casing the problems. I also have an iMac. No problem whatsoever.

I think its the AMD FirePro [D700](https://archive.blender.org/developer/D700) 6144 MB which is casing the problems. I also have an iMac. No problem whatsoever.

Thomas Dinges commented

2014-06-25 04:50:26 +02:00

Changed status from 'Open' to: 'Archived'

Thomas Dinges closed this issue

2014-06-25 04:50:26 +02:00

Thomas Dinges self-assigned this 2014-06-25 04:50:26 +02:00

Thomas Dinges commented

2014-06-25 04:50:26 +02:00

Closing this one now, there is no way for us, that we can fix a OpenGL issue related to a GPU card/driver.

Henk Vostermans commented

2014-10-12 15:34:51 +02:00

Dear Thomas,

Why did you close this demand? I bought the MacPro and I still have this problem. The MacPro I had before (model nov 2010) worked perfect. Can you give me information how to address this to Apple. I also started a discussion with Apple to try to find a sollution. Is there a possibility to pay for a solution from Blender?

Dear Thomas, Why did you close this demand? I bought the MacPro and I still have this problem. The MacPro I had before (model nov 2010) worked perfect. Can you give me information how to address this to Apple. I also started a discussion with Apple to try to find a sollution. Is there a possibility to pay for a solution from Blender?

Thomas Dinges commented

2014-10-12 15:48:35 +02:00

Added subscriber: @jensverwiebe

Thomas Dinges commented

2014-10-12 15:48:35 +02:00

There is no way that we can fix this as far as I know. Blender heavily relies on a proper OpenGL implementation inside the GPU driver, if there are issues, that is outside of what we can do.

CC'ing our Mac mainteiner Jens, maybe he can give you a better tip. Also we have a MacPro 2013 at the Blender Institute and that works fine afaik? @Sergey

There is no way that we can fix this as far as I know. Blender heavily relies on a proper OpenGL implementation inside the GPU driver, if there are issues, that is outside of what we can do. CC'ing our Mac mainteiner Jens, maybe he can give you a better tip. Also we have a MacPro 2013 at the Blender Institute and that works fine afaik? @Sergey

Thomas Dinges commented

2014-10-12 15:50:05 +02:00

Added subscriber: @Sergey

jens verwiebe commented

2014-10-12 17:35:15 +02:00

@ Henk
Is this on 10.9.5 or 10.10 Yosemite ?
I also 'am not satisfied with redraws on 10.10 in some circumstances.
The GM2 and 3 introduced sloppy finder and safari in the mains, sometimes
typing is like being on an i386 from 1990. Imho this could be due the new
gl caching mechanism. ( offline draws for scrolling )
Have not tested Blender in all regards atm. but my MacPro 5.1 ( 2010 ) with
AMD 7970 + 5870 is fine else.

EDIT: watchout for windowserver messages in console log pls and paste here.

Jens

@ Henk Is this on 10.9.5 or 10.10 Yosemite ? I also 'am not satisfied with redraws on 10.10 in some circumstances. The GM2 and 3 introduced sloppy finder and safari in the mains, sometimes typing is like being on an i386 from 1990. Imho this could be due the new gl caching mechanism. ( offline draws for scrolling ) Have not tested Blender in all regards atm. but my MacPro 5.1 ( 2010 ) with AMD 7970 + 5870 is fine else. EDIT: watchout for windowserver messages in console log pls and paste here. Jens

Ton Roosendaal commented

2014-10-12 20:15:34 +02:00

Added subscriber: @Ton

Ton Roosendaal commented

2014-10-12 20:15:34 +02:00

Henk mailed me private for help too, but I cannot add anything sane to this.

The iMac here (AMD) and the MacPro (new) do fine.

The user preferences for buffer swap should just be on "Automatic".
Try Blender in factory settings. Set it to factory, and then save the settings, and quit blender and restart it.

Or go to ~/Library/Application\ Support/Blender/ and delete the directory with the name of the last version. This makes sure no old settings got copied over.

Henk mailed me private for help too, but I cannot add anything sane to this. The iMac here (AMD) and the MacPro (new) do fine. The user preferences for buffer swap should just be on "Automatic". Try Blender in factory settings. Set it to factory, and then save the settings, and quit blender and restart it. Or go to ~/Library/Application\ Support/Blender/ and delete the directory with the name of the last version. This makes sure no old settings got copied over.

Henk Vostermans commented

2014-10-12 21:26:42 +02:00

I deleted everything in the mentioned directory. All the old settings are gone. First impression was OK, but after making changes (project about 450mb) it is not smooth anymore. After changing settings: (2D Texture versus Draw Pixels) it works again until I make changes in project.

Should I now address this to Apple as a hardware problem?

I deleted everything in the mentioned directory. All the old settings are gone. First impression was OK, but after making changes (project about 450mb) it is not smooth anymore. After changing settings: (2D Texture versus Draw Pixels) it works again until I make changes in project. Should I now address this to Apple as a hardware problem?

jens verwiebe commented

2014-10-12 22:08:29 +02:00

This sounds indeed a bit like a HW problem either RAM or VRAM related.
If you enconter this phenomenia with other memory intensive SW as well,
i would be pretty sure it is. Atm. the information is a bit poor to finally judge
but i propose to check the machine at least.
Your report is rather untypical although all out compared machines work
but have not the D700 gpu's afaik. Still could be a rare driver thingie.

My personal guess is hardware too indeed.

EDIT: you still did not mentioned your OS version....

Jens

This sounds indeed a bit like a HW problem either RAM or VRAM related. If you enconter this phenomenia with other memory intensive SW as well, i would be pretty sure it is. Atm. the information is a bit poor to finally judge but i propose to check the machine at least. Your report is rather untypical although all out compared machines work but have not the [D700](https://archive.blender.org/developer/D700) gpu's afaik. Still could be a rare driver thingie. My personal guess is hardware too indeed. EDIT: you still did not mentioned your OS version.... Jens

Henk Vostermans commented

2014-10-13 08:47:29 +02:00

Thanks, will check with Apple to evaluate graphic card.
I will give OS version tonight. I thinks it is 10.9.5.

Thanks, will check with Apple to evaluate graphic card. I will give OS version tonight. I thinks it is 10.9.5.

Ton Roosendaal commented

2014-10-13 09:45:52 +02:00

Your report is very not typical, but you should give much better technical accurate information.

Like:

After changing settings: (2D Texture versus Draw Pixels) it works again until I make changes in project.

That is not good information. It should read for example:

In user preferences, i set "2D Texture to Draw Pixels", save user preferences.
redraw speed then is better, until I edit XXX using tool YYY and it is slow again.
when I save the blender file, and load it back, speed is good agan, until I use tool YYY again.

However, you should not have made that user pref change in the first place. Factory settings are good for testing this issue. You do something that makes texture draw slow. What is that? Maybe you just do things that go beyond the capability of the system, using texture images of 10k x 10k or so?

You work with technology and that is nearly always predictable. Errors you have are due to something you do. Find out how to make it predictable. Then evaluate your actions, skip steps, simplify it, until you have the issue.

Your report is very not typical, but you should give much better technical accurate information. Like: After changing settings: (2D Texture versus Draw Pixels) it works again until I make changes in project. That is not good information. It should read for example: - In user preferences, i set "2D Texture to Draw Pixels", save user preferences. - redraw speed then is better, until I edit XXX using tool YYY and it is slow again. - when I save the blender file, and load it back, speed is good agan, until I use tool YYY again. However, you should not have made that user pref change in the first place. Factory settings are good for testing this issue. You do something that makes texture draw slow. What is that? Maybe you just do things that go beyond the capability of the system, using texture images of 10k x 10k or so? You work with technology and that is nearly always predictable. Errors you have are due to something you do. Find out how to make it predictable. Then evaluate your actions, skip steps, simplify it, until you have the issue.

Henk Vostermans commented

2014-10-13 15:55:15 +02:00

Good news! We changed in the user pref anisotropic filtering settings to 2x and VBO's checked. Then everything functions like a charm.
Thanks for all your help. :)

Good news! We changed in the user pref anisotropic filtering settings to 2x and VBO's checked. Then everything functions like a charm. Thanks for all your help. :)

jens verwiebe commented

2014-10-13 16:30:34 +02:00

Changed status from 'Archived' to: 'Resolved'

jens verwiebe commented

2014-10-13 16:30:34 +02:00

Uhhm ....
VBO set is indeed lot faster but all in all i don't really understand what you described
in releation to this "fix". Perhaps the D700 (-driver) is picky here.

If it works i declare this as sloved then, closing the report.

So an advice for nMP user may be use factory anisotropic filtering ( = 2 ) + VBO'S enabled.

Thx for reporting.

Jens

Uhhm .... VBO set is indeed lot faster but all in all i don't really understand what you described in releation to this "fix". Perhaps the [D700](https://archive.blender.org/developer/D700) (-driver) is picky here. If it works i declare this as sloved then, closing the report. So an advice for nMP user may be use factory anisotropic filtering ( = 2 ) + VBO'S enabled. Thx for reporting. Jens

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

MacPro model late 2013 problems with Blender #40725