Saturday, November 2, 2024

Good Progress and Frustrations

Today was a day that I spent mainly in code, which was great. I got stuck in after breakfast, and managed to get NPC images loading and caching nicely off the server, which is great. All the little extra details about callbacks and so on worked as intended. The image renders nicely if you have it, and if you don't, it fetches it, and then renders it to the screen as soon as it has it downloaded. Huzzah.

And now. The bane of my last four or so hours. Some animations render "now quite right" which is driving me rather bonkers. The new Fighter Class animation was one of those, in a few instances. That got solved. It was a funky value that had worked it's way through into the database at some point. That got solved and resolved.

Player Two entered the game. Floren Wolves. These things just won't render quite right. And I've narrowed it down to what I think is the particular value that's causing the issue (it's a particular width property in one object that is propagating it's way up the food chain to the rendering engine) but why this appears to only be happening in Floren Wolves, when they aren't bigger or smaller than other creatures is at present beyond me to understand. I've also been through the various database entries from start to finish and they all look fine, so again, I don't currently see how the problem comes to be, but I can see that it is, in fact, being.

I will pick up again tomorrow, and hope that a fresh set of eyes finds the issue quickly and easily, but right now, there's rather choice words and utterances flying in my head. They're the same size as other things that render correctly. They seem to have all the right data in the database as do the other creatures. They should, for all apparent purposes, render correctly, yet they do not.

The image shows the issue. The wolves are rendering to the right of where they should be by about half their size. One should be straight under Chester. Another should be between Spend and Sparkie (who's name is obstructed by the trees) yet they all appear to be about half a tile to the right.

Edit: So, turns out that I was really tired last night. When I was looking in the database for the values, I was looking at one object, but thinking I was looking at another. My choice words from last night were used again when I saw the obvious, clear and annoyingly blatant issue. One update statement and things are rendering just how they should. tl;dr; parentID 5 is not the same as parentID 17. fml.

No comments:

Post a Comment

Plink plink plink

So, I've just dropped another internal test build out, capturing another big bunch of changes I've been building up with particular ...