Point() function is too slow!? or what?

Psychophanta · Post by **Psychophanta** » Fri Oct 24, 2008 11:33 pm

SCREENWIDTH.l=GetSystemMetrics_(#SM_CXSCREEN):SCREENHEIGHT.l=GetSystemMetrics_(#SM_CYSCREEN)
InitSprite():InitKeyboard():OpenScreen(SCREENWIDTH,SCREENHEIGHT,32,""):ClearScreen(0)
StartDrawing(ScreenOutput())
LineXY(10,10,14,14,$eeeeee)
; Delay(10); <- uncomment this line and Point() in next line will catch the correct color
color.l=Point(14,14)
StopDrawing()
Delay(100)
CloseScreen()
Debug Hex(color)

See code and comments :roll:

pdwyer · Post by **pdwyer** » Sat Oct 25, 2008 4:51 am

Whats supposed to be different? I get "EEEEEE" no matter what

Baldrick · Post by **Baldrick** » Sat Oct 25, 2008 11:04 am

same as pdwyer, all seems good to me
tried changing Linexy() to

Code: Select all

LineXY(10,10,14,14,15658734)

Gets the same result

Psychophanta · Post by **Psychophanta** » Sat Oct 25, 2008 11:38 am

Without the Delay() I get 0 (black)

PB4.30b4 ATI 9600

Baldrick · Post by **Baldrick** » Sat Oct 25, 2008 12:29 pm

I tried with both PB4.2 & 4.3B4, both work no problem here

pdwyer · Post by **pdwyer** » Sat Oct 25, 2008 12:41 pm

what os? Perhaps it's a vista bug

srod · Post by **srod** » Sat Oct 25, 2008 1:35 pm

Works fine here on Vista 32 with or without the delay.

Psychophanta · Post by **Psychophanta** » Sat Oct 25, 2008 1:46 pm

Grrr. Incredible

I use XP pro SP3

Guimauve · Post by **Guimauve** » Sat Oct 25, 2008 2:14 pm

Psychophanta wrote:Grrr. Incredible
I use XP pro SP3

I use XP Pro SP3 and everything work fine.

Regards
Guimauve

Psychophanta · Post by **Psychophanta** » Sat Oct 25, 2008 2:22 pm

Here you can see directly.

Baldrick · Post by **Baldrick** » Sat Oct 25, 2008 2:24 pm

Just gave it a quick run for you on 3 different machines all using PB4.3b4.
My desktop, an old IBM Thinkpad both on XpSp3 & my old Toshiba Notebook with W98SE, all ran no problems, excepting I had to drop the W98 back to a 24 bit screen to make it run.

Edit: Don't have Vista to check for you....

einander · Post by **einander** » Sat Oct 25, 2008 2:29 pm

Result EEEEEE, without delay.
XP Pro SP 3 - DirectX 9.0c
DualCore Intel Pentium D 820, 2800 MHz
Gigabyte GA-965P-S3
Intel Broadwater P965
NVIDIA GeForce 7600 GT

djes · Post by **djes** » Sat Oct 25, 2008 3:05 pm

Love your blitz-like colours!

Seems this bug is platform/drivers dependant. You found the fix by yourself, could be useful sometimes.

I don't know how we can still code on Windows OS

Maybe sometimes someone will do a paper demonstrating that none of Windows games timing is accurate. Imagine that in real life, playing basketball sometimes with a square ball or +/- 5 mns. :roll:

Psychophanta · Post by **Psychophanta** » Sat Oct 25, 2008 3:13 pm

djes wrote:Love your blitz-like colours!
Seems this bug is platform/drivers dependant. You found the fix by yourself, could be useful sometimes.

I don't know how we can still code on Windows OS Maybe sometimes someone will do a paper demonstrating that none of Windows games timing is accurate. Imagine that in real life, playing basketball sometimes with a square ball or +/- 5 mns. :roll:

Hehe, yes, i can not live without those blitz-like colours scheme.

So, looks like it is a ATI driver issue! ... again i must change it ... aaagh!
And yes, you are right about the internal inaccuracy of windows timing in graphics matter. But i think it is not a windows matter but an IBM-PC architecture one. :roll:

pdwyer · Post by **pdwyer** » Sat Oct 25, 2008 3:38 pm

what did you use for the screen capture avi?