I think candam meant to say 'number one priority now is version 2.0, it's recommended for all to use it!

I'd suggest that's the best course of action too unless you have already done a lot of development in 1.0 (even then it's still probably worth migrating your project to 2.0 if it's not going to cause you too much work).

For 1.0 licensed developer owners: I am considering making one final release of 1.0, do you want it now, or wait a few weeks for more features?

Hi Esenthel, before I give you a definitive answer, are you referring to 1.0 as in the engine itself or just the editor? Because the engine and editor are both two different things to my understanding. Will 1.0 Users still get Engine updates such as HWI, Batching... etc or not?

Hi, I mean the entire 1.0 SDK download package from Esenthel Store (win+mac+android+ios).
For example if I make the final release within few weeks, then the only features that you'll get will be the ones available at the time of the release.
That's why I'm asking when would you like to have the update

with all due respect, I don't think you should retire EE1.0 Without HWI being implemented. We cannot feasably upgrade to EE 2.0 on our project and we would really need the performance increase that HWI would bring to the table. If you can at least give your word that if and when you start on HWI it will be included in 1.0 I would be most grateful, So i would have to say i'd like you to wait and put more features in, as I said HWI is really something we need.

(10-28-2013 03:22 AM)Rubeus Wrote: It might be a good idea to at least implement the features your customers from 1.0 were relying on; to be fair, having those features on the roadmap was something of a promise to deliver.

I give my vote to group which is waiting for more rich version of Esenthel Engine 1.0.
But I have a question related with codes for editor in version 1.0. It is possible to give us more editor codes? Now you are creating new editor 2.0 with new features and new subeditors but for us will be very very helpful when we could modify old mesh editor, data browser or waypoint tab.
In our situation, we create more hacks for unify our editors with your editor and give our designers all tools in one big editor. This is very difficult when we try add new file type to data browser or mini data browser but this is only one example. Another situation, our game is big and game designers are creating hundreds of waypoints. We create small editor where they can add colors or category for waipoint but this is big hack because we cannot touch waypoint in editor, we only override functionality or we create the same functionality once again on our side... This approach significantly increases the production.
I can pay more for full codes of editor 1.0 but is it possible case in your marketing plans?

Unfortunately I cannot do this, because Editor 1.0 lib uses many internal engine functions that are normally not available in the public 1.0 SDK, so you'd need to have full engine source code.
My recommendation is to upgrade to 2.0 where I'm putting more functionalities for making the Editor open for modifications via the Editor Network Interface, many users are already making use of it, for example Tottel made links between objects that are visualized with lines.

Thanks for fast reply!
I understand reason. But in this moment we cannot move to new version of Esenthel Engine because our team count a lot of people and we don't have enough money for licences. Maybe in the future.