The families of Aurora players are grateful the C# version is not going to be available before Christmas so that they can have one last nice holiday time before their loved ones get too busy playing all day

is there a way to track progress? am still checking every other month but apart from changeset posts the closeness to release is not even fuzzy but just impossible to desume

I can't really give a release date. It depends a lot on the availability of my free time and how well I maintain enthusiasm. I can say I am a long way past half way in terms of the functionality but I still haven't touched combat or AI and have about a third of the different movement orders still to do, plus several of the smaller windows. Once I finish working on move orders, I will probably work on new game creation so I can start a test game. I have been working on this since March 2016, so already 18 months in. I would be disappointed if I didn't start posting test campaign reports this year but don't believe there will be a release version before 2018.

Think we will have a workable version by the 11th of december?  Im going on vecation 😀

HMM Nope 

Maybe to make bug reporting less overloading for Steve (for instance, if someone's messing around with the game), maybe we could get a github issue tracker or something?
So we can categorically confirm bugs and also see if it's necessary to reproduce them in cases.

Completely up to Steve - he's the customer for the information in the bugs thread.  The big downside that I see for it is that it's another place people (especially Steve) would need to go to keep up with what's going on.  For one thing, this would probably lead to fewer bugs-that-aren't being answered by the community.

John

Tbh im pretty sure there are a 100 different libs that Steve could tack on at some point to do that so its not a huge stretch to ask for something that would in essence make his life easier. Being a Software developer myself there is nothing harder to debug than someone going "it crashes in Place A" with no other information to go on. A Full Stack trace tells the dev where and when the crash happened and any and all information the system currently holds during the process it was under taking.

Yes. I was supporting the idea that there could be an automated bug sending feature. I'm not sure what the guy's point about "it will be a rewrite so it's pointless" was. Presumably the original idea was to code the auto reporting feature into the upcoming C# version, so whether it's a new version is irrelevant and whether it can be done in VB is irrelevant.

Completely pointless as the new version is a total rewrite and any bugs in 7.2 shouldn't even exist in whatever is coming. We'll have entirely new bugs to find! Also I imagine Visual basic might suck for what you're proposing anyway.

The new bugs will need to be reported and the rewrite is in C#. Unless I've misinterpreted which post you're replying to, I don't really see your point here.

Suggestion, you know how occasionally in the current release it'll have an error that bubbles up and says "report this to the board at this address"? How about adding an auto-generate to send a bug report containing the full stack trace, etc.  Or a "open up Explorer to dump file" with a dump so that it can be uploaded to the boards. 

Steve said in this thread that there months and months work left. So, no there no release yet.