I get this error after upgrade, only in play mode
Set the splat textures to Read/Write enabled in their import settings.
No idea if this is intentional or a bug, but that’ll get you running again.
1 Like
Maybe but this terrain is two years old in the project. Why do I get it now?
Dunno, like I say it might be intentional or might be a bug - just offering a here-now workaround so you’re not stuck staring at the screen like I was tempted to do myself this morning 
The good news is, tab-and-type works again! 
I dont like fixing things that did not need fixing before Unity update. I want to know why the f__ed things up. Before I unf__k them. 
Let me check change log, brb
FYI I hit this the other day in 2017.1.2. Wasn’t upgrading, wasn’t doing anything I can think of that would trigger it. Hadn’t touched the terrain in weeks. Obviously something triggered it, but it doesn’t appear to be 2017.2 specific.
Only thing terrain related in the patch notes
- (951780) - Terrain: Fixed crash when loading a non read/write enabled texture from an asset bundle. Texture will not be shown unless it is marked as read/write.
The way they fix this buy is to force you to mark all textures used by terrains read/write.
1 Like
This should have been marked as a breaking change or something, oh well
Hi, we are looking in to removing the editor warning. However what hasn’t been well documented is that Unity has always marked terrain as readable at build time regardless of how it was set in the importer. Obviously this is also less than ideal and we are looking at how to improve the whole workflow but this is was a bad attempt to make it more clear what was happening.
Thanks for the feedback Jack. As a professionell dev I can tell you messages like this are very alarming. I can understand if a none professionell dev just mark it as enabled and then move on with their life. But thats not the case if you like me have a business to run, every decision we make has to be well thought over. When you slap a exception like this (not even a warning but a exception) it stops all development until resolved.
Thanks again for your help.
Yes fully understood. To give the backstory, the change was supposed to catch occurrences where textures that were destined for terrain, but not read/write, and not processed by Unity build process(e.g. procedural, asset bundle) were causing run-time crashes - in editor playmode and players. We were just a bit over-eager in where that got messaged. Unless you need something else urgently in the current patch I would recommend rolling back to the previous one and hopefully we will have a better fix in the next patch or two.
1 Like
I need this patch sadly But thanks for the heads up, good to hear it will be better for next patch