Ok, i fixed the wrong selection problem of v4 here, but v3_fixed still is better than v5 as the latter cant fill any sequential cuts i make,
(not even in default cube)
There are always some faces missing.
Ok, i fixed the wrong selection problem of v4 here, but v3_fixed still is better than v5 as the latter cant fill any sequential cuts i make,
(not even in default cube)
There are always some faces missing.
I'm surprised you suggest to have this a pop-up, to me this is always the most annoying thing - every time you have to click them away, Isn't not making it a pop up means its at least not annoying more experienced users? Anyone who wants can disable the addon or disable the splash screen.
I think that ASD is fine just like WER. It will be great if we can create 2 "standard" keymaps by switching only ASD and WER keys, rest of keymap should be the same.
The thing is, even if it might sound to be different issues between software and hardware, the root of the issue is the same -- wrapping when doing interpolation needs revisit. And after it all works as it should on CPU then we can investigate why it wouldn't work on GPU. For until then it's not really good investment of time making it so all GPUs matches current CPU behavior because it'll be possibly changed.
Confirmed, i think i'm not applying positions in quite the same way or so. Will look into it ...
@bat3a, it's not strictly speaking easy to solve issue, seems machine arithmetic backfires here.
Strange, maybe worth checking if your memory is OK, ( http://www.memtest86.com/ ), bad memory can randomly corrupt your files.
I haven't tested the code yet but I suggest several things after a first review
Fixed it!
Ended up installing Blender on this laptop, downloading it on a different laptop, transferring it via USB and launching it via blender_app.exe
No idea why it worked, but it did.
I'm not sure why you consider T43795 unrelated. The root of the issue is exactly the same -- wrapping coordinates on the image boundary when doing interpolation. The fact that some devices does expected interpolation in this case doesn't make any difference in the root of the issue.
@ton, its understandable we don't want to have to have long debates each time someone suggests minor UI tweaks (its been an issue in the past),
Fix for T43643 fixed this too. (was same error in fact)
This is a 3rd party addon, not code included with, or maintained by blender.org distribution.
By default the knife tool wont cut through overlapping geometry.