Testing 165 - Report issues here

Please report all issues discovered in Testing 165 in this thread.

1 Like

Release feedback–but no release notes? Dunno what I’m supposed to look for!

Test driven development?

The update is underway at the moment. It includes a resource regeneration so will be offline for a hour or so while it happens. Release notes will be alone in a bit.

3 Likes

Getting disconnected a fair amount… first time was while crafting the beacon. This time I was just chopping leaves on my plot.


I have chunk cache at max and low for download.

Once back in I am getting lag as shown here…

here are my pings:

Are there any strange errors in the logs?

Only Errors and Warn are as follows:
[2017-06-15 15:28:04] ERROR failed to get planet assets for world ‘use_c1_home’ Settlements
[2017-06-15 15:29:34] WARN HTTP request https://gs-testing.playboundless.com:8444/api/map/0/78_73?connectionId=10 responded with status: 0 body: ‘’ error: ‘Failed to connect to gs-testing.playboundless.com port 8444: Timed out’
[2017-06-15 15:29:34] WARN Retrying request for chunk lod0/78_73
[2017-06-15 15:29:34] WARN HTTP request https://gs-testing.playboundless.com:8444/api/map/0/80_72?connectionId=10 responded with status: 0 body: ‘’ error: ‘Failed to connect to gs-testing.playboundless.com port 8444: Timed out’
[2017-06-15 15:29:34] WARN Retrying request for chunk lod0/80_72
[2017-06-15 15:29:34] WARN HTTP request https://gs-testing.playboundless.com:8444/api/map/0/79_73?connectionId=10 responded with status: 0 body: ‘’ error: ‘Failed to connect to gs-testing.playboundless.com port 8444: Timed out’
[2017-06-15 15:29:34] WARN Retrying request for chunk lod0/79_73

Ran this while the game was running in background.

Pinging gs-testing.playboundless.com [54.198.129.76] with 32 bytes of data:
Reply from 54.198.129.76: bytes=32 time=119ms TTL=42
Reply from 54.198.129.76: bytes=32 time=138ms TTL=42
Reply from 54.198.129.76: bytes=32 time=108ms TTL=42
Reply from 54.198.129.76: bytes=32 time=91ms TTL=42
Reply from 54.198.129.76: bytes=32 time=91ms TTL=42
Reply from 54.198.129.76: bytes=32 time=93ms TTL=42
Reply from 54.198.129.76: bytes=32 time=94ms TTL=42
Reply from 54.198.129.76: bytes=32 time=91ms TTL=42
Reply from 54.198.129.76: bytes=32 time=285ms TTL=42
Reply from 54.198.129.76: bytes=32 time=308ms TTL=42
Reply from 54.198.129.76: bytes=32 time=124ms TTL=42
Reply from 54.198.129.76: bytes=32 time=146ms TTL=42
Reply from 54.198.129.76: bytes=32 time=91ms TTL=42
Reply from 54.198.129.76: bytes=32 time=94ms TTL=42
Reply from 54.198.129.76: bytes=32 time=99ms TTL=42
Reply from 54.198.129.76: bytes=32 time=95ms TTL=42
Reply from 54.198.129.76: bytes=32 time=101ms TTL=42

Ping statistics for 54.198.129.76:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 308ms, Average = 127ms

Pinging gsuse1.playboundless.com [54.88.128.84] with 32 bytes of data:
Reply from 54.88.128.84: bytes=32 time=194ms TTL=43
Reply from 54.88.128.84: bytes=32 time=226ms TTL=43
Reply from 54.88.128.84: bytes=32 time=283ms TTL=43
Reply from 54.88.128.84: bytes=32 time=92ms TTL=43
Reply from 54.88.128.84: bytes=32 time=97ms TTL=43
Reply from 54.88.128.84: bytes=32 time=93ms TTL=43
Reply from 54.88.128.84: bytes=32 time=93ms TTL=43
Reply from 54.88.128.84: bytes=32 time=92ms TTL=43
Reply from 54.88.128.84: bytes=32 time=222ms TTL=43
Reply from 54.88.128.84: bytes=32 time=105ms TTL=43
Reply from 54.88.128.84: bytes=32 time=210ms TTL=43
Reply from 54.88.128.84: bytes=32 time=230ms TTL=43
Reply from 54.88.128.84: bytes=32 time=283ms TTL=43
Reply from 54.88.128.84: bytes=32 time=93ms TTL=43
Reply from 54.88.128.84: bytes=32 time=99ms TTL=43
Reply from 54.88.128.84: bytes=32 time=95ms TTL=43
Reply from 54.88.128.84: bytes=32 time=96ms TTL=43
Reply from 54.88.128.84: bytes=32 time=94ms TTL=43
Reply from 54.88.128.84: bytes=32 time=234ms TTL=43

