-
Notifications
You must be signed in to change notification settings - Fork 14
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
Activating Shield Generator Makes Entire Screen Pink #95
Comments
Thanks for reporting this. When testing Ashlands briefly, I noticed a shader error in the log, something along the lines of: Edit: The error message is in fact: Preliminary thought: Valheim 0.217.40 seemingly introduced some new features for modding, so perhaps we can leverage that to 'fix' this shield generator shader so that it is compatible with OpenGL 4.1 on macOS. |
I'll take a look at trying to make a client side mod that'll fix the issue but I don't have much modding experience other than Minecraft. Also I am going to see if I can get it to work using Apple's Game Porting Toolkit. I have been able to get Elden Ring and several other games running smoothly on my M1 Macbook Air using this method. |
I can confirm the game runs via CrossOver 24.x (which contains parts of Apple's Game Porting Toolkit) if that is of any help. Would expect the toolkit standalone to also run the game. |
I have run into the pink issue by dying in Lava. As soon as I get close to retrieving my tombstone it turns pink again and cannot do anything. Just wanted to add this as it's not just Shield Generator problem. |
Very strange. I have beaten the ashlands in several playthroughs (I have practically explored the entire biome on one of them in creative) and haven’t run into that issue at all other than the generator. Is this on multiplayer or single player and is there anything in the area that you suspect might be causing this issue? Also if you can look through your log and see if any errors are being thrown that would be amazing! |
Yes. I've played a bit in Ashlands, raided castles etc. Could you guide me to where the log might be or what it's called? |
You can find the log files here: |
Well I wasn't able to duplicate the issue dying in Lava again but apparently I did go into an area that had a shield generator as it went pink. Here is an excerpt of the log: [Error : Unity Log] NullReferenceException: Object reference not set to an instance of an object NullReferenceException: Object reference not set to an instance of an object [Error : Unity Log] NullReferenceException: Object reference not set to an instance of an object NullReferenceException: Object reference not set to an instance of an object [Error : Unity Log] NullReferenceException: Object reference not set to an instance of an object NullReferenceException: Object reference not set to an instance of an object WARNING: RGBA Compressed BC7 sRGB format is not supported, decompressing texture NullReferenceException: Object reference not set to an instance of an object [Error : Unity Log] NullReferenceException: Object reference not set to an instance of an object NullReferenceException: Object reference not set to an instance of an object WARNING: RGBA Compressed BC7 UNorm format is not supported, decompressing texture |
The pink colour in Unity is usually materials that don't fit the right Render Pipeline. |
Just a quick update: contacted IronGate about this on their official Discord and got the following response:
There is hope 🙌 |
Valheim seems to be released officially for Mac on June 10th |
Closing this issue as the official macOS client is now available! 🥳 (see #104) |
Whenever I activate the new shield generator my entire screen become pink (image below) and even if I leave the area of the shield it remains so. I have tried re-logging and it does not fix it either. This bug seems to only be happening on my mac and not my pc. To end up fixing it I had a friend log onto my world on his pc and destroy the shield generator which made it normal again. Not sure if you can do anything about it or if it is just a bug that the Valheim developers need to fix. Either way if anyone comes across this bug just destroy the generator and everything will be fixed.
The text was updated successfully, but these errors were encountered: