Jump to content

Recommended Posts

Posted

I'm trying to add a TextureAtlasSprite by calling event.map.registerSprite() in a TextureStitchEvent.Pre handler.

 

It's not working properly. I get a TextureAtlasSprite with valid-looking texture coords, but the position in the texture that they refer to is occupied by a different sprite. Looking at the dump of the stitched texture map, my texture doesn't seem to appear in it anywhere.

 

Am I going about this the right way? Is TextureStitchEvent.Pre the right time to do this? Am I calling the right method? The equivalent thing used to work in 1.7.

Posted

It's definitely doubling things up. The two textures I'm adding are being allocated the same slots in the texture atlas as minecraft:blocks/anvil_base and minecraft:blocks/anvil_top_damaged_0.

Posted

I found out what was happening.

 

It seems that the textures are loaded twice when Minecraft starts up. Because I'm keeping my own cache of the sprites that I add, they weren't getting added to the atlas the second time around. Clearing my cache on each TextureStitchEvent solved the problem.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.