- User Since
- Nov 26 2008, 2:54 AM (554 w, 6 d)
Thu, Jul 11
Successfully opened the file, and chose Object Mode, instead of Particle Edit mode, was able to F12 Render. Apparently the crash is only in Particle Edit Mode. Still haven't figured out how to "Commit the Edits" of the Particle Edit, so I can go back and increase the number of Hair Particles??
I have uploaded the file, which now crashes immediately. Open the file, press F12, watch Blender disappear.
I did not even try the Disconnect Hair or the Disconnect All, just Open, F12, Crash.
Hope this helps.
I appreciate the development, congratulations on the RC release.
Jun 8 2019
Thank you for the clarification. The Addon worked on prior versions the week before, and I thought you might find it useful to know, as it is a 'complete crash' out for Blender, yet it worked in prior versions. I have forwarded your response on to Quixel support in addition to my original submission to them, placing it in their lap. I will await to see the response, and will continue downloading newer versions of Blender to see if it gets any better.
Jun 7 2019
May 25 2019
It appears to be working, after being in 2.79 and coming back. I will check it again in the morning, but I must have been doing something wrong. Probably a false alarm. Not sure what the error message meant??
I had turned off the visibility of the Collection into which I had put the Set Elements, that I was then trying to add the Armature to, thus the problem, I think. Just now, selected the correct Collection, added the Bird Armature, without problem, now to fit it.
Thank you for the fine work by all.
May 21 2019
May 13 2019
Dec 19 2018
Sep 6 2016
I just installed the latest BuildBot from the Blender "Bleeding Edge" downloads. I checked, the color picker is working fine. I enabled Node Wrangler, still fine, enabled PBR Materials, still fine. Tired Asset Manager, (which the developer has stated is not yet 2.78 compliant) and the CMD window was coughing up hairballs, for the moment. Seems like your team has snuffed out this one. Congratulations. Best to you on the 2.78 release.
I checked, and I have never changed the defaults. I tried them all and they all seem to work, when just going over to the 'nearby' color choices in the User Preference window, so those do not seem to be a problem. I will look forward to the next RC and see if Node Wrangler acts better. I know that Asset Manager hasn't stated 2.78 compliance yet, and I do not know about PBR Materrials, as both of these threw up 'complaints' in the CMD window. Thank you again for your response and your team fine development work.
I tried the Factory Default, color wheel worked fine, thank you. Node Wrangler, downloaded the latest from their site, but the problem was still present. Turned off Asset Management and PBR Materials as I saw some error warnings in the CMD Window, and turned off Node Wrangler. Color wheel works fine. So "one" of them appears to be contributing. Thank you again.