Jump to content

Morgrhim

Pathfinder
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

9 Neutral

About Morgrhim

  • Rank
    Landlubber

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The post I made that you quoted and changed your startup to was meant specifically for the person I quoted. I modified his startup line to include the correct map. Because he hadn't specified Ocean his server was trying to start the test map.
  2. It's trying to load the test map, you need to specify Ocean: ./ShooterGameServer Ocean -GridConfig=ServerGrid.json
  3. I should have clarified: removing libcurl4 is only really an option if the machine is a dedicated hosting box for Atlas. I would definitely not recommend doing this in an environment where other apps will share the OS.
  4. Mind sharing what distro you're using, including the version?
  5. I would suggest anyone wanting to run this on Linux do two things: 1) If possible, run redis on a separate machine. It's an in-memory database system. While it is highly optimized to have a small footprint, this still means it will be using RAM that your ATLAS server could be utilizing. 2) Read the docs at https://redis.io/topics/quickstart on setting up redis. The guide uses *nix as an assumption for OS, so following it shouldn't be too hard. It covers configuring the server and securing it. That's odd. The seg fault I'm getting is Ubuntu 18.04. It's also referencing the client appid in the error even though I'm using 1006030 as the appid.
  6. For anyone getting something similar to the following: ./ShooterGameServer: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/atlas/ShooterGame/Binaries/Linux/libaws-cpp-sdk-core.so) Your linux distro uses libcurl4. You need libcurl3 to run this. You will need to remove libcurl4 (For ubuntu this means removing libcurl4 and libcurl4-openssl-dev), and then install libcurl3. This error will go away once you do that.
  7. Using the following to install this package: steamcmd +login anonymous +force_install_dir /usr/atlas +app_update 1006030 validate +quit I get the following running ShooterGameServer: Using binned. 4.5.1-0+UE4 7038 3077 408 10 [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. Setting breakpad minidump AppID = 834910 Signal 11 caught. EngineCrashHandler: Signal=11 Segmentation fault (core dumped) It would appear the server is actually being downloaded as a client using AppID 834910 and trying to verify the steam client is running.
  8. This is incorrect. The quest markers work just fine on unofficial servers. You have to convert the coordinates to a 0,,1 value for the quest JSON, which a lot of people aren't doing. This causes the markers to be off. Once you have a PVE island, you need to get the X and Y coords in the editor and then do this: (Quest X Value) = EditorXCoord / (Cellsize * Numgrids) where cellsize is your cellsize in Project->Edit and Numgrids is the number of grids you have on that axis. This should return a value between 0 and 1, which is what you need to use in the json for the quest. You also need to make sure the island you're measuring uses the same PowerstoneIndex as the entry in the json, or it will be weird.
  9. Are you guys talking about the ships of the damned? I keep hearing people refer to "ghost ships", there's only one ghost ship and unless you made a ship path and assigned its blueprint it won't spawn at all. Those little glowy green ships are Ships of the Damned.
  10. This section is for unofficial dedicated servers hosted by the community. Asking about official server fixes here probably won't get you an answer.
  11. How many people do you have on your server at any given time? Also, your CPU has hyperthreading, meaning the PC sees 12 logical cores, not 6. My measurements are based on a 7x7 grid with an average of 60 people on at any given time (testers from before I went live).
  12. Eh, I wrote a powershell script. Make changes in one file, push it to all servers
  13. This does not help when changes are needed after all the grids are up and running. I have a solution now. I wrote a tool to push updated inis to all my servers at once.
  14. There is nowhere near enough information here for anyone to help you: 1) Where do you have steamcmd installed? 2) Where are you running the steamcmd command from? 3) What are the contents of the bat file you're using to run steamcmd?
  15. Yes. I have a total of 264 cores and 3TB RAM to allocate. I'm running 8vCPUs per VM, and 24GB RAM for 4 instances, 57 VMs total. And yes, they are all 1400000.
×