Jump to content
  • Advertisement


  • Content Count

  • Joined

  • Last visited

Community Reputation

100 Neutral

About zdkroot

  • Rank
  1. Actually no, I didn't see that in any of the tutorials o_O Am I really just that blind? I'll test that right now. Edit: Nope, no change. Still won't run with SFML_STATIC; set in the preprocessor. In debug or release. It still complains if it doesn't have the DLLs in the folder though...
  2. Serapth: I didn't use the bundled ones, I compiled my own for vs2011 and for vs2008 I used the ones from the sfml site, and compiled my own, to no avail. Dragonsoulj: I just pasted the code I had been toying with trying to get it to work. I'm pretty sure I've tried every possible permutation of that line, and none of them worked. On the up side, while trying out SFML-2.0, I was reading this and it says you can add SFML_STATIC; to the preprocessor, and change the dependencies to use the -s version of the .libs. That worked. Both with 2.0 and 1.6, in vs2008. I guess that just means it's some kind of DLL issue still? I extracted them straight from SFML-1.6.zip to the Debug directory with the exe, and it still won't display a window. If i set the SFML_STATIC; for the Release config, Release will compile and run fine, debug will not. Thoughts? And thank you both for taking time to help
  3. I've been trying to get SFML to simply create an empty window with a color in it for more hours than I care to admit. I was working through the this tutorial, when I apparently hit a wall. I completed through part 2, everything compiles fine, no errors, but when I run it I just get a blank dos prompt when a blinking cursor that I have to force close. The only debug output is The thread 'Win32 Thread' (0x520) has exited with code -1073741510 (0xc000013a). The thread 'Win32 Thread' (0x2c8) has exited with code -1073741510 (0xc000013a). The thread 'Win32 Thread' (0xe98) has exited with code -1073741510 (0xc000013a). The program '[3700] Pang2.exe: Native' has exited with code -1073741510 (0xc000013a). I've tried both vs2011 dev preview, and vs2008 express (too frustrated to install 2010 also...) and I get the exact same results. For vs2011 I compiled SFML myself, everything seemed to go fine there. In vs2008 I tried both the bundled DLLs and compiling my own, same result both times. Eventually I copy/pasted the code right from the tutorial, no luck. I even downloaded the "up to this point" project file from the tutorial, compiled it with no errors, black box, blinking cursor. This code runs with no problems. int main() { sf::Clock clock; while (clock.GetElapsedTime() < 5.0f) { std::cout <<clock.GetElapsedTime() << "\n"; sf::Sleep(0.5f); } return 0; } As soon as I try to create a sf::Window or sf::RenderWindow, it just hangs at the blinking cursor. This does not run. int main() { sf::RenderWindow Window(sf::VideoMode VMode(800, 600, 32), "SFML Window"); while(Window.IsOpened()) { sf::Event Event; while (Window.GetEvent(Event)) { switch (Event.Type) { case sf::Event::Closed: Window.Close(); break; default: break; } } Window.Clear(sf::Color(255,0,0)); Window.Display(); } return 0; } This also appears in the debug output...I don't know if any of it is bad. 'Pang2.exe': Loaded 'C:\Users\Zack\AppData\Local\Temp\ammemb.dll', Binary was not built with debug information. 'Pang2.exe': Unloaded 'C:\Windows\SysWOW64\atigktxx.dll' 'Pang2.exe': Loaded 'C:\Windows\SysWOW64\atigktxx.dll' In the "modules" menu, sfml-window-d.dll and sfml-system-d.dll and ammemb.dll all have a red ! and the tooltip says "The module did not load at the default load address". sfml-graphics-d is listed and does not have the same error. All three DLLs are in the same folder. It also reports "Symbols not loaded" for everything in the module list except for Pang2.exe and ammemb.dll ("symbols loaded", and "binary not built with debug information" respectively). I'm completely at a loss. I've used freeglut before and had no problems creating a window and drawing to it. Am I missing some dependency for building the vs2011 DLLs? Should I try vs2010 also? I'm rather tired of installing software, my system feels so bloated lately. I run win7 x64 on a core2duo 2.93ghz and a radeon 4870 hd; I updated the drivers this morning. Thanks to anybody that feels like they need a headach...err wants to help. If you need any other information just ask. [color=#ff0000]UPDATE: I added SFML_STATIC; to the C++ preprocessor, and used the static lib files (the ones with -s in the name) and now the I can make all sorts of multicolored windows in SFML 1.6 and 2.0. I'm still not sure of the original issue.
  4. Basically, anything related to the fixed-pipeline, is depreciated. OpenGL and DirectX both use shaders now, but OpenGL maintains backwards compatiblity by using immediate mode, which you don't want The modern 3D programming tutorial I linked uses shaders. Based on your description, it sounds like you want to make an engine, and that's totally fine. Building an engine is something I'm really interested in as well. I've been doing a lot of "game development" research in the last few months, and it seems to me that most people don't have a clear idea if they want to make a game or an engine. Most of the advice is don't reinvent the wheel; if your goal is a game, then you shouldn't. But if your goal is to play with proceduaral terrain generation, and maybe make a game out of it, then do whatever you feel like I would definitely check out Unity, UDK, Ogre3D and recently CryTek3 (I'm leaving off several, just wikipedia game engine), if for nothing other than to play with them and see what a real modern engine can do. They are all complete engines with an IDE that use various scripting languages. They handle everything from input to importing 3D models and assests to sound, etc. I've never played with them much, they may already have a built in means for doing prodcedural terrain generation. Best of luck! It's going to be a long road but I'm on it too, lol. Edit: Further reading.
  5. All of the things you listed are pretty standard. They aren't really frameworks, they're just very thin libraries. OpenGL itself exclusively handles graphics rendering. It doesn't have any way of doing audio, mouse/keyboard input, etc. DirectX has all of those things (DirectSound, DirectInput,etc) so for windows you can simply use DirectX if you want. OpenGL however, actually requires additional libraries. Basically everything you need to know can be found here or here. SDL, SFML and freeGLUT are popular; GLFW is a freeGLUT alternative that also looks good. Only SDL and SFML handle sound, but they all do windowing and input. Qt and GTK+ are for gui building. Vlc for example uses Qt for it's interface. You only need one of those, basically just pick one and use it until you have a reason not to. That being said, if you want to make a game more than you want to learn how to program a graphics/physics engine, you probably want to use an already built one, which will vary depending on what kind of game you want to make. Unity, UDK, LOVE, Ogre3D are all engines that do all sorts of different things. That is, as you said, a whole other can of worms. So what do you want to do? Write an engine or make a game?
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!