User Details
- User Since
- Jul 23 2015, 9:58 PM (486 w, 6 d)
- Availability
- Available
Sep 22 2015
Added a description of how to reproduce and spunkie made a video so it should be clear
Does not happen in 0.19438(active) or 0.19439(newest atm). So it probably was a problem with what you've been reloading? Maybe a corrupt Station/Ship nearby?
Sep 21 2015
-Validated-
Sep 12 2015
Fixed
Sep 11 2015
Sep 1 2015
Confirmed.
Confirmed. When you remove all Main modules the numbers of the secondary and effect modules disappear. Probably because it cant calculate the percentage or sth like that.
All fixed
Aug 18 2015
Tested both blueprints. No Crash or Error.
Confirmed Fix
Well i think he's referring to this:
Aug 9 2015
Beams and Stars are still invisible behind glass. I'll continue testing
Checked all weapons. All working fine
Aug 7 2015
Confirmed
I'll check it now
Aug 5 2015
It's not happening for me :( But i would say it's a compatibility/Driver/Shader Problem. You probably need special Hardware to make it happen.
Aug 3 2015
I can't confirm this
Aug 2 2015
Jul 29 2015
It happens with every Weapon (Even with Damage pulse. Kinda ridiculous when a 20 range damage pulse trys to damage a ship 4000 Away...)
Jul 28 2015
Jul 27 2015
It has to be relatively fast. I get it nearly every time
Jul 25 2015
Not happening for me. CPU load heavily depends on Segment Count, but not on the Flight/BuildMode
On the right door there is 1 rail wich is not assigned to the Speed controller. Assigned it and it's fixed. Oh and you dont have to use 2 Speed Controllers. 1 is enough.
I found it. I'll take a look at it
get newest dev build and go to play.starmade.net
I've loaded it on the Testserver it's woking alright. Maybe you can come too and show me?
I dont quiete understand what you mean. Images or Blueprint would be nice
I'll take a look at it
Jul 24 2015
I can't confirm this in 0.19338. Of course the blueprint provided is missaligned ,but when i redock the arm and save/load it again it's working perfectly well. Maybe it's fixed by accident?
Maybe someone to who the problem ocurred can test it in the newest dev build, because i don't see i problem here.
Jul 23 2015
Never mind when
Tested in 0.19338 and it seems like it's working.
Can you test it in the newest dev build and tell me how you reproduce it?
confirmed