-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Fast Leaves are broken #132
Comments
I will have to dive into this since we just set the render type with Mc normally it handles the rest so idk if it’s a midlander issue or something, what platform and Mc version are you using/have you tried any other platform or version |
I've tried using the default forge launcher, on 47.2.20, 1.20.1. Switched launchers and also disabled all mods aside OhTheBiomes... I've actually found out a bit about why this issue happens, apparently bwg doesn't define the rendering method in the block model for it's leaves. Take a look at how acacia leaves are structured: {
"parent": "minecraft:block/leaves",
"textures": {
"all": "minecraft:block/acacia_leaves"
}
} After i added that in a resourcepack it kinda works, but the thing is, the inbetweens (where it's currently transparent), become all black and not exactly a dark greenish as other leaves, so yeah, that's all i could gather out of it |
We do the samething as normal mc |
That's odd, hmm are you able to replicate this issue in your side ? Maybe it's something on my end |
So I can recreate it on NeoForge and Forge but on fabric it works fine which leaves me to believe it's an issue with how Forge like platforms handle the rendertype changing during graphic settings changes |
I'm gonna close this as there's nothing we can do on our side unless we use the Deprecated by forge way of using the vanilla map. This should be reported to forge as a issue with the rendertype not changing with the graphics properties |
anything i can do? Should i update forge or something like that? |
No It just needs to be fixed by the forge team |
Hi, first of all sorry for "reviving" this, but I've encountered this recently as well and started looking to see if I can fix it with a resourcepack.. and it looks like removing the I'm not a modder but reading the documentation it looks like this field is optional and so far flying around the world I don't see any rendering weirdness of the leaves after removing this field. https://docs.neoforged.net/docs/resources/client/models/#render-types fast (tested using aspen leaf): fancy (tested using aspen leaf): fast settings flying over an entire zelkova forest after removing the render_type field: Edit: after more testing, the only leaves having issues by removing the render_type are the Yucca Leaves |
NeoForge has changed somethings so I will look into it on there side, Forge I am working with on Fixing that can be found here and will be fixed once this pr is merged |
Basically when enabling fast leaves, instead of making their transparent parts opaque/darken, they continue to be transparent, but without rendering the other side.
With Fast graphics:
![image](https://private-user-images.githubusercontent.com/77132244/373071802-07b0b968-0155-4303-b0c7-8db88703eec8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1MTEyMzcsIm5iZiI6MTczOTUxMDkzNywicGF0aCI6Ii83NzEzMjI0NC8zNzMwNzE4MDItMDdiMGI5NjgtMDE1NS00MzAzLWIwYzctOGRiODg3MDNlZWM4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE0VDA1Mjg1N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI3YzJkMzhhNGU4ZjVlMjE0ZTkyYWUyMGViNjk3ZDY1N2MyZDliNzE2ZDhhZDFkZDNmN2M0ZmVlM2U4ODQ2MzEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.UtsYUU0fAf1XY2JCTcKd8NZZJsULCqgerBpsjIDhlHk)
Without
![image](https://private-user-images.githubusercontent.com/77132244/373071852-6ea81c60-81f0-4f06-8823-98399143f4fb.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1MTEyMzcsIm5iZiI6MTczOTUxMDkzNywicGF0aCI6Ii83NzEzMjI0NC8zNzMwNzE4NTItNmVhODFjNjAtODFmMC00ZjA2LTg4MjMtOTgzOTkxNDNmNGZiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE0VDA1Mjg1N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNhNjM4ZGY4NjQwNjFlNmFiZGU1NjEwZWEzOWMyODUzMDRkYWUyMDg5Nzg2ZTI3ODRjZTEyODg3MjA2MDY0YjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.yQfeA_e3pj7swgX5OiSB9NHmjR7znzQyM-NzFHcLdRY)
Expected behaviour:
![image](https://private-user-images.githubusercontent.com/77132244/373071940-9e0d694d-fa80-4a08-99a1-a9c5379134b9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1MTEyMzcsIm5iZiI6MTczOTUxMDkzNywicGF0aCI6Ii83NzEzMjI0NC8zNzMwNzE5NDAtOWUwZDY5NGQtZmE4MC00YTA4LTk5YTEtYTljNTM3OTEzNGI5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE0VDA1Mjg1N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWVhNmI5OTYxMThhZDQxOWY3M2UxOGRhN2FiMDQ0ZjY4MjNhZTJhZDY0YWQ1ZTFjNTNjZjUwZWUwN2M0ZTVlOWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.n-UnMlmD7JIuum9YkhQ3bumOs53AKJ7apPO56VdsHVw)
The text was updated successfully, but these errors were encountered: