Valheim startup error message "Unity Log] GetPixel called on an undefined mip (valid values are ▸ - 6

[llanita]

Unity Log] GetPixel called on an undefined mip (valid values are ▸ - 6

The game worked this morning, tried to play now and it started showing that error and closing down
. Anyone have any idea what that is?
I have mods, Windows 11

[Moonman]

I have the same problem. I uninstalled the game, reinstalled it and have the same error.
I have no mods and fresh install of game on Win 10

[Imhotep]

Originally posted by llanita:

Unity Log] GetPixel called on an undefined mip (valid values are ▸ - 6

The game worked this morning, tried to play now and it started showing that error and closing down
. Anyone have any idea what that is?
I have mods, Windows 11

Save worlds / characters by backing them up. Uninstall valheim. Delete Valheim folder and all of its content. Reinstall Valheim without mods. Test Valheim. Yay it works. Now try to load prior worlds / characters. Not working? mods broke those worlds and or characters.

[Automaton Spy]

Probably need to update bepinex. It works without mods.

[Automaton Spy]

Update: I updated bepinex and it does work fine.

[llanita]

I updated valheim plus with the newest but its still giving me the error message.
Ok for some reason I thought Bepinex was Valheim Plus lol...Off to update Bepinex. thanks

[L1m3r]

Originally posted by llanita:

I updated valheim plus with the newest but its still giving me the error message.
Ok for some reason I thought Bepinex was Valheim Plus lol...Off to update Bepinex. thanks

That happens when some ******* mod authors get the audacity to just include BepInEx in their own mod, thus blurring the lines between mod and mod-platform ...

The asterisks up there are just that ;-)

[jaceandclary1]

Hello, there was this patch 0214.300 today, since I made the update I fly out of the loading screen. small window with a V.. unity 20203........ and the text window is bright red!
We also updated and restarted the server, but we're kicked out anyway. Everything was just working again with Plus and the mods, and now that again, it's slowly making our clan tired of it, does anyone have an idea what it could be?

[llanita]

It worked with the Bepinex update. Thanks

Originally posted by Kzar:

Update: I updated bepinex and it does work fine.

[Nice]

wow, everyone is getting this just now? felt like playing valheim and then now this.. probably not a client thing most likely i reckon the modding team can fix it in a while

[llanita]

Originally posted by Nice:

wow, everyone is getting this just now? felt like playing valheim and then now this.. probably not a client thing most likely i reckon the modding team can fix it in a while

Update your Bepinex mod.

[Nice]

yeah thats probably it thanks

[Automaton Spy]

Originally posted by llanita:

It worked with the Bepinex update. Thanks

Originally posted by Kzar:

Update: I updated bepinex and it does work fine.

You're welcome. It's usually that simple to fix a problem. But it also seems to have broken the first person camera mod which sucks. Bleh.

[L1m3r]

Well this is odd.
I just updated BepInExPack_Valheim[valheim.thunderstore.io] and VH isn't crashing anymore but all the mods that just got loaded get unloaded right before the VH's main window finishes loading...

[Message:   BepInEx] BepInEx 5.4.21.0 - valheim (<DATE> <TIME>)
...
[Info   :   BepInEx] Loaded 1 patcher method from [BepInEx.Preloader 5.4.21.0]
[Info   :   BepInEx] 1 patcher plugin loaded
[Info   :   BepInEx] Patching [UnityEngine.CoreModule] with [BepInEx.Chainloader]
[Message:   BepInEx] Preloader finished
...
[Info   :   BepInEx] 19 plugins to load
[Info   :   BepInEx] Loading ......
.....<SNIP>......
[Message:   BepInEx] Chainloader startup complete
<RI> Initializing input.
New input system (experimental) initialized
Using XInput
<RI> Input initialized.
<RI> Initialized touch support.
[Warning:  HarmonyX] UnpatchAll has been called - This will remove ALL HARMONY PATCHES.

Turns out you absolutely need to update/overwrite the "...\Valheim\BepInEx\config\BepInEx.cfg" because of one change:

[Preloader.Entrypoint]
....
## The name of the type in the entrypoint assembly to search for the entrypoint method.
# Setting type: String
# Default value: GameObject
Type = GameObject

"GameObject" replaced the previous "Application".

I usually don't just overwrite configs because of possible changes I made - in this case I had modified some logging stuff.

So it works now but it was wired/odd seeing all mods being loaded only to be unloaded immediately afterwards without any real error messages.

[NimrodClover]

I just started getting this error crash today after over 1300 hours of play time. I started playing just after Mistlands was launched.

I've done nearly everything this and other threads have talked about as there are several. I'm about to give up and delete the whole not-launching game. I've never had to play around with the game files so I don't even know if I've backed up the correct files for my world/player data. Is there a guide to this ? Haven't found one yet.

No mods either, so I even tried loading BepInEx and added some plain mods, like "better ladder" and such to see if that fixed it as others have said it helped them.
From what I've read, it is not mods, as several non-mod users are crashing with the same error and when I added the most recent BepInEx as outlined above the game loading seemed to work smoother yet still crashed at the same point. It did it regardless for me with or without mods.

I'm going to just dump everything and reload vanilla and what I think is my game data and if I lose 1300+ hours worth of play, well that is just too bad - will probably never play it again.

***Addendum***
I deleted everything off the machine, then copied my previous saved content back in (this had the testing mods I mentioned above) then deleted just the mod components so the file "looked" like an un-mod version and ran that Frankenstein of an install. The first time I got the same fail. I was about to give up totally when I decided to reboot my machine. This gave me an error that Steam was keeping my machine from closing. After I forced that and relaunched Valheim and it all worked in vanilla format with the most recent version. Plus I still had all my progress and builds. Also, I've been playing over 1,400 hours.

[Melian]

I have the same problem. No mods. Uninstalled and reinstalled, didn't help.

Edit: works after rolling back the patch. Right click the game in Steam, go to properties, then betas, and set it to default_old.

Edit: And now it updated and crashes on startup again.