Search results

To the server they are just a block id inside a chunk. The client is the one that decides when and how to render the lod objects.

The plan right now is to have one chamber block type for each branch type. So a ship strong in jump will have lots of jump nodes connected in various ways. Then you'll configure each chamber to it's specific node. The exact flow is not known and will be looked at closely during play testing.

The problem with most game servers and real time systems, will be dealing with the main loop time. Starmade makes use of threads when feasible, but many functions are faster even in a base loop due to contention and locking between threads. This makes clock speed very important. I've observed...

Hey Maarten, That sounds frustrating. We'll need to find out what's happening. Will you start a thread in game support so we can get logs and make a proper bug report for this?

Which xeon specifically? You'll want to check support for the simd instructions used for asteroid/terrain generation. Some of the old processors don't have it. EDIT I see it in the title. Need to look at support for SSE, but ideally it supports avx512.

Have you tried logging out and logging back in? Are they still there?

Ship Systems 2.0 only requires reactor stabilizers once the reactor gets large enough. If the reactor is large enough, then there is a minimum distance required to get 100% of the effect from a stabilizer. In the proposal, You can place them closer if you want. The game won't stop you. There is...

Balance and tech point consumption will be based on configs.

The concern is you can't start with a shell and work inward?

Are you in steam or standalone?

Is that actually recent? or are those left overs?

They who play, play freely. Those that must play, can not play.

Oh man... I love it