TGEA 1.7 bug: interlockedcompareexchange64 could not be located
by Jack Stone · in Torque Game Engine Advanced · 05/28/2008 (2:34 pm) · 2 replies
I recently downloaded TGEA 1.7.0, and I can compile in release and in debug builds with no errors and no warnings. Although I had to make the following change to sfxprofile.cpp:
Changed:
// if ( mResource && SFX )
// mBuffer = SFX->_createBuffer( this );
To:
if ( (mResource != NULL) && (SFX!= NULL) )
mBuffer = SFX->_createBuffer( this );
I doubt this has anything to do with my issue, but I thought I'd mention it, since it's the only change I had to make to compile the project.
The release build and all the demo games work fine, however, when running the debug build I get the following error:
"The procedure entry point InterlockedCompareExchange64 could not be located in the dynamic link library KERNEL32.dll"
I did a search on the internet, and the forums for this, and I could find very little information. Apparently it has something to do with "forwarding" the location of a function? I've never encountered a problem like this before, so I wouldn't mind some advice on how to proceed.
I'm not sure if my system specs are relevant to this issue, but I'll post them anyway:
WinXP pro, 2 Nvidia Geforce 7900 GTX Go's in SLI. (GFX Drivers haven't been updated recently because of the difficulty in finding new drivers for laptops, could this be the cause of the issue? If so, I could try to find some modded drivers.)
Thanks,
Jack
Changed:
// if ( mResource && SFX )
// mBuffer = SFX->_createBuffer( this );
To:
if ( (mResource != NULL) && (SFX!= NULL) )
mBuffer = SFX->_createBuffer( this );
I doubt this has anything to do with my issue, but I thought I'd mention it, since it's the only change I had to make to compile the project.
The release build and all the demo games work fine, however, when running the debug build I get the following error:
"The procedure entry point InterlockedCompareExchange64 could not be located in the dynamic link library KERNEL32.dll"
I did a search on the internet, and the forums for this, and I could find very little information. Apparently it has something to do with "forwarding" the location of a function? I've never encountered a problem like this before, so I wouldn't mind some advice on how to proceed.
I'm not sure if my system specs are relevant to this issue, but I'll post them anyway:
WinXP pro, 2 Nvidia Geforce 7900 GTX Go's in SLI. (GFX Drivers haven't been updated recently because of the difficulty in finding new drivers for laptops, could this be the cause of the issue? If so, I could try to find some modded drivers.)
Thanks,
Jack
Torque Owner Redacted