Yup, it seems again, my code never builds on an ATI GPU!

I'll be able to debug this later more properly with a friend, so don't worry. It'll work, it's just that there are always some quirks I forget.

EDIT: Yeah, I did the same stupid mistake I did once of mixing up ints and floats. NVidia GPUs are more forgiving in that, and it's been nearly an year from using these that I forgot, sorry. Wait for take #2.

Try out these two shaders if you want. They're pretty horrible at the moment regarding optimizations obviously, but I didn't really expect to even put something like it online.

Does not work there.
Symptoms are the same as Edgar, 30 second black, and a grey background after.

And the good news is that it's running at my display refresh rates ;-)

"Technique lighting did not validate. Skipping."

Edit: BTW I have a Radeon 5470 and MediaPlayerClassic let me play with it's shaders without problems. I use the latests drivers, 10.12, on W7 64.

Did you try the shaders I attached in the last post? Those fixed the problem I had with seeing just a white texture in an integrated 6100GT. Of course, it works incredibly slow, because it's a very crappy card.

Of course, it could be that it's still not compiling on ATI, but I can debug that one more in detail later.

If I rendered much more awesome models(and textured) it would've been more obvious. I think the tiles are a pretty good example, those look great since they're textured.

Cool, that's my old card.

The shadow shader seems to be compiling correctly, it's the lighting the one with the problem.

Well, I wouldn't know how to debug it without a card for sure. All I can say is if you want, start commenting parts, except these lines:

struct PS_OUTPUT
{
    float4 color : COLOR0;
    float depth : DEPTH;
};

PS_OUTPUT ps_main(float2 normalMapTexCoord : TEXCOORD0)
{

    PS_OUTPUT Out;
    float4 color;

color = tex2D(texture, normalMapTexCoord);
Out.color = color;

return Out;

technique lighting {
  pass {
    FragmentProgram = compile glslf ps_main();
    VertexProgram = NULL;
  }
}

So yeah, you can comment pretty much everything inside ps_main(). If you see something visible, then you can try adding more and more lines until it screws up. That would help, if you're willing to do that.

EDIT: Oh, and don't comment the global variables that are above ps_main. Otherwise, the program will fail when setting them.

That's CG, not C++. Unless I misunderstood what you said.

I tested it just now, it's pretty impressive
I haven't seen much of this way of 2D rendering before. Do you have any plans of making a full engine or a game with this? Would be interesting :p

Performance seems fine, but one thing I noticed is that the application uses about 236MB of video memory. Will this increase a lot if you build this into a full game?

Works smooth with a GeForce 8800GT in Win7-64.

That's the card I have!

It's my new card.

Then again, I did buy it like 2 years ago. That's "new" to me, since I'm old now.

Speaking of the second object_light.cgfx :

First, I went back to using
FragmentProgram = compile latest ps_main();

Then if I comment out lines 79-234 (everything), then I get to see the assorted isometric diamond floors, the mansion, the guy in armor, and the column. I tried to take a screen shot, but it captures the desktop underneath for some reason.

If I comment out line 219
// Out.color = color;
and line 233
// Out.depth = 1.0-depth;
which effectively returns the color retrieved from the Tex2D call at the beginning, then I get a gray screen, which makes no sense, since it is returning the same PS_OUTPUT as it was when I commented everything out.

If I comment out lines 113-158 (the while (i<32) { block), then I get a gray screen again, so I don't think there's anything wrong with that chunk of code.

If I comment out lines 161-203 (the if (directional_strength > 0) { block, then I still get a gray screen.

If I comment out lines 113-203 (both of the previous blocks of code) then I get a gray screen with all the objects in black, which makes sense since final_light is initialized to 0.0.

What values of final_light would make every color turn grey(transparent?)?

I don't really know how I could isolate the problem anymore.

Something else that doesn't make sense is why it works for some people, but not for others. All ps_main is doing is returning a color, and that should be the same for everyone.

All four versions have the same result, a white screen with dark grey cutout rectangle on the bottom of the screen.

I changed all the
FragmentProgram = compile glslf ps_main();
to
FragmentProgram = compile latest ps_main();
and reran each test.

Results :

version _a -
Displayed all the objects.

version _b -
Same as _a.

version _c -
Looked somehow different than _a and _b, and the column was tinted pink.

version _d -
Only showed a gray screen.

So it looks like the problem is with casting shadows somehow.

Using version _d, if I comment out this line :
luminance2 -= 0.12*al*directional_strength;
Then it displays like version _c, with a pink glow on the column and rectangular prism.

Edit for your edit :
I tried the shader you attached in your last post, and it was back to the white screen with dark grey cutout rectangle again. I changed 'compile glslf' to 'compile latest' again, and then it was back to the gray screen.

If I comment out the same line I did with version _d, then it works like version _c again.

Using all the different combinations you posted, I still get a gray screen.

I just noticed on line 218 you have this :
if (luminance2 < 0.0) luminance = 0.0;

See how it sets luminance to 0.0 instead of luminance2?

Well I changed it to :
if (luminance2 < 0.0) luminance2 = 0.0;
and I still get a gray screen.

The only way it works is if I comment out
// luminance2 -= 0.12*al*directional_strength;
and leave
if (luminance2 < 0.0) luminance = 0.0;
as it was.