@Spike
I'm having a lot of trouble trying to run ftesv (windows or linux, x86 or x64) after version 50xx. I have no issues running my mod with FTE SVN 5066 or FTE SVN 4993, but when I try to run 55xx or above, I get all kinds of errors. The frikbotX bot's get no visible models, also the impulse command that should remove one bot at a time, remove all bots at once.
The server console give some error messages:
SZ_GetSpace: overflow (0+237 bytes of 0)
WARNING: backbuf [2] reliable overflow for (null)
SV_WriteMVDMessage: message overflowed
SZ_GetSpace: overflow (0+44 bytes of 0)
SV_WriteMVDMessage: message overflowed
SZ_GetSpace: overflow (0+233 bytes of 0)
WARNING: backbuf [2] reliable overflow for (null)
SV_WriteMVDMessage: message overflowed
I noticed that the linux version of FTEsv executes my config files 3x (but that also happens with 50xx version).
And with the windows version (x86 and x64), the console gets really slow, it's almost impossible to type commands in it!
In the client side, I get this message:
ezquake's implementation of pext_trans is buggy. dibabling.
I'm having a lot of trouble trying to run ftesv (windows or linux, x86 or x64) after version 50xx. I have no issues running my mod with FTE SVN 5066 or FTE SVN 4993, but when I try to run 55xx or above, I get all kinds of errors. The frikbotX bot's get no visible models, also the impulse command that should remove one bot at a time, remove all bots at once.
The server console give some error messages:
SZ_GetSpace: overflow (0+237 bytes of 0)
WARNING: backbuf [2] reliable overflow for (null)
SV_WriteMVDMessage: message overflowed
SZ_GetSpace: overflow (0+44 bytes of 0)
SV_WriteMVDMessage: message overflowed
SZ_GetSpace: overflow (0+233 bytes of 0)
WARNING: backbuf [2] reliable overflow for (null)
SV_WriteMVDMessage: message overflowed
I noticed that the linux version of FTEsv executes my config files 3x (but that also happens with 50xx version).
And with the windows version (x86 and x64), the console gets really slow, it's almost impossible to type commands in it!
In the client side, I get this message:
ezquake's implementation of pext_trans is buggy. dibabling.
https://tinyurl.com/qwbrasil - QuakeFiles
News