1
Window / No Window :/
« on: March 03, 2010, 02:57:25 am »
Forget it. Switched to SFML 1.5 and recompiled everything - now it works.
Switching could not be easier. Great lib!
Switching could not be easier. Great lib!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Window / Similar problem
« on: March 03, 2010, 02:12:41 am »
I'm using SFML since a halft year now, everything worked fine so far.
Yesterday I continued working on my game project. It has DLL and LIB configurations as well as debug and release configs (speak 4 different configurations). The last time (some weeks ago) I ran it everything worked. Now it does no longer show the graphical window. The console window pops up and the program freezes without showing the graphical window.
A quick assembler code step through showed that the code does not even enter the main function body. It loops endless somewhere in ntdll.dll - no debugging possible here.
This is true for all configurations linking to DLLs (release and debug). Configurations with static linking work. After some tests I found out that linking to sfml-window[-d].dll lets the program freeze. Running a program linked only to the System DLL works correctly.
Does anybody have the same problem? Sounds like a driver problem. I've updated my GC drivers (NVIDIA GeForce Go 7300) shortly, that did not solve the problem. Google does not have an answer either.
Yesterday I continued working on my game project. It has DLL and LIB configurations as well as debug and release configs (speak 4 different configurations). The last time (some weeks ago) I ran it everything worked. Now it does no longer show the graphical window. The console window pops up and the program freezes without showing the graphical window.
A quick assembler code step through showed that the code does not even enter the main function body. It loops endless somewhere in ntdll.dll - no debugging possible here.
This is true for all configurations linking to DLLs (release and debug). Configurations with static linking work. After some tests I found out that linking to sfml-window[-d].dll lets the program freeze. Running a program linked only to the System DLL works correctly.
Does anybody have the same problem? Sounds like a driver problem. I've updated my GC drivers (NVIDIA GeForce Go 7300) shortly, that did not solve the problem. Google does not have an answer either.
Pages: [1]