Most recent update has completely broken my room, ^AwakenFields

Bug Reports Rooms 2
, , ,
1

What device/platform are you having the problem on?

PC

Were you alone or with other players?

Alone

How often does the issue occur?

Every time I load into the subroom

Room Name

^AwakenFields

Subroom Name

DevRoom

Description

As of the most recent update, something has happened in the back end of the rec room, ultimately causing my room, ^AwakenFields, never to load, wholly stuck on 100% forever before sending you back to the dorm room because it failed to load after about 2 minutes. I verified that this wasn’t an issue on my end, as this worked before the update was released, and I haven’t touched it till today.

Here is my log file, Player.log - Google Drive
Please fix this so I can go back to working on AwakenFields

3 Likes
2

A similar issue has happened to me before, the way I fixed it is by reloading the last save through rec.net, I recommend trying that. And if u want to prevent something like this from happening again try cloning ur main Subroom and making another subroom inside that room so in case one breaks the other one still works. Hope this helps!

3

This is private, if you could go into this and into share, set it to everyone with the link as visitor, that would be nice

1 Like
4

I have already done that; I’ve gone back to several saves and even on another couple weeks old version of the subroom with the same code; it broke that room too

I have also tried making a blank subroom in studio, copying and pasting all of the stuff to that new subroom, and then trying to play.

Currently my main workaround is to use studio to build my rooms, I wont be able to do everything but it is a start.

5

Thanks for telling me, didn’t see that it was restricted.

6

Perhaps this loading issue for you is related to this? R2 Call Function and Data Table Bug

If you create a zendesk ticket, they may be able to resolve it for you so you don’t have to wait for another update to ship.

1 Like
7

I read that, and it is helpful; however, this doesn’t help the fact that most prior saves, even ones made a couple of weeks ago that have not been touched, are currently affected. Thus, simply rolling back could cause me to lose months of work, which I am not ready to do.

I would rather wait for the fix and, in the meantime, complete some other projects. I’ll do that; if it doesn’t get fixed in a ship cycle or two, I’ll contact Zendesk. Thanks though.

1 Like
8

These kind of bugs are the worst and need to be fully prioritized if they want to keep up faith in Rooms 2.

It’s late in the work week so you’ll probably not get a response until next week, but I hope when they see it, they start digging into this as soon as possible.

My suggestion as well is to submit a ticket on Zendesk using the “Rooms 2 Bug Report” category and link back to this forum thread in your ticket. Let them know you’d like for someone to reply here and dig into this.

2 Likes
9

Thanks to the developers’ help, we figured out a solution. While we couldn’t magically fix the entire room, we figured out we could use Rec Room Studio to delete all the data table “read cell” chips and upload a build without them to eliminate data table corruption issues.

That does come at the cost of manually adding back all of the data table’s “read cell” chips, but it is better than redoing months’ worth of work by reverting to a previous save.

3 Likes
10

I knew they’d help out. It is in their best interest to keep up faith in Rooms 2 and diagnose issues like this.

W devs, and glad to hear you got a solution.

1 Like
11

Glad you got it fixed!

12

The underlying issue here ‘changing a data table with data table chips already in the room breaks the circuits in the room’ is fixed internally and should ship to everyone in our first Nov update if everything stays on track in the ship pipeline. marked this issue as ‘resolved’ for now and if we see it come back after that fix ships we’ll revisit this thread

3 Likes