• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Crusable77

Problem with my Collision with c++ and SFML

4 posts in this topic

Hello, I have been making a pong clone and I have run into some trouble with collision. It is not that I cannot get collision to work, it is(I think) my approach that is flawed. I have searched on google for help, however I could not find anything.

 

collision.h

 

 

 
 
#ifndef COLLISION_H
#define COLLISION_H
 
#include <SFML\Graphics.hpp>
 
#include "Ball.h"
#include "Player.h"
#include "Enemy.h"
 
class Collision{
 
public:
    Collision();
    ~Collision();
 
    //return true if there is a collision detected
    bool BOP_Collision(sf::RenderWindow& App, const Player* const player = NULL, const Enemy* const enemy = NULL); //BOP = boundries on paddle
    bool BOB_Collision(sf::RenderWindow& App, const Ball* const ball); //BOB = boundries on ball
    bool POB_Collision(sf::RenderWindow& App, const Player* const player = NULL, const Enemy* const enemy = NULL, const Ball* const ball = NULL); //POB = paddle on ball
 
private:
    sf::Vector2f pVector; //vector for the player
    sf::Vector2f eVector; //vector for the enemy
    sf::Vector2f bVector; //vector for the ball
 
};
 
#endif

collision.cpp

 

 
#include "Collision.h"
 
Collision::Collision(){}
 
Collision::~Collision(){}
 
bool Collision::BOP_Collision(sf::RenderWindow& App, const Player* const player = NULL, const Enemy* const enemy = NULL){
 
    pVector = player->getPosition();
    eVector = enemy->getPosition();
}
 
bool Collision::BOB_Collision(sf::RenderWindow& App, const Ball* const ball){
 
 
}
 
bool Collision::POB_Collision(sf::RenderWindow& App, const Player* const player = NULL, const Enemy* const enemy = NULL, const Ball* const ball = NULL){
 
 
}

 

The error is with

pVector = player->getPosition()
. It says "Error: the object has type qualifiers that are not compatible with the member function". Thank you in advance for all your help.
0

Share this post


Link to post
Share on other sites
I am guessing your getPosition method is lacking a const on the right hand side of the method signature.
If I guessed right, it should be something like this:
class Player
{
public:
    Vector getPosition() const; //<- this const
};
Edited by ultramailman
1

Share this post


Link to post
Share on other sites

Why does it need to be constant? Also, thank you, It did work.

Edited by Mathew Bergen
0

Share this post


Link to post
Share on other sites
Look at this signature:
bool Collision::BOP_Collision(sf::RenderWindow& App, const Player* const player = NULL, const Enemy* const enemy = NULL);
The player variable is of type
const Player * const
That means the pointer and the object it points should not be changed while in this function. So if you call a read-write (not const)method on player, the compiler will tell you it's an error. That's why the method should be declared as read-only (has that const on the right side).

It's a good idea to make a method const, if the method does not modify the object. Edited by ultramailman
1

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  
Followers 0