#Gemini constellation research boost speed does not seem to be working correctly

1 messages · Page 1 of 1 (latest)

sinful thorn
#

Several days ago, I completed the Gemini constellation in the Beyond. Then yesterday, while I was progressing on mission number 9 for Polaris, I saw that there was about 12 hours left for the mission. So I thought I would just activate the research boost. And since I had completed Gemini, a single 4 hour research boost should have covered the entire remaining duration of the mission. The research boost was even showing the "x3" logo while active.

However, when I came back at nearly the end of that 4 hours, there were still just over 4 hours left on the mission instead of it being about to finish. So even though the boost was saying "x3", from the times that I saw, it was really only giving me an x2 boost.

My apologies for not having a screen shot at this time. This was my last mission for Polaris and I do not have any other missions anywhere. Assuming that there is another beta reset, then I should be able to replicate the issue at that point.

I did just think of something. I was not logged into the sim for those 4 hours. Would the research boost have a different rate if I wasn't logged on? I think that would be really weird and would probably need to be advertised better if that is the case since that is definitely not an expectation that I woudl have.

sinful thorn
#

I should note that this was in 19_27.

sinful thorn
#

I just checked in version 19_36, and I have some more data.

#

Today, I started a new run for the beyond, and once I had all of the requisite stars, I went and placed all of them into gemini:

Screenshot_2023-08-23_at_14.06.13.png
#

This didn't change the research boost option. But that was expected.

Screenshot_2023-08-23_at_14.06.27.png
#

I then went ahead and timed the first of the North Star missions. I mistimed the start of the timer, but it came out to about a minute and a hald, which was about expected for a 5 minute mission at 3x speed, but there was definitely some error in the timing measurement.

#

Then I started timing the second level. This level was fifteen minutes long, but with the 3x bonus, I was able to get a timing of 5:28. The expected time for this would have been 5:00. But 28 seconds over is just under 10% extra. I could see this being caused by conditions on my computer.

Screenshot_2023-08-23_at_14.11.40.png
#

Next, I went ahead and timed the level 3 mission. Normally, this mission would have taken 50 minutes. The expected time for this with a 3x bonus would have been 16:40 or 1000 seconds. The time that I measured was 18:28 or 1108 seconds. Again the measured time was greater than the expected time by around 10%, so this is still feeling like a 3x bonus.

I should note that all of these runs were done completely within the Beyond simulation with the simulation in the foreground for nearly the whole time.

#

The really interesting thing happened when I timed the level 4 mission, which was normally would have a duration of 2:10:00 or 130 minutes = 7800 seconds. With the 3x bonus, the expected time would be 2600 seconds = 43 minutes 20 seconds (43:20). However, for this run, I had to shut down C2S completely. I had the timer running during this period, so I was able to measure this down time at 37 minutes. The total time for this run was 57:24 or 3444 seconds.

#

Since C2S was down for 37 minutes of that 57:24 time, that means that it was running for 20:24 or 1224 seconds. Multiplying by 3, we find that these 1224 seconds account for 3672 of the 7800 seconds of the normal mission time. In other words, based on the previous runs, we can confidently say that for those 1224 seconds, the mission was running at roughly 3x speed, and this caused the mission timer of 7800 seconds to tick down by 3672 seconds. But if we assume the same 10% extra time as in the previous missions, then the 3672 seconds becomes 3338.2 seconds. Subtracting this number from 7800 seconds, we find that 4461.8 seconds of mission time are accounted for by those 37 minutes = 2220 seconds when C2S wasn't running. If we divide 4461.8 by 2220, then we get 2.01. This means that mission was running with a x2 bonus rather than a x3 bonus while C2S was shut down. To say the least, this is not what I would expect since this is a time bonus, not a resource generation bonus.

#

For the level 5 mission, which normally lasts for 4:40:00 = 16800 seconds, I did something similar. The expected run time with the x3 bonus should be 5600 seconds = 1:33:20. The actual run time was 1:48:42 = 6522 seconds. This is over by about 16.4% which is kind of noticeably larger than the previous 10% overage of levels 2 and 3. However, for part of this run, I was doing stuff in the Mesozoic Valley, and the rest of the time, the simulation was in the Beyond. So if the timer bonus was running at x2 while I was in MV, then this might account for the extra 6.4% of the time.

#

The upshot off all of this seems to be that the x3 bonus that players get when they complete the gemini constellation turns into a x2 bonus when the beyond is not running.

empty raft
#

what the fu-

sinful thorn
#

I can confirm that this bug is still happening in 19_54.

sinful thorn
#

I have been able to confirm this bug in 19_58 as well.

zinc wagonBOT
#

This has been added to our bug tracking system as the issue CELL-1149. As we resolve that issue, updates will be posted back here.

sinful thorn
#

Unfortunately, testing this in 19_70 would involve resetting my Beyond progress, so I do not have any test data for 19_70 at this time.

queen raven
#

@smoky epoch

sinful thorn
#

Since there is a Tea Event going right now, does that mean that going into the Beyond will reset my Beyond progress?

sinful thorn
#

I did check with the most recent release, and this bug is still showing up in verison 20.00.

smoky epoch
#

Unfortunately we have been having problems replicating the issue you are describing, so it might take time to implement a proper fix for now.

sinful thorn
smoky epoch
#

I think is fine for now, as you are the only player so far who have found this so far. We will keep an eye on more reports about this however 🙂

sinful thorn
#

If you are having replication issues, then I wonder if I mentioned that it is really hard to notice this on shorter mission lengths. My apologies if I didn't mention this earlier. It becomes much easier to see with a longer mission length, like say 12 hours. Also, it is possible that I have only been using the special missions (missions associated with specific objects) for testing. Let me take a look and see if it happens with the more general missions like the red dwarf missions.