Startup.blend file is not loaded on startup if userpref.blend does not exist. #69002

New Issue

Narayan Aras · 2019-08-21T18:08:44+02:00

Narayan Aras commented

2019-08-21 18:08:44 +02:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7000

Blender Version
Broken: version: 2.81 (sub 3), branch: master, commit date: 2019-08-20 22:35, hash: daba3e871f
Worked: (optional)

Short description of error
Startup.blend file is not loaded on startup if userpref.blend does not exist.

Exact steps for others to reproduce the error

Remove userpref.blend file from it's usual location
Start blender
Dismiss splash screen by clicking on 3D viewport
Make some change to the file (move the cube)
Save as startup file
Close Blender

Open blender

Startup file is not loaded

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7000 **Blender Version** Broken: version: 2.81 (sub 3), branch: master, commit date: 2019-08-20 22:35, hash: `daba3e871f` Worked: (optional) **Short description of error** Startup.blend file is not loaded on startup if userpref.blend does not exist. **Exact steps for others to reproduce the error** - Remove userpref.blend file from it's usual location - Start blender - Dismiss splash screen by clicking on 3D viewport - Make some change to the file (move the cube) - Save as startup file - Close Blender # Open blender Startup file is not loaded

Narayan Aras commented

2019-08-21 18:08:44 +02:00

Added subscriber: @raindrops

Abid Maqbool commented

2019-08-21 19:52:48 +02:00

Added subscriber: @AbidMaqbool

Abid Maqbool commented

2019-08-21 19:52:48 +02:00

Can confirm in Blender 2.81. Seems fine in Blender 2.8 Stable... so latter disordered..

Narayan Aras commented

2019-08-22 16:16:42 +02:00

This comment was removed by @raindrops

*This comment was removed by @raindrops*

Philipp Oeser commented

2019-10-30 12:56:16 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-10-30 12:56:16 +01:00

#59451 is related btw.

Philipp Oeser changed title from ~~Blender cannot save the two-column layout of toolbar in the 3D Viewport~~ to Startup File: Blender cannot save the two-column layout of toolbar in the 3D Viewport

2019-10-30 13:00:22 +01:00

Reiner Prokein commented

2019-10-31 11:16:20 +01:00

Added subscriber: @tiles

Reiner Prokein commented

2019-10-31 11:16:20 +01:00

Some observations here:

Do a fresh installation, remove everything from the appdata folder. Start Blender. Don't click at the NEXT button in the splash screen. Resize the tool shelf to two columns. Now save the startup.blend, close and reopen Blender. The tool shelf will be single column.

Now do a fresh installation, remove everything from the appdata folder. Start Blender and click at the NEXT button in the splash screen. Resize the tool shelf to two columns. Now save the startup.blend, close and reopen Blender. The tool shelf has kept its status. It is two columns now.

But compiling with this startup.blend results in a single column layout again.

Some observations here: Do a fresh installation, remove everything from the appdata folder. Start Blender. Don't click at the NEXT button in the splash screen. Resize the tool shelf to two columns. Now save the startup.blend, close and reopen Blender. The tool shelf will be single column. Now do a fresh installation, remove everything from the appdata folder. Start Blender and click at the NEXT button in the splash screen. Resize the tool shelf to two columns. Now save the startup.blend, close and reopen Blender. The tool shelf has kept its status. It is two columns now. But compiling with this startup.blend results in a single column layout again.

Reiner Prokein commented

2019-11-01 10:28:40 +01:00

The problem appears at the commits from 31.07.2019. The commit from 30.07 are fine. The commits from 1.08 have the problem. I can unfortunately not get any closer since the commits from this day does not compile with Visual Studio. It throws errors with FFmpeg and another file, which gots fixed later at this day. But one special commit jumped into my eyes here. Better said two.

31.07.2019 - Cleanup: remove BLO_update_defaults_userpref_blend
31.07.2019 - Preferences: don't store preferences in the startup

This is a rewrite of how some settings are stored. And that's where storing the state of the tool shelf rows may got lost. My C fu is unfortunately too weak to fix the problem. But i hope the informations can be of use.

