Yeah, same thought. There is an exchange between devs to some extent inside a private part of the forum, but i’m rather sceptical that they discuss their software design in such detail on there.
The nature of complex APIs is that you can’t account for everything in your initial design, so they are bound to change in the beginning. At some point, at least the longer existing functionality needs to be set in stone.
It would appear that VEAO were bit by being early adopters of the API. The finger pointing towards ED is getting a bit old, though. Nowadays, most other devs seem to manage quite well, so as time drags on, the shift of blame does start to raise further questions.
I can’t know- but off the top of my head would be the fact that they are having these problems.
Maybe, just maybe, VEAO tried to take the shortcut through some physics issues and now are paying the price for it…
That’s a fact. But that doesn’t tell us if other developers are having similar problems or not.
For all we know, other dev. deal with their problems and solves them. Not saying this is the case, just that we don’t know because VEAO says so.
