- User Since
- Oct 10 2018, 9:43 AM (32 w, 23 h)
Tue, May 21
Mar 6 2019
Jan 30 2019
Jan 12 2019
Jan 6 2019
Just tested in a newer version of Blender 2.80. The Spin tool and Spin Duplicate tool are no longer affected.
Dec 23 2018
Dec 21 2018
Dec 20 2018
Dec 18 2018
Dec 15 2018
Dec 14 2018
As far as I can tell, the face orientation colours are not themeable. Are you able to add a proposal for the addition of this feature? (as far as I can tell non-developers can't make proposals.)
Dec 13 2018
I agree with you, it does look nicer, I just find the old face orientation colours more useful. For example, I applied a sub-division surface modifier to my mesh and some of the faces were acting a bit weird. I put this down to possibly bad topology because none of the faces were that dark grey colour. I spent a couple minutes trying to fix the topolgy and gave up. I then opened the same file in an older 2.8 build to see if a certain bug was in that one and that's when I found my face orientation was pretty much random on the object.
I had the exact same issue. Two RX 570's reported and Blender crashes if the "false" GPU is enabled while rendering. Doing a clean install of the drivers fixed it for me.
I checked an older build 4c31bed6b46 from roughly the 30th of November. Both the issue I've reported (T59306) and this one aren't there. The issues are probably related.
Dec 9 2018
I'm also able to reproduce it here.
CPU: Ryzen 5 2600
GPU: RX 570 4GB
OS Windows 10 Home 64bit
Blender 2.8 Beta e79bb957fc3
Dec 7 2018
Just tested it with Blender 2.8 version 497a9ef7a39 on an RX 570 4GB with driver versions 18.12.1 on Windows 10 and I'm unable to recreate this issue.
Dec 3 2018
The smoke domain appearing black was caused by the fact that you'd plugged the "Principled Volume Shader" into the "Surface" output and not the "Volume" output. (Note: Blender crashes for me when switching the "Principled Volume Shader" to the "Volume" output while viewport rendering is activated on frame 1, I've reported the bug here: T58569)
The option to increase the number of cuts by using the mouse wheel is still there, you just need to use the keyboard shortcut rather than the tool from the tool bar. To do this, ensure that the loop cut tool is not select then press "Control+R". Now the loop cut will behave as expected/how it was in Blender 2.79.
Dec 2 2018
I think the developers designed it this way so you can still navigate around your scene even with a tool is active. The top bar should be used for adjusting the number of cuts:
Dec 1 2018
@Kent Davis (mac4kent)
To convert your materials to work in Blender 2.8, you'd need to follow these steps:
- Open the original file in Blender 2.79.
- Change your render engine to Cycles.
- For every material, add a node.
- Add the an image texture to the node.
- Select the image that matches the material.
From the looks of it, the file in Blender 2.79 is using the Blender internal render engine with all textures attached to Blender internal materials. In Blender 2.8, the Blender internal render engine was removed and a method to transform Blender internal materials into EEVEE or Cycles materials currently isn't in place with no apparent plans for the future. As a result, the textures aren't integrated into the materials for the object in Blender 2.8 and thus the textures do not load in Blender 2.8.
Nov 30 2018
@Brecht Van Lommel (brecht)
I've rendered the scene (it was missing textures so the test wasn't identical) and the total time of render was roughly 15 hours on my Ryzen 5 2600. I believe the issue may be on the users end (E.G. Other programs using the CPU, overheating and thermal throttling on the CPU, etc) but more testing would need to be done to ensure this isn't the case. I'll leave this task with you.
I'm roughly 8 hours into the render of the scene with the missing textures. I'm 48% complete and the estimation lists another ~8 hours until completion (The original prediction was ~2 hours. This has extended due to the fact that the original estimation based on the rendering of the sky, but not to the 150 hours you were reporting). I'm using the same system as before:
CPU: Ryzen 5 2600 (Used for this render)
GPU: RX 570 4GB
OS: Windows 10 Home 64bit
Blender Version: Blender 2.8 beta 26d5a3625ed
Nov 29 2018
@Mattis Kristensen (mattismoel)
I don't know if this will make much of a difference, but are you able to include textures in your blend file so we have identical test setups?
I'm also unable to reproduce the error, however, I'm on windows. Blender 2.8 26d5a3625ed.
Could this be your issue? https://developer.blender.org/T57596
@William Reynish (billreynish)
I would consider this a bug as every other tool (take the bevel tool for example) respects edits made in the top bar prior to the tools use. And if this is working as expected, then why is the steps option included in the top bar if it does nothing?
Nov 28 2018
I'm no longer able to reproduce this bug in Blender 2.8 565de7750b9. However, I'll leave this open and let the developers decide whether or not to close this report.
Nov 26 2018
I've tested this with an RX 570 4GB on Blender 2.8 9abcf56fa88 (November 26th) and I'm unable to recreate the crash. Try updating blender and your graphics drivers and see if the issues persist.
Nov 25 2018
Nov 24 2018
I'm still capable of reproducing this bug in recent versions. Probably is a Window's thing then.
Nov 18 2018
@Christopher Anderssarian (Christopher_Anderssarian)
Are you also able to test this bug? https://developer.blender.org/T57645
Nov 15 2018
The Vega 8 GPU is running driver version 17.7
The RX 570 is running diver version 18.10.2