Inicio Explorar Axuda
Iniciar sesión
goingbrokegames
/
o3de
Fork de O3DE/o3de
3
0
Fork 0
Ficheiros
Rama: development
Ramas Etiquetas
o3de
/
Gems
/
AtomLyIntegration
/
TechnicalArt
/
DccScriptingInterface
/
3rdParty
/
Python
/
README.txt

README.txt 2.3 KB
Permalink Histórico Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243 
  1. DccScriptingInterface (DCCsi)
    2. 

  2. 

  3. This location can be extended with additional 3rdParty Python Utils, Tools, Packages, etc.
    4. 

  4. 

  5. These are not installed or distributed with O3DE
    6. 

  6. 

  7. However, there is some stubbed scaffolding in place.
    8. 

  8. 

  9. This is a bootstrapped sandbox for installing python libs (version bootstrapped procedurally):
    10. 

  10. C:\Depot\o3de-engine\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\3rdParty\Python\Lib\2.x\2.7.x\site-packages
    11. 

  11. C:\Depot\o3de-engine\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\3rdParty\Python\Lib\3.x\3.10.x\site-packages
    12. 

  12. 

  13. Any libs installed to this location will be accessible (use at your own risk)
    14. 

  14. 

  15. For instance, if you want to add py2.7 compatible libs, for apps like Maya2020:
    16. 

  16. "C:\Depot\o3de-engine\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\Tools\DCC\Maya\readme.txt"
    17. 

  17. 

  18. These pyside2-tools can be useful, and they are not pip installed, nor distributed.
    19. 

  19. "C:\Depot\o3de-engine\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\3rdParty\Python\pyside2-tools"
    20. 

  20. 

  21. pyside2-tools instructions:
    22. 

  22. 

  23. 1. clone the repo in this location: C:\Depot\o3de-engine\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\3rdParty\Python
    24. 

  24.     >git clone https://github.com/pyside/pyside2-tools
    25. 

  25. 

  26. 2. to use as a python package ...
    27. 

  27.     find this and copy:
    28. 

  28.         "< local DCCsi >\3rdParty\Python\pyside2-tools\pyside2uic\__init__.py.in"
    29. 

  29. 

  30.     and rename to this:
    31. 

  31.     	"< local DCCsi >\3rdParty\Python\pyside2-tools\pyside2uic\__init__.py"
    32. 

  32. 

  33. 3. add to PYTHONPATH: < local DCCsi >\3rdParty\Python
    34. 

  34. 	in .py something like: site.addsitedir(DCCSI_PYSIDE2_TOOLS)
    35. 

  35. 

  36. See: "< local DCCsi >\config.py"
    37. 

  37. 

  38. Substance Automation Toolkit (SAT) Instructions:
    39. 

  39. Substance has a licensed python API for automating material data workflows.  By default, their instructions cover installing it to a python 'system interpreter', however if we want to install it for use within the DCCsi (for custom tools) or even potentially to build inter-op and integrations with O3DE editors, we want to install it in a way that is accessible.
    40. 

  40. 

  41. Install Substance Automation Toolkit 3rd party library to DCCsi 3rdParty sandbox:
    42. 

  42. 

  43. > C:\Depot\o3de\python> pip install "c:\< path to >\SubstanceAutomationToolkit\Python API\Pysbs-2021.2.2-py2.py3-none-win_amd64.whl" --target="C:\Depot\o3de\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\3rdParty\Python\Lib\3.x\3.10.x\site-packages"
    44.