Antialias - strange behavior

[LP]

I had no possibility to check the demo you posted (still downloading it at 100 Kb/sec)... The antialiasing seems to be a bug (and I already thought on solution)... I'll release the fix today in several hours...
EDIT 1: noticed that antialiasing "works" (On or Off?) 1 of 5 times when the application starts... THIS problem doesn't seem to be related to Asphyre - antialiasing is set every time you "InitDevice".
EDIT 2: I've checked your demo, noticed some faults with sprites (I think you SHOULD check the RealSize property for this), besides the application switched full-screen and windowed mode several times here - the screen blinked for a while... I'm not sure what you do but it appears that you either initialize the screen several times or switch "Windowed" property in run-time, when PowerDraw is initialized, several times or so... Application took some time to run here but since I could not understand the language well, when I selected first menu - it exited

[Huehnerschaender]

Nightmare,

could you please download this little sample and test if it runs showing the framerate on your PC?

http://www.asigermany.de/works.zip

That would be very kind.

[Nightmare_82]

It seems that you are more satisfied with the second screenshot you posted, but in this antialiasing is OFF.
The first screenshot shows antialiasing ON and here I guess the lines appear, because of the reason why lifepower has implemented the REALSIZE property of textures.

You're right. Sorry, I thought the screenshot with the lines would be without Antialias.. I only looked at the lines. What does the REALSIZE property ?

I'll test your example now.

@Lifepower: thanks for your hints. I'll take a look at my code. You have to choose the secound point to start the game.

[Huehnerschaender]

A texture has a size, lets say 256*256.

Realsize means, that if you set it to 254*254 the engine will show/render the image without the left, right, top and bottom line of the picture.
This sounds weird, but when using antialiase the "blurring" of the image reads pixels next to the pixel it is rendering in all directions and calculates middle values. The pixels on the borders have no "neighbours" and so black is assumed as pixel on the concerning side. Thats why you get the black border.

This is only my understanding of Realsize. I guess Lifepower can tell you if I am right or not :lol:

EDIT: Another hint. I examined your vtdb and as I can see you use texture sizes up to 1024*1024.
These are not supported by older graphic cards. So if you want your game as compatible as possible you have to tile your textures in pieces of 256*256 at maximum. I posted a topic here related to this and other users told me that because as I used bigger textures and textures of non power of 2 (eg 800*600) they were not shown on different graphic cards.

[Nightmare_82]

OK, I'll try that.
I tested your program. It runs well. the color value is : 4026531840 and the caption says "NO ERROR".
I have a gefore4MX and win2k.

[Huehnerschaender]

Aha, thank you... And the framerate is shown too?
You have NVidia Card installed... which version of driver do you use? Latest Detonator (61.77)?

[Nightmare_82]

yes 61.77.
But the framerate is always 0.

[Huehnerschaender]

When framerate is 0 then you have the same problem. The program hang up!!!! You can see it when moving the windows out of screen and bring it back it is not repainted.
Thanks for testing this.

[LP]

The problem with mentioned example is probably related to Nvidia Hardware. On ATI this example works perfectly. But on Nvidia cards, "Present" method in Direct3D returns "D3DERR_DRIVERINTERNALERROR". Manual explains:
"If D3DERR_DRIVERINTERNALERROR happens during 3-D rendering, the runtime returns it at the IDirect3DDevice9:resent call. The application can do one of the following:
End, with the pop-up window saying that the application cannot continue because of problems in the display adapter and that the user should contact the adapter manufacturer.
Attempt to restart by calling IDirect3DDevice9::Reset, which is essentially the same path as recovering from a lost device. If IDirect3DDevice9::Reset fails with D3DERR_DRIVERINTERNALERROR, the application should end immediately with the message that the user should contact the adapter manufacturer." Oh well...

[Huehnerschaender]

I have ATI card in my laptop and this one creates bluescreen and reboots.
So it works not on all ATI-cards!

Hanging up is one thing, bluescreen should never happen.

EDIT: I have a PC with Win2000 and NVidia Card (GeForce 2 MX 400) and this is the only PC I can get it work. The driver is the same as on the other PCs. (61.77 This one is for XP AND 2000)