I was using esenthel 1.0 since last few month and I become such a huge fan of this engine that I went ahead and got my self a license. I thought creating new object types and managing resources will be easier in the esenthel 2.0

Now when I am using esenthel 2.0 at every step I feel esenthel 1.0 was lot better.

Anyway as the product development is going towards esenthel 2.0 I am not going to whine much about it.

Here are few things that I am struggling with, they are all related to the esenthel 2.0

1. The file names are all encrypted (why they are not in just plain English)? I can't browse through the folder it feels weird.

2. 2.0 lacks the cloth and destructible object editing, somewhere on the forum it is mentioned, "all of it is possible through code" May I ask how.

3. Where can I see the cpp files, I wanted to create destructible objects and I don't know what parameters it take.

4. Interface of esenthel 2.0 is so different it feels like a new product all together, again i will have to go through the learning curve, the usual F1 also does not work.

5. What is the project structure for 2.0 , I exported my 1.0 project it is only showing me the data folder no code?

You should have the construction method documented for all the basic object type supported in the engine. If the user has to struggle for a something as simple as instantiation of the object it means a huge road block.

could you please make esenthel 1.0 sdk available? If Esenthel 2.0 is work in progress it will make sense to give people a chance to use a complete product.

The engine is good and it really has potential but you have to take care of this entry barrier otherwise there will be problem for user adoption.

Hi and welcome on the forums!

First of all: EE 2.0 (although usable and stable) is still a work in progress and is still missing some features compared to 1.0 that will be added in the near future. You can check what, here: http://www.esenthel.com/community/showth...p?tid=1507

1. I don't think it's a bad thing. You just end up with 2 folders: 1 for all your source assets (.fbx, .tga, .psd, .max, .blend, ...) When you import them (drag/drop), they get put in the project folder as an encrypted file. Which is fine because you don't need to touch them in Explorer again.

2. I haven't used any cloth or destructables so far. It's not in the 2.0 editor, but you can check the EE RPG 2 example for cloth on the main character (wizard). Both of those features are on the way, as you can see on the roadmap.

3. There are no .cpp or .h files in EE 2.0. They're merged into 1 "code" file (which I find really convenient, btw). The best way to find info, is to just open any code file, and press "ctrl + F", then just type in something like "destruct" and you'll find everything you need. Just put it on "text in files" and enable search in "Engine" as well.

4. True. It took me a while to get used to the interface, and to be honest, I still prefer the one from 1.0 (sorry EE :( ). Now it just feels like a hovering GUI. But I think the asset management is pretty neat.
The F1 key does not work (it guides you to these forums) because previously, it would show the help file which is currently only for EE 1.0

5. I'm not sure what you mean.


As for the instantiation, you can just get that info from the Engine files (the green folder (library) named Esenthel Engine) + the tutorials project.
But I agree, 2.0 needs a bit more features. Personally, I'm fanatically looking forward to a shader editor.

Note: These all suggestions I am making to help improve this nice software. These are all constructive feedback.

Thanks for the Answers, I really appreciate it.

1. I didn't know it is some kind of encryption method. I thought it might be a encoding problem. In that case I am strongly against it. It means you are now restricting us in editing the files and sharing it. Most of the time I use notepad++ for coding (I am doing that from many years now) or VS. Now I can't do that. Esenthel editor UI is not that fluid and you will never be able to provide us the functionality that VS or other popular editing software can provide.

I will suggest to not encrypt the program files.

2. & 3. So i can't see the cpp file. How exactly i will get the information about object creation then?

Quote:you can just get that info from the Engine files (the green folder (library) named Esenthel Engine)

The header file just tell me to use the objparams and it is not written anywhere what parameters are required for destructible objects. Its hidden!

4. Interface is really not good. The developers of this engine should take some help from the community. I am sure there will be many helping hands here who will work to improve the look of this software. The accessibility is really a problem. If you want to provide a cross platform solution please make separate builds for each platform if you are trying to put everything in the same software you might screw the interface.

5. This is really not the best practice. Either you provide us a world class code editor or let us use what is already there.

So after hearing you it feels like Esenthel 1.0 was a better software in all regards.

(08-06-2013 07:07 PM)ronghester Wrote:  Most of the time I use notepad++ for coding (I am doing that from many years now) or VS. Now I can't do that.

Yes, you can.. The code editor in 2.0 is not your only option. You can still use VS like in EE 1.0

(08-06-2013 07:07 PM)ronghester Wrote:  2. & 3. So i can't see the cpp file. How exactly i will get the information about object creation then?

Quote:you can just get that info from the Engine files (the green folder (library) named Esenthel Engine)

The header file just tell me to use the objparams and it is not written anywhere what parameters are required for destructible objects. Its hidden!

That's perfectly normal.. No commercial engine is going to allow you to have its .cpp files.

(08-06-2013 07:07 PM)ronghester Wrote:  So after hearing you it feels like Esenthel 1.0 was a better software in all regards.

I liked the UI in EE 1.0 more. I think the asset management in EE 2.0 is a LOT easier and more convenient.

1. Every thing I do requires access to names of files (e.g., sound, images). These are referenced in a user editable text file and are loaded and displayed under specific timing conditions and can number in the hundreds.

I actually stopped playing with Esenthel after realizing that there was some impasse with respect to dealing with plain files. Perhaps I misunderstand and there is another solution that I haven't considered.

Alexsee, I believe that is still possible with EE 2, just not the standard way of things.

ronghester, it may help to know that there is an "Import 1.0 project" option on the opening screen of EE 2. That should help get you up and running.