I also concur, my F710 gamepad instantly crashed starmade upon hitting joystick button 1 (thumb stick buttons)

Unfortunately, someone else needs to handle this issue.

I finally got a friend of mine online to test this bug with, and as such, the results shall be posted soon.

Bug confirmed, shields on docked stuff are not covered by ion affect on the mother ship.

-QA Testing-

Interesting issue, However, with the recent change to 25% there needs to be some counter balance. This could also promote tactical targeting instead of derping the mother ship itself.

I shall conduct my testing shortly, However, Note that I know this to be true from my countless ally misfires after weapons trials. The ai simply does not update.

-Confirmed- This bug was not hard to reproduce at all?

This issue is so rare, that it may be related to save files.

On death, cargo items do drop from inventory and fail to update.

-Confirmed-, Tested a wide range of settings from default to yours, and I'm unable to tell what setting affects this, So i'm going to guess that this is global and an issue across the board.

Claiming.

Claiming, I've seen this before. Should be in queue soon ;)

-Confirmed-
I am able to reliably reproduce this affect 100% of the time by simply putting items into the cargo block and pulling them out again.

Claiming.

Many of these transparency issues cannot be solved due to the rendering engine used, (OpenCL) You will see many of these issues in minecraft too, So i've heard.

Tested with ion and stop affect

Reassigning back to Tim

Merging bug reports.

In T919#37496, @luizsilveira wrote:

I have a base on a planet. On the shipyard, build a ship that has turrets or other docked entities. Dock the ship to the base. Logoff, wait for server restart. When you come back some of the turrets are in the planet core.
Same happens if, in build mode, I create a docked entity to the base. On server restart that docked entity will be in planet core.
These do not happen if I spawn a ship from a core and then manually dock it to either the base or the ship.
One thing that may be relevant is not renaming the docked entity upon creation. I just leave it whatever pops up.
It seems to be the exact same bug as reported here: http://phab.starma.de/T834 , except that mine get sent to the planet core because I'm in a planet sector.

Still unable to reproduce, Asumming was fixed with the compl

-Closing-
Well Above 30 days since last reply.... Assuming bug is fixed

Claiming.

Claiming.

I was unable to reproduce this affect

I am able to reproduce the stated affect.

In T944#35135, @Napther wrote:

Perhaps they dont need to touch? When the "Distance to re-dock" code is implemented, a much lower ranged one could be used to snap rail dockers onto rails when they are 1-2 blocks away. That is unless the code for distance stems from the entity itself, and not where the dockers are placed

-Testing-

-Testing-

In T891#32887, @Chandler wrote:

Everything is working for me thus far. Do you have a good blueprint that you can upload here? That way I can get closer to the circumstances of the issue.

In T865#31880, @schema wrote:

step size will only be 1/4 slabs. i don't think it would look good if you could scale half a block. half a block step size might also mess with the physics of an astronaut for other things (ability to climb almost vertical walls)

Attempting to place weapons on the 2th action bar will result in no desc when in flightmode

Testing..

Power cap transfers to designs quite annoying and confusing also happens for anything docked.

In T590#31535, @plusnine wrote:

It has been a few patches since I have tried to put custom groups that were working back in. I will try again on my next texture pack release and report what happens.

Testing..

It would seem that when a ship is docked wedges, corners, curves and other non cube shaped blocks will auto kick you out of gravity upon pushing against them.

Reclaiming..

This bug report was very hard to do but I was able to get nested tabs to work.
Clearly there is something I am missing so I require some more information.

This bug report has been in the open queue far to long, I shall take a crack at putting this into queue as no one else seems to want to.

TLDR: Shipyard computers seem to think that it needs five slots to fit a multislot item into its storage, And they don't seem to stack with armor already there unless there is already 5 slots(or more)open

It would seem that this is correct upon trying to see info on a planet edge it does not work in build mode however attempting to do so in astronaut mode works just fine.

It would seem that if you manage to undock a turret before the main station is below 50% hp or its faction block is destroyed then the turret will not be decayed.

Testing...

Unable to reproduce possible random affect or another cause.

Since Nuclearfun was unable to reproduce I shall now take a crack at it

-Confirmed and tested on latest dev build-

GTX 760, Latest drivers and dev build, AAA Controlled by app

I used Smiling Demon's settings for my test, My default also had no problems if required to list I shall.

This does not affect my GPU (GTX 760) With latest gforce drivers.

Yay, Bugs to test!

-Confirmed-
Able to reproduce this affect by simply going in and out of the sector

I have been given permission by Spunkie to process this as I am able to reproduce this affect

Basicly, The shipyard is not saving a smd2 file that is needed for over a set amount of distance from the core.

In T658#26603, @cyberus111 wrote:

Why was this downgraded? Missing entire chunks of ships isn't important?

Increasing priority due to the following affects this has on gameplay: