era5or

mail sent, forgot to include link to thread sorry, but enough detail in log too see the error... also, your client/server detects windows 10 as windows 8.1+ if that happens too have any effect is unknown..

Not so much a bug report as such, but figured it could be causing memory/performance issues. This suddenly appeared in my server log while playing on a dedi server hosted on my local machine for a friend and myself.. 5 failed to aquire C:\...\FactionDatabase.cpp: 485, accessMutex after 1000000 tries 5 failed to aquire C:\...\FactionDatabase.cpp: 485, accessMutex after 2000000 tries 5 failed to aquire C:\...\FactionDatabase.cpp: 485, accessMutex after 3000000 tries 5 failed to aquire C:\...\FactionDatabase.cpp: 485, accessMutex after 4000000 tries

update on remote server issues it seems ports do not work see screen grab http://imgur.com/75FDEOq as you can see ive set port in bat file as u said, this seemed too fix the issues, visualy anyways.. as the server shows game port stays as 31000 however when i use a port sniffer it infact is not using any port except default steam ports... so at present it has no gameport for anything too connect too... kinda weired!

I can confirm Beta branch now shows up and stays listed just fine now :P

adding -- port 31000 too the server bat file seemed too clean up the port issue. however the server is still not listing from my machine at home... also the public server showsup in list but then becomes unavalible very quick? another thing also, is I am unable to connect too the public server that shows up, but im assuming this that server is not running beta

ok just done another test, results quite intresting... installed and run steamcmd version on local machine at home - setup using launcher gui you provided.. all worked just fine, ports and logs showed it using 31000 and steam loged on just fine.. zipped up and coppied the entire install and the roaming galxy files too my remote box.. unpacked fine etc... ran the server with exactly the same setup/configs that were created on local PC runs fine with 1 big exception! the game port RESET too 27000 I repeat this is identical install and build of ini files, as i have simply copied the entire 2 folders onto remote PC.. What could be causing the reset ? Home_Log_Sat_Feb_11_20-54-18_2017.txt Remote_Log_Sat_Feb_11_13-01-06_2017.txt

steam install was left at default settings steam cmd was set to 31000 as per my firewall routing etc and I had steam open and running minimzed during the 2 tests

Quite funny looking at the logs, cause now it would seem that the forced port fails too keep the port, but authenticates too steam fine, where as the standard port fails all together lmao

Ok just done complete reinstall of both options for running the server... Option 1) Steam Client Install via steam its self and downloading Beta version. Option 2) Steam CMD Install via steam command using appdata beta beta validation command. Both seem too download and install fine, however there are a lot of files in different places for one... and both come out with different results when trying too run the server! I have attached both output files... Steam_CMD_Install_Sat_Feb_11_12-37-41_2017.txt Steam_Client_Install_Sat_Feb_11_12-35-37_2017.txt

When trying too load server via steamcmd app_update 565060 -beta beta just gives me the non beta version for some reason? different app id for beta maybe?

@ShutdownOnFailedCommand 1 @NoPromptForPassword 1 login anonymous force_install_dir "C:\Program Files (x86)\Steam\steamapps\common\Avorion" app_update 565060 -beta beta validate quit seems to get the normal version not beta, so I cant get it via that command unless u have a differnt App ID number for the beta client I can use

OpenGl error, probably due to it being windows 7 box on a remote machine that has no gfx output card :P

I ran the steam client, loged in with my login/pass, selected your game, then opt into beta etc. It downloaded latest etc. then launched server using defaults, then closed the server down, changed the port and re-run the server. and boom thats what I got above.

