Search results

I don't have a blueprint of it currently, due to me having fully deleted the installation, and I have no idea how to replicate the issue, it just happens

Well, its the same entity causing the crash with the display blocks, the file names may have changed, and I cant replicate it on other servers as I don't have the things setup elsewhere

Alright, here is the new crash log

Yes I am, Ill post my crash log when I get back on my computer

This crash is still present, will there be any actual fix to this?

Trident, of course, flies anyway because Desi doesn't give a fuck what I think is impossible

While Im not disagreeing with most of your statement, I do have to contradict the differentiation, as display modules DO diferentiate between AAA and aaa when you apply regex in the correct manner, however it is not case sensitive for standard sensor blocks as you mentioned

Alright, sounds good, Ill be on the lookout for it!

Well, I can confirm that the standalone launcher is launching the hotfix, as I made a point of checking the log version before I sent it to lancake last night, as far as the steam version, its been acting weirdly with the versions, I dont know if I can post the log I sent lancake from my phone...

I'm not at home currently, but Lancake has a log that IS the current version, from the standalone launcher, when I was trying to see if I could work out the issue, also, the second log I posted IS from the hotfix, as I have currently posted 3 logs on this thread

Like I said, thats an issue with steam, version doesnt matter as both the regular release and the hotfix do it

Upon creation no, occasionally it will crash when I'm placing and using display blocks, but SP seems to have less issues with the crash (can place more display blocks before it crashes) Ok, SP is now getting the Crash Loop, now with an ArrayIndexOutOfBoundsException: 64 However I tried this...

Ok, I can confirm, it is not Steam that is the issue, I did a fresh install from the website, and first login got the crash

It has come to my attention that Jake_Lancia has been suffering an almost identical crash. He is not running Starmade through Steam, and this is the last bit of his latest log with the crash: [2016-10-18 15:56:58] java.lang.NullPointerException [2016-10-18 15:56:58] at...

Yeah, Ill try it outside of Steam when I get home, if it works that means something about the Steam download is messed up I would guess

That is the log from the lastest version, it was from the latest crash I had, after deleting and reinstalling the steam installation, could it possibly have something to do with Steam?

Yes, my game is on v0.199.253a

For the past 24 hours I have been plagued by constant crashes upon placement of display modules, with interspersed times where these crashes do not occur, and times where I cannot even load my character in on a server. Lets start from the beginning: -This all started occurring when I went...

This update fixes an issue where slaved modules would not work as intended when connected to more than 1 parent. Adds a single input for the clock on the Factory Control Module

VERSION 2 IS NOW OUT (Minor fixes to slaving capabilities, and updates to promote ease of use.) Update Log: This update fixes an issue where when a slaved module was connected to multiple active parents and when one parent was turned off, the slave would turn off if allowed by the memory latch...