ENIGMA Development Environment

I normally hate to bump topics but this is really important. I have now found an optimization for OpenGL1 static models that we were originally utilizing. Originally with fixed-function immediate mode and call lists there was drastic memory usage and crashing for some of us, I then sped models up by implementing vertex arrays, and now by compiling those with a gl call list I can buffer all of that to the GPU and remain compliant with GL1.1 which everyone's hardware supports including polygonz.

The framerate went from 13fps to 201 fps. The ram usage went from 100-113MB's down to 49MB's and then to 44MB's with the addition of clearing the data only for static models once they are buffered.
Note: Do not compare this to the earlier results of other systems, it was tested on a better graphics card, this system now outperforms GL3 and D3D9 on my computer.


Project Mario has also gone from 237/239fps for me to 261fps. These performances boosts should be for most games, but especially for those with very large models that have plenty of polygons.

This is the pull request where I am working on the improvements.
https://github.com/enigma-dev/enigma-dev/pull/788

Evidence of Display List and GL1.0 compliance.
http://wiki.processing.org/w/Display_List

Robert, I didn't code D3D9, so I don't really know how to fix it there. The code is slightly different there.

Harri, I am displeased to hear this, that is a very very poor excuse. The code is not that hard to follow, all of the Direct3D docs are online just like GL, and the functions themselves by virtue of verbosity are self-explanatory. You know much more about matrices than I do, I've never even taken a matrix math course yet, in my life, and I managed to write the transformation code for D3D. Please make an earnest attempt to do so, I believe in you.

What would help in this situation is for someone to post the contents of output_log.txt and we would know the exception that occurred.

Alright that all sounds good to me, so I should just not worry about the additional thread functions right now?

Yes it would be easier to utilize the CLI, because you literally just pass the file path to it and it will build it. However there does need to be a way to shut it down, a stop button for instance, and do other things.

The state of RadialGM is just the GUI, there is no functionality, that is what needs done, it needs resources added, file handling and hooking up the editors to the resources. Now the reason this has been so slow is we've constantly been debating how to make it extremely modular and abstract. I may disregard all of this and begin programming it to be at least functional and then we can focus on improving small aspects of it as we go, like we've done with the rest of our projects.

Yes definitely, check the manual.
http://enigma-dev.org/docs/Wiki/D3d_set_projection_ortho

Hey Breakdown, allow me to reiterate that you make really nice posts, people should take this as an example of how a post should be formatted. Not many people take the time to write coherently and place links and images nicely in a post.

Since you can't think of a name let me just throw one at you, SpaceCraft. Not sure how you feel about that but anyway, you got an ETA on the alpha version? I'd love to test it out for you!