Posts: 6,419
Threads: 74
Joined: Mar 2002
Quote:Lillo, why don't the "exit" button work? I have to CTRL+ALT+DEL to exit wetspot. Tested it on 2 computers running win9x.
BTW, how can I get the screen params after screen?
Like
Screen 14
How do I get the screen dimensions: 320 * 240? Where in memory are they located?
BTW, great job!!!! I will test it's speec as compared to my TinyPTC sprite routines, And add some external routines in 32 bit like translucency, collision detection, etc.
Check docs, man  LOCKSCREEN, SCREENPTR, UNLOCKSCREEN...
Posts: 268
Threads: 9
Joined: Dec 2004
Wetspot 3? I already started it in C some years ago, but never managed to finish it due to lack of good gfx... http://www.ecplusplus.com/wetspot3
relsoft: the window close button is not working because the program code does not handle it... it's the same old code from 1996, I applied just the tiny little modifications to make it compile with FB, what'd you expect? :roll:
Making it to respect the close button would be as easy as adding a check for INKEY$+"X" in the main game loop though...
About getting screen mode info, some days ago I added a SCREENINFO new function, to get current mode width, height, depth, color mask, driver name and more infos. In CVS or in next release.
About speed, test the fullscreen modes. The windowed modes still use C color converters so they're not that fast... I've not yet written MMX versions as I wanted to be sure the C routines were ok first with 0.11.
Posts: 242
Threads: 29
Joined: Dec 2004
Quote:Making it to respect the close button would be as easy as adding a check for INKEY$+"X" in the main game loop though...
I don't think this is the entire problem. I also have to ctr-alt-del and kill the program in task manager. This is not from using the window close [X] button, but even just trying to ESC out of the program. I get the program ending text on the screen, but it will never shut down.
If I compile the program as -s console, then it will close, but it always has the console screen running in the background.
I think it has something to do with the screen switching in mid-program:
Code: IF AbortGame = TRUE THEN
Message "GAME ABORTED!"
SCREEN 0: WIDTH 80
PRINT "WetSpot v0.9"
The aborted message appears, but the screen switch and further processing never happens.
ature has its way of warning a person away from danger: The distinct black and white coloration on a skunk, the chilling buzz of a rattlesanke, a redneck handing you his beer and saying "Watch this!"
Posts: 268
Threads: 9
Joined: Dec 2004
This is weird, here I don't have zombie processes even if I compile and run Wetspot with -s gui... What version of Windows are you running? The gfxlib DirectX driver uses Win32 threads, and maybe threads initialization has changed between Windows versions, so I have to accomodate something there...
Posts: 3,279
Threads: 170
Joined: Nov 2003
Hey lillo, now how about a port of the frankly much better Wetspot II?  Wetspot II is definately the crown jewel of QB arcade games.
I'd knock on wood, but my desk is particle board.
Posts: 979
Threads: 27
Joined: Aug 2001
Wetspot 2 used EMS and the Blast! library, as well as some old sound blaster routines. It would have to be an actual port, not a recompiling on a freebasic.
Posts: 3,279
Threads: 170
Joined: Nov 2003
Hence why I said "port". 
I'd knock on wood, but my desk is particle board.
Posts: 268
Threads: 9
Joined: Dec 2004
I guess W2 will be ported not so soon... As stated, it'd be a real port, and it'd require some code overhaul; dunno when I'll find the time and will to do the job. Guess only FB 0.11 and FMod will be needed though.
Posts: 242
Threads: 29
Joined: Dec 2004
Quote:This is weird, here I don't have zombie processes even if I compile and run Wetspot with -s gui... What version of Windows are you running? The gfxlib DirectX driver uses Win32 threads, and maybe threads initialization has changed between Windows versions, so I have to accomodate something there...
I am running XP Pro SP2 with the latest driver updates on everything, running the 9.0c version of DirectX.
I wouldn't call it a "zombie" process as it doesn't actually close down. I have to go into task manager to end the program, but if I don't then it just continues to run visibly on the screen using whatever free CPU cycles are available. The program will minimize, etc., it just flat out refuses to close.
ature has its way of warning a person away from danger: The distinct black and white coloration on a skunk, the chilling buzz of a rattlesanke, a redneck handing you his beer and saying "Watch this!"
|
