• Content count

  • Joined

  • Last visited

Community Reputation


About spiedie

  • Rank
    Silver Initiate

Recent Profile Visitors

355 profile views
  1. Dedicated Conclave Servers

    I've been having a few issues loading instances lately. Sometimes they freeze as seen in the first spoiler (last part of the log, unedited including the times at the end). This results in following instances to start and freeze like in the second spoiler (full log, freezes after "Found 26 cache blocks..."). Not only does freezing like this cause an instance to be inaccessible, but if more are launched after, it takes down all 5 other instances running on the engine (all players in those 5 instances disconnect and host migrate, see third spoiler). Is it possible to have these loading actions time out at some point? afaik, disk activity is 0%, so it seems to be a locking issue. Having these instances close themselves would already solve a lot of the issues.
  2. Dedicated Conclave Servers

    For reference, 24 instances at default (60fps, highBandwidth=0) during quick steel event (6 players per instance) was about 12 Mbit/s upload. I think 8 players was 600kbit/s per instance (this was during snowball events). Total data during last snowball event, 4 day weekend (close to new years eve?) was 300GB uploaded and 120GB downloaded.
  3. Dedicated Conclave Servers

    The 18+ instance windows changing their title (the fps counter) 240 times a second appears to be too much for the gpu to handle. You likely wont ever get this issue tho. Minimizing the windows also fixes this.
  4. Dedicated Conclave Servers

    I run up to 24 instances at 120Hz. At 240Hz i started having issues with the gpu (server hardware integrated, just meant to produce output, its really bad) when running 18 or more instances. Note that this is a dual socket E5-2670 (v1) system, so 16 cores and 32 threads. For comparison, most modern quad-core systems can run 6 instances at 60Hz.
  5. Dedicated Conclave Servers

    I've been working on tools for hosting for a while now. As it's quite stable at the moment (no changes since U21), i might as well share it here now. It's still a work in progress, and might not be as easy to set up as i want it to be (there is an app included to do the required setup). Source code Soon (TM). https://github.com/Spiedie/WarframeServerManager @dreamquestwhen choosing VPS, make sure it's not IP banned by DE. I know AWS EC2 is banned. Estimated requirements from the my readme: ~500-700 MB ram per server instance + OS ram requirements ~1 core per server instance ~20GB disk space per 6 instances you want to run If your server is running windows, you don't need any VMs, making ram requirements a lot easier to manage (using 9GB ram for 20 instances on windows 8.1). @maciejs "Free for all" is kinda confusing in the selection, as Annihilation is commonly referred to as Free for all (FFA). I think "Public" would make things less confusing.
  6. Dedicated Conclave Servers

    For anyone with issues with their servers, change "version=7" to "version=8" in your DS.cfg :)
  7. Dedicated Conclave Servers

    You are running one of the variant modes. those shut down after 5 minutes when they're not active. I think DM variant is the default mode if nothing is specified. Have you set up your DS.cfg? (%localappata%\Warframe\DS.cfg)
  8. Dedicated Conclave Servers

    Create a shortcut to the Warframe exe (Warframe.exe for 32 bit, Warframe.x64.exe for 64 bit). In target, add " -cluster:public -allowmultiple" the the end. so if installed in C:\Program Files\Warframe, it looks like Its a bit different when using steam, but same idea For launching servers, there is a bunch of info here: Another tip is to launch a server using the launcher, exit (press Q while having the server selected) and check the first line in the logfile (%localappdata%\Warframe\DedicatedServer.log). It shows you exactly what is given to the process to launch the server.
  9. Dedicated Conclave Servers

    Results for the day...
  10. Dedicated Conclave Servers

    Is it possible you need to patch it first? I found a few of those log entries in my logs, and for each of them i got another log ~20 minutes later with a different build version.
  11. Dedicated Conclave Servers

    Kind of expected that. Oh well, time to work more on hosting apps :) Speaking of which, any chance instances can exit gracefully using windows commands? taskkill is supposed to send WM_CLOSE, but still kills the instance immediately. How bad is it to force kill the server instances in terms of unclosed connections etc (only if they have 0 players)?
  12. Dedicated Conclave Servers

    @[DE]maciejs Are all AWS and other cloud provider ips banned? I'm currently trying hosting on AWS and get error 403 when patching. Same for checking leaderboards. I'm assuming they are banned due to previous DDoS attacks. Is it possible to unban specific ips that people want to use for hosting?
  13. Dedicated Conclave Servers

    @[DE]maciejs What is the expected behavior of running the launcher with -headless without -dedicated? Ive been using that to patch-only on systems without gpu. Right now it patches headless, then starts the game normally, which fails without gpu (which is exactly what i want). The issue is that when using this with remote desktop, the launcher hangs on "Warframe can not be run remotely." when trying to launch the game. Is this the expected behavior? If not, could there be a -headless -patchonly option of some sorts?
  14. Dedicated Conclave Servers

    Thought id share my minimum spec requirements test. So i tried hosting on a Pentium 4 3.4Ghz (2004) yesterday and it ran surprisingly well. At 7 players it reached 100% cpu at times but was at >55 fps all the time. Gameplay was actually good, except for some joining from NA to EU.
  15. Dedicated Conclave Servers

    So i encountered this when shutting down a server with players in it (Q): sometimes after "ok to exit" the server starts spot-loading a bunch of stuff that was just cleared from memory, before clearing it again and exiting.