Announcement

Collapse
No announcement yet.

Stop hardcoding a kill-switch for Bloom & Split-Screen

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stop hardcoding a kill-switch for Bloom & Split-Screen

    Tim Hobson

    Hi Tim, Do you remember this AH post?

    Please return control back to developers, so we can toggle critical Split-Screen options.
    Why make us build from source, just to fix a single hardcoded kill switch for split-screen.
    The existing problem doesn't even affect every project / dev, so why not let us decide???


    1. Bloom
    2. MotionBlur
    3. TemporalAA


    For sure, disable these by default as before. But add a new option to re-enable them:

    As A: an Experimental Option Or B: Just make all three an INI setting like LPV etc.


    Click image for larger version  Name:	NoBloom.jpg Views:	1 Size:	580.4 KB ID:	1420482

  • replied
    im really confused, according to the github comments they already solved this in another branch of theres which has yet to be merged into the master branch, but is it going to happen for any future public release?

    Leave a comment:


  • replied
    Imagine-Games Spoondog jojo8026 Syed Fabulous_hotdog Mosel3y TheVFXGuy marevalo Ketan keyle RyanHughes Diego_Visualma
    Originally posted by Imagine-Games View Post
    the answerhub page with like 5000 votes (okay it was like 55 votes) seems to be missing, what gives?
    UPDATE:

    Ok so... Epic hid ISSUE-57785 recently because its classified as a 'Feature Request' not a Bug apparently. Under Epic's new policy the Community can't vote on feature requests anymore just bugs! ... Who knew! ... Anyway its still 'live' in the system and marked as To-Do afaik. But is that a fix to the split-screen / post-process renderer, or just killing the Kill-Switch? Not 100% sure.... But Epic hinted that even a PR for the Kill-Switch, would go a long way to resolving this.

    So....long story short.... I reached out to a couple of active knowledgeable devs on the Community and as of today there's now a PR.

    A huge thanks needs to go out to Project.Gheist for the PR. Also a shout out to LowEntry who also looked into this. As regards testing out the PR itself... If someone can help with that it'd be great, as my 2 overheating Asus ROG rigs are toast. Summing up, the PR gives Epic something to consider rather than just having an open-request. Feel free to PM any contacts you have at Epic as well separately to offer encouragement, as posts here aren't read that much.
    Last edited by ClavosTech; 08-26-2018, 05:50 PM.

    Leave a comment:


  • replied
    the answerhub page with like 5000 votes (okay it was like 55 votes) seems to be missing, what gives?

    Leave a comment:


  • replied
    Jon X
    Kalvothe
    Originally posted by Jon X View Post
    I've put in a New Feature request - UE-57785. Please understand that this request may not be implemented or prioritized.
    Hi Jon, This now shows up as :

    UE-57785 Unknown Issue
    Can you say why its been hidden / deleted?

    Thanks!

    Leave a comment:


  • replied
    Originally posted by Spoondog View Post
    Must be one of the most voted, unimplemented features?
    Seems like an easy fix too. Any update Epic?

    Kalvothe Amanda.Bott Stephen Ellis

    Leave a comment:


  • replied
    Must be one of the most voted, unimplemented features?

    Leave a comment:


  • replied
    <Bump>

    Vote here

    Leave a comment:


  • replied
    Originally posted by franktech View Post
    hzn84 Dec1234 hiro12hiro

    <<Bump>> - Trying to get a few more votes for this.
    Get out ahead of the next Fortnite-Engine changes...
    You mean when they break more stuff in the engine lol

    Leave a comment:


  • replied
    hzn84 Dec1234 hiro12hiro

    <<Bump>> - Trying to get a few more votes for this.
    Get out ahead of the next Fortnite-Engine changes...

    Leave a comment:


  • replied
    Originally posted by RexVex86 View Post
    Just voted, thanks for the initiative!
    No worries, thanks for voting. Hopefully Epic will show this area some love soon ...

    Leave a comment:


  • replied
    Originally posted by franktech View Post
    Just voted, thanks for the initiative!

    Leave a comment:


  • replied
    dragonfly2 MrRabbit pr4wl Melisande Eduard Gotwig HenningAx Sushii Sushii eudrea


    Interested in an easy way to Enable Bloom & Split-screen? - Please Upvote this...

    Leave a comment:


  • replied
    Originally posted by Fabulous_hotdog View Post
    I had a tutorial on how to enable bloom in split screen: https://www.youtube.com/watch?v=llg_7JpI1Uo&t=228s

    Hopefully this clears things up on how to do it!
    I think the point here is not to download source code from github and compile just to enable bloom etc in split screen. Just make it an option (somewhere in ini file), not in the code.

    Leave a comment:


  • replied
    I had a tutorial on how to enable bloom in split screen: https://www.youtube.com/watch?v=llg_7JpI1Uo&t=228s

    Hopefully this clears things up on how to do it!

    Leave a comment:

Working...
X