Ok endedup using steam too download the beta, via my steam client login etc, which has installed fine. Still has issues connecting though from external sources.. Ive run CurrPorts which shows the following AvorionServer.exe tcp 31000 too local address 0.0.0.0 AvorionServer.exe udp 27003 too local address 0.0.0.0 AvorionServer.exe udp 31000 too local address 0.0.0.0 Logs shows Sat Feb 11 10:42:25 2017| Enabled Traces: Sat Feb 11 10:42:25 2017| Avorion server Beta 0.10.2 r7493 running on Windows 7 starting up in "C:\Users\eRa5oR\AppData\Roaming\Avorion\galaxies\dedi" Sat Feb 11 10:42:25 2017| CPU: GenuineIntel 1 Cores Sat Feb 11 10:42:25 2017| name: Avorion Server Sat Feb 11 10:42:25 2017| seed: doPHNEVuuG Sat Feb 11 10:42:25 2017| port: 31000 Sat Feb 11 10:42:25 2017| max online players: 10 Sat Feb 11 10:42:25 2017| save interval: 600 Sat Feb 11 10:42:25 2017| broadcast interval: 5 Sat Feb 11 10:42:25 2017| max loaded sector time: 300 Sat Feb 11 10:42:25 2017| weak update: yes Sat Feb 11 10:42:25 2017| worker threads: 4 Sat Feb 11 10:42:25 2017| generator threads: 2 Sat Feb 11 10:42:25 2017| difficulty: Veteran Sat Feb 11 10:42:25 2017| infiniteResources: no Sat Feb 11 10:42:25 2017| collision: 1 Sat Feb 11 10:42:25 2017| access list: Blacklist Sat Feb 11 10:42:25 2017| public: yes Sat Feb 11 10:42:25 2017| authentication: yes Sat Feb 11 10:42:25 2017| listed: yes Sat Feb 11 10:42:25 2017| steam networking: yes Sat Feb 11 10:42:25 2017| administrators: 'ra5or' Sat Feb 11 10:42:25 2017| Starting up 4 worker threads... Sat Feb 11 10:42:25 2017| Loading jumping entities... Sat Feb 11 10:42:25 2017| Galaxy initialized. Sat Feb 11 10:42:25 2017| SteamGameServer_Init call failed Sat Feb 11 10:42:25 2017| Error starting steam-based networking. Defaulting to standard TCP/UDP protocols. Sat Feb 11 10:42:25 2017| Further steam-related error messages can be safely ignored. Sat Feb 11 10:42:25 2017| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 Sat Feb 11 10:42:25 2017| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 Sat Feb 11 10:42:25 2017| Everything looks and seems fine but still unable too establish a connection without using my VPN network :(

so too make sure im getting the correct version here... this should be my install script ? Using Naggerknife's Server Installer -btw @ShutdownOnFailedCommand 1 @NoPromptForPassword 1 login anonymous force_install_dir "C:\Program Files (x86)\Steam\steamapps\common\Avorion" app_update 565060 -beta quit

0.10.2 r7448 ? as my dedi is still trying too use 27000 according too logs Sat Feb 11 09:16:44 2017| Enabled Traces: network Sat Feb 11 09:16:44 2017| Avorion server Beta 0.10.2 r7448 running on Windows 7 starting up in "C:\Users\eRa5oR\AppData\Roaming\Avorion\galaxies\dedi" Sat Feb 11 09:16:44 2017| CPU: GenuineIntel 1 Cores Sat Feb 11 09:16:44 2017| name: Avorion Server Sat Feb 11 09:16:44 2017| seed: 0KJcYI6zqm Sat Feb 11 09:16:44 2017| port: 31000 Sat Feb 11 09:16:44 2017| max online players: 10 Sat Feb 11 09:16:44 2017| save interval: 600 Sat Feb 11 09:16:44 2017| broadcast interval: 5 Sat Feb 11 09:16:44 2017| max loaded sector time: 300 Sat Feb 11 09:16:44 2017| weak update: yes Sat Feb 11 09:16:44 2017| worker threads: 1 Sat Feb 11 09:16:44 2017| difficulty: Veteran Sat Feb 11 09:16:44 2017| infiniteResources: no Sat Feb 11 09:16:44 2017| collision: 1 Sat Feb 11 09:16:44 2017| access list: Blacklist Sat Feb 11 09:16:44 2017| public: yes Sat Feb 11 09:16:44 2017| authentication: yes Sat Feb 11 09:16:44 2017| listed: yes Sat Feb 11 09:16:44 2017| steam networking: yes Sat Feb 11 09:16:44 2017| administrators: Sat Feb 11 09:16:44 2017| Warning: Your server does not have an administrator assigned. Sat Feb 11 09:16:44 2017| Starting up 1 worker threads.... ok Sat Feb 11 09:16:44 2017| Loading jumping entities...no file "C:\Users\eRa5oR\AppData\Roaming\Avorion\galaxies\dedi\jumps.dat" found Sat Feb 11 09:16:44 2017| ok Sat Feb 11 09:16:45 2017| Server UDP: Starting up at port 27003. Sat Feb 11 09:16:45 2017| Server UDP: Starting up receiving. Sat Feb 11 09:16:45 2017| Server UDP: Resolving localhost, port: 12345 Sat Feb 11 09:16:45 2017| Server UDP: Send packet to 127.0.0.1, port: 12345, size: 1024 Sat Feb 11 09:16:45 2017| Server UDP: Some packet received from 127.0.0.1, size: 0 Sat Feb 11 09:16:45 2017| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 Sat Feb 11 09:16:45 2017| Game Port: 27000 Sat Feb 11 09:16:45 2017| Steam Port: 27021 Sat Feb 11 09:16:45 2017| Steam Query Port: 27020 Sat Feb 11 09:16:45 2017| Polling Port: 27003 Sat Feb 11 09:16:45 2017| Sat Feb 11 09:16:46 2017| Server connected to Steam successfully Sat Feb 11 09:16:46 2017| Server is VAC Secure! Sat Feb 11 09:16:46 2017|

Could you explain a little more on this as I dont see how binding to IPS will help custom ports issues, surely all that will do is bind the server.exe too a dedicated IP, which on a multihost system would be a local internal IP.. which would then have the same issues of firewalls/portforwarding etc of custom ports? either way. when will the beta version be going live so I can see if this bind to ips will actualy help or not :P

Thanks for the reply Aki, I can at least implment the price side of things for now, but yeh i think its smart waiting too see how the faction/alliance stuff may change in next update. Im currently waiting on the custom ports too work, as atm it seems too fallback to a hardcoded steam default ports no matter what im doing :(

Aki, Im a fan of your simple sethome script as it works 100% server side, however is there any chance you could either modify too my needs or point me in the right direciton too dig in and modify it somewhat :) Heres what im thinking... (So I can have the command setup as public use) 1) Charge player money amount for activation (customizable via script) 2) Upon activation reverse faction standing of current home system (something too do with home.x home.y when I was looking at code) 3) Upon activation add faction standing for new home system, eg closest faction too where command is issued. Logic would go something like this.. Cmd Activated Grab player current home faction too args Grab player current sector faction too args If money check correct then apply faction changes else fail with error msg regarding money etc Something like that, Im sure you get the idea of what im sugesting :)

