# Multi-Room Simulator Local Forwarder issue

**URL:** <https://community.coherence.io/t/multi-room-simulator-local-forwarder-issue/525>\
**Category:** Bug reports\
**Created:** [May 20, 2024, 6:09pm UTC](https://community.coherence.io/t/multi-room-simulator-local-forwarder-issue/525 "2024-05-20T18:09:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\
**Post date:** [May 20, 2024, 6:09pm UTC](https://community.coherence.io/t/multi-room-simulator-local-forwarder-issue/525/1 "2024-05-20T18:09:54Z")

</div>

## Description, details and error message(s)

When Multi-Room Simulator Local Forwarder component is enabled in cloud environment, it is now creating a connection. This means when creating and joining a room as client, 2 simulator objects get created. This did not happen before.

## Expected behaviour

I was able to resolve this by disabling this component when uploading to the cloud, but ideally this should not have to be done. This component should not try to create a connection in the cloud environment.

This was already how it functioned before, so I’m not sure what changed.

I will be very sad every time I spend 5-10 minutes to upload a cloud build for testing, only to find I forgot to disable this component, so I’m going to have to disable and reupload again 😭

## How to reproduce

1. Add all components for MRS scene
2. Upload build to cloud, create and join room

There will be 2 simulators in the DontDestroyOnLoad scene

## Environment

SDK: 1.2.1  
Unity: 2022.3.4f1  
OS/Platform: Win10

---

<div class="post-metadata">

**Author:** ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)\
**Post date:** [May 21, 2024, 10:54am UTC](https://community.coherence.io/t/multi-room-simulator-local-forwarder-issue/525/2 "2024-05-21T10:54:26Z")

</div>

We talked on Discord, but for posterity: we’ve raised this issue internally and are investigating.

---

<div class="post-metadata">

**Author:** ![frarees](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/frarees/32/461_2.png) [@frarees](https://community.coherence.io/u/frarees)\
**Post date:** [June 6, 2024, 8:25am UTC](https://community.coherence.io/t/multi-room-simulator-local-forwarder-issue/525/3 "2024-06-06T08:25:50Z")

</div>

Fix for this coming on 1.2.3, which I estimate will come out in 2 weeks time.

---

<div class="post-metadata">

**Author:** ![frarees](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/frarees/32/461_2.png) [@frarees](https://community.coherence.io/u/frarees)\
**Post date:** [July 1, 2024, 9:03am UTC](https://community.coherence.io/t/multi-room-simulator-local-forwarder-issue/525/4 "2024-07-01T09:03:28Z")

</div>

v1.2.3 update is available.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/b3aa79eb9519fac7aad7eba18f15a1e8ce60f6e2.png) [@system](https://community.coherence.io/u/system)\
**Post date:** [July 1, 2025, 9:03am UTC](https://community.coherence.io/t/multi-room-simulator-local-forwarder-issue/525/5 "2025-07-01T09:03:50Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.