Page MenuHomeFeedback Tracker

APXS analyser in mission "two impact craters"
Closed, ResolvedPublic


Hi I think that the
APXS analyzer is maybe broken or the mission named "two impact craters" in career mode have a bug..:

Look photo


Legacy ID
Steps To Reproduce

Use the standard rover for the mission.
Drive to a rock that you need to analyze.
activate the APXS by pressing the icon of the drill.

You will now get the error " no target in range". Look photo

Additional Information

I tried to ram the rock, no effect.
I tried to use both ends of the rover, no effect.
I tried to use the side of the rover, no effect.

When I go to mission control and press the rover ( on the map ) then I get a list of parts on the rover. It say it have an APXS ( advanced particle x-ray specternomer. ) and it is "OK"
So im pretty sure my rover i working..

Also I notised that tough the rover have a camera in both ends, then only one of them work. Maybe this is the problem since it cannot look/mesure the distance with the end of the rover that have a bug... Just a guess.
( all parts on the rover are OK).

Event Timeline

delevero edited Steps To Reproduce. (Show Details)Aug 1 2013, 6:17 PM
delevero edited Additional Information. (Show Details)
delevero set Category to category:bugs.
delevero set Reproducibility to Always.
delevero set Severity to None.
delevero set Resolution to Fixed.
delevero set Legacy ID to 1122412210.May 9 2016, 9:47 AM
delevero added a subscriber: delevero.


It IS POSSIBLE to scan if the rover are put in reverse and driv into the rock.
It take alot of adjustment and luck to make it work.


The problems is that the trigger is very small.

I think the trigger need to be made a bigger so it is more easy to scan rocks.

Bohemia added a subscriber: Bohemia.May 9 2016, 9:47 AM

i think its better this way ... in real life your scanner cant just easely scann things serveral meters away . you need to be like one cm or simthing like that away from it

FredyC added a subscriber: FredyC.May 9 2016, 9:47 AM
FredyC added a comment.Aug 3 2013, 9:04 PM

Yeah, watch for your distance indicator, it works only when there is exactly 0 distance. Having 0.1 doesn't work. Usually it means you really have to ram into that rock.

Scanners surely have some range to be able to work. Other thing is if you need to grab some sample physically. That should be solved with some arm, that can reach there.

mintme added a subscriber: mintme.May 9 2016, 9:47 AM
mintme added a comment.Aug 4 2013, 7:01 AM

The Second crater on Mission "two impact craters".. the rock that needs APXS i have scanned and analyized a few times now and it will not make the task complete.

FredyC added a comment.Aug 4 2013, 8:23 AM

APXS can scan every rock, but only those highlighted are valid for mission. You have to be sure, that you are facing rover with correct side where APXS instrument is installed.

mintme added a comment.Aug 4 2013, 8:28 AM

yes make sure your not on the side with your camera. then get up to the rock and you need to get its distance to the rock to 0 not 0.1 but zero. just take it slow. ramming will not work.

Reject added a subscriber: Reject.May 9 2016, 9:47 AM
Reject added a comment.Aug 4 2013, 3:18 PM

This isn't an issue at all, Scan the same rock(the one highlighted) a few times and it will work, the rover needs to be flat, not moving and APXS should be on the front of the rover, with the cam at the back, this give a better reach for the APXS.

I found if I built a rover and put it on the back the solar arrays would stop me from getting close enough to the flat rock.

Please note that by default the APXS is located on the FRONT of the of the rover. On your screenshot, the rover's back is facing the rock. Please confirm that the issue persists after you made sure that the correct instrument is facing the rock.

I was not able to reproduce the issue. I scanned the rock without a problem.

Salat added a comment.Aug 16 2013, 5:12 PM

APXS range has been slightly increased, so scanning rocks with it should be somewhat easier. The problem with mission not registering succesful scan has been fixed and should be fine in next development build.