-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|309|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
SoCoder -> Blogs Home -> Blogs


 
power mousey
Created : 05 January 2007
 

Unbelievably Amazing

about Cobra part 2

whoa!!!

on a post shroom made in the Cobra forum about how Cobra was originally bombing out in Windows Me, I decided to try the Cobra demo out on my old Compaq Presario.

My old Compaq Presario has Windows 98, an AMD K6 and running at around 500MHz, and also Trident integrated video memory.

SO I loaded up and ran...ran the orignal Cobra demo. The Cobra demo without the patch or upgrade. Guess what!!?
Unbelievable it ran. yes!, I swear and oh my gosh it ran.

I tried most of the examples. But mind you since its an older computer, the cpu is an AMD K6 and running at around 500 Mhz. Well, for example the bobsnake program was running and slithering at around 9 to 12 frames per second. The image and video quality was really good as well.

Of coursde with that dang balasted! debugger on and enabled, the performance and smoothess kinda hit the skids.
Again, I don't mind the watermark screen...its kinda cool too. And I can tolerate the nag screen too.
But hey Graham please get rid of the debugger being permanently enabled on the demo. I...and I'm sure others cannot get a good or accurate apprasial of using and coding in Cobra and with this demo.

I even tried my sprite program. A whole lot better that when it ran on my HP computer. I think the Trident video integrated memory and maybe the architecture of the Compaq could be better than the Sis60 video integrated memory on my HP computer.
I still have to balance and weigh smoothness and performance versus the quality of the sprite or the image moving. I really tweaked the valuse of my time limiting algorithm , the value contained in the Pause() comamnd and function, and also the width and height movement increments as well.
I'm sure I'll still have to get a 3d graphics card for my HP computer...or maybe just get a new desktop or laptop too.

cheers,
power mousey

 

Comments


Friday, 05 January 2007, 16:30
Jayenkai
Why do people keep going on about the debugger?
That's really not a bad way to stop people sticking with the demo, in my experience.

I mean, look at the Blitz Demo. You get 30 goes (is it days/runs?) out of it, and then you either buy it, or you give up.

Cobra's way, so far, there's no limit to the amount you can use the demo, but it limits the language so that if you want to really go for it, you have to buy the full version.

I think it's a great way of doing things.
Friday, 05 January 2007, 16:43
power mousey
no its a good way.

sorry Jay, disagree with you.

I'd rather have the 30 days than put up with a debugger that will limit the performance of both the example programs and programs that you create.

the watermark logo and the nag screen is enough! Believe me. sheesh.
and how can people get a accurate performance rate on their programs??

<shakes head in disbelief> ...whatever,

power mousey
Saturday, 06 January 2007, 03:27
JL235
I'd rather have the 30 day trial then Cobra's limitations. Purely because although the Blitz debugger has only put noticble speed constraints when I have had large amounts of variables (like an absolutely massive array), it's also about the feeling of being able to test the real program. Not a debugger constrained version.

But it doesn't really suprise me that it worked on an old PC.
Saturday, 06 January 2007, 10:01
garand
I have not tried it but I would also like it to be that you can see what the performance is on the language. I would not buy a language if I can not see the capabilities of the language.
Saturday, 06 January 2007, 11:03
HoboBen
Apparently Oscar is going to release some exes of programs compiled without the debugger... maybe this'll give an idea of the speed.