Andrew Schoen

Seems like there may be some issues with kiss3d (which would presumably have to have the same update) based on the tests.

@OTL given that this would require a corresponding fix in Kiss3d, how would you prefer we proceed?

As in without one or the other? Neither works in isolation. I did test a couple others, such as Vignette, and those do work as expected.

Just in case a [non] working example is useful, here is a code sandbox link: https://codesandbox.io/s/react-postprocessing-ssao-smaa-and-bloom-demo-forked-jvtvz After looking at it, I am not positive that standard `Bloom` is working either....

> Hey, disabling autoclear seems to work! > > ``` > > ``` > > There are probably side-effects to this workaround though. Hmm. What are the versions of the...

That is super strange. The only substantial difference I see between your example and mine is that you are using `.tsx` and my example is `.jsx`. Not sure if that...

@warrenseine I can replicate the clear behavior in an example with Spector.js. For another purpose, I had made a simplified example of what I was working on, and adding the...

@cptSwing The solution now is to use `` (see [here](https://github.com/pmndrs/react-postprocessing#selectionselect)). I have found this to work for me pretty well, as long as I kept `autoClear={false}` in the ``

Just to connect some threads, I ended up creating a ROS2-compatible version of `tf2_web_republisher` but am still having issues with both `ros2-web-bridge` and `rosbridge_server`, documented in [rosbridge_suite#552](https://github.com/RobotWebTools/rosbridge_suite/issues/552)

Hi, thanks for the response. I did that and got the following: ``` DEBUG=ros2-web-bridge* node bin/rosbridge.js ros2-web-bridge:index ROS2 node started +0ms ros2-web-bridge:index Starting server on port 9090 +1ms Websocket started...