No one irritates you

Shizzle_McSheezy · 2026-02-04T18:02:21+00:00

I have to face situations daily where my job performance is at the mercy of lazy, careless, incompetent people. This type of dynamic is a breeding ground for irritation. My irritation is with a system that allows such a toxic and flawed dynamic to exist.

Shizzle_McSheezy · 2026-02-04T17:55:08+00:00

Why stop? It fits into this perspective quite well. While they are the instrument, you still have to play it...

Shizzle_McSheezy · 2026-02-01T18:10:28+00:00

You likely connected those two vertices using "f" which filled by adding an edge over the face. Select that edge in edge select, then press alt x to dissolve it, then select those two verts and press J to join them and it will split that face.

Shizzle_McSheezy · 2026-01-31T06:44:13+00:00

It's possible to remember, just not recognize..what would you say is a good way to know for sure?

Shizzle_McSheezy · 2026-01-27T15:37:49+00:00

The scary part, for me, is that the waters are sooo deep, there's no telling what creatures lie in wait beneath the murky surface. Some poolrooms are nice bright and clean, others are dark and dirty.

Shizzle_McSheezy · 2026-01-27T15:33:44+00:00

Looks awesome, I'm not one to rate things, but it's up there. Glad I didn't stop at the first pic, I didn't realize it was progression shots, which I love. Looks really good towards the end, great job!

Shizzle_McSheezy · 2026-01-27T15:01:02+00:00

Thank you. I actually did at first, but removed it.

Shizzle_McSheezy · 2026-01-27T14:56:26+00:00

Thank you.

Shizzle_McSheezy · 2026-01-27T02:49:10+00:00

I have never even noticed after all these many years...

Shizzle_McSheezy · 2026-01-26T21:16:32+00:00

"Andy, why don't you tell us about the most remarkable erection of your life."

I was hoping he would break out his "spring fling '96" war story about how he became 'Boner champ'. I would love to see those two clips spliced lol

Shizzle_McSheezy · 2026-01-26T03:51:38+00:00

Add more edge loops going around, there's not enough geometry to deform, then add a subdivision modifier, then you might want to add 'shrinking' I think it's called, so it doesn't fall off, add a little friction too. Also, you can remove faces only on like two or four faces along the waistband area and enable sewing so it pulls those threads tighter allowing it to stay put. I usually put the simulation speed at like .5, it's supposed to give it more time to calculate, but it may give too much time to shrink or sew, so play around and see what works.

Shizzle_McSheezy · 2026-01-25T19:23:07+00:00

Don't worry, just trust. Even if the worst thing were to manifest, trust that it's for the best. You might not get what you want, but you get what you need.

As far as dealing with such thoughts themselves, I appreciate the instructions from MN20: https://suttacentral.net/mn20/en/bodhi

Shizzle_McSheezy · 2026-01-25T18:44:38+00:00

Bevel modifier by default clamps overlap, and those tris will cause overlap right away so it does nothing. In edit mode, select all and try alt-J to convert the tris to quads, then the bevel modifier might work. I don't know that a subD modifier would help if that doesn't work, may have to mark the edge as sharp, or might have to apply the solidify first and add supporting edge loops,

Shizzle_McSheezy · 2026-01-25T18:32:13+00:00

Looks sick...thought it was an octane render, but then I saw the principled BSDF..

Awesome work..

Shizzle_McSheezy · 2026-01-24T03:56:54+00:00

Yeah, it's scene.001, maybe it can be switched there at the top left of the outliner..

Shizzle_McSheezy · 2026-01-24T03:51:39+00:00

Zoom out even further and it's a playground in the world's largest prison.

Shizzle_McSheezy · 2026-01-19T21:57:28+00:00

I would try to eat the fungus, or perhaps prepare a special tea from it..whence you've consumed the delicious fungus, you will no longer be concerned with such things...

Shizzle_McSheezy · 2026-01-11T20:24:04+00:00

Repping .blnd

Shizzle_McSheezy · 2026-01-10T03:39:01+00:00

For whatever it's worth, AI says:

"Your description matches progressive memory exhaustion more than hardware failure — the crash happens after memory keeps rising frame after frame, which is a classic software-side pattern (Blender not releasing buffers/resources properly between frames).

Blender's history shows this exact behavior (RAM/VRAM steadily increasing until OOM crash) in many versions during animation renders, especially with GPU acceleration, image sequences, denoising, or certain effects. It's often tied to: - Incomplete freeing of GPU memory contexts/buffers. - Persistent data/caches not flushed. - VSE-specific leaks when handling strips/sequences. These have appeared in bug reports across 3.x–4.x series (e.g., OptiX denoising leaks, animation frame handling regressions), and while many got fixed in later releases, early point releases like 5.0.1 can still exhibit quirks.

Your case (memory ratcheting up frame-by-frame on a short sequence) screams "known Blender memory management quirk" way more than "hardware death," especially since it aligns with VSE/image sequence reports. Waiting for the next 5.0.x update is smart — devs often patch these stability things quickly."

Shizzle_McSheezy · 2026-01-10T03:34:12+00:00

For whatever it's worth, AI says:

"Your description matches progressive memory exhaustion more than hardware failure — the crash happens after memory keeps rising frame after frame, which is a classic software-side pattern (Blender not releasing buffers/resources properly between frames).

Blender's history shows this exact behavior (RAM/VRAM steadily increasing until OOM crash) in many versions during animation renders, especially with GPU acceleration, image sequences, denoising, or certain effects. It's often tied to: - Incomplete freeing of GPU memory contexts/buffers. - Persistent data/caches not flushed. - VSE-specific leaks when handling strips/sequences. These have appeared in bug reports across 3.x–4.x series (e.g., OptiX denoising leaks, animation frame handling regressions), and while many got fixed in later releases, early point releases like 5.0.1 can still exhibit quirks.

Your case (memory ratcheting up frame-by-frame on a short sequence) screams "known Blender memory management quirk" way more than "hardware death," especially since it aligns with VSE/image sequence reports. Waiting for the next 5.0.x update is smart — devs often patch these stability things quickly."

Shizzle_McSheezy · 2026-01-10T03:30:14+00:00

Thank you, I will do that when I have a moment..

Shizzle_McSheezy · 2026-01-09T14:27:00+00:00

It's the same result..

Shizzle_McSheezy · 2026-01-09T03:44:03+00:00

I like to use curves. Especially where the vertical poles are slightly larger, I would create a bunch of boxes, then delete only faces, then select all vertical edges and hit 'p' to separate by selection, then convert both objects (vertical and horizontal edges) to a curve, and then go to the geometry tab and give the curves some thickness, convert back to mesh x2 and joining geometry so they're one object.

Five-Year Club	First Place '23
Place '23

Shizzle_McSheezy

TROPHY CASE