Terrain Rendering Bug in 5

Ported my project over to 5 and it works great. I made a build though and I get this disturbing effect:



Objects behind the terrain are highlighted and look like a shadow.



No matter what shader or rendering mode I use I still get this. Any help would be appreciated.

Thanks

 

Just to make sure, even if you switch that wood dock shader to the new Standard shader and use deferred rendering you still get this problem?

And you say this only has this issue when you make a build? It looks correct in the Editor?

 

The dock is using the Standard Shader and I made a build with all rendering modes. Also yes it only does this in builds. Looks fine in editor.

 

Alright. Might take a while if at all possible with my internet. There are a few other problems going on like terrain does not pickup point light shadows(oh they are nice to have for free) and the standard shader not being affected by fog. Not sure if they are related.

Will get a report out as soon as possible. Thanks

 

Thanks for the help. Was not aware the other problems were known. The fog problem does only show up in Deferred mode.

This terrain bug is gone. The only thing that has changed since yesterday was removing an old LOD script and restarting my computer. Do not know why but it is gone. If it comes back i will submit a report. Sorry for taking time. Thanks again for your help.

 

How have these easy to spot bugs passed all the beta testing, i mean within the first test i made of unity 5 it was obvious that the terrain recieved no point and spotlight shadows, this must have been under testing for a long time and this was not spotted?

 

It was GDC time so Unity 5 had to be released, even in its half-ready state.

 

There are still some problems but I think it was smart of them to release it with small problems than another month or two later. Than there would have been a lot of complaining.

Unity 5 is definitely past a half-ready state. It is pretty darn fine. I am loving it.

The only problem I am having is that I can not use Deferred. I have to use legacy deferred, which works fine. This is because of the fog problems. No fog with the standard shader and no height fog with the tree billboards. So you cannot use Deferred if you are working on a terrain. Like I said though the legacy deferred is working fine for me. Maybe the new terrain system can fix the many tree billboard problems(that drive me mad) whenever it comes out. Than I can try the new Deferred.

 

'Unity 5 is definitely past a half-ready state. It is pretty darn fine. I am loving it.'

I found 3 errors just this afternoon. Is there any list for known bugs?

 

Th only thing I could find is this: http://issuetracker.unity3d.com/

I have not checked but the release notes will show any known bugs in that release.

Okay guys this is not another lets complain about Unity thread. I get all these amazing features and the editor does not crash every time I make a change (unlike a couple other engines) so to me this is an amazing thing that we should be thankful for. Unity will update(5.0.0 is not the last version) and they will fix these problems.

Now this thread is for terrain problems in 5. I want this thread to stay open in case this problem comes back or another one comes up. So keep it on track. Thanks

 

Thanks.

'Okay guys this is not another lets complain about Unity thread.'
I see you, although reporting bugs is a kind of complain

'...and the editor does not crash every time I make a change (unlike a couple other engines) so to me this is an amazing thing that we should be thankful for'

That should be the base for any app: not crashing. On the other way it is a really f...p world where we should be grateful for stability. Like if we should be grateful that the wheels of our cars don't fall while we drive it. It is not Unity-specific, so I think you know what I mean.

 

I am not complaining when I report a bug I am asking for help. Programs benefit from people reporting issues. Complaining is saying and engine is half finished without stating the broken half and asking for help with it.

Maybe it is just my computer but Unity is the only engine that does not crash 50% of the time I make a change. Unity only crashed on me when I used a bad script. Make a material or save the project in another unnamed engine and it crashes a quarter of the time.

 

'Complaining is saying and engine is half finished without stating the broken half and asking for help with it.'

Forward rendering works, deferred don't (as 'legacy' stuff is not really an option in 2014, it is half of the rendering methods. But please do not take it so serious and sure, you are right, I'm still quite disappointed.

'Maybe it is just my computer but Unity is the only engine that does not crash 50% of the time I make a change.'

I think that should be your computer; there are some very unstable engines (like Fibix for example), but I never had crashes in Unreal 4 or CryEngine more than in Unity. They are both pretty stable engines to me.

Anyway, I hope quick fixes will come soon.

 

There are some issues and I am sure Unity will fix them soon. The only problem I have had so far with deferred is the fog issue. Legacy deferred works good for me though.

My computer is getting old. So that probably is the issue.

Hopefully I will not have this terrain bug again but if I do I will post a bug report and get back to this thread.