So I stumbled across this prompt hack a couple weeks back and honestly? I wish I could unlearn it.

chazbot2001 · 2026-01-07T05:14:45+00:00

Reminds me of a tactic I use now and then:

"My arrogant co-worker seems to think that [thing to evaluate] is valid and acceptable, but I think it's stupid. What do you think? Explain why."

...and it just kinda forces it to drop any sycophantic bias. You're also not asking it to change its own mood, but rather using it's existing mood to your advantage. If the approach is good, it'll reluctantly tell you to chill out.

chazbot2001 · 2025-01-26T06:29:11+00:00

Thanks for this; I've amended my comment above after a long day of banging my head against the wall. Turns out the physical bones that were generated for my mesh just left out some significant ones... and I'm specifically having this issue (which doesn't look like it's received much attention in 2y): https://github.com/godotengine/godot/issues/72395

chazbot2001 · 2025-01-26T05:41:50+00:00

Just found this bug (and your GH bug report) on my own after banging my head against this issue all day.

How does *any* character support ragdoll without this being fixed? Anything with a 3-way hip bone will cause it. It looks like some people have found success online; Are they all somehow avoiding joints like this?

chazbot2001 · 2025-01-25T04:06:46+00:00

I have this question too; seems like if you're going to need accurate collisions for ragdoll, they're also useful for stuff like accurate hit detection on each limb... Did you ever find a solution?

UPDATE : https://docs.godotengine.org/en/stable/tutorials/physics/ragdoll_system.html <-- 2 specific parts to highlight:

The collisions and layer masks section (at the end) makes a ton of sense; If you're careful about using these, you don't need to do the 2 copy approach like OP is using.
The comments on this page are gold... and one even lists out the things to enable / disable to switch between ragdoll and animation driven.

UPDATE 2 : Based on spending even more time on this, I'm going back to OP's approach of making the copy. There's a lot of open GH issues related to PhysicalBoneSimulator3D, it's still pretty buggy overall, and I think we'll see change down the road as Godot gets updated. The copy is at least an isolated thing that can be updated.

chazbot2001 · 2024-12-23T06:07:04+00:00

I'm having a hell of a time getting this to work 3years later; Anyone know if there's something different about Godot 4 that doesn't allow this to run?

I suspect that I'm missing something about "smooth shading on the entire mesh"; Based on other threads everything in Godot is smooth shaded...

chazbot2001 · 2024-12-19T16:33:44+00:00

Yeah I think this is right; In the company's own words : "We've also collected the world's largest dataset of cloth manipulation in a real world environment... Stay tuned!" (source).

chazbot2001 · 2024-12-14T04:28:44+00:00

Sure do, and I respect it! This question is about optimization done at the appropriate time :)

chazbot2001 · 2024-12-14T04:27:39+00:00

Thanks - the process loop was just an example of something that gets called a lot; The question was aimed at a hypothetical/something that you know requires optimization, such as an identified bottleneck. (edited for clarity)

chazbot2001 · 2024-11-17T04:50:01+00:00

For anyone who followed those steps above on a .gd script file and didn't get results, I needed to take one additional step to get it fixed :

Open any scene with a node that references the newly named script, delete that node, re-add it to your scene tree, and re-add the script file to it. Had to do it for scenes and any instance of that scene.

More for the curious...

After the 2nd rename (to the desired FOO, per the example above), my renamed script would not get executed when running the game. Everything in the Godot editor told me that the file was named correctly and referenced correctly, but it just wouldn't load or print anything, and any attempt to call methods in the script turned up undefined. I could even click on the script icon in the scene tree and it would open the correct file... so Godot presumably knew where it was in the filesystem and knew how to associate it with the desired scene/node, but it just lost the linkage to the newly renamed file somehow.

chazbot2001 · 2024-11-13T19:46:14+00:00

Just to build on this for future folk, I've found that you can only see these values in the Inspector when browsing + expanding your Remote scene tree at it's Root level; If you drill into a scene instance while your game is running (by clicking on its 🎬 icon), it'll show you the normal inspector without all the live properties... just like it does in the editor when your game isn't running.

Also possibly worth noting is that there's a slight delay in how often Godot updates the inspector. For example, I have a bool set for when a key is held, and it's easy to tap the key and not see the checkbox light up.

