This is a defect in the rendering engine. I don't know much about rendering myself, but from what I've seen, the most likely reason this happens is that all or many polygon images are stored in the same file, and sometimes zooming out can cause the engine to render neighboring polygon images in said file.
This was a one-off rare error that happens occasionally. I've seen it myself a few times. However, this type of thing is not saved in the scene file, which is why nobody can see the original fog-like scene.
Last edited at 2021/09/27 03:41:13 by UnityDogGaming04
If you click "delete" on a scene, it will make it private, so only you can see it. This allows you to have an online copy of the scene without anyone knowing about your secret projects!
Hi, ivylin1288! I have a scene with exactly the function you're looking for. It was a concept of mine for years before I put it together. It is pretty complicated, but it does exactly what you need, though in a strange way. Here it is, but make sure you read the credit information before you post anything:
http://www.algodoo.com/algobox/details.php?id=242384
I apologise if the code seems a little complicated or setting it up is tricky. Hope this helps!
I'll see what I can do, Xray. The whole mathematical structure of PID control is still relatively new, so it may be a while until I get something working.
I mean hey, you can always slow the time down by a factor of four or five... hundred... thousand! It increases the margins for time-sensitive error, to give you practically hours, days, years, before you really have to do something! Thanks for the kind words!
I have! If I flick hard enough, I won't hear the pencil hit the table. It's basically impossible to see in real time, so all I can go off is whether I feel a faint vibration in the table or if I hear the tip clip the edge.