marioq82

Uninstalled and reinstalled Leadwerks. Fixed issue. No clue what caused it in the first place, but I'm happy to be back on the productive track. Thanks Slastraf for the recommendation.

I have not tried that yet, but I will give it a shot before attempting to roll back the drivers and then post the outcome on the forum.

Whenever I attempt to Run/Debug a game the program seems to freeze up and display "(Not Responding)" in the window title bar. I have to manually close the program, or click on the Stop button in the Script editor, to return back to the Leadwerks editor. I have a Radeon HD 7870. The issue happened with both the 15.8 and 15.9 beta drivers. Not sure when the last time that it worked, as I haven't used the engine in some time, but I will attempt rolling back the drivers. Anyone else experiencing this issue? I've attached a screenshot of the issue.

I was having the same issue, but was able to fix it. What brand graphics card do you have? Have you ever copied and pasted DLL files directly into the Leadwerks folders? If so, try removing all DLLs and restarting.

So I rolled back my AMD drivers to version 14.4 and noticed something interesting. After the fresh install my settings were defaulted to have Crossfire enabled. I ran Leadwerks and everything worked perfectly. I then went into Catalyst Control and disabled Crossfire (my normal preference setting, as I have my primary monitor on one HD7870 and my two auxiliary monitors on the second HD7870) and attempted to run Leadwerks again, this time receiving the error. I decided to then test this out on the more recent driver versions. I had the same results on version 14.9, and received a "runtime error R6025 -pure virtual function call" message when running with driver 14.11.2 (beta) and Crossfire enabled (exception_access_violation when disabled). So for now, it seems that I will stick with version 14.9 and will just have to continue enabling Crossfire before deciding to work with Leadwerks, which doesn't seem like too much of a hassle. I'll still continue to look for a solution to the problem, whether it be with new driver updates or a different configuration with my settings and/or setup.

Yes. I am running on Windows 7 64-bit.

I removed all AMD video drivers and the software ran perfectly. Updated to latest AMD beta driver, back to not working. Just going to have to find the last stable version and install. Will also try to submit the issue within AMD forums.

So I went back into VS and stepped through the debugger and found that the program kept crashing once it attempted to access the atioglxx.dll. Upon further research, I found the following link (http://forums.relicnews.com/showthread.php?276523-ATI-driver-update-14-9-broke-HW2-(atioglxx-dll-access-violaton) which shows that others were having similar problems with ATI/AMD drivers. So I simply went into my driver repository and replaced the current atioglxx.dll with the previous version. Fixed the issue in VS. EDIT: This does not fix the issue when attempting to launch Leadwerks through Steam.

I started having this same problem yesterday when I attempt to launch Leadwerks from Steam. Also, when I attempt to debug and run my project from Visual Studio I receive a "R6025 pure virtual function call" error message. I'm currently using an AMD 7800 series card. Had no issues prior to yesterday. Updated AMD drivers to current 14.301.1006-141009a-176674E(beta) package hoping that would solve the issue, but no dice. Currently have Catalyst Version 14.9, OpenGL Version 6.14.10.13085 installed. Don't know if any of that information will help, but thought I'd provide it.