• 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
SleepySlowpoke

SFML Directory or File not found

8 posts in this topic

I'm starting off and making my first video game, as of now I'm working on the starting screen and title screen. I've made a GameScreen, SplashScreen, and finally a ScreenManager file.
 
The ScreenManager file itself is coded as so (Reminder: I just started this a few hours ago and don't entirely know what I'm doing so don't judge).
 

#ifndef SCREENMANAGER_H
#define SCREENMANAGER_H
#include<string>
#include<iostream>
#include"GameScreen.h"
#include"SplashScreen.h"

#define ScreenWidth 1600
#define ScreenHeight 900
class ScreenManager
{
    public:
        ~ScreenManager();
        static ScreenManager &GetInstance();
        void Initialize();
        void LoadContent();
        void Update();
        void Draw(sf:: RenderWindow &Window)

        virtual ~ScreenManager();
    protected:
    private:
        GameScreen *currentScreen, *newScreen;
        ScreenManager();
        ScreenManager(ScreenManager const&);
        void operator=(ScreenManager const&);
};

#endif // SCREENMANAGER_H

My main file is as so
 

#include <iostream>
#include<SFML/Graphics.hpp>
#include<ScreenManager.hpp>

using namespace std;

int main()
{
sf::RenderWindow Window(sf::VideoMode(ScreenWidth, ScreenHeight, 32), "Dash")



while(Window.isOpen())
{
sf::Event event
if(Window.GetEvent(event))
{
if(event.Type == sf::Event::Closed || event.key.code == sf::Key::Escape)
Window.close();
}
}

return 0;
}

I get an error with #include<ScreenManage.h> saying that there is no such file or directory when compiling.

 

I've checked the name and don't really have enough knowledge or experience to fix the problem by myself, google as well hasn't really helped so if anyone could help me or direct me to a tutorial on how to fix this I would greatly appreciate it.

0

Share this post


Link to post
Share on other sites

Is your file named ScreenManager.h or ScreenManager.hpp? Your #include uses the .hpp extension, but you call it a .h file in your post.

0

Share this post


Link to post
Share on other sites

Is your file named ScreenManager.h or ScreenManager.hpp? Your #include uses the .hpp extension, but you call it a .h file in your post.

 

It is ScreenManager.h but the other part is ScreenManager.cpp

0

Share this post


Link to post
Share on other sites

The problem isn't related to SFML. I think you should #include "ScreenManager.h" in your main instead of the cpp cause (even if it didn't pop error)-logically that's your class definition and where creating an object should apply.

 

Hope I helped and goodluck with your game =]

 

//Haven't used it yet but FLARE (rpg) game engine could be helpful in case you're a novice like me, it seems clean and awesome. smile.png

Edited by rijvgt
0

Share this post


Link to post
Share on other sites

The problem isn't related to SFML. I think you should #include "ScreenManager.h" in your main instead of the cpp cause (even if it didn't pop error)-logically that's your class definition and where creating an object should apply.

 

Hope I helped and goodluck with your game =]

 

//Haven't used it yet but FLARE (rpg) game engine could be helpful in case you're a novice like me, it seems clean and awesome. smile.png

 

I changed it to <ScreenManager.h> but it still gives me the same error

0

Share this post


Link to post
Share on other sites

 

The problem isn't related to SFML. I think you should #include "ScreenManager.h" in your main instead of the cpp cause (even if it didn't pop error)-logically that's your class definition and where creating an object should apply.

 

Hope I helped and goodluck with your game =]

 

//Haven't used it yet but FLARE (rpg) game engine could be helpful in case you're a novice like me, it seems clean and awesome. smile.png

 

I changed it to <ScreenManager.h> but it still gives me the same error

 

Mhh you havent posted the file where you implement the screenmanager... but you can see examples from the flare engine on what you are trying to achieve. Even if it has nothing to do with the fact that you're both using SFML, they seem to be following C++ standards.

 

For example you can see the #include "GameSwitcher.h" in the main https://github.com/clintbellanger/flare-engine/blob/master/src/main.cpp

 

And how it is implemented:

https://github.com/clintbellanger/flare-engine/blob/master/src/GameSwitcher.h

https://github.com/clintbellanger/flare-engine/blob/master/src/GameSwitcher.cpp

Edited by rijvgt
0

Share this post


Link to post
Share on other sites

Change it to
#include "ScreenManager.h"

^As I recall, all of your personal includes(files that you create yourself) should be surrounded by quotes and not angle brackets. At least that's the rule I follow and it seems to work. As Spyderzone said I believe this is the issue and not xxx.h vs xxx.hpp

0

Share this post


Link to post
Share on other sites

^As I recall, all of your personal includes(files that you create yourself) should be surrounded by quotes and not angle brackets. At least that's the rule I follow and it seems to work. As Spyderzone said I believe this is the issue and not xxx.h vs xxx.hpp


That is not true in general. While it is true that the big three C++ compilers (MSVC, gcc, Clang) use a similar heuristic for "" #includes (add the including file's directory to the search paths), this is not actually enforced by the standard (the standard allows adding an implementation defined heuristic to "" compared to <> but does never qualify what to do). So, writing really standard compliant code would require setting the correct include directory search paths in the build system.

That is something I in general prefer to follow in non-trivial projects.
0

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