Marcel
- Marcel1
- JIRAUSER638382
- America/Detroit
- Yes
- No
4 issues
Key
Summary
Status
Reporter
Assignee
Created
MCPE-126434
Changed Description:
I'm attempting to create a custom higher resolution realistic texture for Axolotl's and noticed the feet and legs appear to double up and look glitchy when RTX is turned on but look fine when RTX is turned off.
Here is a link to the pack if you want to check out the glitch: https://drive.google.com/file/d/1PY0YRGuxf8Q3fSUmqYZgJfNohj1q8An_/view?usp=sharing
Thanks,
-Marcel
The part I want to flow? If by flow you mean glow, I don't want any of it to glow but it seems to have other plans haha. Thanks!
I find the solution at least for 256x packs is to open the folder for the pack, then go to textures folder. in there you should find a "terrain_texture.json". Open that up in notepad and change ""num_mip_levels" : 4" to ""num_mip_levels" : 0" and ""padding" : 8" to ""padding" : 0". Then save.
My theory is there seems to be some sort of hard programed limit of around 350mb for block textures in the current MC RTX build. Mip mapping generates 4 other smaller and smaller versions of the textures to use for distant blocks, so that quickly fills up the space allotment for block textures, which in turn makes the game generate lower res textures to start with, so it can fit them all within this limit, but it doesn't do a very good job of it.
A fully complete 512x pack or greater would be way over this 350mb limit to begin with, so no matter what, it's generating low res textures even without mip mapping turned on, until they remove or increase this size limit.
Pack creators shouldn't be selling broken packs. They would clearly be getting the issue too and are just choosing to ignore it. I'd be asking for my money back if I paid for a high res pack that didn't work properly. I believe the limit when RTX was in beta was around 100mb, so they upped it a bit to around 350mb when they came out of beta, but it's still unacceptably small.
BTW here's a free 256-512x RTX pack you could try if you want. No donation, no ads, no pay wall, just google drive. Download links are in pinned comment.
https://youtu.be/XQeZT76iMPc
I made sure it was just under the size limit that triggers that error.
Hello,
This bug is still present in the latest 1.17 version.
Another thing I noticed is when a torch is placed near the chain the whole chain will light up regardless if there are blocks in between them blocking the light.
https://youtu.be/qU02PwMHusk
Here is a link to the pack: https://drive.google.com/file/d/1ZInHO_iyS_EKFDlppuRp3JHwX1td6zVD/view?usp=sharing
Hello,
Here is the pack with the 256x items added back in and you will see most of the items do not render correctly when RTX is turned on but then look correct when RTX is turned off.
https://drive.google.com/file/d/1ZInHO_iyS_EKFDlppuRp3JHwX1td6zVD/view?usp=sharing
Thanks,
-Marcel
Hello,
There's no way to change resolution in game.. I was just opening the textures in photoshop, resizing, saving and re launching the pack to show the issue is only with high resolution items. But here is an example pack to save you the effort.
https://drive.google.com/file/d/1evzOpJ7mncCBSpvfyTsOJsp5GizMTHhy/view?usp=sharing
The iron sword and gold sword are now the exact same texture, the only difference is iron is 256x256 and gold is 128x128. If you turn RTX on and bring up the iron sword you will see half of it is cut off, but then when you switch to the gold sword the whole thing is there. If you turn RTX off you will see that the whole thing is there for both the iron and gold sword.
I have done the same thing with 3 records as well. Record blocks , cat and chirp are now all the exact same texture, the only difference is record_blocks is 256x256, record_cat is 128x128, and record_chirp is 64x64. With RTX on you will see 2/3rds of record_blocks is cut off, half of record_cat is cut off, and chirp is all there. But if you turn RTX off they all appear fine.
Thanks,
-Marcel
Some new findings while working on my 1.17 update to my texture pack. With the 120 or so new textures I hit this limit around 320-330mb. I also found the more textures you have the lower this limit becomes. Even just adding a .json file to link something new to an old texture will decrease the space available. I found I was just under the limit then added a couple .json files to link potted azaleas to the normal azalea textures and boom error popped up and I still had to go through and lower the resolution of like 6 other textures before it allowed the new ones without the error, even though I didn't actually add any more size or textures. So the amount of textures, even if just linked to other textures, seems to have a big impact on what size the game allows you. So a half complete pack seems like it would allow you more texture space then a fully complete pack which is super annoying. I also noticed when you get pretty close to the limit the game is now adding some weird seams to animated textures like fire, water, and lava for no apparent reason.
For a Non-RTX pack with mip mapping enabled I hit this limit around 165mb. Also it seems this error has nothing to do with the amount of memory your system has. The limit is the exact same on my 8GB GPU and 64GB Ram System as it is on my friend's 4GB GPU and 16GB ram system.
I thought bedrock was supposed to be the superior version of Minecraft when it came out with this RTX version, yet it can't even handle much more then a fully complete 256x texture pack... Java on the other hand can handle 1024x or greater texture packs a few GB in size with shaders no problem. The only limit there is what your computer can handle.
Recently I found a way to squeeze a bit more high resolution textures into my pack before hitting this limit. I had 4 1024x1024 textures in what was otherwise an all 256-512x pack. I thought they were pretty insignificant though since only like 2% of the space in those textures was actually used. (stage 0 of beetroots, carrots, potatoes and wheat) and they were only about 45kb each. I decided to resize them to 512x to see if it would allow me to up a couple 256x textures to 512x. 70 512x texture/normal maps later is when things started to glitch out again and a couple past that the error was hit again. Went from about 320mb to 345mb of block textures.
So in conclusion to texture pack creators, avoid 1024x1024 textures, the game really doesn't seem to like them no matter how insignificant they may seem...
With that said, I still have hundreds of other 256x textures I'd really like to bring up to 512x, so this limit is the most annoying bug in the game. It would be good to know at least what the exact limit actually is, so I'm not having to constantly waste hours trial and erroring to see what works and what doesn't... Is it texture file size? Is it texture resolution? Is it the overall combined resolution of every texture? Is it triggered sooner with multiple different resolution textures then if everything was the same? Is it a programmed max system ram amount the game is allowed to use? Is it a programmed max GPU memory amount the game is allowed to use? Is it something totally different? Is it just block textures? Is it blocks combined with one or a couple of the other texture folders? Is it all the textures in the game combined? Sooo many possible variables. 😝