123
-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|423|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Blitz    


Page : 1 2 Next
Prev
Fri, 27 Apr 2007, 06:52
Jayenkai
Blitz3DMan has suggested that it might be the image drawing that's the problem.
I don't think it is, but best to be safe, right guys?

This bit of code will create 100 random images, then draw them over and over again onto the screen, starting with 200, and ending up with lots and lots and lots!
At the point that the framerate drops below 50* the program will make a note of the number of images onscreen, and start again.
It will do this 5 times, and then start again with bigger images.

Should take about 2 or 3 mins to complete the whole thing. (although I didn't time it! It just felt a long time!)



My results



*Note, I chose a 50fps limit, incase some people's systems can't go above 60.. If a system can't go above 60, then the frame rate ticker-checker thing would be completely messed up!

-=-=-
''Load, Next List!''
Fri, 27 Apr 2007, 09:15
JL235


If I remember, I'll run it again after a clean boot and on a different laptop.

I don't think drawing multiple images through should really be a problem. Blitz should be able to cope. When it was playin sound though it was sometimes completely out of time with the image drawing. Strange.

This has got me thinking on how useful a Blitz profiler would be. Their is one that comes with Ruby and it's so useful.
Fri, 27 Apr 2007, 09:40
steve_ancell
Here's mine, is this good or bad ?.


Fri, 27 Apr 2007, 09:52
Jayenkai
Diablo, your results are incredibly chaotic!
Maybe running it twice might get a better result?

64x64 pixel sprite abilities are more or less what I'm watching for, and we've not hit anything less than 500.. So. Not anything worrying, so far.

Steve, both yours + Diablos appear to be better at doing larger sprites than mine is. Aww


(But then, who would dare to fit that many 256x256 pixel sprites onscreen at once, anyway?)

-=-=-
''Load, Next List!''
Fri, 27 Apr 2007, 09:55
Mog
Test ran with Computer #1



-=-=-
I am Busy Mongoose - My Website

Dev PC: AMD 8150-FX, 16gb Ram, GeForce GTX 680 2gb

Current Project: Pyroxene
Fri, 27 Apr 2007, 10:35
shroom_monk
Grrr... the silly thing's been running for more than 10 minutes, and it's only on test 16 out of 30!!! Shall I just give up now? This is taking forever!

-=-=-
A mushroom a day keeps the doctor away...

Keep It Simple, Shroom!
Fri, 27 Apr 2007, 10:39
shroom_monk
Hmmm... Having looked at the code, I'm convinced that this will never, ever finish, so I'm gonna start again!

-=-=-
A mushroom a day keeps the doctor away...

Keep It Simple, Shroom!
Fri, 27 Apr 2007, 10:46
shroom_monk
I discovered that if I changed the line

to

then it went faster. But judging by my results, I think they're messed up and wrong...



On test 16, before I altered that line, the framerate was 0, most was 0, and the images had got to over 2000 and it wasn't going anywhere. So I gave up.

-=-=-
A mushroom a day keeps the doctor away...

Keep It Simple, Shroom!
Fri, 27 Apr 2007, 10:55
flying_cucco
Old-skool Tablet PC:


Fri, 27 Apr 2007, 11:02
Jayenkai
Well, looks like both TabletPC, and "A PC that by now probably has it's own Mushrooms" won't be running Hero any time soon!

Shroom, try changing the "Images=200" to Images=0 and then see how far you get.

-=-=-
''Load, Next List!''
Fri, 27 Apr 2007, 11:28
shroom_monk
Just because my computer has mushrooms growing inside it, doesn't neccesarily make it slow!!!

Anyway, with Images=0, it was really quite fast!



-=-=-
A mushroom a day keeps the doctor away...

Keep It Simple, Shroom!
Fri, 27 Apr 2007, 14:05
Blitz3Dman


-=-=-
There are 10 kinds of people in this world -

( Insert 16 remarks about to what extent people know hex here )
Fri, 27 Apr 2007, 14:47
Jayenkai
TEN!?!

FFS, Shroom, TEN!?

Your system can draw no more than ten images onscreen per frame?
Is that right?

That can't be right? Someone tell me that's not right!!

-=-=-
''Load, Next List!''
Fri, 27 Apr 2007, 15:05
flying_cucco
Update: I changed images=200 to images=0 as suggested. A truer result is below


Obviously, pretty pants. But with fullscreen on things are a bit better

Fri, 27 Apr 2007, 15:09
Jayenkai
Wowwie!!

Good think I added a fullscreen option the other day!

I always wondered why some people only ever did things in Fullscreen! I always found the constant res-change/screen flicker annoying, but if you're getting REALLY bad Windowed games, that's as good a reason as any!

-=-=-
''Load, Next List!''
Fri, 27 Apr 2007, 15:19
Blitz3Dman
Here is my results having changed image=200 to image=0




Is this what I was supposed to have happen?

-=-=-
There are 10 kinds of people in this world -

( Insert 16 remarks about to what extent people know hex here )
Fri, 27 Apr 2007, 15:34
JL235
After a fresh reboot:



After then changing the code a little, I got what looks like a far more consistent result. First the code:



Then the results:



I've added a variable 'SecondChance' which starts at 5 and counts down to 0 when it fails. The idea is that what is causing the chaotic results before, is being caught out by the odd frame. By counting down instead it usually makes it count down 2 early on, then further into 0 when it really is being pushed.

I presume Blitz also uses threads behind the scene, as I get some strange performances. Just the window was updating behind the reast the rest of the program. Playing the 'all complete' sound and opening notepad whilst still performing the last test for around 30 seconds after the program should have closed. Almost all the 'test complete' sounds were played behind when it should be, often by almost a whole test (maybe a second call to play the sound is prompting the first to finally run).

I'd recommend removing the sounds.

|edit| I also correctly indented your code. |edit|
Fri, 27 Apr 2007, 15:44
Jayenkai
Playing the 'all complete' sound and opening notepad whilst still performing the last test for around 30 seconds after the program should have closed.


It does WHAT?!

I don't mind freakish results, but is it REALLY doing that?
I mean, if it is, then.. That's just wrong.
That's a language NOT doing what the code is saying.
The "ExecFile" doesn't get called until all loops are done. If that isn't happening, then any and all of our games could potentially do anything, at any time!

-=-=-
''Load, Next List!''
Fri, 27 Apr 2007, 16:05
JL235
That's what I thought. But maybe it's a Windows problem rather then a Blitz one.
Fri, 27 Apr 2007, 16:37
MikeT
I got the following...


athlon xp2500, 1gb ram, geforce 6600gt

hope this helps

MikeT

-=-=-
One life - live it
Sat, 28 Apr 2007, 00:15
shroom_monk
Yes Jay, your program is right!

My Computer Sucks!!!!!!!


|edit| And the results from fullscreen mode:

Oh, and test 30 was still running. |edit|


-=-=-
A mushroom a day keeps the doctor away...

Keep It Simple, Shroom!
Sat, 28 Apr 2007, 01:34
flying_cucco
Ow thats bad. What graphics card do you have? If its intergrated, what chip is it?
Have a look quickly by bringing up the 'run' box and typing 'dxdiag'.

My Rage is 10 years old! If you have a P3 era box you should have better than that - maybe this is a driver/directx problem.
Sat, 28 Apr 2007, 01:41
shroom_monk
dxdiag Name: Intel® 82810 Graphics Controller
Manufacturer: Intel Corporation
Chip Type: n/a
DAC Type: n/a
Approx. Total Memory: 5.5MB
Current Display Mode: 800 x 600 (24 bit) (default refresh rate)
Monitor: hp pavilion mx70


|edit| ^That's from the 'Display' tab.^ |edit|

-=-=-
A mushroom a day keeps the doctor away...

Keep It Simple, Shroom!
Sat, 28 Apr 2007, 04:56
Prospero


Not sure what happened on image size 32 test 2 - think that it threw a wobbly when I moved the mouse over some taskbar items

My PC:
Windows XP Pro SP2
DirectX 9.0c

Athlon 64 X2 5200+
2Gb RAM
2x XFX Geforce 7900GS SLI

(SLI doesn't make much difference. I got similar results with and without it activated )

-=-=-
https://www.zolyx.co.uk/
Sat, 28 Apr 2007, 13:12
Nolan


AMD Athlon X2 3800+
1Gb RAM
Geforce 6100


-=-=-
nolandc.com
Sat, 28 Apr 2007, 15:30
flying_cucco
My desktop PC:


AMD Sempr0n 3000+ (Socket A), 2.1GHz
1 GB RAM, DDR 333MHz
Nvidia GeForce 6600GT (AGP), 128MB
Windows 2000

I too have noticed some really wierd things. the sounds played several seconds EARLY, then the test carried on drawing. It becomes noticeable in the last 10 tests. I thought I was imagining it, until the last one - "tada!" - fully two seconds before it finished adding and drawing images on the screen.

|edit| And I don't know why the results pwn MikeT's, as we have roughly similar hardware. |edit|
Page : 1 2 Next
Prev