Main while loop is not executing

[masskiller]

I know I'm not supposed to use macro's, but that isn't going to solve the problem now, is it?

Granted that it may not solve the problem, but still it doesn't hurt. It's better to cultivate good habits than bad ones.

[FRex]

Os and compiler? Did you try using debugger to see if the code executes?
The fact that adding line to the loop fixes it makes me think you have your compiler settings wrong and it optimized out entire loop for some reason. I'm probably wrong but that'd be really cool.

So? You can do all the 3D magic with OpenGL and use SFML just as context creator and optional audio output.

But then you'd not use clear(), especially not in sf::Window

Where's the pure C when he's using SFML, a C++ library? (I probably didn't get that joke...)

Knowing c++ isn't prerequisite for knowing OpenGL, he might be experienced C coder, migrating to c++. Joke: Carmack had around 10 years of experience in OpenGL and C and none in c++ at the point of beginning id tech 4(Doom 3, Quake 4, everything before was just C) engine that was his (company) first real c++ project.

If you want to reply to that send me a pm, enough goofing in this thread.

[genzm]

os is windows, and i'm using visual studio c++ professional 2012.
If this would be a compiler setting (which I actually would doubt), what could I do to change it?
In debugger the code does execute and updates the title.

// edit
Another thing I just realised:
If I do add a line which prints out some text, I get a very high amount of frames per second (over a 1000). even though vertical sync is set on. Shouldn't vertical sync limit it to 60 frames?

[FRex]

Use sf::Time instead of unsigned and do +=clock.restart() on it, you can compare them easily too, you can do like time<=sf::miliseconds(FPS_PDATE) or something. I suspect your loop goes over 1000x per second, miliseconds get truanced in C/C++ int way to 0 and debugger stepping slowed that down and let clock build few miliseconds up. If you don't know what change I'm talking about tell me and I'll make change for you to try.

Vsync can be forced off in setting for GPU and I think it only affects fullscreen.

[genzm]

Use sf::Time instead of unsigned and do +=clock.restart() on it, you can compare them easily too, you can do like time<=sf::miliseconds(FPS_PDATE) or something. I suspect your loop goes over 1000x per second, miliseconds get truanced in C/C++ int way to 0 and debugger stepping slowed that down and let clock build few miliseconds up. If you don't know what change I'm talking about tell me and I'll make change for you to try.

Vsync can be forced off in setting for GPU and I think it only affects fullscreen.

I'm not really sure what you want to change. But indeed, when using

window.setFramerateLimit(60);

It all works just fine. I still don't really see why this solves my problem, but I'm glad I'm getting some progress.

[FRex]

sf::Time fps_counter;
while (true)
    {
        fps_counter += c.restart();
        ++fps;
        if(fps_counter >= sf::milliseconds(FPS_REFRESH)) {
            char buffer[32];
            int av = (int) (fps * 1000) / fps_counter.asMiliseconds();
            sprintf(buffer, "%d - frames per second", av);
            window.setTitle(buffer);

            // reset
            fps_counter = sf::Time::Zero;
            fps = 0;
        }

        //draw();

        window.display();
    }

[genzm]

Oh, I see, like that

I tried it and it executes the loop. This is off course a better use than a simple integer.
Thanks for the tip.
But I still don't really understand why this fixed it :/

[FRex]

1. Loop is going too fast, clock gains some fraction of milisecond.
2. Get that fraction as int = rounded down to 0.
3. Reset Clock.
4. Repeat.

Console io, debugger and setFramerateLimit slowed loop down enough to build up more than fraction of milisecond in clock so it wasn't truanced to 0.

[genzm]

Ok, this would explain why the title isn't updated.
But the rest of the loop (the commented draw() function), and other steps like controls,...
They should still be executed?

[FRex]

Yes, and display() is getting executed.

[genzm]

Oh no sorry, I see.
The functions I wrote for example to check controls, all used this int to know the difference in time. Since there was no difference, nothing changed.
So, that's solved
Thanks for all the help everyone. I wouldn't have found it by myself.