Startup Glitches ~ (ASCII User Prefs 'blend' file format feature request) #54416

New Issue

Master James · 2018-03-24T22:36:29+01:00

Master James commented

2018-03-24 22:36:29 +01:00

Had a dozen problems when upgrading from 2.79 to 2.79a
Seems like there was all sorts of problems with User stored Addons.
I deleted all of them (Upsetting and undesirable) and continued to look at problems with Console output.
Remaining is 4 duplicates of

search for unknown operator 'VIEW3D_OT_cursor3d_enhanced', 'VIEW3D_OT_cursor3d_enhanced'

[I tried adding back in the addon I think was related but that made no difference]

Only when I delete both startup.blend and userpref.blend (from the Users/Pissed/AppData/Roaming/~/2.79/config folder) does this error go away. [It's suggested to not be a huge problem but remains unacceptable to leave glitches like this floating around.]
I don't want to delete all my User Prefs and whatever else is hidden away in there. (Which I've done now so not happy with that)

First problem in my estimation is you do not have a human readable ascii format for this User Preference etc. information.
I would seriously reconsider the wisdom of this decision moving forward.

You should actually break down whatever in there into more files then those two.
This way the culprit corrupted files can be purged without loosing all information. It's clearer where and when in what part people say "oh I deleted that operator.blend file and still have my preferences.blend file and am happy etc. but you have a clearer defined problem to address."
I don't think I need to elaborate on the value of the user also being able to edit correct and clarify to you what portion of the human readable portioned pref files is faulting.

So I've lost all my preferences, have no idea what the hex is/was in there, etc. I figure that ultimately this is caused by other ancient under-sights (in early dev dayz) triggered by problems with mem pointers or 'what have you' in there that make you feel you need a binary format.

My suggestion/Recommendation/Feature Request is that you:
Purge what can be human-readable into separate multiple more distinctive files, and then the stuff you really can't do without putting in a binary blend file can stay there and hopefully it's not as important to the users as their User Preferences.
Consider a none binary 'blend' file format and possible new extension 'blender' with the ability to select while saving ascii instead of binary format, which will be ascii as a default phasing out binary or suffer the alternative of providing binary blend file, editors, corruption detectors, fixers etc.

It's broken think about what I've suggested/requested, thanks for listening it's good to vent even when I know it will fall on deaf ears.

