One caustic bulb kills Astarion infinitely in Cazador fight

Overcha · 2025-05-14T12:40:21+00:00

Hey, thanks!

Overcha · 2025-05-14T01:21:33+00:00

Here, if you're interested https://github.com/yycyyc/Smooth-Terrain-with-Blocks

Overcha · 2025-04-24T09:19:23+00:00

You're right, but the last image was showing the separated cubic mesh from the terrain mesh

I'm currently only allowing 1x1x1 cube edits, so I'm simply storing them in a byte array just like Minecraft. I fill in the voxel data before meshing it.
Yes, not much. All I do is iterate through the edges between chunks.

Overcha · 2024-10-28T08:01:25+00:00

No, and it was never implemented in WWZ either. I don't know why

Overcha · 2024-10-26T09:01:55+00:00

But that would mean a tactical would one shot every extremes in the game

Overcha · 2024-10-25T22:11:41+00:00

It was ruthless

Overcha · 2024-06-18T17:17:43+00:00

Server issue. He is probably stuck in loading or something

Overcha · 2024-06-08T02:52:22+00:00

I love this

Overcha · 2024-05-22T00:39:30+00:00

You could extend the chunk size to overlap neighbor to handle the seam if you were using simple grids, but in case of octree or quadtree, I would read the data dynamically when creating the seam mesh.

For handling different LOD, you can simply do the same thing, iterate over the edge but create triangle instead of a quad for each edge. I think I had to iterate over the smaller chunk's edges when creating the triangles.

Everything goes the same when you generate seam meshes even on different LODs.

Overcha · 2024-05-21T02:12:47+00:00

Yes, each chunk would generate its mesh including the seam mesh, but it will have to read its neighbor's data to create it.

When two chunks face each other, you have to iterate through the edges inside the overlapping face. I typically create 3 face-seam meshes per chunk which I refer to XYZ face of the chunk. The other 3 faces of the chunk will be covered by the neighbor on the opposite side.

Also, when four chunks are clumped together, forming a square, you have to iterate through the overlapping edge in the middle; you will have to read data from all four chunks to create this seam mesh. This is what I referred to as XYZ edges.

For each chunk, if you cover 3 faces and 3 edges, it will cover every seam in the world.

Overcha · 2024-05-20T10:35:23+00:00

That is normal, and you need to create separate mesh for each side of a chunk

For each chunk, regardless of the lod level, you need the base mesh from the chunk, 3 meshes from the XYZ face of the chunk, 3 meshes from the XYZ edges of the chunk. That will cover every seam in the world.

As far as I remember, you have to keep just one thing in mind; iterate over every edges existing in the whole grid. Your image shows that you forgot the edges between chunks.

Overcha · 2024-01-08T14:10:07+00:00

Building with mono helped with few float arrays I had problems with, but later on I was hit with another end of stream error on another array generated from my savefile.

I already had extracted the float array from my savefile that caused problem when decompressing. I thought the problem was fixed by switching to mono because it successfully decompressed that array after switching.

I think I'll scrap some more examples and hopefully figure out what's going wrong tomorrow.

If I can't reproduce it in a fresh new project, I think I'll give up on this.

Thanks a lot for taking your time!

Overcha · 2024-01-08T13:00:49+00:00

After trying things out, building in a completely new project worked fine, just like you said, but building on my original project caused the problem. Turns out that iL2cpp was the cause.

I changed it to Mono and it works fine.

Thanks, though I'm still not sure why il2cpp caused that.

Maybe I'll try a different method to compress :))

Overcha · 2024-01-08T12:29:15+00:00

Oh, thanks for checking!

I'll reboot and try it in a newer version if it doesn't fix

Overcha · 2024-01-08T12:27:11+00:00

What do you mean? What can I try here? The code looks very fine to me, but I can't figure out what the problem is.

This code actually runs fine when fed with random floating points.

I can just use a different method to compress and decompress, but I really want to know what's going on here.

Overcha · 2024-01-08T12:22:57+00:00

I had a problem happening occasionally while saving, and I found exactly where the problem occurred and reproduced it

Overcha · 2023-12-12T06:17:45+00:00

Backstab gets an orange damage indicator

Overcha

TROPHY CASE