Minecraft Forums

Quote from eleazzaar»

Hey, has anybody ever tried to do a "Better Leaves and Grass" effect to leaves with block models? Looks to me that there's no way to make it look good with "Graphics" set to "Fast". Am I missing something?

Well, fast mode doesn't do much of anything anymore (most of what it used to do has been slowly removed). If you go into spectator mode, you'll see that leaves aren't actually culling themselves in fast mode (see bug report MC-85312) so the loss of transparency is for no reason.

So with that said, I'd either advise you to advise your users not to use fast mode or make it into an add-on pack (not well supported by the content sites, but still).

Hey guys, don't want to take the painstaking task of converting 1.8 clock/compass animations to the ok-I-get-it-cool-for-models-though-I-could-do-that-with-the-animations-before-so-a-bit-too-complex-for-regular-items-1.9 format?

There IS a better way now, introducing this thing I've been making for the past few days, a python-fu script for GIMP:

https://gist.github.com/insomniacUNDERSCORElemon/9cc23ce7c1e5c9e4379e

How to use:

1. Copy all of the script's text
2. Open desired 1.8 clock and/or compass animations (the RIGHT-most file seems to be the one that uses the filter)
3. Go to filters>Python-Fu>console
4. Paste the script's content
5. ???
6. If everything runs smoothly, no red text will appear and comments will show up with info

(if you opened clock AND compass, close the one it just did, clear the console and hit enter, and then paste the script again.... if any issues occur, try doing each image individually and then closing GIMP before you run it again)