Had a dozen problems when upgrading from 2.79 to 2.79a Seems like there was all sorts of problems with User stored Addons. I deleted all of them (Upsetting and undesirable) and continued to look at problems with Console output. Remaining is 4 duplicates of ``` search for unknown operator 'VIEW3D_OT_cursor3d_enhanced', 'VIEW3D_OT_cursor3d_enhanced' ``` *[I tried adding back in the addon I think was related but that made no difference]* Only when I delete both startup.blend and userpref.blend (from the Users/Pissed/AppData/Roaming/~/2.79/config folder) does this error go away. [It's suggested to not be a huge problem but remains unacceptable to leave glitches like this floating around.] I don't want to delete all my User Prefs and whatever else is hidden away in there. (Which I've done now so not happy with that) First problem in my estimation is you do not have a human readable ascii format for this User Preference etc. information. **I would seriously reconsider the wisdom of this decision moving forward.** You should actually break down whatever in there into more files then those two. This way the culprit corrupted files can be purged without loosing all information. It's clearer where and when in what part people say "oh I deleted that operator.blend file and still have my preferences.blend file and am happy etc. but you have a clearer defined problem to address." I don't think I need to elaborate on the value of the user also being able to edit correct and clarify to you what portion of the human readable portioned pref files is faulting. So I've lost all my preferences, have no idea what the hex is/was in there, etc. I figure that ultimately this is caused by other ancient under-sights (in early dev dayz) triggered by problems with mem pointers or 'what have you' in there that make you feel you need a binary format. My suggestion/Recommendation/Feature Request is that you: Purge what can be human-readable into separate multiple more distinctive files, and then the stuff you really can't do without putting in a binary blend file can stay there and hopefully it's not as important to the users as their User Preferences. Consider a none binary 'blend' file format and possible new extension 'blender' with the ability to select while saving ascii instead of binary format, which will be ascii as a default phasing out binary or suffer the alternative of providing binary blend file, editors, corruption detectors, fixers etc. It's broken think about what I've suggested/requested, thanks for listening it's good to vent even when I know it will fall on deaf ears.

Master James commented

2018-03-24 22:36:29 +01:00

Added subscriber: @MasterJames

Ray molenkamp commented

2018-03-24 22:48:53 +01:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2018-03-24 22:48:53 +01:00

Changed status from 'Open' to: 'Archived'

Ray molenkamp closed this issue

2018-03-24 22:48:53 +01:00

Ray molenkamp self-assigned this 2018-03-24 22:48:53 +01:00

Ray molenkamp commented

2018-03-24 22:48:53 +01:00

Hate to play straight into your hand, but sadly i have to abide by the tracker rules an close this as a feature request. here's the standard blurb, sorry man!

Hi, while we love to hear these ideas, this is not the right place for them. This website is mainly used to track bug reports and not feature requests. But luckly, there are some other nice solutions you can take, so please use one of the other forms of communication listed below:

https://rightclickselect.com/
Fun board mailing list: https://lists.blender.org/mailman/listinfo/bf-funboard

Hate to play straight into your hand, but sadly i have to abide by the tracker rules an close this as a feature request. here's the standard blurb, sorry man! Hi, while we love to hear these ideas, this is not the right place for them. This website is mainly used to track bug reports and not feature requests. But luckly, there are some other nice solutions you can take, so please use one of the other forms of communication listed below: https://rightclickselect.com/ Fun board mailing list: https://lists.blender.org/mailman/listinfo/bf-funboard

Vuk Gardašević commented

2018-03-24 23:20:16 +01:00

Added subscriber: @VukGardasevic

Vuk Gardašević commented

2018-03-24 23:20:16 +01:00

Sorry to hear about the add-on issues, but those can arise when saving user preferences, if the add-on for instance crashed before.
The add-on in question is quite complex and is in Contrib folder for a reason of not yet being stable enough.
Generally Blender has the startup blend as the primary way of storing settings. So any add-ons and settings will be stored there if the startup file is generated while they are enabled. That means that both files can have add-ons enabled, which can lead to issues of the errors being present. userpref.blend will override certain settings like theme, add-ons enabled and various other User Preferences settings.

There is several ways now to try to deal with issues:

Save a startup blend without any add-ons enabled or with only a few true and tested ones like IO that come enabled by default.

 All other add-ons should be only stored with Save User preferences. That means if anything goes wrong redoing the user_pref file will be easier.
The Help > Save System Info gives a list of enabled add-ons their paths and versions.

Using application templates.

Those allow to have several startup blend files with different configurations and settings including the add-ons enabled.

Concerning the proposal it all depends how blender files are stored -> a memory dump. If there is something wrong at the moment like some broken add-on those can affect the saved startup / user preferences file.

The contents of the User Preferences can be previewed in the Outliner > User Preferences.

Sorry to hear about the add-on issues, but those can arise when saving user preferences, if the add-on for instance crashed before. The add-on in question is quite complex and is in Contrib folder for a reason of not yet being stable enough. Generally Blender has the startup blend as the primary way of storing settings. So any add-ons and settings will be stored there if the startup file is generated while they are enabled. That means that both files can have add-ons enabled, which can lead to issues of the errors being present. userpref.blend will override certain settings like theme, add-ons enabled and various other User Preferences settings. There is several ways now to try to deal with issues: - Save a startup blend without any add-ons enabled or with only a few true and tested ones like IO that come enabled by default. ``` All other add-ons should be only stored with Save User preferences. That means if anything goes wrong redoing the user_pref file will be easier. The Help > Save System Info gives a list of enabled add-ons their paths and versions. ``` - Using application templates. ``` Those allow to have several startup blend files with different configurations and settings including the add-ons enabled. ``` Concerning the proposal it all depends how blender files are stored -> a memory dump. If there is something wrong at the moment like some broken add-on those can affect the saved startup / user preferences file. The contents of the User Preferences can be previewed in the Outliner > User Preferences.

This repo is archived. You cannot comment on issues.