hi, this may or may not belong in “bugs” depending on how one looks at it.
the environment does not appear to be made available on toe start (or, more specifically, before everything else starts to initialize), even though it is configured properly and reports the Environment linked and ready:
if I turn off cooking for the component in question:
and then re-enable cooking:
it loads the missing modules.
looking further down my textport logs, I notice that the manager loads well after many other portions of the app:
2025-06-11 07:59:58,658 - INFO - TDAppLogger.tdPyEnvManager_logger - PID:43465 - /Aleph/lib/tdPyEnvManager - Environment /Users/rosco/wkspaces/2412-ldi/Aleph2/Aleph2_vEnv was linked and is ready. Context is: {'type': 'Python vEnv', 'envPath': '/Users/rosco/wkspaces/2412-ldi/Aleph2/Aleph2_vEnv', 'executablePath': '/Applications/TouchDesigner.app/Contents/Frameworks/Python.framework/Versions/3.11/bin/python3.11', 'osPath': [], 'sysPath': ['/Users/rosco/wkspaces/2412-ldi/Aleph2/Aleph2_vEnv/lib/python3.11/site-packages']} (DAT:/Aleph/lib/tdPyEnvManager/TDPyEnvManagerExt, fn:linkEnv, ln:962, absFrame: 0, frame: 533.0)
as per the Considerations documentation, all extensions are not set to init onStart – only tdPyEnvManager is:
the expected behavior here would be that the vEnv is available immediately onStart, before everything else… is there a way to force this to load prior to everything else, or is the expectation here that the user needs to init all vEnv calls (extensions, etc.) with built-in delays?
which leads me to a more profound question: what determines the load order for components in a toe, and is there / could there be a way to set this order more efficiently than dozens/hundreds of run() delays?
thanks!
