Regression: Find default blender executables

[F-Brar]

In general, #179 looks like a good feature, but it still doesn't work on macOS. In version 0.0.22 the path to Blender has to be selected manually on every launch.

I use different Blender versions in development and really like the possibility to tag them with custom names. Is there an option to keep using the old paths in vscode settings ("blender.executables")?

Here is what mine looks like:

    "blender.executables": [
        {
            "path": "/Applications/Blender421.app/Contents/MacOS/blender",
            "name": "Blender 4.2.1",
            "isDebug": false
        },
        {
            "path": "/Applications/Blender420-production.app/Contents/MacOS/blender",
            "name": "Blender 4.2.0-production",
            "isDebug": false
        },
        {
            "path": "/Applications/blender365.app/Contents/MacOS/blender",
            "name": "Blender 3.6.5 (LTS)",
            "isDebug": false
        },
        {
            "path": "/Users/<user>/source/repos/blender-git/build_darwin_debug/bin/Blender420_debug.app/Contents/MacOS/blender",
            "name": "Blender 4.2.0 (debug)",
            "isDebug": false
        },
    ],

I would also argue that, as long as a feature is not even tested in macOS, it shouldn't be released. Don't get me wrong, most of the new changes are really great and I love that this extension is getting so much attention recently. For mac users this regression means we have to stay on version 0.0.21 for now though.

Let me know if you need any additional info.

[zebus3d]

The same thing happens to me in CachyOS Linux.

[Mateusz-Grzelinski]

The logic in code is: blender.executables should take priority and never dissapear. The settings from VS code should apperar first and then the paths that are found automatically - see screenshot in #179.

What exacltly can you see? If there is a path that you want to tag with name, please add it to settings - it should no longer apper as long path.

Not every blender installation can be found automatically see #185. There are way too many ways to install blender to find them all of them. Please report you installation methof we can try to support it.

as long as a feature is not even tested in macOS

I do not have a mac to test on... As long as the feature does not break mac I can still release it to windows and linux.

[F-Brar]

Thanks for the quick reply. It seems there is a problem on macOS that prevents the blender.executablesfrom showing. When I execute Blender: Start, I just get the standard 'Choose a new Blender executable...'. In version 0.0.21 all blender.executablesare visible.

[luckychris]

i have the exact same problem on macOS. I have to choose my blender executable everytime i try to execute Blender:start.

[Mateusz-Grzelinski]

I checked and the problem is not obvious. I have no access to mac os so I either need more logs or we can do a debugging together. Some log might be here, there should be some lines with JacquesLucke.blender-development:

[luckychris]

@Mateusz-Grzelinski : if you tell me how we can debug together and if i don't have to install a 2 hour program, we can try....

[Mateusz-Grzelinski]

no, those logs do not help. can you reach on on chat.blender.org? seems to be sensible place to do a session. @grzelins:blender.org we can have a call in afternoon/evening

[Mateusz-Grzelinski]

the fix whould be now live in 0.23!

[luckychris]

works perfectly! Thanks for the quick fix!! You are awesome!

[F-Brar]

Thanks a lot for the quick fix! 💯