Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

A 1.19 replacement for TextureUtil.uploadTextureImageAllocate


BananaPekan
 Share

Recommended Posts

Okay so in my older mods I have used TextureUtil.uploadTextureImageAllocate to load textures from outside of the mod at runtime.

But now that I need this feature back in 1.19 I cannot find it or any replacement.

Can someone please tell me what was it replaced with or at least how to do the exact same thing in 1.19?

 

Thanks in advance.

Link to comment
Share on other sites

That's a pretty esoteric question. 🙂

 

You have to navigate 2 different changes;

* The change of name from the old forge mappings to the mojang mappings

* The change of graphics engine

 

Here's how you can do it:

Find where your method is used in vanilla, e.g. in 1.12 with the stable_39 mappings this is SimpleTexture.loadTexture()

Find the same processing in 1.19 which also happens to be called SimpleTexture.

Now compare the 1.12 vanilla code with the 1.19 version, so you can determine the modern way to do your processing.

 

It won't always be as "easy" as this. Sometimes you would have to repeat the process.

e.g. If you couldn't find SimpleTexture in 1.19, find where SimpleTexture.loadTexture() is called and locate that processing in 1.19

 

However, in this case, you can already think of something that loads "external images". Minecraft player skins.

So you can look at and adapt what that does - SkinManager

Edited by warjort
  • Like 1

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Link to comment
Share on other sites

Thank you! that worked!

59 minutes ago, warjort said:

That's a pretty esoteric question. 🙂

 

You have to navigate 2 different changes;

* The change of name from the old forge mappings to the mojang mappings

* The change of graphics engine

 

Here's how you can do it:

Find where your method is used in vanilla, e.g. in 1.12 with the stable_39 mappings this is SimpleTexture.loadTexture()

Find the same processing in 1.19 which also happens to be called SimpleTexture.

Now compare the 1.12 vanilla code with the 1.19 version, so you can determine the modern way to do your processing.

 

It won't always be as "easy" as this. Sometimes you would have to repeat the process.

e.g. If you couldn't find SimpleTexture in 1.19, find where SimpleTexture.loadTexture() is called and locate that processing in 1.19

 

However, in this case, you can already think of something that loads "external images". Minecraft player skins.

So you can look at and adapt what that does - SkinManager

 

Link to comment
Share on other sites

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
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.

 Share



×
×
  • Create New...

Important Information

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