There was this error prompt in 2.8 only if you expand the Volumes tab in File Manager and start clicking on disk drives. In 2.8 Volumes tab is closed by default so you won't get the error message just by pressing on Open in the File menu, also this error prompt in 2.8 won't close the File Manager Window completely, because, I guess it was not opened as a separate window.
- Use booleans instead of ints for cache->original
- Fix Gpencil matrix
- Fix crash due to drawing with buffers not big enough
just fix the crash for now, drawing assert will be handled in a seperate commit
This is intended behavior for the face orientation overlay. The reason for this is that otherwise the shading will be effected in the display. Cycles, EEVEE and workbench renders them correctly.
Thanks for working on the docs! For screenshots like these, please hide or crop out the headers, timeline and status bar. Then the focus is fully on the nodes and the resulting render.
I fixed the drawing glitches I could reproduce.
Makes sense! Just made and tested the change, everything should be working now.
- Optimize fcurve lookup
Here you go:
Is it the same issue as T69808?
Could you share a simple file with the steps to reproduce the problem?
This would facilitate the investigation.
@Campbell Barton (campbellbarton), do you know what may be happening?
Ok, I found out "default.001" etc. are added to the list of Screens every time you open new window. They don't disappear when you close it, though. That's why I have them saved in my startup file.
This works as intended.
In Blender an object can only be scaled towards its axis.
Therefore if the axes are not well aligned, an approximate result is obtained.
You can solve this by making a parent with another object but this aligned to the cursor and then scaling the parent.
Can't update graphic drivers since Nvidia introduced many bugs on my card
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 399.24
Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-16 21:02, hash: rB76650402f300
This is indeed not a bug, it's simply a property that's written to Alembic and that's not read by Blender. Alembic is quite bad in this respect, in that there is no well-documented open standard in which such properties are defined. I'd be very happy if you can prove me wrong on this one.
👍 Thank you too, @Juan Gea (juang3d) !
Can you update your graphics drivers there are almost a year old, might be a driver issue.
- so BKE_scene_unit_scale compensates for length, but does not for velocity (I think this is on purpose though...)
This is most likely caused by one of these recent commits:d3ab930 13 days ago Fix/cleanup error handling in paths generation for private ID data case. 6f1fa7a 2 weeks ago Fix/enhance new RNA path from real ID helpers. 64efbbc 2 weeks ago Make Scene Master collection 'Private' ID data, like root nodetrees. 34ed58d 4 weeks ago Fix T68971: Copy As New Driver from Material node creates a bad reference.
- Rename transform_op_mode_*.c to transform_mode_*.c;
- Rename transform_op to transform_ops;
- Rename transform_op_orientation to transform_ops_orientation;
@Sybren A. Stüvel (sybren): what is the default if we dont have custom normals in the .abc? smooth/flat?
Thanks for the report.
Perhaps we should only use imm_draw_circle_wire_3d in this part of the code, as far as I see it we just need to replace one line. This reduces the complexity of the code and makes it more readable.
Is this a new issue in 2.81, or did it also happen in 2.80?
I can confirm that, though only when using a custom UV input.
Try this file:
If you connect Texture Corrdinates with UV to the Noise Texture it works, with the UV Map node it doesn't.
Tried with 2.81 (sub 11), branch: master, commit date: 2019-09-17 09:24, hash: rB271c6794d629
@Germano Cavalcante (mano-wii) it's probably better to revert to the old behavior, do you think it would be hard to implement?
@Philipp Oeser (lichtwerk) You mentioned that there were some drawing asserts. I haven't been able to reproduce them, not sure that the drawing code changes are needed.
Do I miss something?
@Philipp Oeser (lichtwerk) Do you have idea what is the reason of this?