How would one add the salvage captin option as a server side only mod, eg client doesnt need any files. If its at all possible?

Have you tried setting up a new server with same SEED as old, then copying over the player.dat files from the old too the new... May not 100% fix the issue but should at least keep player stats etc and the galaxy layout I would think.

I believe the admin is ment too be the name you use in your client too login not your Steam ID if you wish too add the steam ID manualy you can do this via the admin.xml in your %appdata% roaming area. be sure too add it in this area of the file using Notpad++ as the file is XML <administrators> <admin name="PLAYERSNAMEINCLIENT" id="STEAMID"/> </administrators>

Your problem is your target starting directory, it should be the locaiton of the server application NOT the roaming profile. If you are using windows, setup a shortcut too AvorionServer.exe with a target simlar too this "C:\Program Files (x86)\Steam\steamapps\common\Avorion\bin\AvorionServer.exe" -t network --galaxy-name dedi As you can see mine is stored in my steamapps folder inside a folder called Avorion, as it runs dedicated. the -t network will give you a little more network output information also too the logfiles you would normaly see in the roaming directory. name of my galaxy is simply -> dedi <-- change this too name of your save folder inside the roaming profile area

Also having same issues as above, quite frustrating, as I have multiple servers running for different games, so I need a custom port solution asap... Log file included... seems too work fine via my VPN though, most likely cause the VPN client/server is routing the ports automaticly serverlog_Wed_Feb_01_09-31-29_2017.txt