I've been doing nothing in the way of extra rendering. I originally thought it was something to do with me compiling in VS2005 -- but I've been compiling in VS2003 lately due to the memory issues and I'm still getting this kind of crash. Either it would randomly crash in studiorender.dll, or it would crash in the EnemyDistance() function for no apparent reason.
Sometimes I'll go an entire round or two in the game with no problem, and sometimes it'll happen within seconds of starting it up. It's happening at insanely random times. It's been doing this practically since I exported the source of the mod and started working on it. I only just posted about it because it's starting to drive me nuts that the team and I can't have a very good playtest without the game completely crashing for someone. I've been figuring it was something I'm doing but now that I know other people are getting this too I guess it's not the case :\ -- Andrew Garry Newman wrote:
-- [ Picked text/plain from multipart/alternative ] Hey I just got this crash too! I thought it was because I was messing around rendering a model twice ( http://gmod.garry.tv/img/garrysmod/01_NOV_2006/gm_construct0005.jpg) - are you doing anything like that? There isn't much else I've changed and it does seem like a pretty random crash. How long has it been happening to you? On 11/1/06, Andrew Orner <[EMAIL PROTECTED]> wrote:I'm having issues with random crashes in the studiorender.dll library. I don't think it's due to a driver issue as I'm running the most up-to-date driver, but it is still a random crash. Running the MDMP through debugger tells me this: ExceptionAddress: 2c00ae3f (studiorender+0x0000ae3f) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 02d9cd58 Attempt to read from address 02d9cd58 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 000c1338 2c00b338 00000000 00000b52 00003f7e studiorender+0xae3f 000c13cc 2c017f5f 00000000 00000020 0000044c studiorender+0xb338 000c1464 2c00bc41 3fa4f800 2508f280 000c14f0 studiorender+0x17f5f 000c147c 2c002f30 000c14f0 00000000 00000000 studiorender+0xbc41 000c14a4 0dbc64c4 000c1500 00000000 000c150c studiorender+0x2f30 000c1540 0d880b84 bf5846ce 000c1558 00000000 engine+0xe64c4 000c1574 0d85d3f9 000c1644 000c15f4 000c15bc materialsystem+0x30b84 000c1590 0d85d469 000c15d8 000c15dc 000c15e0 materialsystem+0xd3f9 000c15a8 3f48c8ca 3f48c8ca 3f48c8ca c3fe0000 materialsystem+0xd469 000c15ac 3f48c8ca 3f48c8ca c3fe0000 43140000 0x3f48c8ca 000c15b0 3f48c8ca c3fe0000 43140000 c31e0000 0x3f48c8ca 000c15b4 c3fe0000 43140000 c31e0000 3f800000 0x3f48c8ca 000c15b8 43140000 c31e0000 3f800000 00000000 0xc3fe0000 000c15bc c31e0000 3f800000 00000000 00000000 0x43140000 000c15c0 3f800000 00000000 00000000 44d4f50a 0xc31e0000 000c15c4 00000000 00000000 44d4f50a 3f7faa27 0x3f800000 PRIMARY_PROBLEM_CLASS: STACK_CORRUPTION FOLLOWUP_IP: studiorender+ae3f 2c00ae3f 8b1490 mov edx,dword ptr [eax+edx*4] I don't think this is something I can personally fix. Could this be a hardware issue, an engine issue, or something I might have somehow brought in with my mod? If it is something that I might have brought in with my mod, is there any possible way of debugging what it might have been? Thanks, -- Andrew Orner Lead Programmer, No More Room in Hell _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders-- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
