Images corrupted about mcpe_viz

[Plethora777]

I'm on the case. It's a fun & maddening investigation.... Mojang did some deep weirdness to save storage space for worlds... Back to it. I'll update when I've got it solved.

[phunni]

I noticed in the final point of the Changes list here that they no longer use Block IDs. Could this be the cause of this bug? would it also mean that mcpe_)viz won't work anymore? I'm really hoping not since I use mcpe_viz extensively with my worlds...

[phunni]

Cool - thanks. As I said, I'm really hoping the changes they've made haven't broken mcpe_viz. I'm so used to using it's hard to imagine Minecraft without it!

[vvanhee]

Just upgraded to 1.2.13 and new saved maps won't work MCPE_viz. When I don't get a crash on start of processing records, I get weird images like posted above. Progress window shows lots of "WARNING: Did not find block variant for block(Mob Head) with blockdata=0 (0x0) MSG3". And lots of other did not find block variant messages for other blocks. My old non-upgraded saved maps still work. I love this program -- anything I can do to help, let me know!

[vvanhee]

You may have already seen this, but if not, it is a description of changes in how blocks are represented in Bedrock now: https://gist.github.com/Tomcc/a96af509e275b1af483b25c543cfbf37

[ynleborg]

Mine is broken too afer updating Realm to 1.2.13 :(

[Thunder33345]

they are changing it non stop i suggest halting it for some time after it became more stable

[Plethora777]

@vvanhee thanks very much for that link. I'd already updated the code to deal with most of the new chunk record stuff. The info in that link should help with the rest (packed bit madness!)

[Plethora777]

@Thunder33345 sort of agree, the stuff they are doing.... seems strange. Like writing code for an early computer with 4k of storage strange... It's very flexible but also sort of insane. I don't see the clear benefit of this packed bit business. I guess it saves space, but the cost in, well, sanity is high. And the space savings are lost as soon as you have a sub-chunk with a high number of diff blocks.

[Plethora777]

Just pushed an update - give it a try. Please note that --spawnable no longer works because the new paletted chunk format does not store block light info. (This is too bad)

[phunni]

Cool, will hopefully be able to give it a try this evening.

…

On Mon, 9 Apr 2018, 17:00 Plethora777, ***@***.***> wrote: Just pushed an update - give it a try. Please note that --spawnable no longer works because the new paletted chunk format does not store block light info. (This is too bad) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#56 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKiW0gnVX14dQJItr1YcjYtfqmTXdlckks5tm4V6gaJpZM4Sja03> .

[vvanhee]

Wow, that was quick! Fantastic! Will try it tonight.

…

On Mon, Apr 9, 2018 at 10:59 AM Plethora777 ***@***.***> wrote: Just pushed an update - give it a try. Please note that --spawnable no longer works because the new paletted chunk format does not store block light info. (This is too bad) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#56 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAgOSdvgQe34dNBcCQu-SAHQq63T_Qgnks5tm4V5gaJpZM4Sja03> .

[phunni]

Just ran it and it seems to have worked, although I get a lot of:

WARNING: getBlockByUname failed to find uname=minecraft:hardened_clay

That's the only one I get now. I was getting loads of different ones before I copied the mcpe_viz.xml. Has the config changed much/at all? I haven't copied it over my existing one, so I'm assuming not since it works.

[Plethora777]

@phunni Yep there will be loads of those until we have it covered in the XML file. I added "uname=" for blocks. I'll need to add support for aliases as there seems to be some inconsistencies. I just wanted to get an update out that worked first :) Need to think about how to handle the diff unames

[vvanhee]

So far it’s looking great! I ran into a strange issue only on level 15 where it’s showing large areas of bedrock — anyone else seeing this?

…

On Mon, Apr 9, 2018 at 2:33 PM Plethora777 ***@***.***> wrote: @phunni <https://github.com/phunni> Yep there will be loads of those until we have it covered in the XML file. I added "uname=" for blocks. I'll need to add support for aliases as there seems to be some inconsistencies. I just wanted to get an update out that worked first :) Need to think about how to handle the diff unames — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#56 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAgOSQmWPf6Fzc6ntDiTvYB9A8Z1Fh7Tks5tm7dwgaJpZM4Sja03> .

[vvanhee]

I can reproduce the problem with bedrock on level 15 using a new map, then every 16th layer has odd issues — starting at level 14 and hitting the up arrow should demonstrate the issue. Layers 31, 47, 63, 79, and 95 seem off compared to layers above and below, with odd pixels of air at regular intervals or other issues. Then going way up, I don’t get 100% air as I think I should, with the top solid blocks not getting erased. I should probably open a new ticket. Thanks!

[Plethora777]

@vvanhee Just pushed an update for that issue - thanks for pointing it out

[Shkyrockett]

It looks like there is a new Chunk version in the latest beta.

§3Skyblock §2Challenge.mcworld.zip

[vvanhee]

Great!

…

On Sat, Apr 14, 2018 at 10:30 AM Plethora777 ***@***.***> wrote: @vvanhee <https://github.com/vvanhee> Just pushed an update for that issue - thanks for pointing it out — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#56 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAgOSdt8hJt1lZdDfwr4JsV0w4IjEJTfks5tohYsgaJpZM4Sja03> .

[Plethora777]

I think this may be fixed by the new versions lately. I'm going to close this. Please feel free to open a new one if it's still a problem.