• Advertisement


This topic is now archived and is closed to further replies.

OpenGL OpenGL 2d Hockey Rink

This topic is 5596 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Looking for tips on how to draw a 2d hockey rink, for use later in a game. Something similar to the surface in NHL 96 (Sega Genesis). I was thinking drawing the flat ice first (square with textured bitmap) and then the lines, and then the boards, logos, etc... The problem is later on I''ll need to be able to easily calculate collisions. Unfortunately there is little documentation on hockey games on the WWW. Any advice appreciated.

Share this post

Link to post
Share on other sites
Use OpenGL. Draw the lines and make the rink. For the boarders put in pictures and such. Also, instead of looking up hockey on the WWW, check out programming and 3D API''s such as opengl

Share this post

Link to post
Share on other sites

Thanks, I''ve already found that project and looked
into it. None of the links to download on that
web page work, and the source code isn''t on the ftp.

If you have the source code to the mhockey project, or
know where to get it, that''d be appreciated. I emailed
all the addresses on that web page and they all come
back "user unknown". Maybe Electronic Arts bought them
out or something

I have drawn a rink with simple lines to scale of an actual
NHL rink. I think what I''m going to need are the following:
- Textured Ice Quad for Main Ice Surface
- Textured Red line and blue line quads to overlap the main ice surface (I hope once I get going I can modify the ice texture to look skated on)
- Faceoff Circles
- Red lines coming off these cirles (slot area)
- Textured goal net quads
- Textured plexi glass quads (transparent)
- Not sure how to handle the corners yet.

For an idea of what i''m kind of going for:
www.cs.dal.ca/~rodgers/NHL96_000.bmp and
I''ll post what I come up with (should be funny) in a couple

Share this post

Link to post
Share on other sites

Hey, tried to send you the source to mhockey 0.50 at the e-mail address specified in your profile but the mail borked with this (changed the address in this posting for yer privacy):

The original message was received at Thu, 24 Oct 2002 17:04:42 -0300 (ADT)

----- The following addresses had permanent fatal errors -----

(reason: 501 5.1.3 Path data: Perhaps this should have been a dot (.) instead of colon ( ?)

If you have another address to send it to post it in another message and I''ll send you the source (~400k), if you want the windows binaries/models/grafix/sounds I have them too (~1.4 meg) ...

Share this post

Link to post
Share on other sites
draw a quad for the ice surface with a repeating texture that looks like ice (either smooth glassy ice like NHL94 or the snowy ice with shavings on it from NHL95... or if you''re badass transition from one to the other over the course of the period). After the quad draw the blue and red lines, the circles, face off dots, etc either using glLines and such or with textured polygons, but regardless of which you use blend it with the ice surface. For the boards, glass, and seats you might want to use a modeler if you want anything halfway decent.

- outRider -

Share this post

Link to post
Share on other sites

I emailed you from an address to send the files.
It''s greatly appreciated!! mHockey is a 3d project
which might be a little out of my scope, but I think
it''ll show me a lot of useful things. If you didn''t get
the email, the address is rodgers AT cs.dal.ca


Thanks for the great advice! I am going to load up
NHL94 tonight and NHL96 and compare the ice textures.
NHL96, Damn you New Jersey devils! (Me == Wings Fan)
I found NeHe''s tutorial on blending:
Hopefully that will help me with making the red line
look like part of the ice.

- There are tutorials out there on making glass in
OpenGL, might look at them later on. For now a
decent bitmap that I can texture at both ends will
suffice. Now if I could make something where you could
see the players reflection slightly when they are
in the corners, while still seeing the fans behind the
glass, now that would be sweet.

- As for transitioning the ice between glassy and snowy,
not sure how I''d do that. Knowing OpenGL, it''s probably
not too hard.

Share this post

Link to post
Share on other sites

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
      Thank you
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement