Copy the map folder into the client Worlds folder. /home/sdtd/engine/Data/WorldsI will try that. Are there any changes I need to make to the config.xml ?
The Steam forum did mention that 7DTD is heavily dependent on single threaded performance, if I remember correctly.
I am running a 12core Threadripper 1920X overclocked to 3.7Ghz (instead of the base 3.5Ghx) with a gob of RAM, but I'm not getting very respectable performance so far (perhaps due to an older video card).
Just a thought: Would it be worth while trying to run a 7DTD server instance separate, as well as a client instance on the same system to offload the ...offloadable tasks to different threads on the CPU? ...thus making the game more multi-threaded at the expense of other resources?
thanks brotherHi there,
as it was suggested to me I open a new thread on my management scripts and native Linux server support. This is basically following up on the thread Dedicated Server without hacky workarounds though this is in Linux Bugs where it might be overlooked.
I created a full set of management scripts for a Linux based 7dtd server. This allows basic operations like starting/stopping as well as advanced things like a few event hooks.
(This also includes native Linux engine files so you do not have to use workarounds like Wine to run 7dtd. Unfortunately these files are 32 Bit only so far but at least they can be run on 64 Bit hosts without any problems.) No longer valid, 7dtd provides "built in" 32 bit and 64 bit Linux support since A14
For the full documentation on the management scripts go to https://7dtd.illy.bz/.
Regards,
Alloc
I may have missed this somewhere somehow, but I am trying to have 2 instances running at the same time on my machine, one with 7 day bloodmoon and one with a daily bloodmoon. I can't seem to find where i can set the daily instance to 1day though. I know I can do this with a local game on my computer, but I was wanting to run both instances on my server that is using Alloc's linux installation scripts.
Yeah, running dedi + your client separately might help with performance vs running a listen server from the game (assuming the system has good enough specs in terms of cores + especially RAM, which seems to be the case for you).I'm reposting this from a thread that was more based on performance, but I may get a better response here:
...I'm running on Kubuntu 21.04 (Early Adopter)
Just edit the config.xml for that one instance to say BloodMoonFrequency=1. I don't see what the issue would be without further infoI may have missed this somewhere somehow, but I am trying to have 2 instances running at the same time on my machine, one with 7 day bloodmoon and one with a daily bloodmoon. I can't seem to find where i can set the daily instance to 1day though. I know I can do this with a local game on my computer, but I was wanting to run both instances on my server that is using Alloc's linux installation scripts.
You may already know this but I just wanted to throw out that you should separate the running ports a bit .. don't put them to close together in sequence. As an example I like to put my servers at least 10 port numbers apart.I may have missed this somewhere somehow, but I am trying to have 2 instances running at the same time on my machine, one with 7 day bloodmoon and one with a daily bloodmoon. I can't seem to find where i can set the daily instance to 1day though. I know I can do this with a local game on my computer, but I was wanting to run both instances on my server that is using Alloc's linux installation scripts.
The one with issues as both client AND server ON LINUX is AMD Phenom II X4 3400Mhz 4 cores, 4 logicla processes.Curious, what's the exact CPU model you use?
Someone replicated the error by attempting to run a dedicated linux server on the same type of hardware and got the same type of error.Curious, what's the exact CPU model you use?
That's me. @AllocI'd used this machine when we were testing A20, up to experimental and it had worked as a server. Was going to recycle it, but saw the posts about a20.4 on AMD and decided to test it. If you want any more testing done on it, I'm open to that. I'd just figured, it's so old, just ditch it if it doesn't run your software anymore.Someone replicated the error by attempting to run a dedicated linux server on the same type of hardware and got the same type of error.
Output log here:
https://pastebin.com/PWM6wXa5
Sorry, I figured since it was part of the Linux Native server and all...Also, wrong thread![]()