Sprites/Animations not working correctly in First Person Mode

[Torri 800]

Good evening,

It's been a long time since AAO has received any meaningful updates. While the Instant Text functionality is definitely a neat addition, and is proof of just how much work AAO has on its hands to catch up to modern standards (Although instant text was already possible in the past, just more accessible now), this update is not without its flaws, namely...

Major Grievances which need direct addressing. This particular grievance is so bad, it's making me wonder why I'm still trying to work on my Trial, and I say this because the Frames have become incompatible with First Person perspective, such as the scene where the protagonist is deliberating with their assistant prior to entering the courtroom. It's also worth mentioning that this bug is inconsistent and doesn't apply to every Frame in a Trial. (Not to mention previous bugs that have appeared previously such as the GIF bug from last month.)

Basically, this new bug causes characters to assume a single, randomly selected sprite, and they always revert back to that sprite despite my changes to said Frame. This isn't the only bug that irks me. First Person/Offscreen Mode is also no longer compatible. If the character's name is speaking the dialogue, they WILL appear, again, as a single randomly selected sprite. I say single because every Frame that is affected uses the exact. Same. Animation/sprite selected for that Frame every single time. To make matters worse, even deleting the affected Frames and creating new ones will change the sprites to the random sprite I mentioned earlier.

Because this is so insane, I decided to go a step further to qualify the grievances via video demonstration, here's the link:

https://www.youtube.com/watch?v=HSgrmhxi9ds

Please prioritize fixing all aforementioned bugs before proceeding with any updates. Thank you.

[Enthalpy]

As I mentioned in the announcement update:

Our priority for the next update, which we want to come out fairly soon, is to patch any problems we inadvertently introduced.

So what we need from you all right now isn't to be told what we need to prioritize, but patience and clear, precise statements of what the problems are. While the video was helpful, it took some effort to figure out exactly what you were trying to say.

In the interests of having clear, precise statements of what exactly the problem is, here are some reproduction steps:
1. Create a frame with a place and a character sprite.
2. On that frame, assign the speaker to be a different character. You can confirm that at this time, the length of the frame's characters array is 1.
3. Hover over the display, so that the minieditor appears. This will cause the speaker's sprite to appear. You can confirm that at this time, the length of the frame's characters array is 2.

[Enthalpy]

I need to go to bed already, but my intuition is that on this line of code, we need to add

Code: Select all

character_info.profile_id = frame_data.speaker_id

as a precondition, rather then enforce it a few lines down.

[Enthalpy]

This will be fixed by this pull request. Once it and this other PR are merged in, I'll try to get AAO updated ASAP.

[Enthalpy]

This is now fixed! If there are no reports of this still being an issue, I'll close this in a week.

You will still need to remove characters inadvertently created due to this glitch, unfortunately.

[Torri 800]

This is now fixed! If there are no reports of this still being an issue, I'll close this in a week.

You will still need to remove characters inadvertently created due to this glitch, unfortunately.

Thank you so much for fixing it so quickly. I do apologize for not being code savvy - it's why I couldn't articulate the grievance as concisely as I should've. Rest assured, the next time I report a bug, I'll be sure to recreate the bug in a concise step-by-step format.