PlaneShift

Support => Technical Help: IN GAME bugs (after loading world) => Topic started by: davj on December 24, 2006, 06:11:35 pm

Title: microsoft visual c++ runtime error
Post by: davj on December 24, 2006, 06:11:35 pm
whenever i quit the game an error window appears saying

"Runtime error!

Program:<location_of_game_directory>\psclient.exe

R6025
-pure virtual function call"
Title: Re: microsoft visual c++ runtime error
Post by: Karyuu on December 24, 2006, 08:47:22 pm
Known and rather "ancient" issue. It doesn't affect gaming, so a fix for this isn't likely to appear immediately - more pressing bugs demand attention first (http://img137.imageshack.us/img137/4929/usedusedusedvi7.gif)
Title: Re: microsoft visual c++ runtime error
Post by: tokyolamb on December 24, 2006, 09:31:28 pm
This would be an easy fix, they should fix it ASAP. its interfered with my gaming a lot of times =(
Title: Re: microsoft visual c++ runtime error
Post by: steuben on December 24, 2006, 09:42:23 pm
/me points to the source code, #planeshift-build, and the dev team app
knock your self out.
Title: Re: microsoft visual c++ runtime error
Post by: Karyuu on December 24, 2006, 09:47:23 pm
Quote from: tokyolamb on December 24, 2006, 09:31:28 pm
its interfered with my gaming a lot of times =(

Perhaps you would care to explain how this message, which appears after you quit the game, has interfered with your gaming lots of times? (http://img151.imageshack.us/img151/7151/pleasedhc3.gif)
Title: Re: microsoft visual c++ runtime error
Post by: neko kyouran on December 25, 2006, 03:43:12 am
Maybe he's usng a mouse with limited clicks on it.  or a keyboard with a limited amount of times he could push the spacebar, enter key, or escape key. (i think that covers them all)

Playing Diablo and Diablo 2 with do that to you.
Title: Re: microsoft visual c++ runtime error
Post by: Nikodemus on December 25, 2006, 11:57:28 am
Quote from: neko kyouran on December 25, 2006, 03:43:12 am
Playing Diablo and Diablo 2 with do that to you.
Hehe.

But i wonder, Does the fact that PS closes itself very long, has something to do with that error?
To me it may even close itself for 3 minutes, while the use of RAM is slowly droping by 1-4 MB/s.
Is it becaue PS is saving errorlog.txt?
I can't close it instantly by killing the process, but that is not the point. If syste can do it almost instalntly, PS should also be able to close itself that fast.
ideas?