TECHNICAL SUPPORT / WEB APPs BUGS

I have recieved since today 22-5-2013.

I literally have 6GB of log files containing the same message.

client000.log => client200.log
log000.log => log303.log

2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.
2013/05/22 04:17:45 WRN 293283712 <Unknown> misc.cpp 852 setVect : setVect: cannot compute the vector, keep the old one.

Any clues?

I removed write access to the directory to reject ryzom from writing as temp solution.

Just noticed I have a bunch of client.log with exactly the same content:

2013/07/12 15:56:56 WRN 13d8 client_ryzom_rd.exe misc.cpp 855 setVect : setVect: cannot compute the vector, keep the old one.

Thankfully it's only client000.log thru client020.log, 105mb in 2 days. I'd still like to understand what's with this error.

The amount of logged errors seems to be at least 10 per each tenth of a second. My logs started at 16:11 and ended at 01:45 when I logged off.