pink build
blue build
To preface this, we are using Unity 2019.3.0f6 and URP 7.2.1.
About 1/3 of the time we load a scene of our game (in build only) it is tinted pink with an orange strip at the top (pictured in “pink build”) or blue with a green strip at the top (pictured in “blue build”), until you enter the next scene. The other 2/3 of the time the screen is fine.
After looking through the shader compilation in the log, it appears that all of them are loading (nothing in the output changes between when pink/blue build happens and when it doesn’t). We then tried turning on and off different components on the camera just to isolate what might be causing the problem, (as the tint effect only happens below the Unity canvas so we thought it might be a problem with the camera/postprocessing).
We’ve narrowed the problem down to the Bloom Override on our Volume Profile on the Volume Component for Post Processing. Turning off the Bloom Override makes the problem go away in build, but we would like to keep the Bloom effect.
the volume component
We’ve tried printing all of the values under the Bloom Override to see if there is an anomaly when it does the pink/blue v.s. when it doesn’t, but there is no difference. Literally nothing is different in our logs when it works and doesn’t work. The only thing we know for sure is that turning off the Bloom fixes the problem. If anybody has run into this, this is a desperate call for help, because we have absolutely no idea where to go from here.
graphics settings screenshot 1
graphics settings screenshot 2
This is probably, a rather individual problem. Since people with a similar problem have not yet answered, I will advise a general and simple solution. Create a new project, where there will be new settings URP, and already add a bloom effect in it. If everything works well and bloom works, then transfer these settings to your project (preferably create a backup, just in case).
If that doesn't help, then as an option, try changing other settings that appear before 2/3 of the game works well. Maybe it's some individual effects, that create a problem. Or according to my assumptions, in a vignette. It can also be in a sprite, that is drawn on top of the bloom (It is advisable to do all this, in a separate backup, so as not to accidentally break the project). Also, the problem may be in the camera, if the URP settings, sprites, etc. work well, and the bloom effect should not fail.
As a last resort, if this also does not work, then try to send a complaint to Unity support. There is a possibility, that this may be a mistake in the bloom effect itself.
Although I will assume that bloom removes the problem. But the error is in something else, and is displayed at the moment when the bloom effect is turned on. But since the URP is quite new, I do not exclude that this is a mistake of the bloom effect itself.
I had a similar problem in the past, it fixed by changing LUT size to (16 or 32 or 64...), in urp asset settings/ post-processing.
Related
I've been working on a fairly large project in Unity. Until recently, we weren't using universal render pipeline (URP) and made that change. When we did, all the bloom effect we already had in place to create a neon glow look for our game disappeared, and everything looks opaque. All the tutorials I found say that it's fairly simple to add this effect, but I can't make it work. I'm starting to get suspicious of the Cinemachine in the main camera, since it's brought us problems in the past. I'll just state some of the things I've tried:
The post processing checkbox is ticked in the camera view.
My materials have emission turned on with colors that used to work before URP.
The camera has the volume component, with an override of bloom and the values of intensity and threshold super high.
I've also dropped a global Volume in the scene with a volume component with bloom effect (one solution suggested I do that)
I think that's everything. Please let me know of any suggestions!
I copied a project over from a different PC which had multiple scenes that needed to be baked.
The problem is in this one scene there are several different objects that textures seen to be stuck on black, even though I've changed the color of them. Some materials that where imported also seemed to be grayed out and I couldn't make any changes to them.
I'm not sure whether this is a baking issue or something to do with the material. I have tried to put the object on a different layer and used a real-time light and it does make it lighter but still nowhere near the color i set it too.
There are some textures/ Objects that are used in different scenes that seem to work fine but in this scene they don't...
None of the settings have been changed and it is the same version of unity on both PC's.
The issue:
What it is supposed to look like (from previous version):
When trying to optimize my game the biggest problem seems to be the device.present. Been going through some forums and i couldnt really find any useful answers. What is usually the main problem associated with this?
There are just many things that could cause this but the main reason is because the Thread is blocked by the graphics driver in a way to let the GPU catch up.
These are the specific reasons:
1.Image Effects
Check your camera. If you have Image Effects such as Flare Layer, Anti-aliasing and others, disable them.
2.UI Effects
Check all your Images, RawImages and Texts. If you have an Outline, Shadow or Position As UV1 component attached to the Images, RawImages and Texts, this could cause the problem. Usually when you have multiple of this attached to one
Image, RawImage and Text.
3.Bad Light Settings
Select your light and make sure that the Resolution under the Shadow Type is not set to Very High Resolution.
4.In the Quality Setting change the V Sync Count to Don't Sync.
5.Check for Sprites and Images with 0 alpha then disabled them
6.From the Player Settings, disable Auto Graphics API then change the Graphics API to OpenGLES2.
7.Custom Shaders
Are you using custom shaders (non standard shaders)? Disable it temporary. An expensive or bad written shaders could cause this problem.
Those are the usual problems. It is very possible that yours is a different problem. I suggest you enable/disable items one by one and you will likely find the problem.
If not, then consider creating new project and scene. Save out your old game as prefabs or assets then import them one by one into the new project. Don't import them at the-same time because the problem might appear again. Import then test then import again and test until you find the problem. If the problem is no longer there then it's likely an Editor Settings problem.
I'm currently testing how baked lightmaps work with models which I made in blender. After building lightmaps I noticed that they are really pixelated in some areas. Then I was trying to figure out which part of lightmap i causing this effect. It seems that it's Indirect Resolution, because when i turned it down as low as possible, pixelated parts completely disappear.
The problem is that form what I saw in other projects Indirect Resolution is much lower than Baked Resolution so I don't know why in my project it looks like this. I also tried to crank up Indirect Resolution but results weren't satisfying.
These lightmaps might seem fine to you but you can clearly see darker areas that look like "splash" and doesn't match resolution of the rest.
There are screenshots of how lighting works with two different setups:
This is setup that i used for lightmap in first screenshot:
First screenshot:
This is example of low res part in screen above:
Second screenshot (the only change is Indirect Resolution changed to 20):
Try adjusting the lighting-map settings of the object in the Lighting Window, especially the Advanced Paramters.
I have finished my game in Unity already.
But whenever I'm trying to build the game, it stops at the point as shown below. Does anyone know the reason why it happens? It always stops at the same point....
It's a problem with baking the lightmaps on your scene.
Unity doesn't like huge objects when it comes to baking lightmaps on them and it can certainly kill the light transport on a build.
You can try to open the Window menu from the main Unity menubar and search for the "Continues baking" checkbox under Lightning and uncheck it.
Or you can just split your bigger objects on your scene which may cause this problem.
Here's a thread detailing the issue a bit.
I've also seen people working around this problem by disabling Global Illumination altogether so that may be a solution for you as well if you are using it and you are willing to give up on that feature.
Edit: Another thread about this sort of thing with a decent solution - not sure why I didn't remember it for first but it's a good idea before trying to split your huge objects to mess with their "Scale In Lightmap" property as well to reduce the lightmaps' size.
You can also try the "Advanced Parameter" options.