Project

General

Profile

Emulator Issues #5805

[Feature Request] Stackable Post-processing shaders

Added by Sonicadvance1 about 6 years ago. Updated 8 months ago.

Status:
Work started
Priority:
Normal
Assignee:
Stenzek
% Done:

0%

Operating system:
N/A
Issue type:
Feature request
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Proposing the ability to stack multiple post-processing shaders on top of each other and also allowing each shader to have multiple inputs in to it.

Related issues

Blocks Emulator - Emulator Issues #5804: Graphic Addition SuggestionDuplicate

History

#3 Updated by degasus about 6 years ago

and link them all together :-)

i hope you won't make a draw-call per shader? Should be flexible and fast enougth

#4 Updated by Sonicadvance1 about 6 years ago

Yea, I'm not silly enough to make it do a draw-call for each shader.

#5 Updated by Sonicadvance1 about 6 years ago

  • Milestone changed from Next to 4.0

#6 Updated by delroth over 5 years ago

  • Milestone changed from 4.0 to Current

Status of this for 4.0?

#7 Updated by NeoBrainX over 5 years ago

Unlikely to happen, given the non-trivial question of how to properly implement this without making stuff be ridiculously slow.
Also, creating a proper GUI around this shouldn't be regarded as trivial, either.

#8 Updated by Sonicadvance1 over 5 years ago

Sadly enough, I figured I would get this done back when I was still working at my old job. My new job doesn't allow me enough time to work on the JIT core and complete this feature for 4.0

#9 Updated by delroth over 5 years ago

  • Milestone changed from Current to Next

Ok, marking this for next milestone then so we don't forget about it.

#11 Updated by delroth over 5 years ago

  • Milestone changed from Next to Current

4.0 was released, moving Milestone-Next to Milestone-Current.

#12 Updated by delroth over 4 years ago

  • Milestone changed from Current to Next

Moving to next milestone since these issues are not critical to a new release.

If you feel strongly about this issue and want it to block the next Dolphin release, please assign yourself as owner and re-add Milestone-Current.

#13 Updated by JosJuice over 2 years ago

  • Milestone changed from Next to Current

5.0 was released, moving Milestone-Next to Milestone-Current.

#14 Updated by JMC4789 over 1 year ago

  • Status changed from New to Work started
  • Assignee changed from Sonicadvance1 to Stenzek

Stenzek did indeed start something like this, I think it bitrot though.

#15 Updated by JMC4789 8 months ago

  • Milestone deleted (Current)

This is a non-essential feature that I don't think we can necessarily rush and shouldn't block a release if we do manage to get everything else fixed. Still would be really nice.

Also available in: Atom PDF