I'm glad to see I wasn't the only one having some weird knife stuff happening. It created double and sometimes triple vertex, on top of creating random geometry next to my model. Had to check every time I used it, was kind of crazy.
How precise do you have to be? Because I'm getting some funky stuff. I'm starting to feel like I accidentally did something wrong with this particular piece. When I first went into edit mode I had to delete a weird double, and it's been doing this on almost every cut I make. Sometimes it even creates a third vertex that's not attached to anything. It's really weird.
It's probably just easier to start that piece over, but I'm curious to see what you find because I'm floored on that one. Every time I cut that particular section something totally different happens, which is kind of funny at this point.
aamyeha Thanks for the .blend file. I opened it and it appears to be the default blender scene (cube, camera, light) rather than a treasure chest model...but I still tried my knife tool on the cube and it worked fine for me 🤔
Could you try resetting your Blender to factory defaults and try the knife tool again? You can do this with File > Defaults > Load Factory Settings
I tried before asking and it didn't change it. I reset my settings, turned off add-on I had installed, and it didn't change. I even deleted both parts and recreated from a cube and... it still did it.
But I can't recreate the problem on a new file, so I'll just scrap the whole thing and start over.
I really don't know what I did, but I created a monster lol
Thanks again :)
If any are interested, I found what caused this!
I had to look into the bug section of 2.8 to find a few persons having this problem, and one mentioned the clip start value in the View panel. Mine was at 0.001 which for some reason caused a problem with the knife tool. After changing it to a higher value at 0.01+ the knife tool worked normally! So below that number cut tools might act funky, good to know!
Appreciate you taking the time to figure this out. If I have this problem, I know what to do now. Hopefully BF is aware of this, and it's on the docket for future releases.