Sometimes a PSSE won't open after install. This is almost always caused by an unexpected Python configuration.
If you're struggling with MOD, see the MOD Debug Notes
Behavior:
- Start PSSE
- result: PSSE splash screen appears, then PSSE instantly closes.
This one is painful because there are no error message. The best way to get some usable error messages is to run PSSE in the command line.
Open cmd.exe then run this command:
"C:\Program Files\PTI\PSSE35\35.4\PSSBIN\pssecmd35.exe"
If you see a python error about the encoding library, this section is for you.
This bug happens because the Python version that PSSE finds is not compatible. You can fix this by setting your
user environment variable PYTHONHOME to the location of your Python3.9 64bit installation.
Make sure you set your user variables not the system variables. To set env variables see Google
Setting PYTHONHOME can sometimes have undesired behavior. You can also launch PSSE from a bat file that looks something like this:
SET PYTHONHOME=c:\Python39
start "" "C:\Program Files\PTI\PSSE35\35.4\PSSBIN\PSSE35.exe" %*
When you start PSSE it adds the the PATH found in this registry key to your python sys.path:
> reg query HKEY_CURRENT_USER\SOFTWARE\Python\PythonCore\3.9\InstallPath
HKEY_CURRENT_USER\SOFTWARE\Python\PythonCore\3.9\InstallPath
(Default) REG_SZ c:\Python39\
If this registry entry points to the incompatible version of Python it will probably cause issues.
PSSE seems to ignore the PATH env variable when it looks for the python install it's going to use.