# Issues using effect composer on safari mac (threes r120)

**URL:** <https://discourse.threejs.org/t/issues-using-effect-composer-on-safari-mac-threes-r120/21362>\
**Category:** Questions\
**Tags:** post-processing\
**Created:** [December 8, 2020, 5:56pm UTC](https://discourse.threejs.org/t/issues-using-effect-composer-on-safari-mac-threes-r120/21362 "2020-12-08T17:56:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertoranon](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/robertoranon/32/11836_2.png) [@robertoranon](https://discourse.threejs.org/u/robertoranon)\
**Post date:** [December 8, 2020, 5:56pm UTC](https://discourse.threejs.org/t/issues-using-effect-composer-on-safari-mac-threes-r120/21362/1 "2020-12-08T17:56:00Z")

</div>

Hi,

I found a strange issue using the EffectComposer with Safari on Mac. If I just use a RenderPass, everything is fine - however, if I add any pass (say, a ShaderPass with a luminance shader), then, depending on the near plane of the camera, some objects appear/disappear as the camera gets closer/farther to them.

E.g., camera near set at 0.1, objects at distance around 300 from the camera, objects appear/disappear as the camera moves.

If I set the camera near to 1, then the problem disappears.

Everything renders fine on Chrome or Firefox on the same machine.

I could publish some example, but what has the camera near to do with the passes I am using?

Thanks for any help!

---

<div class="post-metadata">

**Author:** ![Mugen87](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/mugen87/32/5645_2.png) [@Mugen87](https://discourse.threejs.org/u/Mugen87)\
**Post date:** [December 9, 2020, 10:48am UTC](https://discourse.threejs.org/t/issues-using-effect-composer-on-safari-mac-threes-r120/21362/2 "2020-12-09T10:48:23Z")

</div>

> [@robertoranon](#):
>
> I could publish some example, but what has the camera near to do with the passes I am using?

When using a simple shader pass (e.g. with `LuminosityShader`) then nothing. A live example would be helpful to investigate the issue.