Wed, Feb 26
Technically bpy.ops.render.render() should use it's own depsgraph and it should be an instance, not a new state, so this may be a bug.
I was just suggesting quick workaround.
Well, if mesh instance is destroyed by calling ops.render.render(), we will have to refactorize the code to render first, and evaluate after (The complete code is of course not simplier than this example: this is for glTF export).
Is there any problem to evaluate it twice? (performance, memory usage?)
Tue, Feb 25
@Julien DUROURE (julien), did @Richard Antalik (ISS)'s comment help solve the problem?
(I don't know if it is worth investigating further as this does not seem like a bug, but it works as intended although poorly documented).
Mon, Feb 24
I am not really familiar with depsgraph implementation here, but I will assume, that bpy.ops.render.render() will use depsgraph to evaluate another scene, so your mesh instance will be destroyed by calling this operator.
Sun, Feb 23
I want to bump this, since fix seems to be really so simple (one line of code). @Campbell Barton (campbellbarton)
Fri, Feb 21
Thu, Feb 20
Committed improved support for 2x2 matrices separately rB1e3ffd1f872b: mathutils: support for to_2x2 as well as non-square matrices
Made some changes to matrix parsing, using a generic function.
Wed, Feb 19
It looks good, I didn't see any problems.
If @Campbell Barton (campbellbarton) doesn't have any observations, I can commit (this week maybe).
This seems like a terrible solution, since I imagine plenty of people have python installed alongside Blender
Honestly, I took everything python related out of my system variable path in my environment variables. I had already uninstalled python, but its files still existed on my hard drive and so did the system variable pointing to them. (I believe Anaconda which installed python 3.7 for me automatically adds this pointer to the path)
Files from the appdata directory may be loaded because of this:
Judging by the process monitor, I assume we will conclude that Blender was loading python scripts from a path library instead of its default library?
I've scrubbed every instance of python on my computer and removed all python pointers in my environment variables and path, then restarted for good measure.
Don't know that program at all, but here's what I could find when trying to import numpy, it seems to still be sourcing from another installation of python, but you might know better.
can you trace the process with process monitor and validate that the _multiarray_umath.cp37-win_amd64.pyd file is actually being read from the blender folder and not some other place?
Same exact thing with 2.83, file is included, import fails. =c
I've downloaded the portable to desktop, unzipped and verified there is indeed the numpy multiarray as seen in the attached images (if I can attach them).
It may be worth trying Blender 2.83, which has changes to ignore Python environment variables:
Tue, Feb 18
Don't Install Blender, try the portable build instead.
Open the folder and check to see if
the blender_debug_log.cmd batch file has this in it
I have not updated my PYTHONPATH environment variable since that github post, I can try that in a moment.
@Evan Wilson (EAW) the debug batch files reset the PYTHONPATH var, i'm 100% sure it is not set when blender starts with those.
First, I copied my python37 site-packages into my Blender2.8.2 python folder (the second option in the link you provided). This did not work, so I proceeded to the first option.
Opened blender via blender_debug_log.cmd
went to scripting tab
same error as mentioned above when trying
Can't repro on windows with the official 2.82 or latest master
No, it does not.
When you start blender with the blender_debug_log.cmd batch file located in the blender folder, does it work?
- Unfortunately the Thonny IDE doesn't allow to choose which Python to Install. I don't have Python installed manually anymore and didn't have this problem with Python 3.7 64 bit when I did. And I did another workaround using Thonny's feature virtual environment (I know it's Python feature, but the IDE allow to manage it).
- I tried the "latest buildbot" (blender-2.83-d0c159ae9745-windows64) and the problem persist.
Mon, Feb 17
It should not be looking outisde the blender folder for addons ever since rB7c2f0074f3fe2411daa7a6e351d7cbc535246871 can you still reproduce this on the latest buildbot ?
Can you trying installing python 64 bit instead?
Sorry, commented on wrong review...
@Richard Antalik (ISS) Tested with 2.83 Alpha .
Able to reproduce the issue.
For safety i also tried entering pose mode and applying pose to rest.
Same result as previously.