Known Problems and Future Improvements

This page lists currently known problems (bugs) and suggestions for future improvements for Centurion. Most of these have been reported/suggested by users. You can participate by reporting bugs and suggesting improvements too. You can track items of your interest here and also contribute to suggested solutions or make comments about urgency and usefulness. For this, each item has an individual page with more details, ideas how to fix/implement, and the scheduling.

FI#23: Enemies details in job definition window
In the combat analysis the properties of the enemies are shown and can be understood very quickly, for example hit points, initiative, flanking and so on. It would be very useful to have these as a tooltip when defining a job… Details.
FI#21: Optimisation – Specify Target Grid
Please allow to configure the grid level that Centurion is optimising to. Sometimes it is sufficient even for optimisations (not just useful generals) to stop at 8x or 4x. Precision might be enough and it may save calculation time. Details.
FI#20: Re-calculate All
Can we have a re-calculate all button/menu option? When I change general skills etc, I want to go to a save and run all the calculations again to get the updated numbers. Currently I have to click on each entry and click ‘Run’. Would be nice to be able to click one button to add all jobs back t the queue. Details.
FI#17: Truncated Fields in Adventure Plan
Some fields in the list of adventure plan items are truncated, i.e. the information contained in them is often too big for the available space. There is a tool tip that pops up but it is only there for a few seconds. Details.
FI#18: Gameplay with Checkboxes
While the gameplay in the agenda is a good idea, it would be more natural/convenient/simple if it worked with checkboxes rather than buttons and a filter. Details.
FI#16: A Name for Jobs
Allow jobs to have a name, much like adventure plan items. This would allow to better distinguish them in the job list. The command line may serve as a way of distinguishing them but it is lengthy and inconvenient. Details.
FI#14: Best General & Book Feature
There is a best general feature, but would it be possible to make a best general & book feature. Ie give them an army (or armies) they are going against, give them a selection of generals to test, and let the program run each general with each combo of books. Just for those of us who aren’t great at deciding how to spec out generals for certain adventure series. Details.
FI#12: Highlight the main/boss camps for easier identification
Original request: “Was ich auch noch super schick fände: wenn in der Lagerliste für ein At die Hauptlager irgendwie kenntlich gemacht wären, fettgedruckt oder farbig hinterlegt z.B. Ok, wär Luxus, aber fein. :-)” Details.
FI#9: Reduce calculation time by avoiding recalculations on smaller grids
There seems to be a lot of wasted calculation when reducing grid size. If I run a job where there is a small range of possible troops allowed, the grid calculations (x64x, x32x, x16x, etc) all seem to repeat the same calculations for the hi and lo range of troops numbers, at each resolution. Finally, as resolution drops below the give range, there are additional calculations for the middle of the allowed range. I am guessing this is how it works by looking at the “progress” column. There is enormous potential for speed up by saving calculations at points in the grid which will be repeated in the next smaller resolution. Details.
FI#5: Improve Runtime Performance on UsefulGenerals
Running a useful Generals query right now, still only using one core, seems like this would be a good query to run on multiple cores/threads, one for each general Details.
FI#4: Easier Access to Enemy Troops and Their Names
You can’t print all the (emeny) troops and their names, nor can you hop over to the browse and look at it when you have the window open to enter them into an attack. Maybe you should add them to the end of the manual as an appendix so they can be looked up, or printed from there. Details.
KP#13: Poor Optimisation Result (Lock) (by Derwish77)
The following command line leads to a poor optimisation result: “-Camp=JuHolz#11 -Objective=Lock -Attack=*BSK;*GSS;Tav“. Details.
KP#8: Generals buttons (by CHS)
The graphical generals don’t give an easy way to see the difference between original and new generals. Details.

Solved: KP#1, KP#2, KP#3, KP#4, KP#5, KP#6, KP#7, KP#10, KP#11, KP#12, FI#1, FI#2, FI#3, FI#6, FI#7, FI#8, FI#9 (part 1), FI#10, FI#11, FI#13, FI#15, FI#19, FI#22