Ping statistics for 54.88.128.84:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 283ms, Average = 154ms

The testing server are hosted in the US East (Virginia). Your ping currently is 600ms which is above the 500ms max so it will kick you after a while and it looks like some intermittent issue. Given your other pings are much lower this looks like routing issue at the moment. You can tell you ISP, as its Amazon data centre they may look at it or they may well resolve it.

1 Like

Will do thanks!

I know that there is a note in the patch about:

  • [new] Objectives & Feats - Some tasks are not being tracked correctly.

Just wanted to note that the objective: Building a Crafting Furnace Part II
is not tracking as well. I believe this was not accessible in the previous release due to not being able to enable the crafting objectives.

-Till

1 Like

Thanks for the information, we’ll make a note that it’s still not working.

1 Like

Is it normal, or just me that I dont lose stamina while sprinting? (Just started testing now.)

1 Like

Stamina is not lose at all, but it’s good :grin:

2 objectives that not working.

I got problem to use the first 2 spots in inventory, they are grayed out, if i move the tools to another spot it works.

2 Likes

Whats the story with coordinates? it reads like 395N and 394E. I actually like it this way as its intuitive and I dont have to learn which one of the 3 numbers is NS axis and which one is WE axis. However, after going North and hitting its maximum value it doesn’t change to South maximum (and then going down to 0), but starts counting the North value back to 0.

So the releases for me are actually getting worse. I hope this actually doesn’t hit live for a month or so, because this is completely unplayable. Bugged beyond all reason, and there are only more being added every two weeks.

This is where the testing version ends for me, as in I cannot progress in ANY of these objective lines beyond the point I have reached with them.

STORAGE BLOCKS (not actually tested)

  • Have not unlocked any recipes for storage blocks, cannot unlock any recipes until I level up. I am miles away from the next level, and since I cannot complete the other objectives, I cannot even reach a point where I can test this one

BUILDING A CRAFTING FURNACE

  • bugged, already been reported

SHARING YOUR CURRENT LOCATION

  • bugged, already been reported

THE MERCHANT’S TRADE

  • Tried to coordinate with @boundmore so we could find each other and test this objective
  • Coordinate system is bugged, cannot figure out which direction to head in as sometimes the numbers are increasing, sometimes they are decreasing, with no discretionary motivation for them doing so.
  • I tried to warp directly to his beacon from sanctum, put me (what i think is) hundreds of coordinates away
  • Even on voice chat, were entirely unable to find each other, gave up after a few minutes and discovering the bugged coordinates.

So progression is at a standstill beyond this point for me. I would need to unlock a bunch of recipes and level up through passive means for hours to even test anything else. Have seen no progress in addressing bugs or game-breaking issues for the past month. Not sure if any of this is even valuable to report at this point, as many of these issues have been present for the last 3 testing releases and haven’t been addressed.

1 Like

my suggestion is to bring the objectives and things from test which currently work to live - while keeping the other bugs/broken things in test

I say this due to the fact that live as great as it is - is getting somewhat a bit been there, done that kind of thing now - we need more stuff to do in live and etc - and because of this the update will most likely get pushed further and further back (which is not a bad thing because you need to fix a lot of stuff i understand this) its just, well we need some more things to do in the live version IMHO - with people moving/stocking/inventory sorting on live for the *upcoming in a week * change but that seems like its going to be a while now due to the new bugs found on test which i will not report on because it already has been

Some sentence fault.
Should probably be a “use” there.

1 Like