ENIGMA Development Environment

It should work. Don't ask me why, i didn't make the parser ! 

The code in "Definitions" is not parsed. It needs to be valid C++. In valid C++ you need to have that semicolon at the end (it doesn't matter if it's on one line or several). So it's a typo in the wiki and someone should fix it.

It looks fine on my machine (GeForce GTX 760, Linux, Open GL3). Unfortunately, I do not have a Radeon machine to test this on.

That is good news.

Your lighting demo is just a black screen for me. I tried pressing del/insert, moving mouse, and using WASD (in case camera was off) but it's always pure black..

That is bad news.
1) Try commenting out glsl_program_default_set() and glsl_program_reset() lines (first 6 lines in draw even of the single object). Then run in GL1.1. And then run in GL3 and see if you get the same lights.
2) Try downloading the egm again. I changed it so you start in the middle of the lights (previously starting position was the player turned away, thus you see only black screen initially when not using mouselook).
3) Try looking at console output of the program, it will output information about shaders at startup.

The logo shown at the beginning of the game looks hideously ugly, but everything else looks fine.

What is ugly exactly? Does it look the same as in GL1.1? That is what we are trying to replicate and so GL3 won't look any better by itself. Although I do plan to make a topic about this - maybe it's time to ditch GM and it's rendering and go for something better? It will break compatibility slightly (especially 3D games), but would open a lot of doors for improvements.

So I implemented lights in GL3 some time ago, but I didn't do it in Master branch because AMD fails. It worked fine and dandy on Nvidia, but on AMD it didn't render models with lights for some reason. After days of testing I still didn't figure out what the problem is, but I did found a workaround. I send color data to GPU even if they are not used. This reduces FPS slightly (goes from 1170 to 1150 on Nvidia), but now it at least works on AMD. Additional investigation should be done into that matter, but at least we can have lights now.
So this is how it looks like on AMD with GL1 and GL3:


You can see that they are not pixel identical, but very close and this is about the difference you might even expect from different card vendors when using FFP (GL1). But at least AMD draws everything now.

The default shader (per-vertex lighting which emulates FFP) is quite bad and basic. That is the idea for now, as we wanted both systems to be compatible. But if you want to make something that actually looks good, then you might have to use your own shaders. This is of course possible, but until now you couldn't override what is actually the "default shader". So your code looked like this:
glsl_program_set(shr_my_cool_effect_shader);
//Draw the cool effect
glsl_program_set(shr_my_default_shader);
//Draw normally with a custom default shader instead of this:
//Create
glsl_program_default_set(shr_my_default_shader);

//Draw
glsl_program_set(shr_my_cool_effect_shader);
//Draw the cool effect
glsl_program_reset();
//Draw normally with a custom default shaderIt is not a big change, but the reason I point this out is because we now could theoretically allow extensions which override this shader automatically. Like imagine a "Per-pixel lighting" extension, you Enable it and it automatically sets the shader. The extension doesn't even need to have functions. Sadly though, extensions still can't modify or inject code into events. So right now it's not possible to do it without a function, but it might be in the future. Like I made an example:

Here I switch between shaders with keyboard:
if (keyboard_check_pressed(vk_insert)){
glsl_program_default_set(shr_per_pixel);
glsl_program_reset();
}else if (keyboard_check_pressed(vk_delete)){
glsl_program_default_reset();
glsl_program_reset();
}The glsl_program_reset(); is required because the _default_ functions don't actually bind the program. They just set what the default one is.

I can't be sure about AMD as it was broken before, but my Nvidia implementation works a lot faster than before. The current master is actually very broken, I have about 250fps on it. After fixing lights I got it up to 1090FPS (which is what it was before and is with GL1), but I also did additional caching and now get about 1180FPS, so there is an improvement. Others should probably see it too.

Please test these changes, by downloading from this branch - https://github.com/enigma-dev/enigma-dev/commits/GL3-cleanup
Especially AMD users should test. Try with Project Mario as well as other examples and games. You can also test this: https://www.dropbox.com/s/r17cwch4962voi8/3D_Lights_test.egm - It's the lights demo where you can see the default FFP emulation and the sample per-pixel lighting. You can switch between them using Delete and Insert, look around with mouse and move with WASD.
It would also be useful to know FPS in examples like Project Mario before (the Master branch) and after (this one).
If everything is okay and nothing else breaks, then the branch could be merged.

When you say compressed does it compress everything ? Meaning if I use uncompressed resources in my games will saving to EGM cause recompression each time ? that sucks major balls.  Or is it just using non lossy compression or what ?   I know that EGM files can be opened with 7z, WInrar, etc.
I know it does compress images but it is my understanding it uses PNG.  So does this mean each time I save it recompresses a generation on image, sound ,etc ?

It compresses the files, not the format. So no, it's not lossy and doesn't degrade your images or sounds. It's a regular .zip.

I remember the cool ones which allowed you to customize it, like put blocks of rubber with letters and symbols on the bottom. Then there are the ones which allow you to select dates and numbers on the top, but they are less customizable. Haven't really seen a stamp in a few years though.

I shouldn't have to change the display resolution to make the game scale right.

You don't have to change the resolution. You have to set the port correctly.

Yeah, I am fixing GL3 right now. I fixed lights in this branch (https://github.com/enigma-dev/enigma-dev/commits/GL3-cleanup), but AMD keeps crashing on it. So I need to fix that.