Given the number of questions, I think @Guljaca could be a great help in writing the manual, pointing out certain things in the game that should be clarified.
If he had been more polite, of course.
Based on his profile, he is a Russian speaker. In my day job, I work at a multi-lingual company that includes many (ex-pat) Russian speakers who produce work in Russian and participate in Russian Telegram and Slack channels.
I can read Cyrillic but have a limited understanding of the language so I generally translate everything into English. Every single Russian I work with is unfailingly polite when speaking English and when communicating in Cyrillic.
It’s not a translation problem - he is like that in Russian too 
2 Likes
Problem wasn’t his several questions or why he wasn’t looking by himself rather than asking, problem is that every post from him contains a complain against the game, against the developer that did not address that certain aspects as he would instead do since for him everything is very easy and obvious to implement, so the developer is basically dumb for not having addressed these.
Like he had paid for Aurora so has the right to said certain things, he did not get that Aurora was made by a single person on his free time, that it is free and not involves a triple AAA company with millions.
4 Likes
Hey, referencing the jump endlessly thing, I had reported this earlier and I think Steve explained what was happening and made some changes for it in at least one of the Aurora versions somewhere. TL;DR: Fully automated surveying by combining the Survey next X Bodies/Locations and Move to System Requiring Geo/Grav Survey standing orders works up to a point, until the next place it should move to is too far away for the automated logic. Keeping the standing orders and manually ordering the fleet to where it should go next should solve the issue and have it resume automated surveying.
Basically, the automated “Survey System” or “Move to System Requiring Grav/Geo Survey” standing orders in the original code had limits to how far it would look. In the case of survey system, it would look for surveyable points within X billion km. If a fleets only standing order was one of the survey system orders, it would basically “give up” surveying if it didn’t see any surveyable bodies or locations within that limit, even if the system was not 100% surveyed. Common problems with binary star systems or massively spread-out asteroid belts.
Similarly, I believe the “Move to system requiring Geo/Grav Survey” orders also had a limit, and basically if it knew there was a system it should move to, but that system was beyond the number of jumps the pathfinding algorithm would look, it would get stuck just jumping back and forth through the same jump point.
When this happened to me in case #1, I would order the survey ship to manually fly to a far-off unsurveyed body, and once out of manual orders the Standing Order would take over again until once again there were no unsurveyed locations or bodies found within the km limit. Similarly, when I saw a survey ship jumping between points, I would manually give them orders to an unsurveyed system at which point the automate standing orders would take over again.
I believe in the current or next Aurora version Steve exposed the KM range limit for in-system automated surveys and for # of jumps for Move-to orders so you can configure them to be higher if you wish. I can’t verify where though, as much like constantly waiting for the next research to finish before designing a new ship, I’ve kept holding off starting a new game until 3.0.0 is released.
EDIT: I found this in the v2.6.0 changelogs for the GeoSurveying at least, not sure if there was one for Grav:
Maximum Geological Survey Radius
Currently, Fleets with standing orders to conduct geological surveys will only consider bodies within ten billion kilometres. This is from their current location (if they have no existing orders), from the last location in their orders list, or from the last surveyed body if they have a standing order to survey multiple bodies.
For v2.6, this range can be changed. There is a new text entry field in the Misc tab of the Fleet tab of the Naval Organization window called Maximum Geological Survey Radius, where the range can be set. A 0 value will be ignored and the default 10b km used instead.
The radius could be increased for very large systems, or used to restrict surveys to a small area - for example, a gas giant and its moons - if the system contains hostile forces.
Thanks for this, I haven’t had such a hearty chuckle in a while.
1 Like