bl3.2.1 Wont show "load preferences: from 2.93 #100699

New Issue

Rombout Versluijs · 2022-08-30T03:11:35+02:00

Rombout Versluijs commented

2022-08-30 03:11:35 +02:00

System Information
Operating system: Windows-10-10.0.25188-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94

Blender Version
Broken: version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: bcfdb14560
Worked: (newest version of Blender that worked as expected)

Short description of error
Normally when you open a fresh installed new Blender version. It will show the dialog where we can set the keymap and also ask if user wants to import preferences of a earlier Blender version. For me it only shows the keymap dialog but not the import function.

Exact steps for others to reproduce the error
01 install blender 3.2.1
02 run blender 3.2.1
03 We are greeted with splash screen with keymap options
04 missing is the import preferences function

**System Information** Operating system: Windows-10-10.0.25188-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94 **Blender Version** Broken: version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: `bcfdb14560` Worked: (newest version of Blender that worked as expected) **Short description of error** Normally when you open a fresh installed new Blender version. It will show the dialog where we can set the keymap and also ask if user wants to import preferences of a earlier Blender version. For me it only shows the keymap dialog but not the import function. **Exact steps for others to reproduce the error** 01 install blender 3.2.1 02 run blender 3.2.1 03 We are greeted with splash screen with keymap options 04 missing is the import preferences function

Rombout Versluijs commented

2022-08-30 03:11:35 +02:00

Added subscriber: @RomboutVersluijs

Rombout Versluijs commented

2022-08-30 03:23:38 +02:00

I been checking some code and the issue is that it only looks for minor versions. In the userpref.py file there is the operator

preferences.copy_prev

the cls previous_versions only check back one minor version

@classmethod
    def previous_version(cls):
        # Find config folder from previous version.
        import os
        version = bpy.app.version
        version_new = ((version[0] * 100) + version[1])
        version_old = ((version[0] * 100) + version[1]) - 1
        print(version_new)
        print(version_old)
        - Ensure we only try to copy files from a point release.
        - The check below ensures the second numbers match.
        while (version_new % 100) *10 == (version_old % 100)* 10:
            version_split = version_old // 100, version_old % 100
            if os.path.isdir(cls._old_version_path(version_split)):
                return version_split
            version_old = version_old - 1
        return None

So do i really need to install every version from 2.93 to 3.2.1 to get 3.2.1 using my previous preferences?

I been checking some code and the issue is that it only looks for minor versions. In the userpref.py file there is the operator ``` preferences.copy_prev ``` the cls previous_versions only check back one minor version ``` @classmethod def previous_version(cls): # Find config folder from previous version. import os version = bpy.app.version version_new = ((version[0] * 100) + version[1]) version_old = ((version[0] * 100) + version[1]) - 1 print(version_new) print(version_old) - Ensure we only try to copy files from a point release. - The check below ensures the second numbers match. while (version_new % 100) *10 == (version_old % 100)* 10: version_split = version_old // 100, version_old % 100 if os.path.isdir(cls._old_version_path(version_split)): return version_split version_old = version_old - 1 return None ``` So do i really need to install every version from 2.93 to 3.2.1 to get 3.2.1 using my previous preferences?

Rombout Versluijs commented

2022-08-30 03:49:09 +02:00

as a workaround i manually copied items from 2.93 user folder to a new 3.2 folder. Did get some warning mainly due to addions not being updated. I tend to use one blender version as the main addon folder. But i guess i need to start using a new major version for this with all the API changes going from 2.93 to 3.2.1

Pratik Borhade commented

2022-08-30 05:29:02 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-08-30 05:29:02 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Pratik Borhade commented

2022-08-30 05:29:02 +02:00

Thanks for the report. If I understand correctly you want to import settings from last installed version, right?
And so far that option shows up if we've previous consecutive version installed, did i get you correctly? I'm able to confirm this behavior after removing the userprefs file.

Thanks for the report. If I understand correctly you want to import settings from last installed version, right? And so far that option shows up if we've previous consecutive version installed, did i get you correctly? I'm able to confirm this behavior after removing the `userprefs` file.

Rombout Versluijs commented

2022-08-30 16:50:22 +02:00

Correctl, ive saw some old reports when the 3.0 branch went live. Some users which could not load the previous preferences. That one went from 2.93 to 3.0. Though i would think everyrone would have this bugs as it only looks for minor version.

