- User Since
- May 28 2018, 9:53 PM (110 w, 1 d)
yea, the description isn't true
Sat, Jul 4
Alright. I'll be closing this task.
Edit and change the tag to BF Blender
Setting rendering device to Optix is for RTX cards only, Didn't it warn you in the preferences "no compatible gpus found"? yours is GTX, which doesn't fully support it, only the the Optix Denoiser. For using the optix denoiser, go to the preferences you should have your rendering device as CUDA. Ok. Now put cycles as the render engine and set Optix denoiser under the Properties Editor->Denoising->Viewport change from open image denoise to Optix.
Are you using a pen with pressure sensitivity or a mouse?
You reported as addon bug.
I had to record that screen with phone because the print would look fine in other monitor.
When it quickly flickers is because I change resolution.
Fri, Jul 3
Align - to put two or more things into a straight line.
The operator says "Align UVs on X axis". So it would means to put things on the X axis in a straight line. That's not what it does.
The X axis is horizontal. But the operator will align in a vertical line, but that's not the Y axis either, because it's not centered, it puts in a line of the average X coordinate.
The problem is not the word Align, it's how it was used. Align on X should renamed to "Align vertically" and Align on Y should be renamed to "Align horizontally".
Thu, Jul 2
A developer should triage it
Wed, Jul 1
Oh, that's weird, I don't get why it's not in the overlays panel.
Sun, Jun 21
Thu, Jun 18
It's okay, I trust you.
Tue, Jun 16
Mon, Jun 15
@Campbell Barton (campbellbarton) poking once again.
Sun, Jun 14
Mon, Jun 8
Jun 6 2020
Jun 3 2020
Oops, I forgot to mention to go into front/side/top views, etc. That's what I meant to report, sorry!
I don't like idea of this behavior being documented like this without a meaningful design reason. People need the grid without the axes, or the axes without the grid. The toggles are there, so they should work in any view. Or at least make the blue of the toggle faded like when the wireframe overlay is disabled, to tell the user when the toggle is useless, but again, i'd preffer having it more useful. Maybe make it a known issue, idk.
May 30 2020
May 27 2020
May 26 2020
@VertexSupa (VertexSupa) This is not the place for discussion and your comment is a bit disrespectful. I dare you to look up the youtube channel of @Paul Kotelevets (1D_Inc) and say he isn't professional.
Come on people, the UI team decision is made. The cursor changes are postponed for 2.90 or later, as it needs more design time and a better plan. It's not just adding a checkbox in the user preferences that will solve it, and the official 2.83 release is in a bug fix only stage. If you really need the arrow you will need to be more patient or build your own blender 2.83. Hold your complaints and feedback for when there is a proposal and devtalk thread for it. The devs are already aware of your personal needs, you'll just have to wait. Also consider helping fund.blender.org so that they can hire more developers and speed up the process.
Thank you so much. <3
May 22 2020
Operating system: Windows 10 (1909)
Graphics card: Intel(R) HD Graphics 630, version: '4.5.0 - Build 188.8.131.5276'
I used to have the latest drivers provided by my manufacturer(Acer) but they were giving me issues not only with Blender, but also with the latest Windows 10 version. So I downloaded drivers directly from Intel, and now everything works fine.
May 21 2020
May 19 2020
Today I discovered that all this time I could have just simply toggled "Edge" in the overlays panel inside edit mode to get the edges highlighted in vertex mode like they were in 2.79. Why didn't anybody tell me that? 😃
May 18 2020
2.9 behaves as like what I said about 2.83. The bug is partially fixed, the emiter shows correctly in the preview, but the hair doesn't.
See the preview vs the render in 2.9:
Can confirm it from 2.80 up to 2.83. Couldn't open it in 2.79b (crash).
I'm also on windows and with the same 445.87 driver.
It looks fine if you render it in Cycles or Eevee, but it's messed up in the viewport render preview with Cycles. Here's a more simplified version of that file:
Note that in 2.83 this bug is partially fixed, the object shows correctly in the preview, only the hair doesn't preview correctly.
Exact steps to reproduce:
Change the viewport mode to Render preview.
May 17 2020
May 15 2020
To me, this would be way better in the Item panel when you press N.
May 14 2020
To me it just isn't worth it "knowing better" what mode we're in if we can barely see the selection. The points in vertices locations were always a good enough indication of vertex mode. And if it really was the case, then why did they remove the dots in the middle of faces in face mode? If anything, they made it harder to know what selection mode we're in. Also, why not make these same design changes in the UV editor to be consistent? Good that they acknowledged and fixed it for xray and wireframe views, but it is even harder to see in solid mode then it was to see in modes that were fixed... This is a bad and inconsistent design decision. I know you all are very busy, but it's just wrong to not acknowledge mistakes.
type poliigon in the search bar, it does'nt show up?
This addon works fine for me in 2.82.
May 12 2020
Do you know if this will this be refactored and this limitation be removed as part of the library overrides project?
@Ankit (ankitm) This file was created from scratch in either 2.82 or 2.82a, just don't remember which. But it doesn't matter now, looks like Pablo fixed it. yay!