It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Whenever allowing the game to run for a long time (including in background), especially if it's for 24+ hours - item randomization in shops and ship vendors starts to fail, producing series of idential items and ships.

When this bug happens, 2+ ships or items appear in stock which are completely identical. Often in pairs (two ships - identical in their looks, stats, passives, class, everything), then another pair of different ships from the same vendor at the same time "further in the list".

This video demonstrates 5 common armor items, of which 4 in a row are entirely indentical.

https://www.youtube.com/watch?v=YAabd8Tddp4

P.S. This bug possibly also affects not-so-long play sessions to lower extent - hard to say.
Thanks Fins.

I saw your 'Mini Striker' and other stuff on Discord. Letting the game run for +24h is something I still want to do, mainly for profiling memory usage. But it is great to already have a few things on the list to watch for while testing. I'll make a bug ticket for this RNG issue.

Best regards
Ingmar
avatar
RFG_Ingmar: Thanks Fins.

I saw your 'Mini Striker' and other stuff on Discord. Letting the game run for +24h is something I still want to do, mainly for profiling memory usage. But it is great to already have a few things on the list to watch for while testing. I'll make a bug ticket for this RNG issue.

Best regards
Ingmar
I am still running same game instance, now something close to ~48 hours. Can see no RAM leak whatsoever, ~2789xxx kb process at the time (16 Gb machine). Few small glitches here and there, most of them promptly fixing themselves, nothing serious.
After all, it seems there are possible circumstances where significant memory leak occurs. With some ~60 hours long session, the game process ended up being over 3.5 Gb in memory. I could go on with it, but now having the leak possibility confirmed, i restarted the game to see how big in memory the game process would be when "fresh". Which, for me - is ~1.7 Gb. I.e., half the size before the restart.

Knowing there are folks with powerful rigs who like to keep game clients running in background for weeks, this won't do... :(
Update: the item/ship randomization bug indeed also happens without long play sessions: now i got it merely ~1.5 hours play session. This time it produced four ships in a row with exactly same cost, and three of those ships were completely identical scouts. Video of it:

https://www.youtube.com/watch?v=XA2mHPaPzGw

Chances of 3 identical ships in a row happening as a coincedence - would be at least the following:

1 / (6^2 x 5^2 x 10^2) = 1 / (36 x 25 x 100) = 1 / 90000 ~= 0.001%.

where
- 1 / 6^2 is the chance to get 3 ships of same class in a row;
- 1 / 5^2 is the chance to get 3 ships with same passive in a row;
- 1/10^2 is the chance to get 3 ships with same paintjob in a row (using _very_ modest estimate of only 10 possible painjobs).

In other words, if it's "just coincedence" - one would need to browse through at least 90000 ships, on average, to see 3 such identical ships _once_. And i see such occasions repeatedly. Something's very wrong with randomization code...

Save file with those scouts - sent to Ingmar.
Post edited May 06, 2021 by Fins_FinsT
Update: another "1 in 90000+ tries or rarer" bad case of this bug. As before, it's 4 ships with same price, 3 of them completely idenctical - though this time it's not gunboats. Once again, not a long play session - slightly above an hour after start of the game.

https://youtu.be/Fdyxhk9KFn4