From my perspective it's a bug since the arm is not moving, but a sound is being played...
May 11 2016
Okay, reworked title and description. I hope it's clear what I want.
This is not about cheating, but to increase usability by automizing tasks.
I am aware this might be a little bit against the idea of a simulation, but after resetting my robotic arms around 30 times to the initial position I am quite annoyed of it. I feel an automatic function would be okay since I expect NASA would use similar functionality to help the operator of a rover...
Community might give votes if they like the idea or not.
So long, up to the devs if they like it :-)
I still have the same problem in game version 0.8.174 and provided my save file.
You can connect to the vehicle "Liberty" and try yourself.
I agree to that. I'd rather mount the camera to the front and the APXS to the back...
I have the same problem with my rovers occasionally, too.
A broken wheel can be less pain, because the rover keeps moving.
When having a major part failure with the wheel stuck it's even worse than breaking it...
Well okay, that was not obvious right now since the descriptions on how items work are not yet available within the game.
Anyhow I did not yet find a field to tell the player the current radiation level, whilst atmosphere pressure and temperature are displayed in the HUD.
Would be great to add that if you have time :-)
I agree on that.
I had several rovers that were already broken when moving the first 20 cm on the landing platform. Once a rover had a major wheel error right after leaving the landing platform - I could not even move 3 m away from the platform.
The invest in a rover is pretty much useless if you cannot even reach your first target scenery?!
Btw, the wheel errors happen to medium quality items, too - right after landing.
Using dev build 0.8.172.
I get the same error message upon starting Gravon.
The camera swings around for around a second, then the game freezes - the console monitor keeps black.
Upon pressing space i have a CTD.
I am using Windows 7 Ultimate x64.
Btw I noticed the last entry in filesystem.log with a timestamp 2 seconds before the time stamp in crash.log:
16:19:27:0952 R 1000e94 :sounds/music/mainmenu.ogg
Maybe that helps?!
I'd like to add, that I feel the explore point should be achieved even when landing near and not exactly on target.
It's okay that the lander misses the exact landing point, but if the mission can still be accomplished it should start, shouldn't it?
So if the lander still hits the area where it should scoop, take photos, etc, there should be a way to do that?!
(I missed some "explore" point in Victoria crate three times in a row with a large lander, almost made my space program bankrupt...)
I think there should be a possibility to steer that lander for game fun over realism.
I had three large landers in a row that failed to hit the designated target point. They missed the correct exploration point by 70 to 90 meters. As a result the mission did not start, so no taking of photos, no probes etc.
This nearly killed my space program, invested and lost around 7.000k without any invest - quite a hard failure on investigating the first crate.
Maybe one could be moving a lander similar to a rover? Moving one "leg" at a time. It would be very slow of course and maybe not that precise as with a rover, but at least one would not loose the money to further run ones Space Program.
Anyhow, why does the game start in first person view?
There is nothing interesting to see until you have touched the ground.
I'd rather suggest to automatically start all missions in 3rd person perspective (as the intro video does, too).