[asdfxD]

thanks for this post, vnc works but the window screen resolution is too small i guess. i installed windows server 2016 ENG, but did not tried a remote connection yet and check if the problem still occurs.

the question about the ram.

computer specs:
i7-7700k
16 GB RAM

dedicated specs:
i7-8700k
32 GB RAM

edit: the same happened on windows server 2016 as well, i switched back to linux.

[asheroto]

Version 6.5.2 Released
- Fixed update issue
- Create shortcut on Start Menu now creates a shortcut for all users
- seDirector now requires a 64-bit architecture of Windows (most computers are 64-bit nowadays)
- Removed 32-bit version of Visual C++ prerequisite in installer
- Reduced file size of installer
- Fixed bug in installer causing shortcuts not to be created
- Updated Chilkat library to version 9.5.0.84

[asheroto]

Originally Posted by asdfxD thanks for this post, vnc works but the window screen resolution is too small i guess. i installed windows server 2016 ENG, but did not tried a remote connection yet and check if the problem still occurs. the question about the ram. computer specs: i7-7700k 16 GB RAM dedicated specs: i7-8700k 32 GB RAM edit: the same happened on windows server 2016 as well, i switched back to linux.

That is weird. Using VNC you can just adjust the screen resolution by right-clicking on the desktop.

I am continuing to test this issue, it seems to only affect some computers.

[br5dy]

Version 6.6.0 Released
- Fixed issue that could prevent seDirector from launching correctly after installation
- Fixed issue launching FTP/SFTP sync, update check, and seDirector updater
- Removed UAC disablement requirement to run seDirector
- Removed Internet requirement for installer to run

[asheroto]

Version 6.6.0 Released
- Fixed issue that could prevent seDirector from launching correctly after installation
- Fixed issue launching FTP/SFTP sync, update check, and seDirector updater
- Removed UAC disablement requirement to run seDirector
- Removed Internet requirement for installer to run

[asheroto]

There was an update bug in Version 6.6.0. If seDirector fails to update automatically you may have to download seDirector from https://sedirector.net/ and reinstall it. Your settings will be fine.

Released 6.6.2
- Fixed bug preventing seDirector from updating
- Fixed bug causing menu to remain if force update is performed
- Fixed bug with UAC
- Fixed bug causing hotkeys to apply on main window when server properties is open

[asheroto]

Version 6.7.1 Released
- Added "custom game" option in Server Properties
- Added Troubleshoot -> "Can my server use this port?" to context menu of servers
- Fixed bug causing Server Properties to remain on top of all window

[Ryan2]

Is there a way to make it so the server only updates only if noone is in the server instead of kicking out the players?

[asheroto]

Originally Posted by Ryan2 Is there a way to make it so the server only updates only if noone is in the server instead of kicking out the players?

I'll add it to the suggestions channel on our Discord and see what kind of response we get from everyone.

The problem with updating only when the server is empty....

Example situation without immediate server update:
- There are 10 players on the server
- The server is out of date and needs to be updated
- User1 starts Steam, which automatically updates their game after launching
- User1 tries to connect to the server, but gets an error message and cannot connect to the server because the server is out of date
- You'd have to wait until all 10 players leave the server

So if it waits until the server is empty, which could be hours, then no other players can connect at all. If the AFK timer is not enabled/working and a user is just idling but AFK, it prevents everyone from connecting

Example situation with immediate server update:
- There are 10 players on the server
- The server is out of date and needs to be updated
- seDirector alerts players in-game and then shuts down, updates, and starts back up
- Update process usually takes less than 10 minutes
- User1 starts Steam, which automatically updates their game after launching
- User1 can connect immediately after the server starts back up

This way everybody can connect after ~10 minutes.

Another solution might be for us to delay the update process by 30/60 minutes, alerting users 30/60 minutes ahead of time, rather than immediately alerting players.

Would it work for you if you could adjust the delay before updating?

- The server is out of date and needs to be updated
- seDirector alerts players that an update is occurring in 30 minutes, reminds when 15 minutes remain, reminds users when 5 minutes remain, begins the 60 second countdown to update

[Ryan2]

My case is different because it will be for 1v1 servers. This program may not work in my case because I would need it to check if there is an update needed before players can connect to it.

The other features are quite useful to me so I will use it for that.

Thank you for the in-depth response.