Graphics glitch on MacBook Pro M1

[milansm]

Hi there,

I bought new Apple MBP 13" M1. The game loads successfully, however, it shows unexplored area white.
See the screenshot: https://prnt.sc/11af6nf

[vic]

Side note: Wow, it DOES work on M1. I guess I'll buy M1 after all...

After my multiple request to the developers, here is what I got to know. Mac development got the devs into so much trouble so far, and so much expenses (IIRC they spent > $100k in resources), that they said "damn never again". These resources never paid back in Mac sales.

I DO hope that this glitch is relatively easy to fix, but AFAIK M1 development is way, way different. Maybe it's only the background color that gets set incorrectly on M1.

[Epyon]

It's unfortunately the problem that I don't have a M1 to test what's wrong, and I definitely can't afford one. It's obviously a bug with MoltenVk's compatibility layer (less probably with M1 itself), because M1's the only device on which this glitch happens, so we're basically hunting for a way to work around it. We're asking around friends hoping someone can lend an M1, and we'll definitely try to nail this bug before 1.0.

[milansm]

Thanks for your reply! Looking forward to playing JH on M1, since my old Macbook is struggling with the game. :)

Also, wish you all the best with the game's sales, someone of your talent and dedication should be able to afford all the equipment they can imagine!

[milansm]

Any news on this? It would be great if we could expect this one to be fixed before 1.0 release :)

[jordanshiveley]

Happy to see that the devs are aware and possibly fixing this? I only have the M1 (traded in my old mac to get one) so having this bug AFTER purchasing the game kinda sucks. Still, ya'll work looks amazing and I can't wait to be able to stream and play this game at some point?

[Pangolin Legends: Arceus]

Originally posted by Epyon:

It's unfortunately the problem that I don't have a M1 to test what's wrong, and I definitely can't afford one. It's obviously a bug with MoltenVk's compatibility layer (less probably with M1 itself), because M1's the only device on which this glitch happens, so we're basically hunting for a way to work around it. We're asking around friends hoping someone can lend an M1, and we'll definitely try to nail this bug before 1.0.

What about this service?
https://www.computerworld.com/article/3605768/how-to-rent-a-virtual-m1-mac-mini-for-12-cents-an-hour.html

[jordanshiveley]

Originally posted by Epyon:

It's unfortunately the problem that I don't have a M1 to test what's wrong, and I definitely can't afford one. It's obviously a bug with MoltenVk's compatibility layer (less probably with M1 itself), because M1's the only device on which this glitch happens, so we're basically hunting for a way to work around it. We're asking around friends hoping someone can lend an M1, and we'll definitely try to nail this bug before 1.0.

any updates on this?

[Epyon]

Working on a possible fix that will land next version, hopefully it will work!

[jordanshiveley]

Originally posted by Epyon:

Working on a possible fix that will land next version, hopefully it will work!

thank you so much for the continued communication!

[Epyon]

We've indentified the exact feature that is causing this anomaly. We're working on a workaround, worst case we'll disable this graphical effect for OSX. Stay tuned!

[vic]

Yaaay!

[jordanshiveley]

Originally posted by Epyon:

We've indentified the exact feature that is causing this anomaly. We're working on a workaround, worst case we'll disable this graphical effect for OSX. Stay tuned!

thank you so much!!

[milansm]

Originally posted by Epyon:

We've indentified the exact feature that is causing this anomaly. We're working on a workaround, worst case we'll disable this graphical effect for OSX. Stay tuned!

Awesome!
Let me know if you need any help with debugging or testing, I'll be happy to help out. :)

[Epyon]

We have a fix, and it seems to be working - it will be deployed with the next version (tentatively June 28) :)

[Epyon]

And update is live! Please report if the issue is fixed!