I was referring to the sound bugs that I mentioned previously. They reared their heads in either 80 or 81 irrc and were fixed. Now they're back. A large part of me is quite concerned that you guys will take them as an acceptable loss and go forward with a release.
I find that now I am even more reliant upon engine behavior. If a large bug presents itself in the engine and you guys don't quash it right away, I'm in trouble.
Here is the reason I care:
Currently, there are some engine bugs in 81.7.1, but they don't really effect me or my users. The only thing that I am in dire need of is isolation mode so that existing spring users aren't effectively punished by the ridiculously long write time of archivecachev7 in that instance. Moreover, my regular users never have issues if they have the proper hardware (in other words, not trying to run it on a 486). The issues that I do get notified about on a constant basis are ones caused because of multiple spring installs. If I had isolation mode right now, it would no longer matter, because isolation mode would ensure that no other spring related files would interfere with an evo installation.
The only reason I am so concerned is because of the autohosts. Evo is engine version agnostic, so even if you guys made a release it wouldn't matter,
but the autohosts are not version agnostic, and considering that I have more or less entirely thrown in my lot with the autohosts, I sit here thinking "Oh shit I'm fucked".
Imo, support for multiple engine versions should be a priority, but I have been basically shouted down on that.
Hopefully this makes it crystal clear where my thinking lies and explains anything that I didn't explicitly address.