Gaming Artlav's Space Engineers Server

Note: ice will be generated in new worlds.

Does that mean that, even if we go exploring past current boundaries on the server, that we'll never find ice?
 
You will only find ice if it's enabled in the world options for the world. After enabling it the ore distribution on all asteroids that haven't been touched by a drill (or damaged in any other way) will change to include the ice, too. Asteroids which had at least one small voxel modified (only modified and the "Central" asteroids are saved on disk in the infinite world) won't have any ice.


Anyway, the server is still at version 1072008 (laser communication addition), and it's good I keep binaries and data of that version in backup to switch to it when I want. :P
 
Anyway, the server is still at version 1072008
We have a problem.

Tried updating the server - i'm getting .NET errors of some vague description, and nothing runs.
I'm kind of on a wrong continent right now, so this stuff can take a while to figure out and/or fix over remote connection (and possibly remote direction-giving).

Expect the server to be down for a few days.

Exception text, if someone know what can it be.
Code:
System.TypeInitializationException: type initializer "Sandbox.Definitions.MyDefinitionManager" threw exception. ---> System.Reflection.ReflectionTypeLoadException: Can not load one or more of the requested types. Check LoaderExceptions property for details.
   in System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
   in System.Reflection.RuntimeModule.GetTypes()
   in System.Reflection.Assembly.GetTypes()
   in Sandbox.Common.MyObjectFactory`2.RegisterFromAssembly(Assembly assembly)
 
There has been released an update which should fix the issue of missing redist, which is what caused the System.TypeInitializationException in most of cases.
 
fix over remote connection (and possibly remote direction-giving).

On an unrelated note, how do you remote connect to a Windows box?

The best solution I've come up with is ssh'ing(with cygwin) in after ssh "bouncing" off my server, but even with cygwin, ssh is...limited on Windows.
 
On an unrelated note, how do you remote connect to a Windows box?

The best solution I've come up with is ssh'ing(with cygwin) in after ssh "bouncing" off my server, but even with cygwin, ssh is...limited on Windows.

I like TeamViewer.
Or use plain RDP if you have a Pro version of Windows.
 
I like TeamViewer.
I'll have to look into it :thumbup:

What I really like on the linux computers is, after ssh-bouncing, I can just do a quick
Code:
x11vnc -listen localhost
and start an SSH tunnel through the server. Then all the traffic goes through the (hopefully more secure) server.

It looks TeamViewer establishes a connection between the two computers directly with NAT punching. That looks fine, as it doesn't appear to leave any ports open all the time or something.


Or use plain RDP if you have a Pro version of Windows.
But I don't have a Pro version :(

</diversion>
Anyway...back to Space Engineers.
 
Let the Windows Update do it's job, installed orb's link, and updated the server again.
Whatever of the three was it, it works now. Thanks for the pointers.
If something is amiss, do tell. I have a backup.

Can't find anything about Ice/Oxygen spawning yet.
The world is procedurally generated, so maybe they spawn on their own?
There is a new option for Oxygen in the server settings, which was set by default.
I left it on. If that causes problems, see above about the backup.

For remote connection i use TightVNC for the Windows machine.
Somewhere along the line RDP got broken on this instance of Windows, giving authentication errors. Otherwise, i would have used it - it's much faster than VNC.
 
Can't find anything about Ice/Oxygen spawning yet.
The world is procedurally generated, so maybe they spawn on their own?

I think orb covered that topic pretty well:
You will only find ice if it's enabled in the world options for the world. After enabling it the ore distribution on all asteroids that haven't been touched by a drill (or damaged in any other way) will change to include the ice, too. Asteroids which had at least one small voxel modified (only modified and the "Central" asteroids are saved on disk in the infinite world) won't have any ice.
 
The server works and the oxygen is enabled (only tested with the helmet off), however there is some issue with the inventory system - I can't put items back to containers or drop them, hand tools are disappearing while they are used, e.g. in the middle of welding (I wanted to build a mini-ship to find some asteroids with ice). It could be some new bug of the dedicated server. I'll check it again later.


EDIT: The inventory issue seems to only have been happening in that session. Now it's working fine, and I've found ice on one of asteroids some 20 km away from the origin, so making oxygen is possible, too.
 
Whatever of the three was it, it works now.
---
For remote connection i use TightVNC for the Windows machine.

Thanks :thumbup:

Artlav, I just checked out your peace moon for the first time.
:jawdrops:


Incredible. It will be more awesome when it's fully functional ;)
(Everyone else, if you haven't checked it out, you should)
 
Hey Artlav, you seemingly own most of the blocks on one of my mining ships (it's named MesonPlatform)

I can't set the ownership on those blocks (outside of grinding down/rebuilding past the computer line, which I'm doing), their ownership is just "theartlav[dead]" I'm wondering how that happened.

---------- Post added 03-23-15 at 11:45 AM ---------- Previous post was 03-22-15 at 10:34 PM ----------

And the server is out of date, even though there's no update news...
 
Last edited:
Maybe he moved (respawned) it.

There was a tiny hotfix earlier today ... as usual. :(
 
There was a tiny hotfix earlier today ... as usual. :(
The best IMO way to have both the updated version and be able to play on the not yet updated server:
  • Switch the update download mode for Space Engineers to update it only when you launch the game.
  • When you see a notification that an update is available, make a backup of: Bin, Bin64, Content subdirectories, and next launch the game to update it.
  • In order to play the old version, move the updated: Bin, Bin64, Content directories somewhere and next move the backed up from before the update: Bin, Bin64, Content back to the Space Engineers.
  • If you want to play the updated version, or if you are notified about another new update, move the earlier updated: Bin, Bin64, Content back to Space Engineers.
 
Does that stop the game updating when you launch it with the old files? :huh:
 
Server should be updated now.

I have no idea what happened to the vessel. Maybe teleporting it done that?
So far the game is updating faster than my toolset, so can't fix it yet.
 
Server should be updated now.

I have no idea what happened to the vessel. Maybe teleporting it done that?
So far the game is updating faster than my toolset, so can't fix it yet.

I don't believe it was teleported, it never got lost...

Don't worry, I'm fixing it manually, it's just a little strange that some of the blocks (but not all of them, like the reactor didn't get changed) changed permissions.
 
Does that stop the game updating when you launch it with the old files? :huh:
Only if there is no even newer update in queue.

Steam doesn't check game files when you launch the game. It only checks metadata. After an update to the most recent version it saves information about the currently used branch ('public' in most cases), build id and manifest id(s), and queues another update for the game only if information about them is changed in fetched from time to time ProductInfoChanges. After an update is done stored file checksums are checked against the game files only when you verify the game cache, hence you can copy the old files into the game's directory and launch the game from them instead just fine, until another update, when you need to repeat some of the points.
 
Back
Top