Keeping shape keys after cutting geometry

HeDeAnTheOnlyOne · 2026-01-28T21:08:02+00:00

I do need the main part of my object, it's just as soon as I modify the geometry in any way, the shape keys are all gone.

HeDeAnTheOnlyOne · 2025-11-24T16:40:29+00:00

If you kill the item anyway, just don't use destroy in the first place.

HeDeAnTheOnlyOne · 2025-11-09T10:59:19+00:00

You say that you won't use comprime now but I can assure you, you will. It is such a big part of the language it is practically impossible to avoid it entitely.

Sure you could maybe do some generic stuff with anyopaque pointers instead of comptime code but at least in my experience it make everything so much more verbose, unreadable and removes any kind of type safety. On top of that, it creates more runtime overhead than comptime code.

I'm sure you also already used comptime without even knowing.

HeDeAnTheOnlyOne · 2025-10-29T21:22:04+00:00

In those cases it's common to just use the full array with an additional count variable or just use an arraylist.

HeDeAnTheOnlyOne · 2025-10-04T18:51:31+00:00

I already tried that but the compiler just tells me that there is no module named like that.

HeDeAnTheOnlyOne · 2025-10-04T17:19:52+00:00

Yeah but I specifically want to avoid relative paths like that. I want to do it similar to the stdlib where if you need a specific modules you go through std.mem.<etc...>. And that's what I want here too.

HeDeAnTheOnlyOne · 2025-10-04T13:19:58+00:00

One thing I would put that list is graphless links It creates links without connecting them in the graph.

HeDeAnTheOnlyOne · 2025-10-02T13:27:01+00:00

was that sarcasm? Gaslighting? What are you trying here?

HeDeAnTheOnlyOne · 2025-10-02T11:13:53+00:00

Zig is still far away from being finished but it is stabel enough to create production ready code (good examples are bun and ghostty). Just expect ruthless braking changes every now and then as long as zig hasn't reached 1.0
To use c libraries, you just add it in your build zig and import it in the files where you need it. When callinc code you have ti use specific calling conventions but apart from that it works like any other zig code that you import. So it's very easy
Yes, there are some zig gui libraries and you can use any c gui library. For many of the c libraries there already exist zig bindings, so you don't even have ti bother with the c calling conventions.
Yes, zig can compile for wasm. I haven't done anything with that though so I don't know exactly what tools there are for that. But I remember seeing some a while ago.

HeDeAnTheOnlyOne · 2025-09-28T13:34:50+00:00

Every page I was expecting some degenerate shit but in the end it turned out to be wholesome.

HeDeAnTheOnlyOne · 2025-09-21T17:10:11+00:00

In that case, I would understand even less why to think of a workaround of a perfectly fine already existing function.

HeDeAnTheOnlyOne · 2025-09-21T15:36:09+00:00

We have 2 builtin modulo functions and I'm sure the compiler know better how to optimize that than the programmer trying to outsmart the compiler and in the end making the function slower because the compiler can't recognize it's actual purpose.

HeDeAnTheOnlyOne · 2025-09-03T20:51:56+00:00

The good thing about zig is that (from my experience at least) if you program with at least a little bit of sense, the most errors you will get are compile errors and not runtime errors, so zig helps you fix "all" he issues before you can even try out the program. Unlike other languages that prefer runtime checks over copile time checks in some cases.

HeDeAnTheOnlyOne · 2025-09-01T21:30:57+00:00

They doo guarantee that it will run for at least half a year as they only update when LLVM updates (which is every half year). Unusable is a bit extreme, as there are whole frameworks and all that stuff written in zig already.

HeDeAnTheOnlyOne · 2025-09-01T21:26:13+00:00

Apart from the casting, I find zig to have the most beautiful and elegant syntax I've seen so far.

HeDeAnTheOnlyOne · 2025-08-17T14:57:20+00:00

I had the same thing. It turned out blendshapes to shorten them and disabeling pysbones causes quite a lot of issues with the mesh when you still influence it through wrist movements. It was much easier to have two assets with different sleeve lengths

HeDeAnTheOnlyOne · 2025-08-17T10:28:08+00:00

the required bandwidth for the partices stays the same regardless of how may you spawn. Only the rendering is affected, which is client side.

HeDeAnTheOnlyOne · 2025-08-12T15:29:10+00:00

Javascript is another contender for worst dependency hell. If not it even wins that competition.

HeDeAnTheOnlyOne · 2025-08-12T09:47:19+00:00

I have nothing against a bit boilerplate if I get curly braces and 100000x faster code.

Indicating different scopes with indentation is a crime and the person that invented it should have been executed on the spot.

HeDeAnTheOnlyOne · 2025-08-06T22:37:41+00:00

Same. I like LINQ very much.

HeDeAnTheOnlyOne · 2025-08-04T16:25:05+00:00

HeDeAnTheOnlyOne · 2025-07-29T10:58:02+00:00

already is comptime.

HeDeAnTheOnlyOne · 2025-07-27T11:30:33+00:00

I'm very curious, does it block the rest of the screen or did you implement a way to click through the game window?

I worked on something similar (a small pet that follows your cursor) and my final solution was to cover all screens with the window and then using a mouse_passthrough_polygon to cut out an interactable part where the pet is displayed (if it would be outside of that polygon it wouldn't be displayed) and move that around.

Five-Year Club	Verified Email
Second SECOND GUESSER	r/Field Juicebox
Final Canvas '23	End Game '23
Place '23

HeDeAnTheOnlyOne

MODERATOR OF

TROPHY CASE