ENIGMA Development Environment

ENIGMA is a game engine, while SDL is a framework. ENIGMA could *use* SDL actually. And it has been tried before. The engine I am slowly working (kind of a rewrite of ENIGMA) actually uses SDL for the windowing, input and some more things.

You have a variable called "new" in the holdItem object. It is reserved name in C++ and parser doesn't handle reserved names in any way. So open your project and replace the local variable "new".

The collision error is weird. You can try changing the collision subsystem and see if that works.

Yeah, sorry I didn't change DX9.

You do have a 12 years old graphics card. That does limit on what you can do with it. I personally don't plan supporting anything nearly as old in the future, but that will probably be outside ENIGMA.

For 1080p the 960 should be totally fine. I have overclocked 970 and I can play every game on ultra without any problems. The new ones will greatly help with VR though, as requirements there are a lot higher (2 * 1080p with 90fps). But if you don't plan to VR (or at least on Utra) then you can hold off for now. I personally think the only VR worth considering is the steam's HTC Vive, but sadly it costs 1k. I will probably skip a generation.

I did try it and it worked. It had an error message at the top (can't remember what it said), but it worked.
Cool midi editor.

Did you make all the widgets yourself? Can you show an example code of a window or something? I'm making widget systems here and there (including BasicGUI extension in ENIGMA) and just wanted to see some other approaches. Textboxes with colored text, like scripting window is a though one. At least to make fast. I had the idea of a simple html parser, but I didn't want all the loops. The ability to rebind keys is something I haven't though about and window snapping. Like dragging a window near the edge of another window and allow them to automatically resize. You don't seem to have it either.

If you are interested in some bug reports / improvements:
1) The midi sound is a little weird. Like having an electrical filter over it.
2) Buttons in midi like "Traspose" have only "ok". So you cannot cancel out. It will probably use your windows instead of GM's later I guess.
3) In code editor emply lines don't have line numbers. I don't know if that is intentional. The numbers are not skipped though. Code editor also has two arrows at the bottom that do some weird mouse chasing, so I don't know what they are meant to do.
4) Some right click / left click functions for the resource tree would be nice. So I don't have to go to top to add new resource.

I see that framerate falls rapidly when few windows are opened. I will check how many draw calls it makes. I believe with texture pages which GM supports it should actually be able to manage the whole drawing in one.

I'm surprised that structs actually work, as I think EDL parser was very far from finished when it was stopped being worked on. I would use structs everywhere if I could.
But in short - EDL != C++. And the things that are written in the wiki about EDL are not entirely true. Those were the planned features. Most of them weren't finished.

I agree partly with Wendigo. But I think we need developers more than users. We won't be able to keep users if nobody is developing ENIGMA itself. Having an active community helps with getting dev's though. There was a total ENIGMA website rewrite some time ago (6 years ago to be precise: http://enigma-dev.org/forums/index.php?topic=610.15 and a broken version http://enigma-dev.org/v5test/# ), but I think as development slowed the need or even the want for more users diminished as well, because that would mean more people coming and saying how something is lacking or not working.

My comments about the requested stuff:
Faster compile time - There are three main things we can do to speed up compilation. For me compilation is extremely fast and takes less than 5-10s, but I have recently seen a PC which it took >30s per compile. So it can be slow for older PC's. What we can do is:
a) Switch from EDL to C++ so there isn't any parsing going. Not entirely sure how much speed this would give as the parsing isn't actually the slowest thing in my tests.
b) Split user code into several and make them individually compilable. Right now all the user code is in one header and it takes a lot longer to compile as it can have thousands of lines. Especially when warnings are enabled (by default) and so console takes like 60% of the time just printing stuff instead of actually compiling. So if the user code was separated into several .cpp files it would be possible to compile them individually. Maybe per object or something. So if the user changes only code in one object the rest won't recompile.
c) Combine several object files into one. Currently during linking it links about 100 files together. This can be slow, especially when link-time optimization is enabled. It is possible to link these together (ld -r) so only one large ENIGMA library needs to be linked whenever the user compiles.

Go with C++ instead of EDL -yes, that is the idea for my "Pure ENIGMA" project, but sadly I haven't had much luck with it yet. It sadly takes a lot of planning and time to make it usable without an IDE. I have a feeling I will need to brutally pull out the ENIGMA engine proper and rewrite some front-end code to make it stand-alone.

Fix LGM stability - Sadly I don't think this will happen. It is tied to the ENIGMA plugin and it seems to be the issue. It also depends on Java and apparently hardware (as it is rock solid on my laptop, but crashes in 30 seconds on my desktop).

edit: Robert, maybe lets merge the branch I have been working on in the past year and make a new installer for users? I think a lot of problems they have posted from engine part have actually been fixed. I will fix any newer bugs that they might find. From then on I will work on separating engine from IDE (Pure ENIGMA) and I don't plan to add new features to ENIGMA directly.