-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
application could not be located, please specify the location of SE application file. #180
Comments
Due to the 2019-08-23 update of Space engineers containing the Economy update, I can no longer get SEToolbox working. SEToolbox is officially dead. I've looked into the changes in SE, but cannot see a way ahead to get it working again. |
It can be "fixed" by reverting to older version - only 72 Mb But new worlds will give this error
|
if it gives a error with new worlds then it isn't fixed |
@Roshag reverting Space Engineers the game or SE Toolbox? |
Space Engineers. And make a copy of it. But it won't open new saves because of faction relationships |
Not fixed yet ? |
So there will be no fix to this problem then, or is it being worked on |
I am still having this issue as well. |
This'd be a real shame if it's not resolvable :/ |
My steam games location are under my D: drive under a raid system.
I have never had any issues with SEtoolbox until now, it reads the location fine but says its invalid.
D:\SteamLibrary\steamapps\common\SpaceEngineers\Bin64\SpaceEngineers.exe
results , says invalid location. never had this issue before.
https://imgur.com/lHSCFcP
When directing it to the exe I get this.
the continue tab will not highlight for me to select continue.
https://imgur.com/dZGLfbt
I have tried both versions of latest SEtoolbox the msi and zipped file with same result.
I will not re-install the game to my C: as space engineers changed the way mods are installed and location has moved from appuserdata to to steam workshop folder itself. this is why all my games are under my raid system to keep my SSD from filling up and taking space.
The text was updated successfully, but these errors were encountered: