- User Since
- Jul 26 2012, 3:13 PM (459 w, 5 d)
I need to amend my previous with the fact that I have updated the operating system one or more times and that an Apple update may have affected this outcome. I am running the current updated Big Sur from the screen capture:
I am optimistic after just downloading << Blender-3.0.0-0e581f619670-macOS.app>> and trying everything I could think of to get Blender to crash. I am still using the same equipment of when I first reported the bug. I turned the screensaver to sleep after 1 minute and minimized Blender and after waking the screen Blender worked normally. I did some preemptory screen blanks and waited several minutes before coming back on with a key press knowing the screen saver would have come on. It won't crash. Let's see if others have the same experience !
Mar 15 2021
Thanks for looking into this. I just now downloaded the latest Alpha: -2.93.0-070010e203f6-macOS, and opened it. It seems normal with camera and light showing with the cube. It must have just been that one version that had something turned off in the code. I'll write it up if it happens on other files. I used this Alpha for an hour and didn't notice any anomalies. Still missing Radeon Pro render for AMD -- I suppose it may be dropped for redesign.
Mar 5 2021
It may be that it only occurs when the Alpha is newly installed in OS X and once something triggers the camera or light to appear, it is no longer acting as hidden.
Hopefully it is an anomaly that will disappear with subsequent updates.....
I also noticed that Radeon Pro render for AMD is no longer available? I have all the Preferences switched on for it still but it is not showing in the drop down.
Mar 3 2021
Feb 6 2021
I just retried the problem with today's Alpha version: -2.93.0-d85c5accecd5-macOS and am happy to say the problem no longer exists!
Jan 29 2021
OK, there is still something wrong with this.
Jan 12 2021
Jan 11 2021
Jan 7 2021
Last night I was thinking of how long I have been using Blender and NEVER knew about Apply. I tried looking to find out about when I needs to be used and there is nothing that as a User seems really clear-cut. As a programmer, I understand Commit and the need to reset the Origin, but from the outside User view, without knowing the coding, it is hard to really get a grasp on when it is vital to making something work right--like mesh on a path. I appreciate Falk's careful explanation of the steps needed but it also strikes me as the feeling I got from "Hitchhiker's Guide to the Galaxy" when we were told Earth was to be "cleared away" and that the notice was clearly posted on Rigel 4. IF you don't have the Item / Transform open while working with this operation, there is no clue that you are doing anything wrong, except it is frustratingly erratic.
Jan 6 2021
USING: Blender-2.92.0-5424b4821d28-macOS (6 Jan 2021)
Thank you Falk and Philipp for the help on this. I have spent a month off and on trying different random bezier curves and meshes to try fitting and it seems the critical thing is to get the ORIGINS to both be at the World Origin to start. THEN each sizing or change needs to be APPLIED although not always--except that the Dimensions and Scale are tied together so that the Scale change from 1.0 means the change needs to be Applied. It is still a mystery sometimes how to get elements together. Down the road maybe more hand-holding controls to make it come and stay together .....
Jan 4 2021
Dec 9 2020
OK, the third time I tried this per above, it worked normally. SO, I couldn't find the DELETE to remove this. It absolutely would not back out at with the mouse pad normally.... on first two attempts.....
Dec 8 2020
Not been a good day for trying to get something simple done. Another crash and image of exactly what I have been trying do. From the prior report, I re-added the point light and went to Ortho top view as shown and < Opt . > merged the vertices shown, then did the same on the lower ones. Next I clicked < 1 > to see the side view and was panning back and forth sideways to see if "I could get away with it" when the crash occurred. (Using EEVEE). Had only been on for ~10 minutes this time. Am I getting a message from beyond no to do this? -- Paul
Dec 7 2020
More crashes from earlier version: Blender-2.92.0-1166110a9d66-macOS. Using the same blend file above ~ Fence4. I added a point light and adjusted the wattage, looked at the camera view <0> and changed the render from EEVEE to Radeon ProRender and then switched back to EEVEE. Next I went to Orthographic top view and zoomed in <+> and selected the roof in Viewport Shading and then in Edit mode selected the top two nodes on the roof and was trying to select the adjacent lower nodes to do a merge when the crash occurred. Got to save more often perhaps?
No longer a problem since 2.91. Resolved for now. Paul
Oct 27 2020
Like I said, it was so unexpected that I have no way of guessing how to repeat this crash. Let's just call it a one-off and close this. IF others get more of an idea of how this happened in the future, they can report it. It happened, so I just passed it along, not knowing if it would happen somehow for others. I don't have any older Alpha's; only keep two or three.
Oct 25 2020
OK, the texture and normal files from Japanese website ready to download: http://www.benkyoustudio.com/Textures/TexturesBrick/
Oct 22 2020
Here's the blend file (should have included above).
Oct 15 2020
OK, well it must be an artifact created by my GPU having something to do with Perspective and Solid view. These screen captures show a slight view rotation and the wedges moving across the mesh surface.
Since it doesn't interfere with anything and only appears in Solid view and Modeling, I suggest moving on and Closing this for now. IF it somehow actually interferes in any important way, I will bring it back up.
Oct 13 2020
Hopefully it will open in Modeling with the 3 wedges of shadow showing. Move the mesh sideways and it becomes obvious. It happens in Solid view and User Perspective. Click 5, into Orthographic and it disappears.
Sorry but I just downloaded the latest version and tried it a couple of times with the same result. I fear that every item in Preferences might be susceptible to this problem. Then again, how many are stupid enough to try this? Maybe time better spent elsewhere for now?
Oct 10 2020
Sorry Robert, now that I see how beautiful the menu is after RT-clicking the Collection, I feel kinda dumb. However, so many graphics programs allow this kind of drag'n'drop that it is like an atavistic action to try it. I hope it is easy to fix.
Oct 9 2020
Thanks you Philipp for showing how to turn off the green edges, but I am curious about why they were marked initially. I can't see anything "sharp" about them as they are on a flat mesh, not on a steep edge. I turned them off an ran Mesh Analysis in Wireframe and there are lots of other "errors" colored but none of those green edges. I then ran 3D Print add-on and Check All. It showed 7 Sharp Edges but none of the green and exactly as expected on tight angles. The marked green edges seem to be specious and perhaps an artifact of having done a Vertex Merge by Distance? Yes, averaging instead of marking seems a better option -- marking green is just worrying and doesn't seem relevant.
Oct 8 2020
Again, check to see the difference between Layout and Modeling—not getting problem using Layout—having lots of problems when in Modeling. Overheating GPU happens just in Modeling when both Solid and X-ray views selected.
I just got the latest build: Blender-2.91.0-099ce95ef36d-macOS. I discovered that in LAYOUT mode this doesn't happen. It only happens in MODELING mode and it happens every time. Modeling mode hates my GPU and will overheat it into a molten mass if left un-aware, No overheating while Editing in Layout mode. Hint Hint.
Oct 7 2020
Thanks for the interest. At this point I'm not sure this needs more attention. The more I read about using AMD's GPU with Blender the more I'm coming to the conclusion that it is not fully compatible. This is an excellent case.
I continued to work with this mesh and ignored the colored edges since they didn't affect the look of the Shading. Eventually I found the Add-on, Mesh: 3D Print Toolbox. One of the choices actually selected all of the SUB-meshes in my entire mesh and corrected it with Make Manifold -- a miracle!
I am just hanging in and muddling through the learning process" by doing" even knowing that without a CUDA compliant / imitating GPU that things are not going to act "normal". I will endeavor to find "errors" and report them but this one I would suggest is just a GPU anomaly that can be ignored but now "known".
Oct 6 2020
I downloaded the 5 Oct. version: Blender 2.91.0-a4f8b2ad7653, and this feature is working correctly now.
Oct 1 2020
My GPU is a premium buy for Mac:
Radeon Pro Vega 48:
OK, I have uploaded the Blend file. I have the two horse eyes in the bottom listed collection. Clicking on "eye" in the Collection listing for each eye works but clicking the "eye" for the view of that collection doesn't work even though the whole collection listing goes dark as expected, the two eyes remain on.
Sep 29 2020
I don't know if this matters but I Appended the Eye from a prior Save. I brought it in as an Object and it went right into the correct place. But clearly it is not responding to any coordinates X , Y , Z in the current open file for Mirroring.
I suspect that my GPU is not a good candidate for using Blender. I seem to find a lot of problems that no one else has mentioned yet.
Sep 26 2020
Apparently using mirroring to try and add eyes to the face does bad things? Unfortunately I'm not sure if I had Mirroring ON when using Decimate--if that complicated things -- I think not. However the effect is very direct when switching it ON and OFF as shown in the screen captures. It looks like the problem is caused when using mirroring as it attempts to mirror using an already existing mesh -- maybe a beginner's mistake, but then how can one make changes later to add more detail using Extrude? I'm thinking that because Sculpt has Mirroring built in that the assumption is that it would be used for this situation.....
Pushing on with the example, this is obviously the wrong way to try to rectify the "under mesh" situation as I will never be able to put eyes on my horse with this still messed up mesh. But I am curious about this occurrence nonetheless. I looked at it in Shading view and it looks alright although there may be some flipped faces to fix as well. I will go to a much earlier version before using Decimate and try something else. I wish Decimate worked to somehow detect and reconnect/remove parallel "under" meshes as it is being used. Maybe this will be a future enhancement.
Look at the screen captures. I sent the blend file to play with. SO, I selected the area that has a mesh under the top mesh which happened when using Modifier Decimate after using Subdivision Surface to remove unnecessary quads. I noticed the double mesh in the face in Solid view when I was finished Decimating and selected the vertexes using wireframe. Next I selected Mesh / Cleanup /Merge by Distance. Upon sliding the Merge by Distance to the right, these marks start appearing. I used the same file again and repeated the process to see what would happen if I continued dragging right and the screen capture shows the result.
Check the view eye of a sub-collection --it not working as expected.
Sep 22 2020
This problem is worse: Blender crashed using Shift-H and Alt- H in sculpt mode. This is the latest build created Today, 5:34 AM: The UN-hidden didn't appear initially until playing with Dyntopo again and then trying to get the rest of the mesh back with Alt-H caused the crash:
Process: Blender 
Path: /Users/USER/*/Blender 2.91a2.app/Contents/MacOS/Blender
Version: 2.91.0 (2.91.0 2020-09-22)
Code Type: X86-64 (Native)
Parent Process: ??? 
Responsible: Blender 
User ID: 501
Sep 20 2020
Thank you Robert for reopening. I dearly need that view option to do effective Modeling and every time I click onto it I can hear the fan starting to work faster and heat starting to accumulate. I can't believe no one else has had this problem or perhaps doesn't recognize the cause. I am adding this message because I am using 2.91alpha and it has the same problem. I will continue to download and use the latest experimental version to see if anything has changed.
Sep 12 2020
What is Invalid is that the issue is resolved--not so fast! Invalid means the same as Resolved? And Normal means all is fine? The labels need a little more clarification.....
I tried 2.91 alpha and thought it didn't have the problem but finally, it sent the GPU to 92% and just hung with no screen movement. So unfortunately it has yet to be resolved. ( I added a message before that it was resolved but found it isn't.)
Sep 11 2020
A clue is that there is no problem with version 2.83.5 (using same blend file too) with this combination of views and I was only able to get the GPU up to 50% with a lot of moving around but then it dropped back immediately when I stopped to zero. Some code difference in 2.90 is causing the GPU to jump to 80%+ and hang there regardless of movement.
I have notified Apple about the problem as well -- whatever the code is, it could be "dangerous" for the way OSX is dealing with it.....
Yes, now it happens every time something is selected in edit mode--even something small in number of edges like a detail in Edit Mode after hitting /.
It doesn't seem to be noticeable at first because it takes a minute to build the heat to get the fan getting louder. The thing is to watch the Activity Monitor and it immediately jumps to above 80% GPU usage with X-RAY and SOLID selected at the same time. I LOVE this mode combo and would like to use it (a thing of beauty) but my system flames out. Somehow MS systems don't have this problem.
Sep 9 2020
OK, caught it in the act this morning (see screenshot). I was using Solid with X-ray view and holding down "." to orbit around to check edit when the fan started getting louder. etc. I think it may be something to do with having both views selected at the same time. Changing from Solid to wire-frame drops the GPU usage immediately, other wise it just hangs at 86% - 92% usage until switched or computer melts..... I assume there is someone else there who is using a Mac to check this out.
Sep 8 2020
Yes, I'll keep Activity Monitor on all the time using 2.9 now. I only have the one GPU:
Radeon Pro Vega 48:
I also continued working with the same file and can't get it to repeat the overheating this afternoon. It happened this yesterday morning 3 times and has ghosted me two other times. Perhaps it's just the particular brief activity / setup I have going that sets the process in motion. I have been using EEVEE occasionally and that shows little if any activity in the CPU and none in the GPU. The SOLID view, doesn't show much that would indicate the overload although I don't have time to turn on Activity Monitor before shutting down the overload--it's that fast when it happens.
I assume I am the only one to experience this and will assume that it too shall go away with the constant Blender updates. I really thought I had it nailed. If no one else finds it in a week then mark this "resolved" again and I'll just be careful until I can get a few versions newer.....
Thanks Ankit for the effort!
Sep 7 2020
Explanation PNG file and actual Blend file attached. I have reproduced this 3 times today and feel satisfied that it should be quickly repeatable. This is the problem that I reported a few days ago but couldn't repeat -- other than a clear sense that the Solid view was somehow sucking up more resources and a problem.
I checked this by selecting the two objects and either already being in Solid view ( or switching into Solid after going in Edit) and then going into Edit Mode and waiting about 10 seconds for the fan to start revving. I then clicked back to wire frame or any other view to stop the overload. HEAT starts belching out of the back right away so be careful.
I don't know what the upper limit of vertices is for this computer--perhaps I have exceeded that limit except that there is no problem with any other view so far.....
Sep 5 2020
I used 2.90 today and tried Minimizing Blender several times and nothing happened. So it is perhaps a coincidence of two processes running at the same time that were antagonistic? So far so good and I'm liking 2.9 a lot and barely had time able to see what it can do!
Thanks for your attention -- I though I had a very bad bug (not looking for attention). IF it reappears in some form that is repeatable, I be back on here.
Sep 4 2020
Yes, I am currently using 2.83.5 with no difficulties. My problem is that I don't have adequate tools to see what is happening with the overheating with the meager Apple tools given. All I can say is that I was shocked when Minimizing to the Dock caused the system to heat and loud fan noise to increase. IF I had just left the room as normal the system could have shut down from thermal overload (I HOPE). I acted just like a render on my 2009 iMac with massive overheating except this was more immediate so I noticed it. I checked to make sure it wasn't rendering. I also checked to see if somehow I had signed up to be part of a server rendering farm (done that). I won't be using 2.90 until this "bomb" is defused. I am surprised it hasn't happened to any others yet. Almost seems like a malware, it is so unexpected.
I am also surprised that high GPU happens primarily with the Solid mode and that it requires so much more than the more refined modes or EEVEE.
Sep 3 2020
See the above comments on Minimizing Blender 2.90! Very surprising. I had to add this comment because I didn't see how to change Status when I added the above.
Two problems, one critical:
Sep 2 2020
Unable to pinpoint reason. Used the same blend file in both 2.83.5 and 2.90. Within a few minutes of moving 1172 vert. subject (not huge) the fan and my SSD iMac starts getting louder and the heat starts pumping out of the back unlike anything I have experienced before. I tried to see what Activity Monitor could show as the cause, but it looks about the same in 2.83.5.
I just wanted to call it to someone's attention, Just loading this file into 2.90 and moving it around and editing doesn't seem to consistently make the heating happen. This is the first day using this version and will continue to watch for what triggers the high GPU usage. I am not using the EEVEE render mode or any image render to make this happen. VERY STRANGE-- it won't come back and be reproducible during each session. Hopefully I am the only one who notices this "ghost". Write if you want specific other info.