Newer versions not opening a 2.82a project correctly #79936

Closed
opened 2020-08-20 03:50:45 +02:00 by Rogério Dec · 10 comments

System Information
Operating system: Windows 10 x64
Graphics card: Nvidia GTX 1060 6Gb

Blender Version
Broken: 2.83.2 to 2.83.5
Worked: 2.82.a

The same issue of https://developer.blender.org/T78960 actually was not solved until today. I made more questions on that ticket that was not answered.
I had some help at https:*blender.stackexchange.com/questions/191626/how-to-fix-my-project-to-be-correctly-opened-by-blender-versions-newer-than-2-82/. But file theoretically fixed there (https:*blend-exchange.giantcowfilms.com/b/BEZnnD9j/) also doesn't open correctly in newer versions.
I would just like to get rid of version 2.82a, but I can't, because these projects are only opened correctly in this version. At the same time, the Blender people don't give me a solution.

Exact steps for others to reproduce the error
Just follow the same described in https://developer.blender.org/T78960. But this time, if possible, showing the solution for this case.

**System Information** Operating system: Windows 10 x64 Graphics card: Nvidia GTX 1060 6Gb **Blender Version** Broken: 2.83.2 to 2.83.5 Worked: 2.82.a The same issue of https://developer.blender.org/T78960 actually was not solved until today. I made more questions on that ticket that was not answered. I had some help at https:*blender.stackexchange.com/questions/191626/how-to-fix-my-project-to-be-correctly-opened-by-blender-versions-newer-than-2-82/. But file theoretically fixed there (https:*blend-exchange.giantcowfilms.com/b/BEZnnD9j/) also doesn't open correctly in newer versions. I would just like to get rid of version 2.82a, but I can't, because these projects are only opened correctly in this version. At the same time, the Blender people don't give me a solution. **Exact steps for others to reproduce the error** Just follow the same described in https://developer.blender.org/T78960. But this time, if possible, showing the solution for this case.
Author

Added subscriber: @rogeriodec

Added subscriber: @rogeriodec

Added subscriber: @MarcinTwarowski

Added subscriber: @MarcinTwarowski

There was still one collection instanced within itself:
obraz.png
I moved the instance.
obraz.png
divisor282aFIXED_fixed.blend

There was still one collection instanced within itself: ![obraz.png](https://archive.blender.org/developer/F8796682/obraz.png) I moved the instance. ![obraz.png](https://archive.blender.org/developer/F8796697/obraz.png) [divisor282aFIXED_fixed.blend](https://archive.blender.org/developer/F8796702/divisor282aFIXED_fixed.blend)
Author

In #79936#999546, @MarcinTwarowski wrote:
There was still one collection instanced within itself:

When you say "instanced within itself" is it because the name is the same? Does Blender require unique names? If true, it should not allow duplicated names.

> In #79936#999546, @MarcinTwarowski wrote: > There was still one collection instanced within itself: When you say "instanced within itself" is it because the name is the same? Does Blender require unique names? If true, it should not allow duplicated names.

@rogeriodec An instanced collection is a linked copy that contains all objects from the original collection. A collection can't contain itself because it's illogical. Blender 2.82 allowed it apparently. In 2.83 that was fixed.

@rogeriodec An instanced collection is a linked copy that contains all objects from the original collection. A collection can't contain itself because it's illogical. Blender 2.82 allowed it apparently. In 2.83 that was fixed.
Author

Finally, it worked, thank you very much!
Could you tell me which version has this fix to avoid this same situation to happen again?

Finally, it worked, thank you very much! Could you tell me which version has this fix to avoid this same situation to happen again?

Added subscriber: @mont29

Added subscriber: @mont29

I know only what was written in blender/blender#78960. It should be fixed in newest versions. You incorrectly changed status of blender/blender#78960 by the way, from resolved to invalid. @mont29 made the fix .

I know only what was written in blender/blender#78960. It should be fixed in newest versions. You incorrectly changed status of blender/blender#78960 by the way, from resolved to invalid. @mont29 made [the fix ](https://developer.blender.org/rB7484e4529717a61277525bbb6bc9ac7a747e42f1).

Please note that this is not a support website, and refrain from asking that kind of questions here. This is strictly to report bugs, fixes may take some time to reach LTS (and some will not even be backported for various technical reasons).

Please note that this is not a support website, and refrain from asking that kind of questions here. This is strictly to report bugs, fixes may take some time to reach LTS (and some will not even be backported for various technical reasons).

Closed as duplicate of blender/blender#78960

Closed as duplicate of blender/blender#78960
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#79936
No description provided.