Studio: Version Rollback

[Yoggington]

Is there any way to rollback to a previous version of Stud.io?

I installed the latest update (via the patcher) a few days ago and am seeing a repetitive issue, wherein if you touch any programme on your desktop that is not Studio, then Studio gets caught and hangs forever until you force it quit. Maybe it recovers the files you were working on at time of next load, maybe it doesn't. Either way, it's extremely frustrating to load the same project 20 times per hour (and some work lost along the way), and my preferred approach would be to re-install the older version without the bug, and turn off the patching tool until the bug is resolved in some future version.

I run on Mac for the record.

So questions;

1) Where can I find a .dmg file for a version previous to 2.22.11(4)? (Alternately, does the program itself feature steps to rollback from within?)

2) Is it possible to turn off the patch tool and stop getting the updates?

3) Where would I file a bug report?

[aFrInaTi0n]

1. The Download Page of Studio (https://www.bricklink.com/v3/studio/download.page) can be scrolled downwards.. There you can get older Versions of Studio.

If they havent fixed the severe bugs of missing or not correctly shown parts on your machine with the 2.22.11(4) then go back to 2.22.10_1 (Select October 27) - this should be the last one before those bugs occured. (direct link to the .dmg: https://s3.amazonaws.com/blstudio/Studio2.0/Archive/2.22.10_1/Studio+2.0.pkg)

2. On Windows the starting dialog which asks if you like to update can be canceled with "no" and you can work with the installed (and outdated version). Don't know if it applies to the Mac Studio version too..

3. Go to Bricklink and navigate to their Forums for Studio (https://forum.bricklink.com/) and read through the (very long) list of already known / filed bugs (Bugs and Suggestions Index) and if you wouldn't find, feel free to create a new one (How to report a bug). Generally SylvainLS is the mod there and keeps track of user posts etc.

But for that specific bug: Because of its severity of affecting all users, this is already know to them, see Update today (Nov. 16 2022) broke Studio

Edited November 22, 2022 by aFrInaTi0n

[Yoggington]

3 hours ago, aFrInaTi0n said:

1. The Download Page of Studio (https://www.bricklink.com/v3/studio/download.page) can be scrolled downwards.. There you can get older Versions of Studio.

If they havent fixed the severe bugs of missing or not correctly shown parts on your machine with the 2.22.11(4) then go back to 2.22.10_1 (Select October 27) - this should be the last one before those bugs occured. (direct link to the .dmg: https://s3.amazonaws.com/blstudio/Studio2.0/Archive/2.22.10_1/Studio+2.0.pkg)

2. On Windows the starting dialog which asks if you like to update can be canceled with "no" and you can work with the installed (and outdated version). Don't know if it applies to the Mac Studio version too..

3. Go to Bricklink and navigate to their Forums for Studio (https://forum.bricklink.com/) and read through the (very long) list of already known / filed bugs (Bugs and Suggestions Index) and if you wouldn't find, feel free to create a new one (How to report a bug). Generally SylvainLS is the mod there and keeps track of user posts etc.

But for that specific bug: Because of its severity of affecting all users, this is already know to them, see Update today (Nov. 16 2022) broke Studio

Fantastic stuff pal, thanks.

I figured some of this out, but I'm not sure how I missed the earlier version downloads before.

I've gone back to 2.22.11(1) and it's running just fine once more. No issue in four hours of running.

[SylvainLS]

6 hours ago, Yoggington said:

I've gone back to 2.22.11(1) and it's running just fine once more. No issue in four hours of running.

aFrInaTiOn said it all (thanks!).  But beware of 2.22.11(1): Studio doesn’t start when you left it with the ‘Hide parts not available in the selected color’ box checked.  And it has a lot of problems with editing submodels.

[aFrInaTi0n]

Both welcome, glad I could help out :D

Generally: Better wait with updating studio for a week until you go - so you don't run into 1st-day issues which may need additional fixes.

Also before every switch of versions I would recommend to do a final Backup of the old and put it aside, just in case you accidentally save some changes to the .io file and corrupts it (I think the cases are rare, but for huge models with plenty of efforts put in already I personally would really do regular backups into new .io files). Another recommendation: Save the files with a date-prefix in their filename, this makes sorting easy, for e.g. "2022-11-23_my-awesome-MOC.io" (for sorting reasons I would go with YYYY-MM-DD instead of YYYY-DD-MM).