|
Post by wiretown on Aug 1, 2017 22:48:15 GMT -5
I noticed that the level of some of my crew members reported on the manifest page next to the experience point progress bar was higher by one level than what is correctly reported on the individual crew member's stats page. Right now I have 8/19 crew members with incorrect records on the manifest page - all junior crew, no officers.
|
|
|
Post by fallen on Aug 1, 2017 23:42:12 GMT -5
wiretown - thanks for the post and welcome to the forum! There is a similar thread going around about 1.3.11 here, startradersrpg.proboards.com/thread/16278/ios-crew-updating-after-levelingI am not sure if it the same bug, as we don't have a reproduction example on the linked thread yet. Do you see this after paying crew in the spice hall? Does it correct itself if you go back to the main menu and reload the game? Each crew member maintains a little cache of data about their level in memory for quick access, and its clearly this cache is getting out of date somewhere along the line.
|
|
|
Post by wiretown on Aug 2, 2017 8:27:32 GMT -5
In my current game, the changes don't reset after going back to the main menu and reloading the game or restarting the game, and unlike the iOS problem the experience bars don't stay full after leveling. I'll start a new game today and try tracking the problem carefully to let you know when it first occurs.
|
|
|
Post by fallen on Aug 2, 2017 9:36:20 GMT -5
In my current game, the changes don't reset after going back to the main menu and reloading the game or restarting the game, and unlike the iOS problem the experience bars don't stay full after leveling. I'll start a new game today and try tracking the problem carefully to let you know when it first occurs. That is highly appreciated, since it sounds like this is not the same issue as the iOS bug. Anything that looks like a 1, 2, 3 explanation of how we can recreate would be worth its weight in gold. I've already spent some hours digging on the iOS one and it would be tough to go back in there right now without reproduction case.
|
|
|
Post by MintDragon on Aug 2, 2017 13:15:18 GMT -5
|
|
|
Post by fallen on Aug 2, 2017 13:48:47 GMT -5
Looks like this has been fixed for next
|
|
|
Post by Cory Trese on Aug 3, 2017 10:49:31 GMT -5
Yeah fixed.
|
|
|
Post by wiretown on Aug 3, 2017 23:38:22 GMT -5
Yeah, confirmed, seeing the same thing. Thank you all.
|
|
|
Post by fallen on Aug 4, 2017 10:21:48 GMT -5
Yeah, confirmed, seeing the same thing. Thank you all. Awesome! This is fixed for next
|
|
|
Post by wiretown on Aug 19, 2017 13:36:24 GMT -5
So, I hate to be posting this, but this problem doesn't seem to be corrected on Android in v1.3.13. I didn't see that anyone had mentioned it since the new release this week on the thread MintDragon had referred to above or newer threads; so, apologies if someone has already brought it to your attention and this is redundant.
Crew that leveled up after being paid in the spice hall incremented their levels and reset experience point progress bars on the manifest page. However, they did not increment level on the crew member column of the individual crew member's page. Experience point progress bar on the individual page does seem correspond to what is on the manifest page.
Also, it it hasn't already been requested, would you guys add 2-3 more seconds to the time the crew members comments stay up on the android version. The font is small enough that it takes a little longer to read on my phone than I currently get, which is a pixel XL; so, not that small.
Thanks!
|
|
|
Post by fallen on Aug 19, 2017 15:04:43 GMT -5
wiretown - nope, no one else has reported it yet. I haven't seen it, but I will try to reproduce it now. I've increased the time that the dialogs stay on screen by a bit. We'll keep working on Android sizing.
|
|
|
Post by wiretown on Aug 19, 2017 23:31:40 GMT -5
Thanks, let me know if you want me to reproduce it as well. Anything that will help.
|
|
|
Post by fallen on Aug 19, 2017 23:33:58 GMT -5
Thanks, let me know if you want me to reproduce it as well. Anything that will help. Its some sort of data caching issue. I am sure once I spot it, will be an easy fix!
|
|