Author |
Message |
Monk66
|
Sunday, June 07, 2015
Whenever I (Or anyone else) try to PM each other,Our games get crash,So does anyone has Solution for this??
thanks in advance.
|
Monk66
|
Tuesday, June 09, 2015
Can anyone Please solve this Bug??????
There is always a Hope.
|
Eagle
The Purpose
|
Tuesday, June 09, 2015
Welcome to the forums. Present yourself before your problem.
With more information, I might be able to help you.
Were you using the /tell command ?
Which server were you connected to ?
Which version of ZEQ2-Lite were you using ?
Are your messages containing colored characters ? (or ^<number>)
|
Monk66
|
Tuesday, June 09, 2015
Sorry I'm new,
thanks for the reply.
I used the Chat to target button for PM
No matter which server I and the one who I am PMing to get crashed [Our games Close(the windows close)]
I'm using revision 1536 and revolution 5 Both have same problems.
No,Colored or normal it Closes our ZEQ2 windows.
And also people misuse this bug to crash other people.
|
Eagle
The Purpose
|
Tuesday, June 09, 2015
I have just tested. It displays colored characters in the console, which explains why you get crashes. Avoid private messaging through ZEQ2-Lite and use something else for this task. (instant messaging, or vocal/video call).
|
Monk66
|
Tuesday, June 09, 2015
People crash others for fun
|
Monk66
|
Tuesday, June 09, 2015
So,can I do something to make them normal coloured?
|
Monk66
|
Tuesday, June 09, 2015
And some people like Shadow(and 2 - 3 others that I can't name here) have managed to do that anti-Pm-crash
|
Eagle
The Purpose
|
Tuesday, June 09, 2015
People crash others for fun
It's not our business. ZEQ2-Lite shouldn't be played in it's actual state.
So,can I do something to make them normal coloured?
You can't fix this through ZEQ2-Lite. It needs a bit of code change.
|
Monk66
|
Tuesday, June 09, 2015
Oookay....thanks for replying anyways.
|
Monk66
|
Tuesday, June 09, 2015
Oh and Try to fix that bug too.
|
Eagle
The Purpose
|
Tuesday, June 09, 2015
I am not enough qualified to do such things, yet.
The error seems to come from "R_GetShaderByHandle" but I couldn't find it in the source code of the revision 1913. It is probable that it has been fixed in one of the unstable revisions.
|
Monk66
|
Tuesday, June 09, 2015
okay thanks,I'll try to download the latest version,and try it again...thanks again...
|
Eagle
The Purpose
|
Tuesday, June 09, 2015
You already have the latest version. Except if you have an interest toward the development, downloading the unstable revisions won't bring anything to you.
|