I think the real and fair solution here is simple and easy:
1. Base price that stays roughtly the same at least unless new features balloon and add to all platforms (currently it seems somewhat a tick tock, half the platforms are ignored for the other half of the platforms and alike)
2. Stop the upgrade price policy and sell support contracts which can be paused at max 1 year. That way people know that they pay for 12 months, not 'perhaps 12, but could just as well be 8 or 16 months'
That way we all know what we are up to and leadwerks can push things more continously instead of starting to freeze releasing stuff to the licensees just cause its required as selling point at 'last release + 10m' (compare it to Adobes development cycles during standalone CS versions version cloud now)
To me this is what its hurting most, that there is a very high likelyhood that stuff gets pushed back or scheduled in stupid / counter intuitive / developer hurting way when it does not need to be like that and should not be like it.
I got 3.0 with mobile addons, cost me a good $500 and I can't say that I'm satisfyed with how the mobile engine works etc even remotely right now. ITs the least capable, performant and productive engine I've at hand to use (compared to Shiva, UDK, Unity) and a year later its already 'dead' again as its now all about eye candy and linux due to the 'year cycle selling point focus'?? I kinda doubt that there will be going any more cash from my end to leadwerks until the development phylosophy itself gets fixed to a more 'the engine as a complete, real crossplatform product' approach without exclusive yearly focus