NetFix Client improvement ideas

[Vagabond]

I've been using NetFix a fair amount lately. Coupled with the NetHelper improvements made recently (Unfortunately, not in the posted game release, but in the SVN development build), I seem to have about 50% success with others.

I've posted a half dozen usuability improvement ideas. I tried to make each a contained bite-sized chunk as opposed to just barfing a large list in a single issue. These improvements should help with using NetFix and troubleshooting to a degree, but they won't fix any underlying network issues. (That would be beyond my abilities right now)

https://github.com/OutpostUniverse/NetFixClient/issues

If anyone is tracking the process, we have updated both NetFix and OP2Internal (was ForcedExports) to Visual Studio 2017, moved them from SVN to Git, and posted them on GitHub. NetFixServer is compiling fine. NetFixClient is not yet working.

NetFixClient itself is likely fine, but it depends on OP2Internal which in turn requires a custom build event to build an ASM file. Hooman has posted basic steps to complete but no one has stepped up to the plate and completed the work. I hope to find some time in the near future, but would be happy if someone else solves it first.

Until OP2Internal is fixed, not much point in working on these updates, but I wanted to get them recorded while they were fresh in my mind. Don't know if others have additional suggestions.

-Brett

[Vagabond]

Wanted to provide a quick update. We have NetFixClient compiling with VS2017 and working with Outpost 2.

A fair number of changes have been pushed. Most of them are updating to a more modern use of C++ with a couple of bug fixes included. I think this will continue for a while before we start legitimately trying to fix the network connection issues.

-Brett