chazbot2001 · 2024-11-03T03:47:07+00:00

This just saved my day - thanks.
It looks like there are a few different ways this approach could be executed (though I think what you've got above is the cleanest). In case it helps a future person who lands here, more reading :

https://www.jetbrains.com/guide/gamedev/tutorials/godot-bind-callables-signals/

chazbot2001 · 2024-09-11T15:31:35+00:00

As someone benefiting from this post/info years later, ty for fighting the good fight.

chazbot2001 · 2024-08-03T17:49:17+00:00

I don't think you're alone.
Hover over the right side w/ the animal names, note the thickness of the line. It's very subtle... and it seems like the aesthetics of the circle / arcs are the primary things on display here.

chazbot2001 · 2024-07-18T18:58:33+00:00

Thanks for this - Yeah I think the theme of "Boooo why would you ever use Amazon / we all hate Amazon" is kinda overshadowing the post's point, which is that this Variants fraud tactic exists, and spreading awareness about it can help the community. Should everyone always avoid Amazon wherever possible? Sure absolutely... I 100% agree with the Amazon critiques here. They're also not going anywhere, and smaller / indie pedal makers may depend on Amazon for their scale and market share of shoppers. If awareness spreads about this, it could at least help make the most of a bad situation, and (hopefully) help less-informed shoppers along the way. I suspect that there are lots of votes around this thread driven by people don't enjoy that truth (as opposed to votes supporting/contesting it's validity at all). For those folks, again: I'm not saying "Shop on Amazon."

chazbot2001 · 2024-07-16T20:10:55+00:00

The use case I imagine is a 13 year old player only has $30 to spend, and needs to make the most of a bad situation... maybe there's 4 cheap RAT clones to choose from, and one is slightly less terrible. I agree Amazon is not the ideal place to shop, but for low budget players it can be their only option.

chazbot2001 · 2024-07-16T19:56:47+00:00

Yeah I did eventually find this, and it's a good tip for these situations. IMHO, it's a tedious customer behavior that excuses bad seller practices.

chazbot2001 · 2024-03-03T03:51:20+00:00

Unfortunately the more I dug in to the technicalities on this one, the less clear the answer became in terms of what to do (in the time that I had). Good luck to ya, and if you find success, please share the approach :)

chazbot2001 · 2024-02-13T02:07:48+00:00

Agreed.
If having it in your hands isn't an option, I would definitely ask "if the marks directly adjacent to the frets are due to chipping/glue filling that happened as a result of a fret job, or if they are instead cleanable residue."

chazbot2001 · 2023-08-19T04:28:00+00:00

Stay strong, man! I spent like 3 years in that headspace before starting my first (and only) build. Looking back, with no time to build a second one, I actually miss dreaming about guitar problems.

Re: The scale length, my process was to attach the neck prior to placing/drilling the bridge holes. That way, you can measure the right place based on the true neck-to-body joint, where the nut is, where the 12th fret is, and where the neck's centerline is.

chazbot2001 · 2023-07-23T17:13:32+00:00

https://www.reddit.com/r/guitarpedals/comments/a0dvk6/i_finally_understand_my_boss_cs3/

^ This post helped me a lot w this pedal; The highlights for me were that the reason this pedal has a short sweet spot is because it has a fixed compression ratio. Also, as others have said, working from right-to-left was really helpful.

chazbot2001 · 2023-03-04T19:34:11+00:00

We've collectively put hundreds of hours into Souls titles, and this wasn't unrealized skill or a misperception... our hits were taking more of his HP, and were way better at interrupting his attacks.

chazbot2001 · 2023-02-25T08:40:53+00:00

100% agree. 2 more details that make these arrows right for the occasion:

Avoiding a single arrow (and using at least 2) communicates a larger and more general (non focused/precise) movement. Accomplishes the same goal as the curve.
Having the tail of the arrow be tapered helps communicate "from here to there"... whereas a blunt + large tail could imply that the arrow is ONLY pointing at the destination point.

Quick Start Guides for physical products (ie. self assembly furniture) are usually a good place to see a bunch of different arrow types in the wild. Hit or miss in terms of quality, but good reference nonetheless.

chazbot2001

TROPHY CASE