Even though I successfully scan the rock and even get the placeholder results popup the game refuses to recognize the task as completed. I have tried rebooting the game, going back to mission control and then back onto the rover, nothing works.
- Legacy ID
I have the same issue, and I have kept my savefile so you can try.
Other screens can be found here:
I have tried 2 places for the analyse without success. I also have a damaged wheel, I don't know which one it is so.
I am getting this same issue as well. I have tried launching another rover and abandoning my original, but the issue persisted. I was able to complete the rest of the mission without issue.
same having same issue. did you also get very slow descent speed also on this mission?
After trying several positions (a lot) I found one that works
Yeah, it seems that APXS is very sensitive and sometimes it's scanning some other nearby rock rather than the one you require. There should be some visual confirmation what rock you are scanning instead of waiting till it is finished.
Could not reproduce the issue. The task completes no problem. Please note that APXS is fairly sensitive and needs to be set up in the right direction (very subtle movements might be required).
You can still run the scan even if you are not set up properly which will naturally not finish the task.
The best way to set up the APXS is to get the hud to flash red and display the message "READY".
Please refer to the screenshot TKOMQAtest.jpg in the attachments.
@Accolyte: It seems, that "READY" is not enough, because as I had said, sometimes it just scans some other rock or whatever else. There should be visual confirmation about what rock you are really scanning.
Also rover controls in contrary are not very sensitive. There is slight delay when it starts moving and before you release it makes bigger move than intended. Never watched NASA video, but I would bet, they have this easier and it's not about angle of the rock.
It's possible from a different angle. After failing to complete the mission, I drove the rover around the rock to close in from another angle, still not completing the mission. Then I tried a third angle and it worked.
Edit: Maybe I should make clear, that I had the 'READY' message in each of the three scans, and didn't move at all while it was doing the 'radiating' thing. So it should properly work. However, the placeholder results pops up, but the task will NOT be completed. I played this particular mission several times now and never had any issues again. Even though when trying an angle that didn't work in an earlier attempt. But I still believe it's bugged.
Yes, approaching from a different angle is also possible.
The "READY" message should be enough. Only time I failed to scan properly with this message displayed is when I slid down a slope while scanning which interrupted the process.
I have no problem moving the rover very slightly by just tapping the appropriate direction key(s).
Like i said I never reproduced the issue and completed the scans on the first try. As far as I can tell there is nothing wrong with the trigger. The problem is you are not aligning your rover correctly.
It definitely needs more visual cues to make this type of scanning easier. I don't see any fun in scanning same rock 3 times from different angles. Compared to other scanning systems, this is slowpoke.
@Acolyte: You have not been able to reproduce it even with the save I send and not touching the rover, just the scan (which is blinking red?).
Because I have scanned more than 10 times on that exact position on the save and always had the bug reproduced. I am sure I can even make a video of it.
Oops, I missed your save before, UbioZur. I checked your savegame now and even though i was able to complete the task in the end, it took me several attempts. At first it was enough to just move to the opposite side of the rock, but when I tried it again it was still giving me trouble.
I've consulted Dram and he promised he'd have a look at it.
Thanks for your reports and files, guys. We appreciate it even if I was acting skeptical at first :)
This issue should be fixed in next dev build, but I will close it since there are other reports about problems in this specific mission. Thanks everyone for your cooperation.