SE Server Extender logs are inaccessible

[Zach Risher]

Server Extender logs normally deployed to DedicatedServer64/logs are not showing up in file-manager with the rest of the dedicated server logs. I heard they used to be, definitely haven't seen them for the past few weeks that I've been using this tool.

Normally it wouldn't be much of an issue, but with all the current SESE bugs it would be nice to take a look at it.

[remygrandin NA]

The log have changed folder since the project retake of dodexahedron (which is doing a great job as well as tyrisis previously). In the current version, log are diferentiated by instance but in their name only. If you whant the file to go back where they where, i invite you to create an issue on the SESE github page (https://github.com/SEServerExtender/SEServerExtender/issues)

[Zach Risher]

I don't really care about where SESE puts them, I just need them to available through SESM. If you can work with the new naming convention, that's fine. If not, would you mind opening the issue? I think he'd take a request from you more seriously.

[remygrandin NA]

I'm currently deep diving into sese code to try and find the issue about it currently not starting at all as a service. While browsing the code, I found some interesting things that I will try to mod and adapt for it to be able to start without parameter as soon as the main bug will be out. I will also look if I can find a way for sese to save to the server folder it's log as it was before. I'll keep you posted

[Zach Risher]

Yep, understood you're in the middle of a lot of integration work, and I really appreciate all of that!

[remygrandin NA]

Fixed in 3.7.2

[Zach Risher]

Thank you! Works great, just in time for me to get a little debug information on why Extender stopped working again all of a sudden.

#!

23:05:31.5743|Error|SEModAPIInternal.API.Server.ServerAssemblyWrapper.ReflectionUnitTest|System.IO.FileNotFoundException: Could not find file 'C:\Windows\system32\SpaceEngineersDedicated.exe'.

Yay! : )