Copying from
my F95 post. Right now, imgbb isn't loading for me, nor is postimage.cc or even postimage.org, so no image uploads.
------------
So, having some trouble with my orc animation right now because of my own code working against me.
The problem: checking which sex scene to play happens both in the player AND the enemy's scripts. This is terrible because instead of having only one place to look at in order to fix, I have to keep checking two. How is this biting me in the ass? In the form of me not creating a "sex_on4s" for the orc gal. Since that part is written in the player script, I either work on a fix there, or create a proper "sex_on4s" animation for the orc, or create a dummy to stop some of the errors.
As if that wasn't enough, I also have to contend with this shit:
Yes, the face, hair and breasts are on the wrong side. Why? Because fuck if I know, Godot apparently hates working with bones. Keep in mind, this kind of error happens all the time with the orc gal in the editor, though a simple advance on any animation fixes everything's positions.
That's from the editor. Why in the fucking fuck that happens? Turns out it's because I'm being "lazy": the textures for the hair, chin, ear and face are all separate nodes, child nodes of the head shape. This means that, in theory, dealing with the parent node alone should replicate every position and rotation to its children.
This, however, becomes a problem because I'm not doing that straight on the textures, I'm doing that through a "RemoteTransform" node.
I'm not using these RemoteTransforms on the kobold enemy, but I'm using on the player and the princess, and the player's head textures can very easily "glitch" [URL='
https://f95zone.to/threads/released-help-me-brave-sir-knight-a-godot-dev-diary-previously-just-sharing-my-great-idea.171385/post-11784188']if you move left-right fast[/URL], the head takes 1 extra frame to get in place with the rest of the body.
- Now that I actually know the fucking cause, I also understand why this is happening: Godot draws stuff on screen going from the bottom of each scene upwards. Child nodes are always drawn before the parent nodes. Due to the RemoteTransform, ONLY the parent node will be affected, a change that won't travel down until the next frame. Why, however, it's not properly updating while fucking the orc gal as shown way above, I still don't know.
- See, remote transforms were supposed to help in order to properly align the draw order of textures: you put the remote as a child of the bone, then just point to the actual texture, which will ideally be ordered elsewhere, so that it's easier to rearrange what piece goes on top of what, like breasts show on top of the torso, boots show on top of the shins, etc. But Godot's entire draw order is one of the most infuriating aspects of the engine. As I said above, it draws in a reverse vertical order, whatever's at the bottom of the scene's node list is drawn first and on top of other stuff.
Another annoying bug that popped up is that after fucking the orc, she'll remain stuck to the player.
On the bright side, she's properly attacking, being hit and disappearing if she dies instead of fainting.