Sign in to follow this  
ghigared

Having some trouble with rendering

Recommended Posts

ghigared    133

I am currently working with the slick2d game engine (been developing in java for a few years, and finally decided to begin working on a independent game). Been having a blast but ran into a small problem tonight: When i render my tiled map unto screen my fps suffers tremendously. I limited the games rendering to the size of the camera on screen and even then it slows down my fps dramatically, can anyone help? Thanks in advance.

 

 

Basically this is the code that is causing the problems :

 

    for(int i = 0; i < collisionTileGraphics.size(); i++)
            if(collisionTileGraphics.get(i).getX() >= -16 && collisionTileGraphics.get(i).getX() + collisionTileGraphics.get(i).getW()
                <= Variables.WIDTH + Variables.TEST_MAP_TILE_WIDTH )
                collisionTileGraphics.get(i).render(gc, g);

 

Where collisionTileGraphics is an arraylist which holds the screens collision layer of graphics.

 

public void render(GameContainer gc, Graphics g){
        image.draw(x,y);
    }

 

where the image is a slick2d Image.

Share this post


Link to post
Share on other sites
BaneTrapper    1531

Overkill on tags...

Described problem is not lag, or connected to lag in any way. Two java tags first on list "java" last on list "Java" . What is "space" tag for? also "help"...

 

 

Some things you should provide:
Amount of tiles being drawn.
Amount of FPS without tiles being drawn.

Amount of FPS with tiles being drawn.

Edited by BaneTrapper

Share this post


Link to post
Share on other sites
BCullis    1955

If not, your first step is to calculate which tiles are on screen, and draw only those tiles...

I think that's what the giant if statement is trying to do.

 

One way to test if you're properly culling the non-visible images is to throw in a debug "drawcall count" printout at the end of the frame.  Just reset the variable to 0 at the beginning of every frame, and increment it inside the culling branch (i.e. right after the "draw" call).

 

Some kind of scene-graph or space-partitioning tree might make your draw calls more efficient by keeping you from looping through every tile every frame, but at <3000 tiles total, that still shouldn't be a costly loop.  Methinks there's more going on here.  How expensive/heavy is a draw call in slick2D?

 

Edit: fairly expensive, apparently.  Check out this link for some suggestions.  Biggest one is to turn your tiles into sprites packed into the same spritesheet and use the DrawEmbedded call instead of just Draw.

Edited by BCullis

Share this post


Link to post
Share on other sites
ghigared    133

Edit: fairly expensive, apparently.  Check out this link for some suggestions.  Biggest one is to turn your tiles into sprites packed into the same spritesheet and use the DrawEmbedded call instead of just Draw.

 

I'm trying to work with a .tmx file from the tiled software for the map though? I thought it was the most efficient way to do it, since the tiled software works with a spritesheet

Share this post


Link to post
Share on other sites
BCullis    1955

All I know is what I see in your code and what I read on that link: image.draw is a heavy, costly method compared to image.drawembedded.  Did you read the suggestions?  From the wiki:

 

Even if you aren't using texture atlases, you should still use drawEmbedded whenever possible. Calling Image.draw
requires various matrix transforms, plus it sends the quad to the GPU
with glBegin/glEnd. Ideally, you should be minimizing calls to
glBegin/glEnd by using startUse/endUse whenever possible.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this