PlaneShift

Support => Technical Help: Problems BEFORE entering the game => Topic started by: ikorack on August 11, 2008, 09:30:17 pm

Title: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: ikorack on August 11, 2008, 09:30:17 pm
when i start up the client i get an EXCEPTION_ACCESS_VIOLATION at 0056F488 message iv saved the file and i can email it if you want me to.
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: Caarrie on August 11, 2008, 09:36:00 pm
http://hydlaa.com/smf/index.php?topic=31760.0
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: ikorack on August 11, 2008, 09:38:35 pm
My error is not in there
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: Caarrie on August 11, 2008, 09:43:29 pm
read the first post of that thread
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: ikorack on August 11, 2008, 09:43:58 pm
i did and i dont understand it.
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: Caarrie on August 11, 2008, 09:47:28 pm
Although the game is getting more and more stable, crashes still occur. If you know what causes the crash (for example, it crashes everytime you give a certain command), you can check the bug tracker (http://bugs.hydlaa.com) to see if it is already mentioned. If so, you can add information there (or confirm the bug). Otherwise make a new report.
Often, crashes are less clear, and they may be hardware and OS dependent. Instead of making a bug report 'I have a crash', check the OS specific parts of the forum (be sure to read the stickies!). In these cases, please email me the diagnostic file (see below), if it is not yet listed in this thread, at this email address: (http://img132.imageshack.us/img132/2962/emailbk0.png).
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: ikorack on August 11, 2008, 09:48:22 pm
i think ill just wait for it to get fixed by someone.
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: Bubba on August 11, 2008, 10:07:45 pm
Hi Ikorack,

What kind of graphics card/adapter does your system have?

(Note: It might be a good idea to add your system specs to your signature.)

-B.
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: Caarrie on August 11, 2008, 11:19:36 pm
i think ill just wait for it to get fixed by someone.

if you give us no information and dont even send the dump we cant "fix" it.
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: citizen on August 20, 2008, 11:03:49 am
Ikorack, i guess you have an ATI card.
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: Lanarel on August 20, 2008, 07:25:00 pm
Although the game is getting more and more stable, crashes still occur. If you know what causes the crash (for example, it crashes everytime you give a certain command), you can check the bug tracker (http://bugs.hydlaa.com) to see if it is already mentioned. If so, you can add information there (or confirm the bug). Otherwise make a new report.
Often, crashes are less clear, and they may be hardware and OS dependent. Instead of making a bug report 'I have a crash', check the OS specific parts of the forum (be sure to read the stickies!). In these cases, please email me the diagnostic file (see below), if it is not yet listed in this thread, at this email address: (http://img132.imageshack.us/img132/2962/emailbk0.png).
i did and i dont understand it.
Can you tell me what is difficult to understand in that text so I can make it clearer? It should say that you can email the dump file that you are asked to save to me at the email address shown in the image (to prevent spam).
Title: Re: EXCEPTION_ACCESS_VIOLATION at 0056F488
Post by: Liadosian on August 24, 2008, 05:25:57 am
Hello

I have experienced the same failure. Turning off the "Vertex Buffer Object" option in Pssetup seems to help. In my case the setup crashed also. So I had to open the psclient.cfg file and edit the following line to turn off the option:

Video.OpenGL.UseExtension.GL_ARB_vertex_buffer_object = true

Just write false instead of true.

Well, the client works, for now, but Pssetup worked one or two times, and then kept on crashing.