The problem appears at the commits from 31.07.2019. The commit from 30.07 are fine. The commits from 1.08 have the problem. I can unfortunately not get any closer since the commits from this day does not compile with Visual Studio. It throws errors with FFmpeg and another file, which gots fixed later at this day. But one special commit jumped into my eyes here. Better said two. 31.07.2019 - Cleanup: remove BLO_update_defaults_userpref_blend 31.07.2019 - Preferences: don't store preferences in the startup This is a rewrite of how some settings are stored. And that's where storing the state of the tool shelf rows may got lost. My C fu is unfortunately too weak to fix the problem. But i hope the informations can be of use.

Richard Antalik commented

2020-02-05 19:14:19 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-02-05 19:14:19 +01:00

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

Richard Antalik commented

2020-02-05 19:14:19 +01:00

I have re-triaged this report and can not reproduce it.
Can you please check if this is still an issue in latest build?
https://builder.blender.org/download/

I have re-triaged this report and can not reproduce it. Can you please check if this is still an issue in latest build? https://builder.blender.org/download/

Reiner Prokein commented

2020-02-05 21:12:35 +01:00

Yes, that's still an issue. Nobody has fixed this one yet. I have tested it before a few moments with the newest 2.83 buildbot build . There's the above told workaround available for the users. But at the moment nobody can make a working startup.blend file to compile new defaults with a two rows toolbar for example. Or another tool shelf default button than Box Select.

To reproduce:
Remove all stored information in the appdata path. We need a blank Blender.
Open Blender. Do NOT click at the Next button in the splash screen.
Resize toolbar to two rows.
Save startup.blend.
When you reopen Blender, then the toolbar is single column again.

Yes, that's still an issue. Nobody has fixed this one yet. I have tested it before a few moments with the newest 2.83 buildbot build . There's the above told workaround available for the users. But at the moment nobody can make a working startup.blend file to compile new defaults with a two rows toolbar for example. Or another tool shelf default button than Box Select. To reproduce: Remove all stored information in the appdata path. We need a blank Blender. Open Blender. Do NOT click at the Next button in the splash screen. Resize toolbar to two rows. Save startup.blend. When you reopen Blender, then the toolbar is single column again.

Reiner Prokein commented

2020-02-05 21:18:54 +01:00

Forgot to say, the other way to reproduce is to create a two column tool shelf layout, save the startup.blend, and compile with this startup.blend then. With a fresh installation you will have it single row again then.

Reiner Prokein commented

2020-02-06 08:32:49 +01:00

Hm, this bug seems not only to block any new factory defaults in the tool shelf, but also in other UI areas. I saved a startup.blend with a different stretching method in the UV Editor. And compiled with it. And the factory default stretching method is back at Blender defaults then.

Philipp Oeser commented

2020-02-06 09:27:19 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Richard Antalik commented

2020-02-06 15:36:22 +01:00

In #69002#866391, @tiles wrote:
Yes, that's still an issue. Nobody has fixed this one yet. I have tested it before a few moments with the newest 2.83 buildbot build . There's the above told workaround available for the users. But at the moment nobody can make a working startup.blend file to compile new defaults with a two rows toolbar for example. Or another tool shelf default button than Box Select.

To reproduce:
Remove all stored information in the appdata path. We need a blank Blender.
Open Blender. Do NOT click at the Next button in the splash screen.
Resize toolbar to two rows.
Save startup.blend.
When you reopen Blender, then the toolbar is single column again.

I did exactly this and it worked.

With a fresh installation you will have it single row again then.

What do you mean by fresh installation?

> In #69002#866391, @tiles wrote: > Yes, that's still an issue. Nobody has fixed this one yet. I have tested it before a few moments with the newest 2.83 buildbot build . There's the above told workaround available for the users. But at the moment nobody can make a working startup.blend file to compile new defaults with a two rows toolbar for example. Or another tool shelf default button than Box Select. > > To reproduce: > Remove all stored information in the appdata path. We need a blank Blender. > Open Blender. Do NOT click at the Next button in the splash screen. > Resize toolbar to two rows. > Save startup.blend. > When you reopen Blender, then the toolbar is single column again. I did exactly this and it worked. > With a fresh installation you will have it single row again then. What do you mean by fresh installation?

Reiner Prokein commented

2020-02-06 17:41:43 +01:00

I will make a video. Give me a few moments please.

Reiner Prokein commented

2020-02-06 18:46:22 +01:00

Here the bug:the_bug.mp4