Tell me what you think! This is probably the most 'real' coding I've done, first time working with Python, it wasn't too bad (although I'd prefer semicolons to whitespace in most cases) so those of you with more coding experience should get some other converters finished, hehe...

Also, it was quite easy to do the clock.... but the compass? Gah. Instead of using it like the clock does, it's offset to start in the middle and then loop back.... BUT that's just the model order, the image numbers are used the same as clocks. That took me considerably longer than other parts.

Quote from kwerti»

Any ideas on how to transform a vector in one coordinate system to a vector in another (or a rotation in one system to a rotation in another)? 'Cause the display converter can right now convert scale...and that's it.

Sadly, I have no idea. What is the coordinate system change anyways, perspective-->orthographic? I mean, it might help either using MCP and comparing.... I do remember someone saying "use a transformation matrix" but I guess you'd have to figure that out (and I have no idea what it entails other than translation and rotation would probably be different).

I guess the best possible start would probably to take some models and manually modify the display settings of the 1.9 versions to mimic the 1.8 versions as closely as possible... and then see if you can use math to get the old to new with code and then see if it is repeatable for different models.

However, I will say (sorry if I've said it before) that rotation is the most important thing to convert. Most of the reason I think they made this change is how finicky the old system was: you had to scale MOST custom models up, and then because of how the coordinate system works, you had to tweak it to get the models to the middle of the GUI. I think you'll find with many models that, if you were to convert them, they'll probably be close to the new defaults.... like having a scale of 1.062 or translated by 0.0431. Basically, most models will probably change so little from defaults that their conversion can be effective thrown out and replaced with 1 (scale) or 0 (translation).

I say that because I've actually experimented with deleting the display settings on some of my models (like tools) and their GUI/dropped versions were at the perfect size where I probably wouldn't change it much (or at all). Many of my GUI/Ground display settings have a scale of 2 applied. So I'm not sure how that'd work out with a converter, but a cutoff threshold (possibly optional/tune-able) and maybe some rounding would be nice.

Quote from kwerti»

and since the axes are different, the translations would be different as well.

My point in my last post was that translation should be last priority and may not even be needed at all. Most models people make should be centered to the middle. Certainly most of my models fit this, most times I used translation was because scaling and rotation caused the model to be shifted away from the center (usually to the bottom-left). I believe it has been directly stated that the new coordinate system is supposed to fix this.

The only model I can think of off the top of my head that I have translation on not to counteract shifting to the bottom-left is probably doors (because I made a model combined of the block models, so it needed to be shifted up)... and after trying to convert it by hand, it's clear that the translation doesn't need to be changed:

1.8: "gui": {"rotation": [ 0, -20, 0], "translation": [ 0, -3, 0 ], "scale": [ 0.85, 0.85, 0.85 ]},
1.9: "gui": {"rotation": [ 30, 30, 0], "translation": [ 0, -3, 0 ], "scale": [ 0.55, 0.55, 0.55 ]},

They look nearly identical with the rotation/scale change but no change to translation.

---

Also, since it was near the bottom of the last page:

Quote from insomniac_lemon»

Hey guys, don't want to take the painstaking task of converting 1.8 clock/compass animations to the ok-I-get-it-cool-for-models-though-I-could-do-that-with-the-animations-before-so-a-bit-too-complex-for-regular-items-1.9 format?

There IS a better way now, introducing this thing I've been making for the past few days, a python-fu script for GIMP:

https://gist.github.com/insomniacUNDERSCORElemon/9cc23ce7c1e5c9e4379e

How to use:

1. Copy all of the script's text
2. Open desired 1.8 clock and/or compass animations (the RIGHT-most file seems to be the one that uses the filter)
3. Go to filters>Python-Fu>console
4. Paste the script's content
5. ???
6. If everything runs smoothly, no red text will appear and comments will show up with info

(if you opened clock AND compass, close the one it just did, clear the console and hit enter, and then paste the script again.... if any issues occur, try doing each image individually and then closing GIMP before you run it again)

Tell me what you think! This is probably the most 'real' coding I've done, first time working with Python, it wasn't too bad (although I'd prefer semicolons to whitespace in most cases) so those of you with more coding experience should get some other converters finished, hehe...

Also, it was quite easy to do the clock.... but the compass? Gah. Instead of using it like the clock does, it's offset to start in the middle and then loop back.... BUT that's just the model order, the image numbers are used the same as clocks. That took me considerably longer than other parts.

Quote from KnightMiner748»

I'm a rebel, I used translation for my ladder model :P. It was easier than making a separate model just to move it to the center.

But yeah, it makes sense that translation did not change, as the center would not move and changing the units would only make things more complicated (even for Mojang).

Hmm, liking optimization/smaller file size, I did as well. But I tested it out and translation did change, just not [when Y is the only coordinate being changed]....
Test with changing my ladder:

1.8: "gui":{"rotation":[0,-20,0],"translation":[0,-1,-3],"scale":[1.5,1.5,1.5]},
1.9: "gui":{"rotation":[30,30,0],"translation":[-3.25,3,0]},

So it seems Z translation doesn't do anything as a GUI setting anymore since X/Y now control placement as you'd logically expect (moving it on the Z plane would just move it closer to the camera, basically it'd just get bigger).... except z translation actually DOES change Z-buffer! What I mean is, I was messing with the ladder GUI display, it got shifted over behind an item icon.... then I decided to change the Z-translation on the ladder and it moved more IN FRONT of the item icon, the item actually clipping through it! (also on a partially related note: it's interesting to add GUI rotation to item/generated.json, but doesn't look so great because the items don't seem to have much shadow on them, so it makes them look odd.)

Well, I didn't really understand it before and I don't understand it now. Translation is a bit easier to understand.... until rotation comes into account and then it's even more confusing than before. I'm starting to feel like they'll probably change it yet again in the future :/

Although your last line is incorrect since default only really used flat icons and plain cubes in the inventory (anything else is in the middle). Most usability issues with the model format isn't going to be experienced on the same level (or at all) as it is for resource pack makers. Also I half suspect that whenever they run into monotonous tasks they just whip up an automated tool to do it (probably even in java and then just throw it out afterwards) and then the files are done so it's not an issue anymore.