-QA Testing-
Fixed at some point in time
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 17 2016
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
Have same bug when starting the game. will not move past 50% in the initial lanch screen and beta launcher crashes straight to desk top
Last tested version: 0.198.158. Still happen.
Ah, you're referring to Andy's update, thanks for clarifying. SpaceKing does not have admin on our server (original report).
thats the spawn command: [ADMIN COMMAND] LOAD_AS_FACTION from RegisteredClient: SpaceKing (5) [TheKingOfSpace]connected: true params: [cdrone_new_2, cdrone_new_2_1465517322838, 10012]
This should have been fixed for windows, linux and mac. Also needs testing for SP and dedicated servers.
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
-Validated-
-Confirmed-
yeaaahhh .... now we have a problem ^^
From the longer log, it looks like this could be a graphics driver (or input driver) issue. Are they up to date?
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
fixed a while ago, it still closes if you scroll when hovering over the selected item box (top one) but I think that's OK.
Merged tasks, original issue is fixed but shows a slight improvement could do wonders.
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)
I didn't get the impression he was trying to save the ship during combat, just adding shield modules after returning to his homebase and then logging-out. He logged-back in about 9 hours later, and his ship began a destruction countdown immediately upon his login.
To make it right I downloaded a new starter.exe from there (Windows's one, launcher version 16).
Fresh new install last version to C:\Starmade Test (version = 0.198.149)
Start starter.exe ==> Dedicated Server
Start starter.exe ==> Launch Game
Play Online (enter localhost:4242 + username)
Start ingame and play few seconds only.
Then close game and close server.
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
Results of command: grep KillaKrazy serverlog.txt.0 (replaced IPs with xx)
[2016-06-13 13:51:35] [LOGIN] logged in RegisteredClient: KillaKrazy (4) [KillaKrazy]connected: true (/xx:57115) [2016-06-13 14:13:17] [UPLOAD] KillaKrazy started to upload: KillaKrazy_upload_tmp.zip [2016-06-13 14:16:00] [UPLOAD] PlS[KillaKrazy [KillaKrazy]*; id(1102)(4)f(10404)] finished BLUEPRINT upload: KillaKrazy_upload_tmp.zip: [2016-06-13 14:16:07] [BLUEPRINT] KillaKrazy: IMPORT OF BLUEPRINT DONE: TIER1-ArtemisNavalShipyards2_0 [2016-06-13 14:17:51] [BLUEPRINT][BUY] KillaKrazy bought blueprint from metaItem: "TIER1-AllianceSuperCity" as "Rendili Hyperworks"; Price: 281987514; to sector: (4168, 4079, 86) (loadTime: 128ms, spawnTime: 10ms) [2016-06-13 14:17:58] [SPAWN] KillaKrazy spawned new ship: "KillaKrazy_1465827482140" [2016-06-13 14:20:19] [DISCONNECT] Client 'RegisteredClient: KillaKrazy (4) [KillaKrazy]connected: true' IP(/xx:57115) HAS BEEN DISCONNECTED . PROBE: false; ProcessorID: 167 [2016-06-13 14:20:19] [LOGOUT] logging out client ID RegisteredClient: KillaKrazy (4) [KillaKrazy]connected: true [2016-06-13 23:08:37] [AUTH] authenticating KillaKrazy; useAuth: true; requireAuth: true [2016-06-13 23:08:38] [AUTH] Protection status of KillaKrazy is ProtectedUplinkName [username=KillaKrazy, timeProtected=1465825895438] -> protected = true [2016-06-13 23:08:38] [AUTH] PROTECTING USER killakrazy under uplink id KillaKrazy [2016-06-13 23:08:38] [LOGIN] logged in RegisteredClient: KillaKrazy (63) [KillaKrazy]connected: true (/xx:57915) [2016-06-13 23:13:39] [DISCONNECT] Client 'RegisteredClient: KillaKrazy (63) [KillaKrazy]connected: true' IP(/xx:57915) HAS BEEN DISCONNECTED . PROBE: false; ProcessorID: 2151 [2016-06-13 23:13:39] [LOGOUT] logging out client ID RegisteredClient: KillaKrazy (63) [KillaKrazy]connected: true
According to logs, he was logging-in at the moment the server set a 60-second countdown. So I'm going with the assumption he didn't see any sort of warning/reboot message.
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?
This bug can be easily remedied by installing libopenal from your repositories.
Any way to determine what the entity is @schema ?
More info from ongoing discussions
2016/06/14 - 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 2016/06/14 - 03:23:50 [KillaKrazy]: I'm curious if that played a part in this bug happening 2016/06/14 - 03:24:08 [ErthParadine]: Could have - did you just lump those onto the ship? 2016/06/14 - 03:24:57 [KillaKrazy]: Yea I put them inside it. Depending on how long the timer was, that may have triggered the bug 2016/06/14 - 03:33:25 [KillaKrazy]: I'm thinking that adding more systems to a damaged ship may have dropped the hp level below 50% without showing or triggered the overheat
I've removed the --steam requirement for the automatic install path, which should resolve this.
I also may have fixed the overlapping pages issue. I wasn't able to duplicate it, however, and couldn't find a cause.