Author Topic: Beta Branch Patchnotes 0.12.5  (Read 2377 times)

koonschi

  • Developer
  • *
  • Status:
    Offline
    Posts:
    1623
    • View Profile
    • Avorion
on: July 08, 2017, 07:15:30 PM
Patch 0.12.5

Date: July 8th, 2017

This time the patch took us a little longer - we had some trouble pinning down the bug that would randomly (and I mean, randomly) teleport asteroids and stations through the sector, resulting in them intersecting, which would in turn deteriorate performance a lot. But we fixed it, and if nothing else comes up, then this patch and the Alliances update will most likely make it onto the stable branch very soon!

Gameplay
  • Added auto-pay crew for alliances
  • Alliances have the same initial relations as their founder
UI
  • Galaxy map territory is now updated in colors of the currently flown ship (alliance or player ship)
  • Beta branch warning is now only shown once in main menu after starting the game
    • The warning will still show up every session, but only once per session
Misc
  • Improved german localization
  • Improved performance of sector generator
  • Added comment explaining how namespace comment works
Scripting UI
  • Added a Physics component for manipulating physics of an entity
Bugfixes

"As always, user bug reports are marked with [UBR]. Thanks again to everybody reporting bugs and helping us improve the game!"
  • [UBR] Fixed stations and asteroids teleporting through the sector
  • [UBR] Fixed stations and asteroids getting stuck into each other forever and destroying performance
  • [UBR] Fixed unnecessary warnings when converting databases to new format
  • [UBR] Fixed an issue in faction database when starting the game in a directory linked via symbolic links
  • [UBR] Fixed faction war side decision triggering wrongly when repairing ships of one side
  • [UBR] Fixed wrong tooltip description for repair beams
  • [UBR] Fixed incorrect spelling of zinc
  • [UBR] Fixed a crash in trading overview upgrade
  • [UBR] Fixed a crash in diplomacy tab when sorting or filtering
  • [UBR] Fixed a few issues with tutorial when creative mode is active
  • Fixed ships sometimes not moving when strafing
  • Fixed scrapyard not working correctly with alliances
#define TRUE FALSE // happy debugging suckers

If you need help, please post in the forum, don't PM me. If there's something that only I can help you with, contact me via mail.



Jack_Miron

  • Newbie
  • *
  • Status:
    Offline
    Posts:
    44
    • View Profile
on: July 10, 2017, 10:47:41 PM
 ;D thx



shadetheartist

  • Newbie
  • *
  • Status:
    Offline
    Posts:
    11
  • [I APOLOGIZE IN ADVANCE]
    • View Profile
on: July 12, 2017, 02:43:17 AM
Has there been any consideration into equalizing the work that should have been done in a sector the player is not in?

As i understand it, such sectors are updated at a greatly reduced rate for the sake of efficiency. Therefore if i create a captained mining ship and set it to mine in a sector and depart in search of adventure, i would expect the miner to gather resources at the same rate regardless of a player's presence.

In some tests i did in single player i noticed a vastly reduced rate of harvesting from my miner if i was not in-sector. So i assume that the reduced update rate is what is causing that.

Perhaps a simple way implement sectors wherein there are mining entities would be to abstract the ai action away to a "+N Minerals/Jump" or something like that through analysis of player created ships with a captain set to mine. For instance you could count the number of mining turrets * their strength and factor in the speed of the ship and the asteroids in a sector and come up with "+1300 Titanite, +32 Iron per Jump. %64 Titanite, %88 Iron left.", which you could see if you were to hover over the sector summary from the map (which would have a little mining symbol on it or something to indicate your investment there).

I'm thinking per jump to avoid the obvious exploit of leaving your computer on overnight and coming back to a boatload of minerals. It will also encourage exploration.

So yeah any thoughts around that? Thanks :D
//fixed stupid bug lol
//#define TRUE FALSE  // happy debugging suckers