The BLUE SCREEN of FRUSTRATION! - GameCreators Forum

Author

Message

Snafu

20

Years of Service

User Offline

Joined: 25th Jun 2003

Location:

Posted: 16th Nov 2003 21:19

Link

CLS
SYNC ON
SYNC RATE 0
HIDE MOUSE
P=1
TRUE = 1
FALSE = 0

tilesize = 16
playersize = 16
screenwidth = 640
screenheight = 480
xtiles = screenwidth/tilesize
ytiles = screenheight/tilesize
` Here we're calculating how many tiles we need to fill the screen.

DIM map(xtiles,ytiles)
` This creates a tilemap, so we can store the kind of tile at every
` location. (it's a bit bigger than it strictly needs to be, but that's
` because I do a check later on which involves adding one to the elements)

blue = RGB(0,0,200)
brown = RGB(100,50,0)
white = RGB(200,200,200)

REM image values
background = 1
platform = 2
` You'd normally have a lot more of these. One value for each kind
` of tile.
player = 1001

REM Getting our images for the tiles
INK blue,0
BOX 0,0,tilesize,tilesize
GET IMAGE background,0,0,tilesize,tilesize
INK brown,0
BOX 0,0,tilesize,tilesize
GET IMAGE platform,0,0,tilesize,tilesize
` Normally, you'd have a tileset to get all your images from.
INK white,0
BOX 0,0,playersize,playersize
GET IMAGE player,0,0,playersize,playersize
` Normally, you would have a sprite animation sheet to get the player from.

REM Read the map into memory
FOR y = 0 TO ytiles
   FOR x = 0 TO xtiles
      READ map(x,y)
   NEXT x
NEXT y
` skip down to the DATA statement for explanation.

xpos# = 50.0
ypos# = 200.0
` we have to store the character's position as reals (instead of integers)
` because we'll be using gravity.
xspeed# = 0.0
yspeed# = 0.0
gravity# = 0.2
acc# = 0.2
friction# = 0.95
jump# = (-5.0)
player_on_ground = FALSE

DO

REM Find out what tile the player is occupying.
   xtilepos# = xpos#/tilesize
   ytilepos# = ypos#/tilesize

REM Find out what tiles are *beneath* the player.
   undertile1 = map(INT(xtilepos#),INT(ytilepos#)+1)
   undertile2 = map(INT(xtilepos#)+1,INT(ytilepos#)+1)

REM Should the player fall?
   IF undertile1 = background AND undertile2 = background
      yspeed# = yspeed# + gravity#
      player_on_ground = FALSE
   ELSE
      yspeed# = 0.0
      ypos# = INT(ytilepos#)*16
      ` (This pops the player up if he is inside of a platform tile)
      player_on_ground = TRUE
   ENDIF

REM Check keyboard for jump
   IF SPACEKEY() AND player_on_ground THEN yspeed# = yspeed# + jump#

