I worked a long time at a software company that made fax and data modem sharing software. It was privately owned. They used tech support people to test the software, thinking it would be a good way for support to learn the new version. On paper it sounds great, in reality its not. Tech support people tend to look for quick fixes to any issue they find instead of reporting it as a bug. The software gets released and support gets to simply telling the customer the work-around for the issue. Then you get the "feature creep". When a new version was being written by developers, management would come up with what they figured were just little tweaks, it would break the software since it was not planned for initially. Then they find out that it impacts over half the development team that now have to recode their module, and it would take twice as long as it should have due to it worming its way through the code.
Last time I looked into S3D it was privately owned, being managed by a family, the mother being the one holding the purse strings. Her son was supposed to be running it, but he was being micromanaged by his mother. If they are thinking of getting some venture capital people interested, they will be disappointed. VC people will do their due diligence, and know all the tricks. The company I was with at the time tried to get venture capital, the best offer they got was so bad that the existing owner would have to pay them to take it. It was finally bought out by a US based network giant.
You can tell how good the new version will be by its initial version number. Given the length of time it is taking to even get to a alpha release, I am expecting the initial release client will be v5.3.9. It will for sure not be v5. If it is called v5 then they are being dishonest about the version.
Until they announce a beta release with a number of existing customers being offered the beta version.
For the people that figure S3D is a lot easier to use than any of the competition should go back to when they first moved to S3D. It was not anywhere near as easy to use as it is now simply because you have 18+ months experience using it. I have tried the others as well, but, being in my 60s I need to be cognoscente of how much time I have left to learn a new software from scratch. Every different app has their own way of activating features, and quite a few have their own terminology.
I have been playing with other versions, and none of them stream M105 commands constantly with verbose logging enabled. There must be a way of stopping that or at the very least a way to port that stream to a text file so I can get the results of the PID AutoTune that was posted to the log, then got deleted at some hard coded log size limit because I was not sitting there watching the screen to catch the tuned settings.