# Viewer causes renderingGroupId to become invalid

**URL:** <https://forum.babylonjs.com/t/viewer-causes-renderinggroupid-to-become-invalid/35360>\
**Category:** Bugs\
**Created:** [November 3, 2022, 3:40am UTC](https://forum.babylonjs.com/t/viewer-causes-renderinggroupid-to-become-invalid/35360 "2022-11-03T03:40:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![xiehangyun](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/xiehangyun/32/30777_2.png) [@xiehangyun](https://forum.babylonjs.com/u/xiehangyun)\
**Post date:** [November 3, 2022, 3:41am UTC](https://forum.babylonjs.com/t/viewer-causes-renderinggroupid-to-become-invalid/35360/2 "2022-11-03T03:41:20Z")

</div>

Just the new DefaultViewer will cause renderingGroupId to fail in another otherwise normal scene. I suspect that the new DefaultViewer may have changed a constant to cause the problem. npm install and npm dev can be downloaded to reproduce the sample code.

---

_[View the full topic](https://forum.babylonjs.com/t/viewer-causes-renderinggroupid-to-become-invalid/35360)._