I did a print call from the def previous_version and it prints out 301 300 and at the end 299

Correctl, ive saw some old reports when the 3.0 branch went live. Some users which could not load the previous preferences. That one went from 2.93 to 3.0. Though i would think everyrone would have this bugs as it only looks for minor version. I did a print call from the def previous_version and it prints out 301 300 and at the end 299

Rombout Versluijs commented

2022-08-30 17:01:48 +02:00

I was looking at github in old versions and noticed branch 3.0 had hardcoded exceptions for this big step.

Source: blender Github repo

    @classmethod
    def previous_version(cls):
        # Find config folder from previous version.
        import os
        version = bpy.app.version
        version_new = ((version[0] * 100) + version[1])
        version_old = ((version[0] * 100) + version[1]) - 1

        # Special case, remove when the version is > 3.0.
        if version_new == 300:
            version_new = 294
            version_old = 293
        else:
            print("TODO: remove exception!")
        # End special case.

        - Ensure we only try to copy files from a point release.
        - The check below ensures the second numbers match.
        while (version_new % 100) *10 == (version_old % 100)* 10:
            version_split = version_old // 100, version_old % 100
            if os.path.isdir(cls._old_version_path(version_split)):
                return version_split
            version_old = version_old - 1
        return None

I was looking at github in old versions and noticed branch 3.0 had hardcoded exceptions for this big step. Source: [blender Github repo ](https://github.com/blender/blender/blob/blender-v3.0-release/release/scripts/startup/bl_operators/userpref.py#:~:text=%23%20Special%20case%2C%20remove,End%20special%20case.) ``` @classmethod def previous_version(cls): # Find config folder from previous version. import os version = bpy.app.version version_new = ((version[0] * 100) + version[1]) version_old = ((version[0] * 100) + version[1]) - 1 # Special case, remove when the version is > 3.0. if version_new == 300: version_new = 294 version_old = 293 else: print("TODO: remove exception!") # End special case. - Ensure we only try to copy files from a point release. - The check below ensures the second numbers match. while (version_new % 100) *10 == (version_old % 100)* 10: version_split = version_old // 100, version_old % 100 if os.path.isdir(cls._old_version_path(version_split)): return version_split version_old = version_old - 1 return None ```

Rombout Versluijs commented

2022-08-30 17:35:34 +02:00

Here's also a commit which shows that hardcoded values were added to resolve preference not importing

62bff15377

Here's also a commit which shows that hardcoded values were added to resolve preference not importing https://github.com/blender/blender/commit/62bff15377510ce05543afb40526d430a21697f1

Pratik Borhade commented

2022-08-30 17:39:18 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Richard Antalik commented

2022-08-30 22:10:43 +02:00

Added subscribers: @LazyDodo, @ideasman42, @iss

Richard Antalik commented

2022-08-30 22:10:43 +02:00

I can reproduce this, but from commit log not sure what intentions are - whether it is supposed to import pre 3.0 config. @ideasman42 @LazyDodo, can you check this?

Pratik Borhade commented

2022-08-31 04:39:20 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Ray molenkamp commented

2022-08-31 19:23:59 +02:00

I can validate at-least 3.4 won't import a 2.9x config, but i'll be honest we ended up fixing this last time with a bunch of people, my name is just on it since i did some of the low hanging fruit in D10986: Fix Various versioning issues, can't really say this is an area i'm overly familiar with, I'm gonna leave it to @ideasman42

I can validate at-least 3.4 won't import a 2.9x config, but i'll be honest we ended up fixing this last time with a bunch of people, my name is just on it since i did some of the low hanging fruit in [D10986: Fix Various versioning issues](https://archive.blender.org/developer/D10986), can't really say this is an area i'm overly familiar with, I'm gonna leave it to @ideasman42

blender-admin commented

2022-10-13 08:33:50 +02:00

This issue was referenced by 5916e73b28

This issue was referenced by 5916e73b2888537926d9aa71125a265989fa9e5a

blender-admin commented

2022-10-13 08:33:50 +02:00

This issue was referenced by fabf4ee33d

This issue was referenced by fabf4ee33def3b8f3555072ffa1d497ac8355da1

Campbell Barton commented

2022-10-13 08:39:10 +02:00

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Campbell Barton closed this issue