Nevermind on the astro not being sucked in part. Tabbed back in (after server save?) upon finishing this report and found myself inside the wormhole sector itself...

Im getting a LOT of these recently now that Ive started back into fighting other ships and testing. Retry is a temporary fix if it doesnt outright crash.

Yep - had this once too. Tried every way possible in order to convert these back into something useful. Shops didn't buy them, Weren't able to place them, Weren't able to merge the slabs through trying to place them down and using multiblock picker.

I recall (But not tested recently at all) that missile damage also depends partially on the side of the entity hit. A perfect hit to a flat side facing galactic North isnt always the same as a perfect hit from any other side. Could be worth double checking

Yeah, I havent had a crash in recent memory related to this so its perhaps a safe bet that for now it is fixed.

I can say Ive experienced this

As above, its Upload from Local to Multiplayer.
Also wish we can search in that menu than have to scroll a very long drop-down list...

The game hangs for 7-10 seconds when I open the menu, but that is significantly better than crashing outright. Somewhere its fixed itself.

So went and did the test today, got this error but still for the most part crashed/hung.

So this can now be closed I guess but taking a few notes to players or the options like

Remember the default binding for the "Dev" key is applied to the key that generates the "Player Board" . Since this update I put the Radial menu on F1, and the old tab-player board back to Tab and it made all my commands go from F1 being required to TAB being required.

Noticed that a ship going past the default speed will have its speed instantly reset to this default speed upon being nicked or grazed by a pull/push weapon

Just done it again, Fired missiles in .246, these cratered a Target. Jumping to a star does NOT bring up a "Heat Damage Warning" or Proximity warning. Godmode was never enabled. will test it ion next builds when they are available

In recent patches, this is happening again. Overheated a few ships and turrets were there without Nav markers (I play with turret markers disabled normally). Enabling them again showed they were still "docked" to the now deleted ship.

Sadly this is 6 of 1 half dozen the other... Any way to differentiate docked engine nacelles and drones and fighters?

In T1818#76935, @Spindizzi wrote:

Not sure if this is related but I'd had an issue before where launching a ship off a rail with shootout turned caused the ship to glitch into a zone where there were no stars and all around is just solid grey background.
Would look at the distances from anything and it looked like it was NaN, pretty much fixed mostly reconnecting to the session though, although you might be a few km away.

...Well found the problem then. The partition is 100GB in size to separate out steam libraries in case 1 or other fails to load a game as is something that has happened in the past.

I think I may know what is the cause now.

Prior versions feel exactly the same when tested, the CPU caps out almost instantly despite there being relatively few blocks broken.The optimisations are apparently unfelt on my computer, and changing builds so often has caused a number of issues in itself.

When testing in current release, the test ship and target half FPS from 45 to 23 while blocks are being destroyed.

Can do, At least the new Launcher allows hotswapping much easier and faster. A few patches ago the single player F7 lag statistics on HUD has also been stuttering occasionally, when at one point the game showed no load (A flat line) when in single player indicating that the server was having no issues at all almost all the time.

Huh, could have sworn at one point in time the SHP of a ship core depleted as you hit the thing... Oh well

Trying to build some automated door systems is Impossible until this and the Area Trigger bug similar to this are fixed...

*Been around since BEFORE those patches.
I lack the resources to confirm when this issue has been happening

strange, my Gifs are getting cut short AT 10% their total length or something, far, far more cut-off than what the testers are getting

Fired again on single player, this time with a cannon-cannon-Punch found on the fleet Corvette at a shielded target. This target has had numerous /shield_regen false and true statements applied to test if there were damage bugs with some weapon combinations (To which there wasnt any found with my small test)

Sadly not. Could be related to the GL_errors bouncing around a lot... Otherwise Im afraid Ive got nothing more than "It happens. Mostly happening during live weapon tests."

...How very, very peculiar that its specific to Tab+F8...

...this may be a complete over-reaction to the problem to reinstall, because I had assumed that the textures for Heptas and Tetras has been broken for a long time, on one side of the ship, they tile horizontally, on the other, they tile vertically

By changing the assigned Hotbar up/down and going back to the missile computers fixes the lock-on animation, and allows rockets fired to lock on. This sometimes needs to be repeated if a cannon is used in the interim between rocket launches,

Its an older vessel. I can submit it in .sment format onto the Dock for you if it is required that this specific vessel is used in testing... But this is an old, closed issue; the other issue contains a Sment version of this ship in attachments I do believe

Ive managed to get it to occur with this vessel on single and Multiplayer servers

Consoles and Pipes also are valid targets for the Create Docking build option.
I couldnt stop laughing after seeing this post.

Can't reproduce. My salvage beam hit linked systems, unlinked systems and the build block at roughly the same time but no nullpointer.

While I have never "experienced" this myself (My builds have been immune to it luckily) it happens a lot with certain players of the Shattered Skies server, with builds that use lots of closely-docked turrets and other entities.

Then there are people like me, who have used the thrusters in corridors... While its fine for front/back facing rooms, thruster plumes become visible when a corridor is left/right facing.

Steps to reproduce:

When travelling, the original got a little star-struck. I lost some entities in the damage from the star.
Spawning the ship in on the same name a month later, some entities were missing upon deconstruction

I can concur with Ithirahad here. Ive noticed the same behaviour when some of my drones get near to each other as well as another asteroid.

I can say that a slight user-oversight meant that the smaller brick-with-cockpit drones indeed dont have their salvage computer connected with a storage block. Didnt realise this was the behaviour at the time of creating and testing, as my larger vessels were not mining too well at all.

Hmm, I Dont know how it should be, but a ship that's using Millions of blocks of advanced armour shouldn't have its armour HP removed upon the destruction of 1 block. Perhaps put a cap on the amount of armour HP that can be removed in one go from a single block.

It should be noted the amount of stutter scales with the number of Jump Computers linked to logic on this ship. 100 causes barely noticeable stutter, whereas 1000 will generate a lot more.

I should note that its on any ship combo it seems. Got a number of reports from players on Shattered Skies TS and Server that they are getting these random Build mode undo/redo crashes also

It might have been my specific procedure with killing a planet that caused it, but, it happened so many times in a row with my set up that I grew frustrated and gave up in trying to destroy planets. The ship had 200m power and fired off a damage beam-pulse-explosive (100% each) that dealth 17m damage in a single second.

I should note to say that this is just like the fixed bug (For cannons at least) of when a planet plate receives "damage" the core becomes transparent to attack...

"Mirror Cubes Function" Being ignored isnt the issue, its outright locking slabs into incorrect orientations after being rotated, as shown in the GIF.