Unable to open studio due to an issue associated with team create

Bug Reports Studio Bugs
,
#1

image

A few days ago whilst working in studio, it just broke. It happened without warning or any settings being adjusted, and nobody on the team have been able to open it since.

It has something to do with team create. It happened to a previous file, and we discovered through trial and error that it was caused by that being turned on somehow. The broken files can be opened if its a downloaded version, but not if its uploaded with team create on. We’d turn team create off, but you can’t do that without opening the file, which we can’t, cuz were locked out.

ID of the place is: 17513118821

Expected behavior

I expect to be able to open the place file.

A private message is associated with this bug report

5 Likes
#3

Hello @YourFriendZeal thanks for the report. Is this still happening? Could you send over a copy of the studio logs from a recent failed attempt to open? This will contain info which can help me debug the issue for your place.

To find your Roblox Studio log files, you can follow these instructions based on the operating system you are using:

For Windows:

  1. Open the Run dialog by pressing the WINDOWS KEY and R at the same time.
  2. Type %LOCALAPPDATA%\Roblox\logs and press Enter.
  3. The log files will be displayed. They typically have the format <version>_<timestamp>_Studio_XXXXX.log.

For Mac:

  1. Open Finder, then select the Go menu.
  2. Click on Go to Folder.
  3. Type ~/Library/Logs/Roblox and press Enter. This will open the directory containing your Studio logs.

If Roblox Studio has crashed, the .dmp files can be found in a specific subdirectory:

  1. For Windows, they are moved to the logs\archive folder.
  2. For Mac, you can find the .dmp file directly in the tmp directory. Open Terminal and run open $TMPDIR, then look for the .dmp file.

These steps should help you locate your Roblox Studio log files for troubleshooting.

1 Like
#4

Hey hope you’re doing well, following up on this. It’s been a few weeks and without logs we aren’t able to investigate further. I will close this report out, if you are still seeing this issue please make another post on the Dev Forum, and then we will have fresh logs and telemetry on our side to be able to help you out. Thanks!