Here the workaround for the users: the_workaround_for_users.mp4

And i would have loved to show the problem and to talk about the consequences for self builders who needs custom factory defaults. Because this bug now prevents us from having own factory defaults, at least for the tool shelf. But the current version of Blender does not compile here at the moment. Any idea what the problem could be?

Here the bug:[the_bug.mp4](https://archive.blender.org/developer/F8325900/the_bug.mp4) Here the workaround for the users: [the_workaround_for_users.mp4](https://archive.blender.org/developer/F8325902/the_workaround_for_users.mp4) And i would have loved to show the problem and to talk about the consequences for self builders who needs custom factory defaults. Because this bug now prevents us from having own factory defaults, at least for the tool shelf. But the current version of Blender does not compile here at the moment. Any idea what the problem could be? ![notcompiling.jpg](https://archive.blender.org/developer/F8325911/notcompiling.jpg)

Richard Antalik commented

2020-02-06 23:44:50 +01:00

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

Richard Antalik commented

2020-02-06 23:44:50 +01:00

Ok my mistake, I think what I did was open new file instead of restarting Blender.

Seems, that startup.blend file is not loaded if userpref.blend does not exist.
2.79 does not have such problem, but since workaround is quite simple, I would not consider this to be a bug

And i would have loved to show the problem and to talk about the consequences for self builders who needs custom factory defaults. Because this bug now prevents us from having own factory defaults, at least for the tool shelf.

I am not quite sure what you mean by this, but please be aware that this website is strictly dedicated to reporting bugs or patches.

But the current version of Blender does not compile here at the moment. Any idea what the problem could be?

best to ask at https://blender.chat at #blender-coders channel. Do make update and I always rebuild whole solution in MSVC

Ok my mistake, I think what I did was open new file instead of restarting Blender. Seems, that `startup.blend` file is not loaded if userpref.blend does not exist. 2.79 does not have such problem, but since workaround is quite simple, I would not consider this to be a bug > And i would have loved to show the problem and to talk about the consequences for self builders who needs custom factory defaults. Because this bug now prevents us from having own factory defaults, at least for the tool shelf. I am not quite sure what you mean by this, but please be aware that this website is strictly dedicated to reporting bugs or patches. > But the current version of Blender does not compile here at the moment. Any idea what the problem could be? best to ask at https://blender.chat at #blender-coders channel. Do make update and I always rebuild whole solution in MSVC

Alan Troth commented

2020-02-07 00:15:31 +01:00

Added subscriber: @AlanT

Alan Troth commented

2020-02-07 00:15:31 +01:00

This comment was removed by @AlanT

*This comment was removed by @AlanT*

Richard Antalik changed title from ~~Startup File: Blender cannot save the two-column layout of toolbar in the 3D Viewport~~ to Startup.blend file is not loaded on startup if userpref.blend does not exist.

2020-02-07 01:06:28 +01:00

Reiner Prokein commented

2020-02-07 09:44:26 +01:00

2.79 does not have such problem, but since workaround is quite simple, I would not consider this to be a bug

It worked in 2.80. The workaround just works for normal end users. And that a workaround exists even shows that it is a bug.

And i think that you have still not understood the consequences. I really have to do the third video ...

You cut away all self builders that wants to do custom factory defaults at the tool shelf. Self compilers are also users. And even Blender is affected by this. Try to create a factory default with a tool shelf with two rows now. A good example could be the sculpting tool shelf. It already bustes with one row. You most probably need to make it two rows at one point. And this part, to change the factory defaults for the tool shelf, does not work anymore, caused by this bug.

Other factory defaults that gots removed from the startup.blend went into the release\datafiles\userdef\userdef_default.c file. But not the width of the toolbar yet. And not the state of the active toolbar button. Box select is imho a very bad default. Something that i would love to change in my custom factory defaults. And a few other things are also lost now from what i can see.

You could of course create a todo for just the factory defaults part, and separate it from this report. But the cause is this bug here. It's not several bugs. I's one bug with several consequences. When you just fix the end user part, then the bug is just partially fixed.

I am not quite sure what you mean by this, but please be aware that this website is strictly dedicated to reporting bugs or patches.

Err. I usually just report bugs at this tracker. I can of course still be wrong. Humans makes mistakes, i am not different here. But when i report it then i can usually reproduce it, and am under the strong impression that it is a bug. And i have even provided lots of material now to proove it.

This bug here is not even reported by me. I am just somebody who can reproduce it, somebody who understands the dimensions since he is affected, and who is willing to spend the time to explain it in detail and to help with a solution. I even already pointed at the commits and the C files where the problem resides. See above.

I have now seen quite a few showstoppers making their way at the "fix comes in twenty years if even" list. Better known as "Known Issue". I don't want to see this showstopper for self compilers and factory default changers going the same way. It is important and vital to me.

best to ask at https://blender.chat at #blender-coders channel. Do make update and I always rebuild whole solution in MSVC

Thanks for the ideas. I compile at Windows, not at Linux, as the screenshot shows. No make update here. But you can be sure that i know how to compile Blender. That i have pulled the newest versions. Also the libs. And that my periphery software like git and cmake is up to date. And usually compiling Blender works flawless here. Since years.

Well, it fails from time to time since some baddies makes it always into the master. See above, when i tried to catch the commit with the trouble code. But i do not really ask for help to compile Blender here. It's just i wanted to reproduce the problem for you with a video, so that you understand the dimensions of the problem. And just in this moment the compiling failed, the first time since months. Murphy's law. It breaks just in the moment when you need it ...

Now it takes a bit longer, with lots of unnecessary discussions. The video would have been the fastest way to make things obvious. And telling me why compiling fails would have lead to the video.

>2.79 does not have such problem, but since workaround is quite simple, I would not consider this to be a bug It worked in 2.80. The workaround just works for normal end users. And that a workaround exists even shows that it is a bug. And i think that you have still not understood the consequences. I really have to do the third video ... You cut away all self builders that wants to do custom factory defaults at the tool shelf. Self compilers are also users. And even Blender is affected by this. Try to create a factory default with a tool shelf with two rows now. A good example could be the sculpting tool shelf. It already bustes with one row. You most probably need to make it two rows at one point. And this part, to change the factory defaults for the tool shelf, does not work anymore, caused by this bug. Other factory defaults that gots removed from the startup.blend went into the release\datafiles\userdef\userdef_default.c file. But not the width of the toolbar yet. And not the state of the active toolbar button. Box select is imho a very bad default. Something that i would love to change in my custom factory defaults. And a few other things are also lost now from what i can see. You could of course create a todo for just the factory defaults part, and separate it from this report. But the cause is this bug here. It's not several bugs. I's one bug with several consequences. When you just fix the end user part, then the bug is just partially fixed. > I am not quite sure what you mean by this, but please be aware that this website is strictly dedicated to reporting bugs or patches. Err. I usually just report bugs at this tracker. I can of course still be wrong. Humans makes mistakes, i am not different here. But when i report it then i can usually reproduce it, and am under the strong impression that it is a bug. And i have even provided lots of material now to proove it. This bug here is not even reported by me. I am just somebody who can reproduce it, somebody who understands the dimensions since he is affected, and who is willing to spend the time to explain it in detail and to help with a solution. I even already pointed at the commits and the C files where the problem resides. See above. I have now seen quite a few showstoppers making their way at the "fix comes in twenty years if even" list. Better known as "Known Issue". I don't want to see this showstopper for self compilers and factory default changers going the same way. It is important and vital to me. >best to ask at https://blender.chat at #blender-coders channel. Do make update and I always rebuild whole solution in MSVC Thanks for the ideas. I compile at Windows, not at Linux, as the screenshot shows. No make update here. But you can be sure that i know how to compile Blender. That i have pulled the newest versions. Also the libs. And that my periphery software like git and cmake is up to date. And usually compiling Blender works flawless here. Since years. Well, it fails from time to time since some baddies makes it always into the master. See above, when i tried to catch the commit with the trouble code. But i do not really ask for help to compile Blender here. It's just i wanted to reproduce the problem for you with a video, so that you understand the dimensions of the problem. And just in this moment the compiling failed, the first time since months. Murphy's law. It breaks just in the moment when you need it ... Now it takes a bit longer, with lots of unnecessary discussions. The video would have been the fastest way to make things obvious. And telling me why compiling fails would have lead to the video.

Richard Antalik commented

2020-02-07 12:02:00 +01:00

I don't really understand, why this is showstopper. Why can't you click on that next button on the splashscreen?

No make update here.

Please follow https://wiki.blender.org/wiki/Building_Blender/Windows
especially Starting the command prompt section

I don't really understand, why this is showstopper. Why can't you click on that `next` button on the splashscreen? > No make update here. Please follow https://wiki.blender.org/wiki/Building_Blender/Windows especially `Starting the command prompt` section

Reiner Prokein commented

2020-02-07 12:39:42 +01:00

I don't really understand, why this is showstopper. Why can't you click on that next button on the splashscreen?

We still misunderstand each other here. I can do this part. This is indeed a valid workaround for the end user.

But this workaround does not help when you want to compile with a created startup.blend to change the factory defaults. That's where it is a showstopper now. The two row tool shelf does not arrive at the factory defaults anymore. And as told, this is caused by the same bug. Another aspect, but the same cause. The user problem with the minor workaround is just the tip of the iceberg.

The factory defaults for the tool shelf are for example of interest to developers when you want to toy around with some ideas, and the Blender factory defaults are in the way. Like adding more content or tabs to the tool shelf. It is very time consuming to always resize the tool shelf to two rows. Or to change the box select default to tweak, which makes imho more sense.

Please follow https://wiki.blender.org/wiki/Building_Blender/Windows
especially Starting the command prompt section

Again thanks for the advice. I use Tortoisegit to fetch and pull. To compile i double click at the sln file to open VS, and build from there. And as told, usually this works, since years. Haven't found the cause yet. It remains curious.

>I don't really understand, why this is showstopper. Why can't you click on that next button on the splashscreen? We still misunderstand each other here. I can do this part. This is indeed a valid workaround for the end user. But this workaround does not help when you want to compile with a created startup.blend to change the factory defaults. That's where it is a showstopper now. The two row tool shelf does not arrive at the factory defaults anymore. And as told, this is caused by the same bug. Another aspect, but the same cause. The user problem with the minor workaround is just the tip of the iceberg. The factory defaults for the tool shelf are for example of interest to developers when you want to toy around with some ideas, and the Blender factory defaults are in the way. Like adding more content or tabs to the tool shelf. It is very time consuming to always resize the tool shelf to two rows. Or to change the box select default to tweak, which makes imho more sense. >Please follow https://wiki.blender.org/wiki/Building_Blender/Windows >especially Starting the command prompt section Again thanks for the advice. I use Tortoisegit to fetch and pull. To compile i double click at the sln file to open VS, and build from there. And as told, usually this works, since years. Haven't found the cause yet. It remains curious.

Reiner Prokein commented

2020-02-08 09:24:01 +01:00

Have it. Submodules made fun, Locale was missing. Pulling everything from scratch solved the issue.

So here comes the promised third video. The consequences for developers. The factory defaults problem.
Sorry for the size. I have kept it as short as possible.

factorydefaults.mp4

Have it. Submodules made fun, Locale was missing. Pulling everything from scratch solved the issue. So here comes the promised third video. The consequences for developers. The factory defaults problem. Sorry for the size. I have kept it as short as possible. [factorydefaults.mp4](https://archive.blender.org/developer/F8329135/factorydefaults.mp4)

Richard Antalik commented

2020-02-08 23:30:06 +01:00

@tiles Thanks for explanation.
This looks like quite different issue, than this one. Could you please make new report for this?

@tiles Thanks for explanation. This looks like quite different issue, than this one. Could you please make new report for this?

Reiner Prokein commented

2020-02-09 07:58:37 +01:00

Sure. Will do. But it is the same commits and the same change that is responsible for both behaviours.

31.07.2019 - Cleanup: remove BLO_update_defaults_userpref_blend
31.07.2019 - Preferences: don't store preferences in the startup

Sure. Will do. But it is the same commits and the same change that is responsible for both behaviours. 31.07.2019 - Cleanup: remove BLO_update_defaults_userpref_blend 31.07.2019 - Preferences: don't store preferences in the startup

Reiner Prokein commented

2020-02-09 08:41:00 +01:00

Task created, and thanks for your patience.

Sybren A. Stüvel commented

2023-01-31 11:03:53 +01:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2023-01-31 11:03:53 +01:00

I don't see how this relates to the #blender_file project, so I'll remove the tag.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Startup.blend file is not loaded on startup if userpref.blend does not exist. #69002

Open blender