Include startup folder in env of PYTHONPATH

[moonyuet]

Changelog Description

Add startup folder in env of PYTHONPATH
Resolve #33

Additional review information

Build and Install 3dsmax Addon with this branch
Maybe some of the pre-launch hook can be removed after the implementation

Testing notes:

1. Launch Max
2. AYON plugins should be all working.

[LiborBatek]

I have made few AYON tools test and all working without any glitch.

Tried to Open/Save workfile and publish and load stuff in...all good!

[iLLiCiTiT]

I believe this PR is not needed. Because what was set in applications addon is invalid for more than half year. It did work before this PR, right?

[moonyuet]

I believe this PR is not needed.

Indeed

[BigRoy]

For more context to @iLLiCiTiT 's comment see his comment here. Which indeed leaves the question, is this even still needed?

OR is the forced startup script once implemented just because the original way we were setting up the env vars was wrong to begin with? Like, could we avoid the forced startup script instead in favor of just setting the env var?

[moonyuet]

For more context to @iLLiCiTiT 's comment see his comment here. Which indeed leaves the question, is this even still needed?

OR is the forced startup script once implemented just because the original way we were setting up the env vars was wrong to begin with? Like, could we avoid the forced startup script instead in favor of just setting the env var?

but the force_startup_script.py is to execute the maxscript(startup.ms) to register the environment for the ayon plugins in 3dsmax....so it can't be removed.

[iLLiCiTiT]

We could try to remove the pre-launch hook, and setup the ADSK_3DSMAX_STARTUPSCRIPTS_ADDON_DIR environment variable in add_implementation_envs, if that would work.

My guess is that it did not work, or there were issues connected to ADSK_3DSMAX_STARTUPSCRIPTS_ADDON_DIR and that's why we started to use arguments (WILD GUESS).

[BigRoy]

but the force_startup_script.py is to execute the maxscript(startup.ms) to register the environment for the ayon plugins in 3dsmax....so it can't be removed.

My point was merely that: what if that script just exists because we were never able to pass the PYTHONPATH before just because we actually were doing it wrong to begin with? I'm unsure what the startup.ms script does and WHY it's required over any other way. The file itself doesn't seem to describe what it fixes nor what we had tried instead of it.

[antirotor]

If I remember correctly that was because of the compatibility with old versions of max - they've introduced ADSK_3DSMAX_STARTUPSCRIPTS_ADDON_DIR from 2022. Prior to it you had to add command line argument or something like that. Also not all versions were passing PYTHONPATH and the startup script had to be maxscript. But with AYON and newer version, we should set ADSK_3DSMAX_STARTUPSCRIPTS_ADDON_DIR and PYTHONPATH in add_implementation_envs() I guess.