Orbiting after successful launch. No engines no RCS fuel.
simply watching the craft orbit passively, the program occasionally will coredump. Upon restart, I'm given the option to retain flight, whch I accept. Next, from the list of "in progress flights" I am able to successfully resume the fight and eventually, just watching orbit another cordump will occur. This has happened while warping at 25x, I believe it happened once at real time also.
I have noticed generally, since the latest update, that coredumps generally are much more common. However, I have also started using a new device, a Samsung Tab A tablet, 10", so it is also possible that the program is just less stable on this device.
I will try to save this sandbox, and load it on my phone to see if I run into similar problems.
I get these coredumps fairly frequently, and not just during flights I had it happen once when the flight mode activity was loading from the editor. I also had it happen at least once in the editor.
I will try loading and playing around with SR2 with a freshly rebooted device and minimum other device activity.
Obviously the core dumps themselves are something that the app is not handling correctly but I agree that the tightness of resources on the device may well be pushing that button particularly hard.
Is there a mode I can set that will capture debugging info that I can send you after a coredump occurs?
Also, there are a few thoughts I have on tweaks to the UI that would make SR2 much easier to use on a tablet. Where is the appropriate place to submit those?