Search Unity

  1. Calling all beginners! Join the FPS Beginners Mods Challenge until December 13.
    Dismiss Notice
  2. It's Cyber Week at the Asset Store!
    Dismiss Notice

Post Processing works in Editor, but not in build

Discussion in 'Image Effects' started by dgoyette, Jun 7, 2018.

  1. dgoyette

    dgoyette

    Joined:
    Jul 1, 2016
    Posts:
    2,089
    I noticed that the Bloom effect (Post-processing Stack v2) is not working when I create a build of my game. Is there some list of Shaders I need to include in the Graphics settings? I'm already including the Bloom shader, so I'm not sure what else I might need to include. Or is there perhaps some other reason why post processing might not work in a build?
     
  2. dgoyette

    dgoyette

    Joined:
    Jul 1, 2016
    Posts:
    2,089
    It seems that after I do a build, all post-processing effects stop working even in the editor until I switch to a difference scene...
     
  3. arybak89

    arybak89

    Joined:
    Nov 27, 2017
    Posts:
    9
    Having the same issue here. Properties from the PPS are not showing up in the build. I get vary different results from the editor view to the build. Any luck figuring this out?
     
  4. dgoyette

    dgoyette

    Joined:
    Jul 1, 2016
    Posts:
    2,089
    I didn't really figure it out, except to assume that it was related to the PPS2 version I'd been using from the github project. I ended up upgrading to Unity 2018.1 (for other reasons), and found that this isn't occurring anymore now that I'm using the Packages version of PostProcessingStack.
     
  5. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,088
    I'm on 2018.2.2 and deferred fog only works in the editor =[
     
  6. Zoryth

    Zoryth

    Joined:
    Dec 5, 2016
    Posts:
    35
    same thing happening, in 2018.2.5 :(

    EDIT.- actually in my other project it works fine xd
     
    Last edited: Sep 9, 2018
  7. timothy92

    timothy92

    Joined:
    Mar 7, 2016
    Posts:
    11
    Make sure you don't have 2 cameras in the scene, that's a common cause of this problem.
     
  8. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,088
    My game is entirely built dependent on two cameras, using techniques similar to kerbal space program. Sometimes I have more for render textures. It works fine in the editor with three active cameras. Doesn't work in build.

    Do you know more about this "cause"?

    Really the whole reason for using it is because of two cameras... If there weren't two cameras I could use any fog asset just fine. Without the "exclude skybox" option the second camera gets wiped out.
     
  9. Zoryth

    Zoryth

    Joined:
    Dec 5, 2016
    Posts:
    35
    oh, in my project that doesnt work I have 2 cameras indeed
     
  10. Tonieh085

    Tonieh085

    Joined:
    Nov 25, 2016
    Posts:
    14
    Same problem with 2018.2.14
    I have only one camera :(
     
  11. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,088
    I posted it as an issue in the Git in August, still no reply there either =[
     
  12. Lune

    Lune

    Joined:
    Oct 20, 2012
    Posts:
    62
    In my case what solved this issue was:

    delete the camera you had before updating and create a new one, re add the post processing component and it works fine again.
     
  13. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,088
    I will try that. If that solves it you deserve a cookie.
     
  14. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,088
    I still can't get it to work =[
    Worse yet, it does work in a fresh project.
    So there is something, somewhere, somehow that is making it not work in builds for me =[
     
  15. Phoenix116

    Phoenix116

    Joined:
    Jun 30, 2016
    Posts:
    39
    Are you using the post processing from packages? Seems it works much better
     
  16. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,088
    I tried several times to get that package manager to install it, but the asmdef file would always interrupt it and I was never able to. After updating to the latest git zip and after finding that Enviro was interrupting the fog on my two camera setup I was finally able to fix it. !
     
  17. Cloud-Ninja

    Cloud-Ninja

    Joined:
    May 5, 2015
    Posts:
    30
    @malkere - could you please detail the steps that allowed you to get the bloom effect to be the same from the editor to build? I'm experiencing the same issue. Appreciation in advance :0).
     
  18. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,088
    I never had any problems with bloom personally, only deferred fog. I recreated the camera that uses the effects twice, and I updated the package to the latest on the git repository, not using the package manager.
     
  19. CW_Studios

    CW_Studios

    Joined:
    Jun 7, 2018
    Posts:
    1
    Bro I'm having the same problem with the version from the package manager
     
    MaxPirat likes this.
  20. chaseholton

    chaseholton

    Joined:
    Dec 17, 2012
    Posts:
    55
    Currently on 2019.1.1 and it does the same thing for me. I’m using SleekRenderer for light Post Processing for mobile and that works fine on mobile builds. I have a condition that switches based on platform to enable the PPS on anything that isn’t mobile and it used to work, but now it’s not. Nothing has changed code or project wise aside from updating Unity to 2019.1.1.
     
    thisaraunity likes this.
  21. LilGames

    LilGames

    Joined:
    Mar 30, 2015
    Posts:
    208
    Unity 2018.3.8f1 here.
    PPSv2 2.1.6
    Works perfectly in Editor, does not work in builds. Tested Windows standalone exe on a Windows 10, GTX 1060 6gb and WebGL
     
  22. GoGoGadget

    GoGoGadget

    Joined:
    Sep 23, 2013
    Posts:
    666
    Very weird dependencies that seem to break easily in PPv2. A reimport fixed for me in build, then I have had to migrate my own PostFX stack to hold all of its shaders in a "Resources" folder, as anywhere else (for whatever reason) the shaders weren't getting found through non-static FindShader calls.
     
  23. cecarlsen

    cecarlsen

    Joined:
    Jun 30, 2006
    Posts:
    528
    I have the same issue in 2019.1.3.f1 and also 2019.2.0b4. No Deffered Fog in builds. PostProcessing 2.1.6. Windows. Deferred Rendering.

    My player log burbs out this:

    Code (CSharp):
    1. WARNING: Shader Unsupported: 'Hidden/PostProcessing/Uber' - Pass '' has no vertex shader
    2. WARNING: Shader Unsupported: 'Hidden/PostProcessing/Uber' - Pass '' has no vertex shader
    3. WARNING: Shader Unsupported: 'Hidden/PostProcessing/FinalPass' - Pass '' has no vertex shader
    4. WARNING: Shader Unsupported: 'Hidden/PostProcessing/FinalPass' - Pass '' has no vertex shader
    I also tried to ditch the Package Manager and import the newest version directly from Github, but same issue occurs.
     
    Last edited: May 31, 2019
  24. Glader

    Glader

    Joined:
    Aug 19, 2013
    Posts:
    402
    Just encountered this on 2018.4.1f1. I use two cameras, and have used two cameras in this particular scene, for years. Don't know why it's happening all of a sudden recently.
     
  25. ScriptsEngineer

    ScriptsEngineer

    Joined:
    Jun 8, 2018
    Posts:
    2