ypos# = ypos# + yspeed#
   IF ABS(yspeed#) < minspeed# THEN yspeed# = 0.0

REM Check keyboard for move
   IF RIGHTKEY() THEN xspeed# = xspeed# + acc#
   IF LEFTKEY() THEN xspeed# = xspeed# - acc#

REM Update xpos#
   xspeed# = xspeed# * friction#
   xpos# = xpos# + xspeed#
   IF xpos# < 0.0
      xpos# = 0.0
      xspeed# = 0.0
   ENDIF
   IF xpos# > (screenwidth - playersize)
      xpos# = (screenwidth - playersize)
      xspeed# = 0.0
   ENDIF
   IF ypos# < 0.0
      ypos# = 0.0
      yspeed# = 0.0
   ENDIF
   ` Boundary detection.

if P = 1
   FOR y = 0 TO ytiles-1
      FOR x = 0 TO xtiles-1
         PASTE IMAGE map(x,y),x*tilesize,y*tilesize
      NEXT x
   NEXT y
P = 0

endif

` Yes, we are redrawing the whole screen every loop! This PASTE IMAGE
   ` statement puts the tile-type of each location in its proper place.

SPRITE player,xpos#,ypos#,player

TEXT 0,0,STR$(SCREEN FPS())
   SYNC

LOOP

REM The tilemap!

DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,2,2
   DATA 1,1,1,1,1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,2,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,2,2,2,2,2,2,2,2,2,2,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 2,2,2,2,2,2,2,2,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,2,2,2,2,2,2,2,2
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2
   DATA 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2

REMSTART
   What the heck is all this?
   Well, it's our level. Every number represents a tile on our map.
   The 1's represent background, and the 2's represent platforms. I wanted
   to keep the data 40x30 form, so you can see the level relatively clearly,
   but that wasn't possible. Each *pair* of DATA statements is one horizontal
   line of tiles.
   Obviously, there are other ways of designing your levels! You'll want to
   use a tile-mapping program, and save your levels instead of hard-coding
   them in DATA statements like this. But this will do, to show you how the
   array holds the whole level.
REMEND

+ Code Snippet

CLS
SYNC ON
SYNC RATE 0
HIDE MOUSE
P=1
TRUE = 1
FALSE = 0


tilesize = 16
playersize = 16
screenwidth = 640
screenheight = 480
xtiles = screenwidth/tilesize
ytiles = screenheight/tilesize
` Here we're calculating how many tiles we need to fill the screen.

DIM map(xtiles,ytiles)
` This creates a tilemap, so we can store the kind of tile at every
` location. (it's a bit bigger than it strictly needs to be, but that's
` because I do a check later on which involves adding one to the elements)

blue = RGB(0,0,200)
brown = RGB(100,50,0)
white = RGB(200,200,200)

REM image values
background = 1
platform = 2
` You'd normally have a lot more of these. One value for each kind
` of tile.
player = 1001

REM Getting our images for the tiles
INK blue,0
BOX 0,0,tilesize,tilesize
GET IMAGE background,0,0,tilesize,tilesize
INK brown,0
BOX 0,0,tilesize,tilesize
GET IMAGE platform,0,0,tilesize,tilesize
` Normally, you'd have a tileset to get all your images from.
INK white,0
BOX 0,0,playersize,playersize
GET IMAGE player,0,0,playersize,playersize
` Normally, you would have a sprite animation sheet to get the player from.


REM Read the map into memory
FOR y = 0 TO ytiles
   FOR x = 0 TO xtiles
      READ map(x,y)
   NEXT x
NEXT y
` skip down to the DATA statement for explanation.



xpos# = 50.0
ypos# = 200.0
` we have to store the character's position as reals (instead of integers)
` because we'll be using gravity.
xspeed# = 0.0
yspeed# = 0.0
gravity# = 0.2
acc# = 0.2
friction# = 0.95
jump# = (-5.0)
player_on_ground = FALSE



DO
  

   REM Find out what tile the player is occupying.
   xtilepos# = xpos#/tilesize
   ytilepos# = ypos#/tilesize

   REM Find out what tiles are *beneath* the player.
   undertile1 = map(INT(xtilepos#),INT(ytilepos#)+1)
   undertile2 = map(INT(xtilepos#)+1,INT(ytilepos#)+1)


   REM Should the player fall?
   IF undertile1 = background AND undertile2 = background
      yspeed# = yspeed# + gravity#
      player_on_ground = FALSE
   ELSE
      yspeed# = 0.0
      ypos# = INT(ytilepos#)*16
      ` (This pops the player up if he is inside of a platform tile)
      player_on_ground = TRUE
   ENDIF

   REM Check keyboard for jump
   IF SPACEKEY() AND player_on_ground THEN yspeed# = yspeed# + jump#

   ypos# = ypos# + yspeed#
   IF ABS(yspeed#) < minspeed# THEN yspeed# = 0.0


   REM Check keyboard for move
   IF RIGHTKEY() THEN xspeed# = xspeed# + acc#
   IF LEFTKEY() THEN xspeed# = xspeed# - acc#

   REM Update xpos#
   xspeed# = xspeed# * friction#
   xpos# = xpos# + xspeed#
   IF xpos# < 0.0
      xpos# = 0.0
      xspeed# = 0.0
   ENDIF
   IF xpos# > (screenwidth - playersize)
      xpos# = (screenwidth - playersize)
      xspeed# = 0.0
   ENDIF
   IF ypos# < 0.0
      ypos# = 0.0
      yspeed# = 0.0
   ENDIF
   ` Boundary detection.


   
if P = 1
   FOR y = 0 TO ytiles-1
      FOR x = 0 TO xtiles-1
         PASTE IMAGE map(x,y),x*tilesize,y*tilesize
      NEXT x
   NEXT y
P = 0

endif

   ` Yes, we are redrawing the whole screen every loop! This PASTE IMAGE
   ` statement puts the tile-type of each location in its proper place.

   SPRITE player,xpos#,ypos#,player


   TEXT 0,0,STR$(SCREEN FPS())
   SYNC

LOOP









REM The tilemap!

DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,2,2
   DATA 1,1,1,1,1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,2,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,2,2,2,2,2,2,2,2,2,2,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 2,2,2,2,2,2,2,2,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,2,2,2,2,2,2,2,2
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
   DATA 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
DATA 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2
   DATA 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2

REMSTART
   What the heck is all this?
   Well, it's our level. Every number represents a tile on our map.
   The 1's represent background, and the 2's represent platforms. I wanted
   to keep the data 40x30 form, so you can see the level relatively clearly,
   but that wasn't possible. Each *pair* of DATA statements is one horizontal
   line of tiles.
   Obviously, there are other ways of designing your levels! You'll want to
   use a tile-mapping program, and save your levels instead of hard-coding
   them in DATA statements like this. But this will do, to show you how the
   array holds the whole level.
REMEND

I've been looking at this code, and figured I'd try my hand at this tile business. I've read through it, I understand how it's working and could probably replicate it myself without just copying and pasting the code. So, I'm quite happy I've gotten that far. Now, there is one thing however that is bothering me ever so slightly.

All I see, is a blue screen, and a white box jumping around at insane speeds. (I've played with the variables to slow the box down, as to get an idea of what the variables did, and then read through the code)

Having looked at another project I did, I noticed I was using sprites for everything. This seems to work. This GET IMAGE and PASTE IMAGE business isn't really doing the trick. As I said, I used sprites for everything, including the backround etc. What I dont want to do, is have 1200 sprites loaded on the screen, and then have all my enemies and player stuff on top of that. Sluggish? Yes, I think it might get a tad silly. So if anyone out there can tell me, or point me in the right direction, I'd really like to know why this bit of code isn't displaying the brown boxes for the platforms like its supposed to (images) and why the player (sprite) seems to display.

Cheers,

- Steve

Back to top

Profile PM

Snafu

20

Years of Service

User Offline

Joined: 25th Jun 2003

Location:

Posted: 16th Nov 2003 21:20

Link

And yes, I did search the forums before posting

- Steve

Back to top

Profile PM

Pincho Paxton

21

Years of Service

User Offline

Joined: 8th Dec 2002

Location:

Posted: 16th Nov 2003 22:00

Link

I don't really follow your thread very well. If you arent drawing the platforms in your own code then that is a problem with the code. If I can't see the code, I can't help you. Paste image is fast in this example, but 3D plains are even faster. Try 3D!

Draw a background the size of your screen. Save it.

Now in DB...

Load bitmap "Your Background.bmp",1

Make object plain....the size of your screen,1

Texture object 1,1

Position object 1,0,0,500

Set camera to object orientation 1

Now to make your sprites you load their images and you texture more plains with those images.

Position your player character in front of the background a bit.

Position object player 0,0,499..or less

You can now use the same collision code, the same Data code, everything is the same as the example, but you have a faster engine.

Pincho.

Back to top

Profile PM Email Website

Snafu

20

Years of Service

User Offline

Joined: 25th Jun 2003

Location:

Posted: 18th Nov 2003 21:09

Link

Hey Pincho,

cheers, I'll have a play around with doing 2d.. in 3d. If anything, it's the way forward, and I need to start getting my head around 3D, as lets face it.. it's the next generation of gaming. Time to learn I think.

If you'd like to see the code (it's been pasted here before) it's been inserted right at the top of my post. I'm just curious as to why the problem I described occurs? This code appears to have been pasted many times before, and I can't see if it's for DBPro or DB.

Incidentally, I use DBPro.

- Steve

Back to top

Profile PM

Snafu

20

Years of Service

User Offline

Joined: 25th Jun 2003

Location:

Posted: 20th Nov 2003 00:06

Link

Hey,

Pincho - Thanks a lot for the pointer to go 3D, even for 2D. It's giving me all sorts of ideas.

And for no reason at all, SOME OF MEH SPRITES! (Or should I say, textures

)

- Steve

Back to top

Profile PM

Pincho Paxton

21

Years of Service

User Offline

Joined: 8th Dec 2002

Location:

Posted: 20th Nov 2003 00:08

Link

Now that you are using 3D plains you can ghost them to make realistic fire, shadows, and magic weapons.

Pincho.

Back to top

Profile PM Email Website

Snafu

20

Years of Service

User Offline

Joined: 25th Jun 2003

Location:

Posted: 20th Nov 2003 13:02

Link

Yeah, I've seen stuff like that in other "2d" games. e.g Capcom vs SNK 2. Brilliant flashy effects and fireballs, always wondered how they achieved this, and now the logic is oh so clear.

See, this is the kinda help I like. A lil bitta code / quoting from elsewhere to get you started, and all sortsa things open up.

Pincho, do you have any stuff you've made I could perhaps take a look at? You seem to be quite the 2d/3d crossover enthusiast these days

- Steve

Back to top

Profile PM

las6

21

Years of Service

User Offline

Joined: 2nd Sep 2002

Location: Finland

Posted: 20th Nov 2003 14:07

Link

http://developer.thegamecreators.com/?f=dbpro_tutorials

that should help evading the blue screen syndrome.

that's mostly for sprites, but I think it uses the same thing as well all use to get rid of that ugly blue bg. Just change the background color. You should save it to your program template file so that you don't have to write it every time.

Keyboard not detected. Press F1 to continue.

Back to top

Profile PM Email Website

Pincho Paxton

21

Years of Service

User Offline

Joined: 8th Dec 2002

Location:

Posted: 20th Nov 2003 14:23

Link

Most of my stuff was uploaded on the old RGT forum. I don't have a site to upload to. LLRGT only has 250k upload limit. So you'll have to wait for Japers Capers which will be my 2D/3D game. Hopefully by the time that's finished, the new RGT site will be ready to upload it.

Pincho.

Back to top

Profile PM Email Website

Snafu

20

Years of Service

User Offline

Joined: 25th Jun 2003

Location:

Posted: 20th Nov 2003 15:36

Link

las6, yeah, I've read stuff about getting rid of the blue background business, but the issue I have is that the PASTE image command (which'd be the fastest way of doing a 2d platformer without using 3d plains) doesn't ever, has never, and doesn't seem like it ever will want to work for me

thanks for the link though, I'll check it out, perhaps there's something in there that'll give me some ideas. I'm gonna go 3D anyway, and use a slightly different method of plotting the backdrop. Perhaps store co-ordinates in to a file, and read those out, along with size of platform and the appropriate texture to stick on it.

If I might ask another question now.. I'm considering doing the level editor before I start putting the game together, as this'll speed up creating the levels. I can implement the same code in to the game itself, so it's not a wasted effort. This'll give me a chance to get used to how DBPro handles files... Anyone got any pointers on things NOT to do whilst making a level editor?

Cheers,
- Steve

Back to top

Profile PM

Sorry your browser is not supported!

2D All the way! / The BLUE SCREEN of FRUSTRATION!