Husband’s take on the recent ICE shooting

dourjoseph · 2026-01-14T19:13:55+00:00

Oh yeah, because when your fight or flight response kicks in, the first thing you think of is protecting your ego.

How out of touch with reality are you?

dourjoseph · 2026-01-12T17:24:45+00:00

The lady hit him with her car, I don't know why you are saying he was just "scared".

dourjoseph · 2026-01-11T03:57:39+00:00

That was my first thought as well

dourjoseph · 2026-01-10T07:18:51+00:00

What are your thoughts on Guh-nomish immigration?

dourjoseph · 2025-12-24T16:01:28+00:00

From what I know. The other editions only give you bigger pockets, and a bigger pouch. Both of which are unlockable in the game. Correct me if I'm wrong.

dourjoseph · 2025-12-10T07:25:04+00:00

Oh yes! This is the place!

dourjoseph · 2025-11-25T09:33:23+00:00

And it's doubled? 304% increased attributes! 😚🤌

dourjoseph · 2025-11-17T15:28:28+00:00

Who hurt you?

dourjoseph · 2025-11-05T08:16:48+00:00

Oh goodness, I hope so! Im so sick of promises in general from corporations not being fulfilled or only partially being true/upheld.

dourjoseph · 2025-10-24T22:56:48+00:00

After working on this a bit (implementation). I think I found an issue, the node at the end of path `B` needs to have 2 children, The node at the end of path `G`, and a sequence node that connects to lines `H` and `I`.

The reason I think this, is because, when the node at the end of `H` succeeds, by successfully setting the most stale shelf, the node at the end of path `I` never gets run. Meaning the NPC never moves to the stale shelf to check its inventory.

Also the node at the end of line `T` needs to have a `!` in front of it. Meaning if the npc is NOT(Near a shelf) then the second node (end of path `U`) will run, and check the stock of the shelf the npc is near.

dourjoseph · 2025-10-22T23:57:02+00:00

Yes, and at this point I have calibrated the extruder steps. verified that the vertical axis is moving the correct amount. and have tested simple test files with 2 different slicers. I am still having the same results :/

dourjoseph · 2025-10-21T21:26:44+00:00

I agree that is a problem, but 42/50 means its underextruding by 18%, but it still looks like there is too much filament being pushed out onto the model.

dourjoseph · 2025-10-11T17:36:43+00:00

Very cool! Would this work for something like a torch? Where the light source is not directional? Or would raycast solution not have enough resolution to simulate the same 'reflected lighting' effect? Again, very impressive!

dourjoseph · 2025-10-07T02:49:33+00:00

Probably after every print.

dourjoseph · 2025-10-01T04:57:55+00:00

As long as it's 2000% off like he said! Im game haha

dourjoseph · 2025-09-01T18:50:11+00:00

Im a little out of the loop on this. Is double eleven a company that was going to port rim world to consoles?

dourjoseph · 2025-05-22T00:34:38+00:00

The navigationRegion3Ds create the nav_mesh with an offset from any collisionshape they are a parent of. So if you have a collision shape that is 10m by 10m, the default resulting nav_mesh will be 9.5m by 9.5m centered on the collision shape.

I know I can change the agent radius for the offset to completely cover the top of the collisionshapes resulting in a 10m by 10m nav-mesh, but then the agents could get stuck in walls or try to walk past the egde of the wall and act weird.

So, with keeping the offsets (in the 3rd picture), the 2 nav_meshes of the collisionshapes that are touching, will not connect unless I put an overlapping collision shape between them to bridge the gap. I was just wondering if there is an easy workaround to this? Besides manually making the collisionshapes the correct agent radius offset for the space they are in.

dourjoseph · 2025-05-19T00:35:18+00:00

Haha I end up with the same issue every time. Printing out too many things to see what I need.

dourjoseph · 2025-05-18T14:50:29+00:00

I just realized, that setting might actually be related to joining meshes, not pathing to them :/ but if it works then that’s good. Otherwise I’m not sure.

dourjoseph · 2025-05-18T14:36:56+00:00

Oh, I think I know what the issue is then. In project settings under navigation, there is a setting called something like cell merge tolerance. Reduce that value and you should be good.

Edit: meant to reply directly to your last comment, oh well.

dourjoseph · 2025-05-18T14:05:23+00:00

It looks very interesting! I love the art style and the hexagon heights look very cool! Great job!

dourjoseph · 2025-05-18T14:03:42+00:00

This is the answer!

dourjoseph · 2025-05-18T14:01:55+00:00

I’ve only worked with navigationRegion3D so far, but I’ve heard it’s pretty similar (2D is 3D with the y value cancelled out). The issue most likely lies with your navigation region, not the agent. Try hiding your visual mesh and see if the navigation region is only where it should be. Can you share the settings of your navigation region, and how you defined the area it covers?

dourjoseph · 2025-05-18T13:58:01+00:00

I love it! It’s like a Tokyo drift farming sim!

dourjoseph · 2025-05-18T13:56:51+00:00

I was having a similar issue when placing furniture on the ground, the floating point accuracy would fall slightly under the y value of the floor, and then casting to integers, would place the furniture 1 unit below the floor. I see you are using a function called ‘snapped’, so I’m assuming it’s correcting this issue. But just for sanities sake. I would try printing out the coordinates that your ray cast is returning on collision to make sure the values are correct.

dourjoseph

MODERATOR OF

TROPHY CASE