Closed GoogleCodeExporter closed 8 years ago
Original comment by scrawl...@gmail.com
on 22 Mar 2011 at 12:31
The problem is there doesn't seem to be a way to render mygui after the
compositor (correct me if i'm wrong). It has a quite funny effect, it makes the
GUI partly transparent with a blurred version of the render behind it. Looks
cool :)
Original comment by scrawl...@gmail.com
on 22 Mar 2011 at 5:21
Original comment by scrawl...@gmail.com
on 22 Mar 2011 at 5:22
effect on ui:
Original comment by scrawl...@gmail.com
on 22 Mar 2011 at 5:27
Solution could be to remove the compositor when GUI is opened, and show it
again when GUI is closed. (setCompositorActive)
Original comment by scrawl...@gmail.com
on 23 Mar 2011 at 10:25
Another solution: render mygui to a seperate, transparent viewport that is on
top of the normal viewport.
Btw, if the compositor is already in, one could add Motion Blur too.
Original comment by scrawl...@gmail.com
on 23 Mar 2011 at 3:33
Using Dark Sylinc's Bloom implementation, the gui issue seems to have gone.
Original comment by scrawl...@gmail.com
on 23 Mar 2011 at 4:29
Original comment by scrawl...@gmail.com
on 23 Mar 2011 at 5:11
Compositors can now be enabled via config file. GUI exists too, but it doesn't
do anything atm.
What's still missing now:
- Motion blur implementation that 1. actually works and 2. only blurs moving
objects.
- When using the compositors, some overlays like dot on the minimap and gauge
needles are gone.
Original comment by scrawl...@gmail.com
on 23 Mar 2011 at 9:43
overlay needles and player pos dot issue is gone. It was incorrect to use a
different render queue group for them. Instead, this has to be done with z
orders.
Original comment by scrawl...@gmail.com
on 24 Mar 2011 at 9:48
I'm setting this to solved for now, as this issue was only about bloom / hdr.
Motion blur will be addressed after 1.1 release, then this issue can either be
re-opened or we create a new.
Original comment by scrawl...@gmail.com
on 25 Mar 2011 at 10:02
Original comment by tapiovie...@gmail.com
on 27 Mar 2011 at 4:17
Original issue reported on code.google.com by
scrawl...@gmail.com
on 22 Mar 2011 at 12:31