This might be caused by a depth offset made to edge/line by default so that it will not look dashed on a surface (avoid possible z fighting). You can try to turn it off with a method option:

Graphics3D[..., Method -> {"EdgeDepthOffset" -> False}]

Sander, we're looking into the problem and we can reproduce this in-house.

10.4 has a significantly overhauled OpenGL implementation which we expect will improve both the speed and quality of 3D graphics in upcoming releases. If there is a fix for this specific issue, we will work towards providing you and other customers an updated version.

In the mean time, please do provide the output from SystemInformation["Devices"]

Thank you for reporting this issue.

I'd like to see the pre-release program come back. I also have this particular problem, (Retina MacBook Pro with dedicated graphics.)

I set the option to auto-switch, but I think that the computer always uses the dedicated graphics with Mathematica.

I re-installed 10.3.1 until this issue is resolved. There is no problem (as noted by others) with 10.3.1.

Any news on the problem? I'm wondering whether there is workaround now so I can start using 10.4?

@Sander Huisman, Thanks very much for the feedbacks. We take it seriously and are working on 3D performance optimization now.

Also cool: On the higher MacbookPro Retina (Mid2014, 3GHz i7,16GB, Intel Iris 1536 MB) this rotates substantially worse than on the MacBooPro (Mid 2012, 2.9Ghz i7, 8GB, Intel HD Graphics 4000 1536 MB).

M.

Hi everyone,

I have tried this out on many different Macs now. I the latest, very highest spec MacBook Pro Retinas it works ok-ish (much worse than on 10.3.1 though), but on a highest spec MacBook the graphic takes 4 seconds or so to update. The MacBook has no issues on 10.3.1 at all with that graphic.

Cheers,

Marco

I assume you are talking about interactively dragging the Graphics3D object (rotating, etc.). I'm running 10.4 on Win 10. I don't see any slow down when dragging the cubes.

I still observe in version 11.0.0. (and since v 10.4.0) the important speed regression when rotating big 3D objects.

The motion is definitely much more fluid in version 10.3.1.

I am also on OSX (10.9.5), with a mid-2009 macbookpro which comes with two (nvidia) graphics card. Whatever card I switch to, the rotation is faster in 10.3.1

As previously observed by Szabolcs Horvat, I also notice that antialiasing is disabled in v 11.0.0 while rotating (?)

(My 3D graphics test object is Sander Huisman's first Lego shape in this post http://community.wolfram.com/groups/-/m/t/813449)

Really hope this get fixed very soon.

I am seeing the same lack of glitches on the 2016 MacBook after moving the slider all the way to the left (No Antialiasing).

I need to periodically make presentations, so I just bought and tested the Apple USB-C to VGA adapter. Regardless of having the Mathematica window located on the external display or the built-in display, the built-in display shows the glitches when rotating the head (slider back to Highest Quality)--though the glitches are not as persistent or noticeable.

An additional observation (should have posted on the other thread): rotating the 3D head is painfully slow on the MacBook ... Mathematica is using a little over 2 GB RAM and maxing out at 70% CPU during rotation with only one notebook open with one line of code.

That's interesting. It would be interesting to get some comments from people with MacBooks and similar computers (without dedicated graphics).

I got an e-mail from tech support that the matter had been turned over to the developers. Since the original problem was fixed for Macs with a dedicated graphics card (fixed in the first beta for M11), perhaps the problem will be fixed for the rest of the Macs for 11.0.1 or 11.1.

I thought that this issue had been resolved for v11. However, it is resolved only for Macs that have dedicated graphics cards. (During the beta tests, I just checked my 15 inch Retina MBP with a dedicated (NVIDIA) graphics card.)

However, there are other graphics issues that have shown up with V11 for Macs that do not have a dedicated graphics card. This includes all MacBooks, all MacBook Airs, all 13 Inch Macbook Pros (Retina and non-Retina), and some 15 inch Retina MacBook Pros. The dedicated graphics card is an option with the top-of-the-line computer. I have no clue about iMacs, although I believe that the 27 inch models all have dedicated graphics cards, and the 21.5 inch models probably do not.

Instead of having a speed regression, the screen is messed up and the whole computer freezes, requiring a hard restart. I was able to reproduce this with the RotateCubes.nb from the beginning of this thread.

Wolfram support knows about the problem, but they might like to know the extent of the problem. I am basing my list of affected computers on the feedback on the other thread.

no real work-around, the next release of Mathematica will bring improvements.

Btw: Mathematica doesn't have 'patches'.

I was referring to OS X. Not that I know anything about it, but somewhere I saw an upgrade referred to as a patch.

@Sander Huisman, Does that mean that the problem occurs only when older versions are patched, but not when an older version is replaced or El Capitan is installed on a clean disk?

Has the problem been fixed? I am trying to decide whether to upgrade to El Capitan.

I no longer have this problem with Mathematica 10.4.1 - it now uses the hardware accelerated libGL.so from my system. No idea why this became necessary and, further, why it is no longer necessary.

The files/directories may be named slightly differently between Linux and OSX but I think the key library is libGL.so (plus all the symlinks). On my installation this is inside the Mesa subdirectory - maybe on yours it's just in the Library directory or somewhere else?

Thanks I didn't know about this option!

I've never seen any negative correlation between pc speed and performance yet, so very interesting that this can happen!

Ok, so all the slow ones are Macs with El Capitan... well, unlucky us ;) I'm very hopeful a solution will come soon.

Perhaps, you could share also SystemInformation["Devices"] ? I'm not sure if the operating system might be important though...

Hi @Arnoud Buzing

I have attached a notebook with the command you said. I was also wondering what happened to the prerelease program, I think these are definitely things that could have been avoided or at least known before release. I would consider myself quite an extensive user (used it nearly half of my life) that use a lot of different domains of Mathematica and I think that prereleases would be great for the both of us (us playing around with new stuff, and you getting valuable reports in like the one above). I know @Szabolcs Horvat (another 'advanced user') also would like to see the prerelease coming back in order check compatibility of packages prior to a new release (something that is crucial for him and actually for the entire community that can't wait for all the packages made by others to be updated to support the new versions). Is there any such plan? You already have a mechanism in place that me and others used and it worked great! I don't see many downside, apart from perhaps a bit of bandwidth on your side...

Thanks for looking in to this, 3D graphics is at its very core and of course crucial for everyone, fortunately it seems the windows users (the majority of users I guess) are safe...

Attachments:

Your brain is still a bit moveable at 2-3 fps, but i would expect for my simple cubes, it should be able to do at couple hundred fps? (If i can imagine games like farcry or battlefield with many many polygons and physics computations run at 50-100Hz...)

I'm not sure what has caused this...