Jump to content

Recommended Posts

Posted (edited)

Hey there, so I've recently succeeded in combining two BakedQuad sets using IBakedModel, but my problem now lies to adjusting them.

So the way the item works it using it's base texture, then shrinking the texture of the selected item (Currently a placeholder Apple texture) into a smaller 4x4 size compared to the normal 16x16 size.

I've come to find that the format for the quad texture location is 3 floats, each stored into 4 sections of the vertex data (I think). What I attempt to do is shrink the X and Y factors by 0.25, if those are even the two correct positions.

 

What I'm doing just as a test to see what happens is as follows
 

	public List<BakedQuad> getQuads(IBlockState state, EnumFacing side, long rand)
	{
		if (side != null)
			return parent.getQuads(state, side, rand);

		List<BakedQuad> combined = new ArrayList(parent.getQuads(state, side, rand));
		// Take additional item and compress quads
		List<BakedQuad> additonalShrinkQuads = new ArrayList();
		System.out.println("New Set");
		for (BakedQuad quad : additional.getQuads(state, side, rand))
		{
			int[] vertexData = quad.getVertexData();
			System.out.println(vertexData);
			vertexData[0] = (int) (vertexData[0] * 0.5);
			vertexData[4] = (int) (vertexData[4] * 0.5);
			vertexData[8] = (int) (vertexData[8] * 0.5);
			additonalShrinkQuads.add(new BakedQuad(vertexData, quad.getTintIndex(), quad.getFace(),
					quad.getSprite(), quad.shouldApplyDiffuseLighting(), quad.getFormat()));
		}
		combined.addAll(additonalShrinkQuads);
		return combined;
	}

which works, other than the changing the additional quads (the item to display inside of the main item). This is a funny thing that happened from the above code an another snippet I tried to do
 

Spoiler

2017-08-16_15_33_00.png.9decfe2f920794e5cd32aa4dad33a1c5.png2017-08-16_15_26_50.thumb.png.2bd3a5a4da022278585962f1ce7fe7db.png

Yeah, fun times, so any info into how to adjust the vertex data is welcome!

 

Edit: I'd also like to know how to make sure the model is then held like a normal item as well, using the custom method seems to make it held in the weird awkward manner as seen in the pictures. Thanks again!

Edited by mysticalherobine
Posted (edited)

The texture UVs you have are actually the global UV coordinates on the texture atlas. So what you will need is figure out a way to access the texture atlas sprite that was used to bake the quad. In the sprite, you will find min & max global UV coordinates. Now just do some math, and apply the values.

Note: if you're trying to reduce the resolution of the texture, you have to do it completely differently.

 

As for manipulating quads data, you can't just do it on that raw data. Because quads for blocks and quads for items are in a different VertexFormat - the index defining each format element is different. You'll have unpack the quad first (into forge's UnpackedBakedQuad), then manipulate the more conveniently, but still not very, stored vertex data.

Take a look at the VertexFormat class to see how it is constructed.

 

PS: I have a library i use to unpack models, quads & vertices into Java friendly format (easy get&set operations). If you want, you can check it out here.

Edited by Elix_x
Is not are
  • Like 1

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



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Back then there was a number which determined the tier of an item and block. If the block tier is lower or equal to the item number, the block would be mined. this however, has changed and now it goes by "needs_netherite_tool" which is fine, until you realized that some mods had items and blocks that exceeded these values. You can make you own "needs_mod_tool" but I feel that this is more limiting(and just more work) than before. So is there anyway to use something similar to the old tier system while also still being compatible with a lot of other mod tools?
    • Well, when I log in to the server, sometimes within an hour, sometimes within a minute, the server closes and informs me that there was a Ticking entity error. Below is the crash report
    • This forum is for Forge, not NeoForge. Please go to them for support.
    • Forge version: 55.0.0 Minecraft version: 1.21.5 Downloads: As this is the start of a new version, it is recommended that you check the downloads page and use the latest version to receive any bug fixes. Downloads page Intro: Good evening! Today, we have released our initial build of Forge 55.0 for Minecraft 1.21.5. 1.21.5 is the newest member of the 1.21 family of versions, which was released yesterday on March 25, 2025. As a reminder, the first minor (X.0) of a Forge version is a beta. Forge betas are marked as such on the bottom left of the title screen and are candidates for any breaking changes. Additionally, there are a couple of important things to note about this update, which I've made sure to mention in this post as well. Feel free to chat with us about bugs or these implementation changes on GitHub and in our Discord server. As always, we will continue to keep all versions of 1.21 and 1.20 in active support as covered by our tiered support policy. Cheers, happy modding, and good luck porting! Rendering Refactor For those who tuned in to Minecraft Live on March 22, 2025, you may already know that Mojang have announced their intention to bring their new Vibrant Visuals overhaul to Java in the future. They've taken the first steps toward this by refactoring how rendering pipelines and render types are handled internally. This has, in turn, made many of Forge's rendering APIs that have existed for years obsolete, as they (for the most part) can be done directly in vanilla. If there was a rendering API that was provided by Forge which you believe should be re-implemented, we're happy to discuss on GitHub through an issue or a pull request. Deprecation of weapon-like ToolActions In 1.21.5, Minecraft added new data components for defining the characteristics of weapons in data. This includes attack speed, block tags which define efficient blocks, and more. As such, we will begin marking our ToolActions solution for this as deprecated. ToolActions were originally added to address the problem of creating modded tools that needed to perform the same actions as vanilla tools. There are still a few tool actions that will continue to be used, such as the shears tool action for example. There are some existing Forge tool actions that are currently obsolete and have no effect given the way the new data components are implemented. We will continue to work on these deprecations and invite you to chat with us on GitHub or Discord if you have any questions.
  • Topics

×
×
  • Create New...

Important Information

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