Outfits not displaying correctly while using asset files #966
Labels
bug
Something isn't working
Priority: Medium
This issue may be impactful and needs some attention.
Status: Pending Test
This PR or Issue requires more testing
Type: Bug
Inconsistencies or issues which will cause an issue or problem for users or implementors.
Priority
Medium
Area
What happened?
While using assets in OTCR, a visual bug happens when creatures of certain looktypes are moving. I personally tested with OTCR (multiple builds throughout the last two years) and TFS, 1.5 to 1.7.
Few examples;
Posted back in 2023, https://discord.com/channels/888062548082061433/1091770506253959318 I reported the issue showcasing a broken looktype, # 63. Can't upload directly to github, so here's an imgur link. Unknown what my versions were at the time, but it would've been whatever was the most recent at that time.
https://i.imgur.com/cJTwFdm.gif
This certain looktype is not the only one to be broken, but was just shown as an example. Left side of the gif shows OTCR, and the right side shows
Just today, I pulled the latest versions of OTCR (commit c3aace1) and TFS (commit 6982d66) and logged into test. I clicked through a few outfits to showcase multiple that were broken. On this image, the right side, is OTCR with assets files, and on the right side is again OTCR with the exact same asset files just converted to .dat/.spr files with the game feature GameLoadSprInsteadProtobuf enabled.
https://i.imgur.com/Rf1RE11.gif
Recently, another user on discord (_mattzon) posted having the same issue using the most recent version of Canary, OTCR (unknown build) and 1340 CIP client. Can see their post here; https://discord.com/channels/888062548082061433/1306420047853387827/1306420047853387827 The images are again too large to attach to this issue
Would love to move to assets fully if this gets corrected, as the asset files are a lot smaller then dat/spr files, and easier to update.
What OS are you seeing the problem on?
Windows
Code of Conduct
The text was updated successfully, but these errors were encountered: