Nokta
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Nokta
-
-
Already made a in-game report but writing here for visibility too and maybe somebody else have found this nasty one, have a better repro or a workaround to keep playing because, right now, this is kinda killing every game I start.
At some point, usually after I found my second ship in Trinium area with my first one still around, turret systems will stop giving the right amount of weapon slots, both civilian and military.
Meaning, if I put a +5 military turret system on, I won't be able to place 5 military turrets, but usually only 2 or 3. Same for civilian turrets. All turrets system will stop working correctly and new systems you put on the ships will still fail to provide the right amount.
This is true for every new ship built. Turret system will simply stop working correctly limiting the amount of weapons you can mount on both new and old ships.
They work fine at galaxy creation but stop functioning correctly after that.
My first ship had +4 military +5 civilian and weapons where shooting fine. After I encountered the bug in my 2nd ship, I went to modify my first one, removed one weapon and then weren't able to mount it again because of no more available slots.
Sorry for not being able to give a solid repro.
Submitted specific .log in the original bug report but can provide it here too if needed.
Hope this helps somehow because this is really killing my games :S
-
I tried to implement this, but failed at loading the entities (ships) that are not in the current sector. So it is currently not possible.
Cheers. I hope this will be a feature in-game eventually. This game really need a fleet manager.
-
This is great. Thank you.
So if I get it right, is not possible at this time to give orders to ships in sectors you are not in?
Or to order them to change sectors to keep doing what they are doing? This is the most annoying thing about fleet management atm for me :D
Once you have some ships spread over some systems it's a pain to micromanage all of them by having to jump in their sectors all the time.
-
So, for those interested, Koonschi replied to my same post on the Steam forums saying that anti-fighters weapons are planned.
http://steamcommunity.com/app/445220/discussions/0/2765630416828962308/#c2765630416829839707
While I can't wait to see them in game, I still think that regular weapons should still have a chance to deal with fighters, with lower efficency ofc, but not making fighters too easy to kill or, on the other side of the spectrum, virtually invincible as they are right now.
It might take a little while, but you should be able to bring them down eventually especially if they have no reinforcements and their launching ship is dead.
-
Had 3 ship with all kinds of weapons: Plasma, Kinetic and Laser. None of them could hit anything.
Fun fact, I left the game and went back in and magically the fighters that were harassing one of my ships disappeared and went on harassing the allied flotilla.
I was in a scrapyard system and 1 hour later, after my licence expired, they were still there trying to take down those fighters without any success.
Once again, absurd imo.
-
Am I the only one that find a bit silly that 10 fighters can outlast a full-armed flottilla because nobody can actually hit them?
I entered a brawl between two factions by mistake and had to take the side of one faction. After I managed to kill all enemy ships only enemy fighters remained. Around 10 of them.
I had 3 ships with me and friendly faction had like 7, corvette and cruisers. We litterally stood there for 15 minutes trying to shoot 10 fighters down. They kept dodging and eventually started to mow down allied ships while keep pounding my shields into submissions.
In the end I had to just jump away.
I think fighters need to be toned down a bit, this is absurd :S
There's should be a diminishing return chance on the dodge, you can be a skilled pilot but 10 ships shooting all their ordnance at you should be able to hit you... eventually.
Playing 0.14.2
-
I might have had at some point... I have an SSD HD with OS only and not much space on it so when I noticed galaxies saves were in the GB size I think I might have used the symbolic linking to my dump HD (saves not forced on C: but in the game install folder would be reeeeealy great btw).
But I can't find anything Avorion-related in my dump HD and I did make a game reinstall after all.
Should I manually delete the avorion appdata folder and do a new clean install again?
EDIT: I did exactly this. Manually deleted the Avorion appdata folder and did a clean install.
I CAN NOW LOAD SAVED GALAXIES AGAIN
Was a problem on my end after all.
Solved, I guess.
Cheers Koonschi, thanks for your time.
-
Woops, you are right. My bad.
Here should be the correct one:
2017-06-16 21-01-30| Enabled Traces: network scripting threading io database input error warning exception user game system debug sound gl
2017-06-16 21-01-30| Avorion server Beta 0.12.1 r8521 running on Windows 8.1+ starting up in "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server"
2017-06-16 21-01-30| CPU: GenuineIntel 8 Cores
2017-06-16 21-01-30| RAM: 8GB
2017-06-16 21-01-30| name: Load You Fool
2017-06-16 21-01-30| seed: insertrandomseedhere
2017-06-16 21-01-30| port: 27000
2017-06-16 21-01-30| max online players: 10
2017-06-16 21-01-30| save interval: 600
2017-06-16 21-01-30| broadcast interval: 5
2017-06-16 21-01-30| max loaded sector time: 300
2017-06-16 21-01-30| weak update: yes
2017-06-16 21-01-30| worker threads: 8
2017-06-16 21-01-30| generator threads: 2
2017-06-16 21-01-30| difficulty: Normal
2017-06-16 21-01-30| infiniteResources: no
2017-06-16 21-01-30| collision: 1
2017-06-16 21-01-30| access list: Blacklist
2017-06-16 21-01-30| public: yes
2017-06-16 21-01-30| authentication: no
2017-06-16 21-01-30| listed: no
2017-06-16 21-01-30| steam networking: yes
2017-06-16 21-01-30| administrators: 'admin'
2017-06-16 21-01-30| Creating folder: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server"
2017-06-16 21-01-30| Saving xml file: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\admin.xml"
2017-06-16 21-01-30| Filesecurer moving "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\admin.xml~" to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\admin.xml"
2017-06-16 21-01-30| Reading content of file: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\admin.xml~"
2017-06-16 21-01-30| Filesecurer backup content size: 1286
2017-06-16 21-01-30| Reading content of file: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\admin.xml"
2017-06-16 21-01-30| Filesecurer destination content size: 1286
2017-06-16 21-01-30| Initializing sector database...
2017-06-16 21-01-30| Creating folder: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\sectors"
2017-06-16 21-01-30| Initializing faction database...
2017-06-16 21-01-30| Creating folder: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\players"
2017-06-16 21-01-30| Creating folder: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\factions"
2017-06-16 21-01-30| Creating folder: "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\dedicated_server\alliances"
2017-06-16 21-01-30| Read index file.
2017-06-16 21-01-30| Checking for unknown players in folder...
2017-06-16 21-01-30|
-
Here we go, I did the same procedure as above.
https://pastebin.com/fsThdnX4 doesn't look much different than the previous.
If you want the log for the creation of the server I can't post it on pastebin because of size limit (it's a whopping 4.4mb of text and non-pro pastebin is 512kb :o ) so I might need to email it to support if you need it.
-
Cheers. I'll keep an eye out for it and come back with updates.
Meanwhile I'm bound to play multiplayer, I guess :S
-
Ok, here's what I did.
1 - Started a dedicated server with the "-t all" parameter
2 - Server started ok
3 - Logged into the server through multiplayer LAN. Logged in ok. Mined something. Changed sector. Logged off.
4 - Logged back in with server still running. No prob. Position was saved.
5 - Logged off.
6 - Shut down the server.
7 - Tried to start the server up again. It won't start. It does some processing then simply return to the input waiting. No errors on screen.
8 - Tried to start again with or without the "-t all" parameter. Server won't start up again.
Pastebins follows:
Server creation: https://pastebin.com/3KGqEPUE
Trying to restart: https://pastebin.com/fYdbrPF7
This log shows something different: https://pastebin.com/dk3J1b9b
Let me know if you need anything else that might be helpful.
-
And here's the one when I try to load it (I think). It ends like that.
2017-06-13 20-02-13| Enabled Traces:
2017-06-13 20-02-13| Avorion server Beta 0.12 r8487 running on Windows 8.1+ starting up in "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load"
2017-06-13 20-02-13| CPU: GenuineIntel 8 Cores
2017-06-13 20-02-13| RAM: 8GB
2017-06-13 20-02-13| name: Nokta ☯'s Server
2017-06-13 20-02-13| seed: ZCCaj5I9Ni
2017-06-13 20-02-13| port: 27000
2017-06-13 20-02-13| max online players: 10
2017-06-13 20-02-13| save interval: 600
2017-06-13 20-02-13| broadcast interval: 5
2017-06-13 20-02-13| max loaded sector time: 300
2017-06-13 20-02-13| weak update: yes
2017-06-13 20-02-13| worker threads: 7
2017-06-13 20-02-13| generator threads: 2
2017-06-13 20-02-13| difficulty: Normal
2017-06-13 20-02-13| infiniteResources: no
2017-06-13 20-02-13| collision: 1
2017-06-13 20-02-13| access list: Blacklist
2017-06-13 20-02-13| public: no
2017-06-13 20-02-13| authentication: no
2017-06-13 20-02-13| listed: no
2017-06-13 20-02-13| steam networking: yes
2017-06-13 20-02-13| server will exit once all admins logged out.
2017-06-13 20-02-13| administrators: 'admin'
2017-06-13 20-02-13| Initializing sector database...
2017-06-13 20-02-13| Initializing faction database...
2017-06-13 20-02-13|
-
Thanks for the report, can you please post the server log from these sessions?
Sure thing:
Here's the one with the Galaxy creation (I think):
2017-06-13 01-22-41| Enabled Traces:
2017-06-13 01-22-41| Avorion server Beta 0.12 r8487 running on Windows 8.1+ starting up in "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load"
2017-06-13 01-22-41| CPU: GenuineIntel 8 Cores
2017-06-13 01-22-41| RAM: 8GB
2017-06-13 01-22-41| name: Nokta ☯'s Server
2017-06-13 01-22-41| seed: ZCCaj5I9Ni
2017-06-13 01-22-41| port: 27000
2017-06-13 01-22-41| max online players: 10
2017-06-13 01-22-41| save interval: 600
2017-06-13 01-22-41| broadcast interval: 5
2017-06-13 01-22-41| max loaded sector time: 300
2017-06-13 01-22-41| weak update: yes
2017-06-13 01-22-41| worker threads: 7
2017-06-13 01-22-41| generator threads: 2
2017-06-13 01-22-41| difficulty: Normal
2017-06-13 01-22-41| infiniteResources: no
2017-06-13 01-22-41| collision: 1
2017-06-13 01-22-41| access list: Blacklist
2017-06-13 01-22-41| public: no
2017-06-13 01-22-41| authentication: no
2017-06-13 01-22-41| listed: no
2017-06-13 01-22-41| steam networking: yes
2017-06-13 01-22-41| server will exit once all admins logged out.
2017-06-13 01-22-41| administrators: 'admin'
2017-06-13 01-22-41| Initializing sector database...
2017-06-13 01-22-41| Initializing faction database...
2017-06-13 01-22-41| Starting up 7 worker threads...
2017-06-13 01-22-41| Loading jumping entities...
2017-06-13 01-22-41| no file "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\jumps.dat" found
2017-06-13 01-22-41| Loading groups...
2017-06-13 01-22-41| Galaxy initialized.
2017-06-13 01-22-41| Listed server version: 0.12.0.8487
2017-06-13 01-22-41| Game Port: 27000
2017-06-13 01-22-41| Steam Port: 27021
2017-06-13 01-22-41| Steam Query Port: 27020
2017-06-13 01-22-41| Query Port: 27003
2017-06-13 01-22-41|
2017-06-13 01-22-41| Server UDP: Error receiving from 127.0.0.1, error: Connessione in corso interrotta forzatamente dall'host remoto, received bytes: 0
2017-06-13 01-22-41| Installed Steam exception handler
2017-06-13 01-22-43| Server connected to Steam successfully
2017-06-13 01-22-43| Server is not VAC Secure!
2017-06-13 01-22-43| Game Server Steam ID: 90109251269253121
2017-06-13 01-22-44| OnP2PSessionRequest from 76561197993771932
2017-06-13 01-22-47| [Authentication not Enabled] New client: 76561197993771932
2017-06-13 01-22-47| Client accepted: 76561197993771932
2017-06-13 01-22-47| Connection to player established
2017-06-13 01-22-47| Connection accepted from 192.168.1.2:0
2017-06-13 01-22-50| New Player registered: 76561197993771932 [Nokta ☯] index: 1
2017-06-13 01-22-50| <Server> Player Nokta ☯ created!
2017-06-13 01-22-50| Creating sector at (-268:360)
2017-06-13 01-22-50| <Server> Player Nokta ☯ joined the galaxy
2017-06-13 01-22-51| Player logged in: Nokta ☯, index: 1
2017-06-13 01-22-51| Generating new content for sector (-268:360)
2017-06-13 01-22-56| scheduled save for sector (-268:360), 0x6916640, entities: 1571
2017-06-13 01-22-56| saving sector (-268:360)
2017-06-13 01-22-56| player events roughly every 12.71 minutes
2017-06-13 01-22-56| Player Nokta ☯ moved to sector (-268:360) server time taken for change: 33ms
2017-06-13 01-22-56| Creating sector at (-267:360)
2017-06-13 01-22-56| Creating sector at (-271:358)
2017-06-13 01-22-56| sector (-268:360) saved to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\sectors\-268_360"
2017-06-13 01-22-56| scheduled save for sector (-268:360), 0x6916640, entities: 1574
2017-06-13 01-22-56| Generating new content for sector (-267:360)
2017-06-13 01-22-56| saving sector (-268:360)
2017-06-13 01-22-56| Generating new content for sector (-271:358)
2017-06-13 01-22-57| sector (-268:360) saved to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\sectors\-268_360"
2017-06-13 01-22-59| scheduled save for sector (-271:358), 0x11311a30, entities: 879
2017-06-13 01-22-59| saving sector (-271:358)
2017-06-13 01-22-59| sector (-271:358) saved to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\sectors\-271_358"
2017-06-13 01-23-12| <Server> Player Nokta ☯ left the galaxy
2017-06-13 01-23-12| Player logged off: Nokta ☯, index: 1:
2017-06-13 01-23-12| Server is shutting down.
2017-06-13 01-23-12| Saving settings...
2017-06-13 01-23-12| Saving script values...
2017-06-13 01-23-12| Saving factions...
2017-06-13 01-23-12| Saving sectors...
2017-06-13 01-23-12| Saving jumping ships...
2017-06-13 01-23-12| scheduled save for sector (0:0), 0xf6e3f0, entities: 0
2017-06-13 01-23-12| saving sector (0:0)
2017-06-13 01-23-12| sector (0:0) saved to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\jumps.dat"
2017-06-13 01-23-12| Saving groups...
2017-06-13 01-23-12| Saving settings...
2017-06-13 01-23-12| waiting for unfinished sector generation jobs...
2017-06-13 01-23-12| Received valid shutdown message, shutting down.
2017-06-13 01-23-17| scheduled save for sector (-267:360), 0xfc0c060, entities: 1286
2017-06-13 01-23-17| jumps.dat"
2017-0| waiting for unfinished sector save jobs...
c060, entities: 1286
2017-06-13 01-23-17| jumps.dat"
2017-0| saving sector (-267:360)
2017-06-13 01-23-17| sector (-267:360) saved to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\sectors\-267_360"
2017-06-13 01-23-17| scheduled save for sector (-271:358), 0x11311a30, entities: 879
2017-06-13 01-23-17| saving sector (-271:358)
2017-06-13 01-23-17| sector (-271:358) saved to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\sectors\-271_358"
2017-06-13 01-23-17| scheduled save for sector (-268:360), 0x6916640, entities: 1574
2017-06-13 01-23-17| saving sector (-268:360)
2017-06-13 01-23-17| sector (-268:360) saved to "C:\Users\Nokta\AppData\Roaming\Avorion\galaxies\Why U No Load\sectors\-268_360"
2017-06-13 01-23-17| shutting down networking...
2017-06-13 01-23-18| UDP closed
2017-06-13 01-23-18| Server UDP: Connection closed
2017-06-13 01-23-18| cleaning up communicators...
2017-06-13 01-23-18| waiting for unfinished sector generation jobs...
2017-06-13 01-23-18| waiting for unfinished sector save jobs...
2017-06-13 01-23-18| shutting down galaxy...
2017-06-13 01-23-18| shutting down faction database...
2017-06-13 01-23-18| shutting down sector database...
2017-06-13 01-23-18| cleaning up timers...
2017-06-13 01-23-18| Server shutdown successful.
-
Can't load saved galaxies since the new beta update.
1. I start a new galaxy and enter no problem. Fly around a bit.
2. I quit instantly, galaxy get saved normally
3. I try to load the saved galaxy
4. Game gets stuck into Loading Singleplayer and won't move from there.
5. Have to force close the game via task manager
I did a file check, uninstalled and reinstalled. Nothing.
When I rolled back to the previous Beta Build I could create and load new galaxies, no problem.
Looks like an issue with the new beta update.
Operating System: Win 10
CPU: i7-2600 @ 3,4ghz - 8GB ram
GPU: GTX670
LOG:
2017-06-13 20-02-02| Client started: "D:\steam\steamapps\common\Avorion\bin\Avorion.exe" "--serverpath=bin/AvorionServer.exe"
2017-06-13 20-02-02| Enabled Traces:
2017-06-13 20-02-02| Client Beta 0.12 r8487, running on Windows 8.1+.
2017-06-13 20-02-02| CPU: GenuineIntel 8 Cores
2017-06-13 20-02-02| RAM: 8GB
2017-06-13 20-02-02| Init Steamworks...Installed Steam exception handler
2017-06-13 20-02-02| Init Steamworks... ok
2017-06-13 20-02-02| Init Steamworks ok
2017-06-13 20-02-02| Init SDL2... ok
2017-06-13 20-02-02| Getting display mode... ok
2017-06-13 20-02-02| Current display mode: 1920 x 1080
2017-06-13 20-02-02| Creating settings... loading... setting language... ok
2017-06-13 20-02-02| Creating client window...Creating Fullscreen window
2017-06-13 20-02-02| Detected 1 displays
2017-06-13 20-02-02| Display 0: x: 0, y: 0, w: 1920, h: 1080
2017-06-13 20-02-02| Using display 0
2017-06-13 20-02-02| Creating window, x: 0, y: 0, w: 1920, h: 1080... ok
2017-06-13 20-02-04| GetDrawableSize: 1920 1080
2017-06-13 20-02-04| GetWindowSize: 1920 1080
2017-06-13 20-02-04| Creating GL context... ok
2017-06-13 20-02-04| Setting window mode FullScreen... ok
2017-06-13 20-02-04| Creating client window ok
2017-06-13 20-02-04| Init rendering... starting rendering... initialize...OpenGL Context Information:
2017-06-13 20-02-04| Version: 4.5
2017-06-13 20-02-04| VersionString: 4.5.0 NVIDIA 382.53
2017-06-13 20-02-04| Vendor: NVIDIA Corporation
2017-06-13 20-02-04| Renderer: GeForce GTX 670/PCIe/SSE2
2017-06-13 20-02-04| GLSL Version: 4.50 NVIDIA
2017-06-13 20-02-04| GL_MAX_VERTEX_UNIFORM_COMPONENTS: 4096
2017-06-13 20-02-04| GL_MAX_VERTEX_UNIFORM_VECTORS: 1024
2017-06-13 20-02-04| GL_MAX_CUBE_MAP_TEXTURE_SIZE: 16384
2017-06-13 20-02-04| GL_MAX_ELEMENTS_INDICES: 1048576
2017-06-13 20-02-04| GL_MAX_ELEMENTS_VERTICES: 1048576
2017-06-13 20-02-04| GL_MAX_RENDERBUFFER_SIZE: 16384
2017-06-13 20-02-04| GL_MAX_TEXTURE_SIZE: 16384
2017-06-13 20-02-04| GL_MAX_VERTEX_ATTRIBS: 16
2017-06-13 20-02-04| GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS: 32
2017-06-13 20-02-04| Init GLEW... ok
2017-06-13 20-02-04| Init Debug Message Callback... ok
2017-06-13 20-02-04| Set VSync... ok
2017-06-13 20-02-04| Secure BackBuffer... ok
2017-06-13 20-02-04| Init Canvas...Create canvas of size 1920 x 1080... ok
2017-06-13 20-02-04| Init Canvas ok
2017-06-13 20-02-04| Init Refraction Texture... ok
2017-06-13 20-02-04| Init Post Processing... ok
2017-06-13 20-02-04| Init Debug Renderers... ok
2017-06-13 20-02-04| DepthTexturesSupported: yes
2017-06-13 20-02-04| IntVertexAttributesSupported: yes
2017-06-13 20-02-04| DeferredSupported: yes
2017-06-13 20-02-04| LowSpecGPUDetected: no
2017-06-13 20-02-04| Rendering initialized
2017-06-13 20-02-04| Init rendering ok
2017-06-13 20-02-04| Check problematic drivers... ok
2017-06-13 20-02-04| Init shader level... ok
2017-06-13 20-02-04| Init loading screen... ok
2017-06-13 20-02-04| Draw first loading screen... draw... ok
2017-06-13 20-02-04| Init SFX... ok
2017-06-13 20-02-04| Init Input... ok
2017-06-13 20-02-04| Init GameInput... ok
2017-06-13 20-02-04| Init Main Menu... ok
2017-06-13 20-02-05| Init Music... ok
2017-06-13 20-02-06| Apply loaded settings... ok
2017-06-13 20-02-06| Adjust settings to GPU... ok
2017-06-13 20-02-06| Client initialized
2017-06-13 20-02-06| Received stats and achievements from Steam
2017-06-13 20-02-06| STAT_PIRATES_DESTROYED: 0i
2017-06-13 20-02-06| STAT_XSOTAN_DESTROYED: 0i
2017-06-13 20-02-06| STAT_CIVIL_SHIPS_DESTROYED: 0i
2017-06-13 20-02-06| STAT_SHIPS_DESTROYED: 0i
2017-06-13 20-02-06| STAT_STATIONS_DESTROYED: 0i
2017-06-13 20-02-06| STAT_RESOURCES_MINED: 2734i
2017-06-13 20-02-06| STAT_GOODS_TRADED: 0i
2017-06-13 20-02-06| STAT_GOODS_SOLD: 0i
2017-06-13 20-02-06| STAT_GOODS_BOUGHT: 0i
2017-06-13 20-02-06| STAT_GATES_USED: 0i
2017-06-13 20-02-06| STAT_WORMHOLES_USED: 0i
2017-06-13 20-02-06| STAT_JUMPS_USED: 0i
2017-06-13 20-02-06| STAT_SECTORS_DISCOVERED: 7i
2017-06-13 20-02-06| STAT_SECTORS_TRAVELED: 0f
2017-06-13 20-02-06| STAT_METERS_FLOWN: 45266i
2017-06-13 20-02-06| Finished download of workshop plan Prowler
2017-06-13 20-02-06| Finished download of workshop plan FX-4 HQ "Lair"-Class Flagship
2017-06-13 20-02-06| Finished download of workshop plan FX-42 PT "Dagger"-Class Patrol Boat
2017-06-13 20-02-06| Finished download of workshop plan FX-4 FF "Broadsword"-Class Escort-Frigate
2017-06-13 20-02-06| Finished download of workshop plan FX-42 CC "Rapier"-Class Light Corvette
2017-06-13 20-02-06| Finished download of workshop plan FX-4 DD "Claymore"-Class Flakdestroyer
2017-06-13 20-02-06| Finished download of workshop plan Javelin
2017-06-13 20-02-06| Finished download of workshop plan FX-4 TS "Diligent"-Class Cargo Hauler
2017-06-13 20-02-06| Finished download of workshop plan Deimos Class
2017-06-13 20-02-06| Finished download of workshop plan Comet Class
2017-06-13 20-02-12| Starting server 'bin/AvorionServer.exe' with arguments '--galaxy-name Why U No Load --server-name Nokta ☯'s Server --port 27000 --public 0 --safe-player-input false --alive-sectors-per-player 500 --listed 0 --authentication 0 --exit-on-last-admin-logout --admin 76561197993771932 --use-steam-networking 1 --threads 7 '
2017-06-13 20-02-12| Connecting to 127.0.0.1:27000, query port: 27003
2017-06-13 20-02-14| Waiting for Online polling threads
2017-06-13 20-02-14| Online polling threads finished
2017-06-13 20-02-14| Waiting for LAN polling threads
2017-06-13 20-02-14| LAN polling threads finished
2017-06-13 20-02-14| Client UDP: Error receiving from 127.0.0.1, error: Connessione in corso interrotta forzatamente dall'host remoto, received bytes: 0
2017-06-13 20-02-14| Client UDP: Error receiving from 127.0.0.1, error: Connessione in corso interrotta forzatamente dall'host remoto, received bytes: 0
2017-06-13 20-02-14| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-14| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-14| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-14| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-15| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-15| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-15| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-15| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
2017-06-13 20-02-15| Client UDP: Error receiving from 127.0.0.1, error: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione, received bytes: 0
[...] MORE OF THE SAME [...]
2017-06-13 20-02-34| Exited client main loop.
2017-06-13 20-02-34| UDP closed
2017-06-13 20-02-34| Client UDP: Connection closed
2017-06-13 20-02-34| Stopping local server ...
[Turns out is not a bug] Turrets systems and slots
in Bugs
Posted
Yeah, thank you. Turns out I'm just dumb.
I was used to the old system where every turret occupied one slot and never caught how the new system works.
Already got a reply from the support and there is no bug here indeed.
So, I'll turn my not-so-much-bug report into a suggestion as I'd like to think I'm not the only one who got confused by the system:
What about a grid-based interface in the ship display to better represent the slot usage of each weapon? I'm thinking something RPG inventory-like. Right now is very hard to keep track of the slots you have available and how much each turret is occupying. Might help to have a visual clue turning raw numbers into grid "space".
Without you people pointing it out it would have been hard for me to figure out the change, to the point I thought it was a bug (and got really frustrated in the the process lol)! I think players might benefit from more hints on how turrets and slot system works in the future.
Cheers.