or better even both of the lodcube files
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 17 2016
-Validated-
-Confirmed-
-Validate-
-Confirmed-
-QA Testing-
Fixed at some point in time
Jun 16 2016
User error
-Feedback-
Could you please upload the lodcube.vert.glsl file from \data\shader\cube\lodCube ?
i would like to compare it to my version
build .158 ... new generated universe ... still creates Asteroids without even one block
Local SP game on Win7 64bit
how did he enter the target location?
i have seen a weird movement pattern when using "," as coordinate separator lately.
still have to try with "." ... with space the fleet seems to move in the correct direction.
Jun 15 2016
yeaaahhh .... now we have a problem ^^
created on request
This is a missunderstand on your part
Development is aware of the spawn situation.
I do remember that the way spawning in a new game should work will be handled differently in the future (new Spawnstation)
Jun 14 2016
you do get that warning if you try to place blocks on a damaged ship.
(easy to test core-hull-3xsystem block - kill one system block and then add two more while ignoring the warning -> overheat)
03:23:08 [KillaKrazy]: My ship took some damage this morning, about 5% damage to systems
2016/06/14 - 03:23:31 [KillaKrazy]: I went and added about 200k shield caps and recharges without rebooting the system
did the player in question got a warning to reboot before placing the new blocks ?
did he actually reboot before placing them?
did he maybe relog without rebooting and didnt got the warning?
Jun 13 2016
-Confirmed-
Stick and Gamepad support seems to be completely broken as of now.
Jun 12 2016
Jun 11 2016
Because it is missing the codex to play that video .. or some similar problem.
OK .. that is not a bug. its intended behaviour.
by normal means you shouldnt be able to obtain a slab block anyway.
Jun 9 2016
that is aside from my mouse being a 10year old Mx518 the same as for me.
Jun 8 2016
-Feedback-
what server was that problem on?
what was the blueprint ? what size was it?
do you have a logfile of one of those crashes?
no answer , assume broken install
i am pretty sure your ship gets docked past a sector border
Jun 5 2016
this is wrong here, its neither about the game or the registry. so i do have to reject.
Jun 4 2016
-QA Testing-
temporal problem in .137 Dev build
i could reproduce. had nothing to do with cloak or jamming.
problem was already fixed while testing
-Validated-
-Confirmed-
-Feedback-
please drag and drop a log.txt.0 report from the logs folder in here that is from one of those crashes
sounds like a support problem
gone wrong texture update