• Content count

  • Joined

  • Last visited

Community Reputation


About spiedie

  • Rank
    Silver Initiate
  • Birthday

Recent Profile Visitors

125 profile views
  1. PC

    @[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?
  2. PC

    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.
  3. PC

    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.
  4. Running via commandline is already possible:
  5. PC

    Had a crash WAR-1202253. It included a DXDiag timeout (what looked to be a separate error after an Assertion Failure). I tried dxdiag and it is indeed very slow, but finishes after about a minute. Is this timeout in the game or only for the crash handling?
  6. PC

    Its not an issue with your system, 8 is the engine limit (try running a DXDiag scan, it should take a really long time, after killing all servers run it again, should be fast). It is possible to run more however, though id have to ask @[DE]maciejs if it is allowed. Looks to be working just fine for now. He hasn't responded in a while though (much needed vacation? :P)
  7. PC

    Yea, you can run as many as you want on a single account
  8. PC

    I mostly connect to @TheRoaringLions, and he to me and some other guy. Kinda weird :P
  9. Your missing some, add these: -fullscreen:0 -dx10:0 -dx11:0 -threadedworker:1 -cluster:public -language:en Its probably the -cluster one that is required, though @[DE]maciejs should be able to tell us (and fix the guide :)).
  10. PC

    You can restart one with the following, just make sure to change bold stuff.
  11. PC

    I have a feature request looking at latest patch notes: a dummy game mode that doesn't accept players, just for testing. I was using TDM_Alt lately as then i didn't have to kick players out that joined in the middle of a test.
  12. PC

    So i was testing killing instances and starting other ones without affecting existing ones (change game mode being hosted), and got some weird messages. Having a number of instances started and waiting for players, starting another one using the engine (-applet etc), every other instance gets Budget overrun. Can i ignore that or is that gonna be an issue?
  13. PC

    Did some more testing, looks like if the file ends with the number it fails to run the last one. It has to end with a comma or newline. The following runs 4 instances. (no newline at end of file)
  14. PC

    The format for the -dscfg file is VERY strict :P looks like every line has to end with a comma, and key : value require the spaces. In the directory relative to where Launcher.exe is started from. Having this script on my desktop: I needed ServerConfig.txt to be on the desktop.
  15. PC

    Thanks :) I did try some of that stuff and It all works (with some minor issues). I have everything set up to host all game modes anyway on different VMs with a single click, so ill leave it as is for now.