Jump to content

Phoenix125

Pathfinder
 View Profile  See their activity

  • Content Count

    144

  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Phoenix125

  1. Phoenix125
    Again, sorry for delay in my response. Started a new job this week and has taken up pretty all my time. Anyway... Thanks for the update on running ASUU with ChromeSDK's prog... pretty neat that you were able to get them working simulataeously! .. Well, mostly Re: Virus notice: Pretty much any program written in AutoIT (the programming language that ASUU is written in) gets flagged by Windows Defender... even my 2 line mouse mover program gets flagged. I submitted a version a few months back and Microsoft approved it within a few hours, but they said that end users will only get the exception added to Defender with next update.. approx. monthly. The except only applied to that version, so I would have to resubmit for all versions. Since I was putting out updates 1-2x/wk and users only updated Defender database monthly, it was pointless. In my Discord, I have a channel dedicated to the explanation with screen shots of various other antivirus programs saying ASUU is safe. As for the Crash Watchdog... I could easily add an option to have it NOT restart grids shutdown by ChromeSDK's prog. I've added it to my "Wish List". Thanks!
  2. Phoenix125
    Sorry for the late reply.. was on vacation (sorta). I have looked into this awesome idea, but there are a couple main problems: 1. Whenever someone logs out, the grid he/she was in would would have to remain running so they could log back in. With several players, you eventually end up needed most or all servers running. 2. Atlas does an awful job or reporting which grid a player is in or was last in. Quite often, Atlas doesn't "remove" a player from a grid when they cross into another, but apparently puts that player into a "sleeping" status. This causes the player to appear in multiple grids which is very hard to track when moving back into a previous grid. I am working on using the redis to get the last known grid and last online time, which will mostly eliminate this problem, but I just haven't had time to finish that code yet. If anyone reading this has a solution, I'd love to hear it. Thanks for the cool idea.. just not sure I can get it to work well.
  3. Phoenix125
    @shine brightThanks for the feedback. The util should only use around 40-50 MB of memory. Below is a screenshot of ASUU in Task Manager on my 5x5 test server (Windows Server 2016) managing 25 grids. If you are referring to the amount of RAM the Atlas server itself is using, unfortunately the util (ASUU) has no influence on that. The only way I know to reduce RAM usage for Atlas itself is to force Windows to cache some of the RAM to the HD using various utilities, such as Mem Reduct: https://www.henrypp.org/product/memreduct If ASUU is consuming a lot of RAM, please let me know. No one yet has reported a memory leak. Thanks.
  4. Phoenix125
    @Yet The only other thing I can think of, that I didn't include in my previous post, is I added a new beta way to check for online players. It works great for me, but many people are saying it doesn't work for them (I've fixed that in the next release), but check the following setting in the AtlasServerUpdateUtility.ini file or the [CONFIG] button: Check for, and log, online players? (yes/no) ###=yes Check for online players every _ seconds (30-600) ###=60 Check for online players on remote servers? (yes/no) ###=no Use redis-cli for improved accuracy of online players? (yes/no) ###=no Make sure that says No. Otherwise, I am sorry, but I'm at a loss. It is usually a NAT Loopback or firewall issue that causes that status to get stuck at "Starting"
  5. Phoenix125
    I do not understand what you were saying.. sorry. If you are wondering why it is not finding a grid, such as the [PID] -ERROR- Server 0,10 PID() NOT found... That means that the program was unable to find that server. ASUU scans all running Atlas servers and gets the server location from the title of the ShooterGameServer.exe process: If your concern is regarding the "Starting" status, then the problem is with RCON and below is some troubleshooting tips I drafted: What: The "Starting" status changes to "ready" when ASUU gets a valid response from the RCON "ListPlayers" command. - That's how it determines whether the server is ready For connections Or Not. Why: The cause is an error with RCON, which could include the following: - Wrong RCON port assignments. - Wrong RCON IP address. - Windows Defender firewall (or any any other firewall) is blocking ports. - No NAT loopback function with your router. - Wrong server password or typo in password. - The RCON ports are already assigned to another process (any other servers on same machine running same ports?). - Avoid using ports 27000--27100 because Steam uses them: https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711 The Fix: - Change RCON IP address in the AtlasServerUpdateUtility.ini (or click "CONFIG") to your local IP (ie 192.168.1.10, or 127.0.0.1): RCON IP (ex. 127.0.0.1 - Leave BLANK for server IP) ###=192.168.1.8 - Change the ports.. maybe some rouge process is using them! - In ASUU, click "TOOLS" then "Network Conn. Viewer" to display a list of all ports in use. Look for errors. - In ASUU, click "TOOLS" then "Duplicate Port Checker" to makes sure you do not have duplicate ports assigned. - Attempt to send an RCON command using the "Send RCON" buttons and observe the response: this might give a clue as to the cause. - Check the "Detailed Log" for responses to sending RCON commands. - Check the "Detailed Log" for the mcrcon.exe RCON commandline for correct port, IP, and password. example: 2019/08/27 14:48:16 [RCON] F:\Atlas Test Server\AtlasServerUpdateUtility\mcrcon.exe -c -H 192.168.1.30 -P 25710 -p AdMiN_PaSsWoRd "listplayers", Response:
  6. Phoenix125
    @TroubleSteve44yo here Atlas servers do not have local LAN support, like Ark and Rust do. Therefore, you will not be able to connect unless your router specifically has NAT loopback. Most routers don't. A quick test is to have someone else try to connect. If they can connect but you can't, then it's almost for sure the NAT loopback. If NAT is the issue, there are workarounds: https://forum.sector3studios.com/index.php?threads/workaround-if-you-cannot-join-your-own-dedi-server.4672/ If no one can connect, then it comes back to the basics.. which I'm sure you've troubleshooted a thousand times. If all else fails, you can try to run the server without ASUU by running the batch file in the \Batch Files (to run Atlas manually)\ folder of the util. Then try troubleshooting it manually. Good luck!
  7. Phoenix125
    Thanks everyone for the bug reports. Hopefully the latest version here will fix them! Just released! v2.0.1 (2019-08-28) STABLE and BETA branches being used again! Bug fixes (for real this time!). - Fixed: Still couldn't change the "Fast Discord" and "Use Redis for online players." (Thanks to Nyt for reporting) - Fixed: Redis-Server will not start automatically after v1.9.9c. (Thanks to @Yet for requesting) - Fixed: Line 42024 Error: Occurred when mod list in GUS was edited on Blackwood server instead of using wizard. (Thanks to XCITE and @Neitfallfor reporting) - Fixed: Blackwood: If mods were changed in the GUS.ini, the util didn't update the mod list. - Fixed: If ModList was changed in ServerGrid.json, the util would error. - Added: If status stuck at "Starting..." then util now displays a notice and opens a help file in default text viewer. - Added: If "Fast Method" of Discord causes error, the log now shows a recommendation to disable the "Fast Method"
  8. Phoenix125
    All your settings look good. FYI: "IsHomeServer" is not used by Blackwood... I should disable that option in the util for Non-Seamless servers The likely problem is that players need to select "Non-Atlas" servers when searching for the server. If other people can connect but you can't, then the issue is a lack of "NAT Loopback" from your router.
  9. Phoenix125
    @TroubleSteve @1ceMan_Za There are several reasons that an Atlas server won't show up on the server list. - The main reason is as you stated.. ports not being forwarded properly. - Avoid using any ports in the 27000 - 270100 range... Steam uses 27015 and 27030-27037 for its own purposes. https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711 If you're using Blackwood, all clients (players) have to select "Non-Atlas" servers when searching for the server. @Yet Thanks for reporting that. I will look into it and post a fix this evening (I have a long day at work today).
  10. Phoenix125
    FYI: AtlasServerUpdateUtilty (ASUU) now has official Blackwood support.
  11. Phoenix125
    Another update: v.1.9.9a Minor tweaks. - Added: Blackwood Wizard: Added "AltSaveDIR" option. (Thanks to @Neitfall for requesting) - Changed: Wizard: Changed the "Coming Soon!" description for Blackwood to the intended text. (Thanks to @Neitfall for reporting) - Fixed: Util Update: The util wasn't completing the shutdown before running updated util. (Unfortunately, this won't help until NEXT update.) - Added: Added Blackwood icon to "Select Wizard".
  12. Phoenix125
    @Neitfall Thanks for the feedback. I'll add a "AltSaveDIR" option... Good idea. And I completely forgot to change the text on the wizard select window... Lol. As for the ServerGrid.json file: Since Atlas Blackwood does not use the SG file (ASUU does, but not Atlas), I do not have it backup an existing SG file when installing/importing a Blackwood server (it DOES backup when switching from ocean to Blackwood). I didn't even think of adding the backup. I'll add one just in case. Thanks again.
  13. Phoenix125
    For those interested, I finally added Blackwood map support to AtlasServerUpdateUtility! https://www.playatlas.com/index.php?/forums/topic/47724-atlasserverupdateutility-asuu-server-manager-new-blackwood-backups-mod-updater-crash-detection-discordtwitch-support/
  14. Phoenix125
    New update... with Balckwood support!!! (finally!) v.1.9.9 New Blackwood Wizard! Try the new Blackwood map! v1.9.5 - v1.9.9 Highlights - New Blackwood Wizard! Start a Blackwood server the easy way. Automatically updates server and mods with Discord announcements. - Improved shutdown. Monitors save file to ensure saves started and completed. - Added Parameters Editor to Grid Configurator. Now even easier to modify GUS, Game, Engine files. - Several stability and bug fixes. - New startup logo.
  15. Phoenix125
    @Joew Alabel The utility is not yet ready for Blackwood. Most people have been able to get it to work using instructions posted previously, but I am working on the Blackwood Wizard now and plan to release it tomorrow. It has become a much bigger undertaking than I anticipated, but I wanted to make sure I do it right. So for now, just use the default AltSaveDIR naming scheme. If you need to, rename your existing folder. .. or just wait until later tomorrow and try the new version Thank you!
  16. Phoenix125
    Followup: Thanks to AceMan for helping Wicked.. the problem was due to using the router's IP address... for those having the saving issue. Thanks.
  17. Phoenix125
    V1.9.7 released. Critical Hotfixes! Stability release only.. no new cool stuff yet. Due to fixing these issues, I may not get the Blackwood EZ support done tomorrow.. might be Monday. Sorry. - Shutdown sequence had several bugs. - A few other minor stability improvements.
  18. Phoenix125
    v1.9.5 notes: - Improved shutdown. Monitors save file to ensure saves started and completed. - Added Parameters Editor (see below) to Grid Configurator. Now even easier to modify GUS, Game, Engine files. v.1.9.6 released! Hotfixes: Fixed Restart and Stop grid buttons, error if ServerGrid.json has "Templates Section. - Fixed: Rt-Click: "Stop Grid", "Start Grid", and "Restart Grid" were not working properly. (Thanks to Nyt, JOEW ALABEL, and others for reporting) - Fixed: If ServerGrid.json has " "serverTemplates": [" section, the util now ignores it completely. (Thanks to Daniel W for reporting and Daniel & Doublee for helping solve) Starting this weekend I plan to work on easier Blackwood support. Maybe even work on the Online Players redis integration! Just have a couple more busy days to get through.
  19. Phoenix125
    No.. unfortunately I haven't had time to get that done. I plan to have it completed by the end of the weekend. IN the meantime, here's the link to the previous post on how to get it to work with the ASUU:
  20. Phoenix125
    @Joew AlabelI did a major rework of the server shutdown process and I think I accidentally duplicated a variable. I hope to release a fix tonight. If not, it may not be until Friday afternoon Sorry. In the meantime, you can use "Stop Server(s)" Select button to close them. Starting grids and automated restarts fortunately work fine. @flex73The automated backups can only run every hour at most. You can choose day, month week, hours, and minutes, but only at most once and hour
  21. Phoenix125
    Thank you for the logs, but unfortunately the log was not very helpful since the program appeared to simply crash as you stated. I noticed, though, that the KeepAlive is noticing the crash but failing to restart ASUU (AtlasServerUpdateUtility). The KeepAlive log: 2019/08/06 09:28:41 WARNING! D:\AtlasServerUpdateUtility\AtlasServerUpdateUtility_v1.9.5.exe closed unexpectedly. Restarting program. 2019/08/06 09:28:41 AtlasServerUpdateUtility_v1.9.5.exe PID(0) started. Notice the PID(0). It's acting like it cannot find the file. Here's an example if what it should look like: 2019/08/06 23:09:49 AtlasServerUpdateUtility_v1.9.5.exe PID(36480) started. It's possible that Windows Defender or another antivirus is blocking. If not done so already, try adding the AtlasServerUpdateUtility folder your Windows Defender Allow list. It's also possible that the Windows Region (English vs Chinese) is causing issues, although I know of a couple other people in China using the program. If these solutions do not help, let me know. Thank you.
  22. Phoenix125
    @Yet I had never considered running Blackwood simulatenously with an existing map. I planned for running two instances of the util instead. I'll consider adding that.. thanks! As for your program crashing: I haven't had anyone report that before. Do you mind PMing me your AtlasServerUpdateUtility_LogFull_[date].txt file so I can try to troubleshoot? Thanks.
  23. Phoenix125
    @flex73The util has an automated backup option. It backs up the \ShooterGame\Saved\ folder (minus the ocean.A1.1500.atlas backup files), the redis folder, and the util's config files. It can also do full backups of your Atlas installation and any other folders you wish to add.
  24. Phoenix125
    @merlin66676 It works with Blackwood if you do the following. I will be updating it for easier integration, but it might be a few days. Here's a post I placed on my Discord server: For those wanting to use the new Blackwood Single Player, do the following until I update the util: 1. Use the wizard to install your server (even if an existing server.. this will create the temp ServerGrid.json file). 2. After Atlas installation has completed, make the following changes to the ASUU.ini file: [ --------------- GAME SERVER CONFIGURATION --------------- ] Atlas extra command line parameters (ex.?serverpve-pve -NoCrashDialog) ###= -log -server -NoSeamlessServer Map Name ###=Blackwood Import RCON ports from GameUserSettings.ini files? (yes/no) ###=no Server RCON Port(s) (comma separated, grid order as in ServerGrid.json, ignore if importing RCON ports) ###=25710 3. Then restart the util. When you get the following popup, select NO (to the prompt posted below). (Thanks Aceman, noelpy, and others for the info) 4. (Optional) Copy the \AtlasUtilFiles\ServerGrid.json file to the \Atlas Server\ShooterGame\ folder.
  25. Phoenix125
    @flex73The Crash Watchdog is restarting your servers. That usually occurs when the RCON ports are not forwarded or some other RCON issue. Basically, if the util gets no response to the "ListPlayers" command for 5 minutes, it assumes the grid crashed and will restart it. Ideally, try to find out what is causing the RCON problem, but you can also just disable the crash watchdog. In the Config (AtlasServerUpdateUtility.ini file or "CONFIG" button in main window), change the following to zero (0): [--------------- CRASH WATCHDOG ---------------] Number of failed RCON attempts (after grid had responded at least once) before restarting grid (0-Disable, 0-5) (Default is 2) ###=0 Minutes to wait for RCON response before restarting grid (0-Disable, 0-10) (Default is 5) ###=0 Number of crashes before disabling grid (0-Disable, 0-5) (Default is 3) ###=0 If you want, you can look for the response when you send "ListPlayers" via RCON using the "Send RCON" button. It may give a clue as to why the RCON was/is failing.
×
×
  • Create New...