Okay, I think I know what the problem is. I read more about the issue, and it appears that the primitives addon now requires Pixel Shader 3 support (translates to D3D 9.0c). Something tells me that no Intel card goes under that category...

What changed was the fact that FVF was removed, and replaced by D3D9 Vertex Declarations... FVF won't be put back, it just doesn't work for the purposes of using the same structure for OpenGL and D3D... I think I'll add a quick vertex preprocessor for low level videocards unless someone has a better idea.

No worries, D3D driver for the primitives is already such a hack that one more vertex twiddler won't hurt it. This also is a pretty big regression, so I think there should be a workabout.

Can anyone else with an Intel card confirm that it happens for him too?. It may happen only on really old cards, like mine.

Anyway, I guess I'll keep using 4.9.13 a bit longer.

What I do, and it helps separate out my stuff from the built in stuff for the compiler is put all the include and lib files for every thing I build into a specific folder, e.g. c:\mydevfiles\include, c:\mydevfiles\lib, and add these to the include and lib path.

That way everything finds them and I have them all in one place with no duplicates of earlier versions anywhere ready to cause havoc.

This is something I'm wondering about. Any way to cause the CMake generated MSVC files to not put the exe's in a sub folder. Took me a while to figure out that was the reason the demo wouldn't run.

It's trivial: but for the record, my laptop has integrated intel video (I bought it because it was the same price as a netbook on clearance), and XNA device caps says that I have pixel shader 3.0 and vertex shader 3.0 support. I don't have allegro/mingw on it at all though -- just straight up visual studio 2008.

Slightly less trivial: if anyone would like me to test anything on my laptop that might help the next version of allegro, I'd be more than happy to if you reply here or PM me.

I made a workabout for that recently, so older Intel cards should work with the addon again in 4.9.15 (and in the SVN now, which I'll appreciate someone testing in this matter).

Great! Now I just have to fix that spline bug...

>_<

Should be fixed in a few minutes.

The vertex twidller should turn on automatically on cards that don't support D3D 9.0c stuff that we need. The code that turns on the vertex twiddler is this (in prim_directx.c):

      if(!allegro_vertex_def) {
         if(IDirect3DDevice9_CreateVertexDeclaration(device, allegro_vertex_decl, &allegro_vertex_def) != D3D_OK) {
            use_vertex_twiddler = true;
         }
      }

But looks like it doesn't work... I'll have to do more research on how that works on Intel Cards...

Meanwhile, if you don't mind, could you tell me what IDirect3DDevice9_CreateVertexDeclaration returns for you?

Just replace the above code by this and run ex_prim in the terminal:

      if(!allegro_vertex_def) {
         int ret = IDirect3DDevice9_CreateVertexDeclaration(device, allegro_vertex_decl, &allegro_vertex_def)
         printf("%d\n", ret);
      }

EDIT: Also perhaps try this version:

      if(!allegro_vertex_def) {
         if(FAILED(IDirect3DDevice9_CreateVertexDeclaration(device, allegro_vertex_decl, &allegro_vertex_def))) {
            use_vertex_twiddler = true;
         }
      }

How about this?

      if(!allegro_vertex_def) {
         D3DCAPS9 caps;
         IDirect3DDevice9_GetDeviceCaps(device, &caps);
         if(caps.VertexShaderVersion < D3DVS_VERSION(3, 0))
            use_vertex_twiddler = true;
         else
            IDirect3DDevice9_CreateVertexDeclaration(device, allegro_vertex_decl, &allegro_vertex_def)
      }

Sorry to have you test this, I don't have any Intel GPU's at home

That works me, I'll commit that version of it. Thanks a lot!