Search results

I had it working just fine in both single player and a private server, never saw this bug even in the missteps with developing it.

It was a chain drive of my own design, the issue was I let the drives charge and the clock run before I finished the sensors to stop charging just before it's full, and had a faulty logic connection on undock that let a drive missfire. Should've checked the logic better first. Edit: Next...

I'll own up to the error, sorry guys! I made a faulty chain drive that fired immediately after I undocked from a station, leaving behind the clock entity and some turrets - those were probably the reason that something should have been docked but wasn't. On the new copy of the ship (thanks...

Anybody having trouble logging in? I've been getting EOFException after my computer froze and I had to hard reset. I tried deleting my client-database folder, but now it seems like my client can't download the custom block config files from the server.

Thanks for the offer, my player name on the server is Otto_Hartenstein.

Sounds like good rationale to make a fleet of drone torpedo bombers.

Not sure how well I'll keep the FP cost at bay, but next time you catch me online (Otto_Hartenstein), send me an invite. Shouldn't be too hard for me to pack up what little I have in my home system, meant it to be temporary anyways.

Just started on the server yesterday, and am working on a small fleet mining system. Anybody looking to +1 their faction? The single-man base is nice and all, but I think it'd be more fun to have a multi-player fleet for patrolling vs. pirates. Edit: Also, what's the server policy on...

Okay, thanks for the fast responses to this! Edit: Just saw the new dev version on the launcher, no IllegalStateException on starting up a single-player world. Thanks!

I'll try too in a little bit, but that was the same error I was getting after editing the shader files - some function in the game was still calling the extension. I'll post the log files once I have a chance to test myself. Edit: Yep, same error as before from when I changed the shader files...

Okay, fair enough. After a bit more digging and testing, it seems to make like setting the shader files to use version=130 instead of version=120 is a step in the right direction, but the bug that follows after that seems to be tied to the fact that my graphics drivers on this machine (using...

I just switched from 472 too. No suggestions on what to do to fix it on our end? Edit: Well, I got a little farther by changing the version in all the vertex shader files from 120 to 130 with the following commands: cd ~/PATH_TO_STARMADE/StarMade/data/shader/ find . -type f -name "*.vsh"...

I'm getting the same error as well, running on Ubuntu 16.04 64 bit, bundled java. Quick google search suggests that this may be a problem with OpenGL - what version are you running, or are you using different video drivers? I've got: ~$ glxinfo | grep "OpenGL version" OpenGL version string...