On Sunday, 20. February 2011 02:51:01 Dominic Fandrey wrote: > > This was expected that some users will experience that problem. What is > > your operating system and distribution? And most importantly: what is > > your system Hz setting if there exists something like this? > > Operating system: FreeBSD 8-stable development branch
Interesting. I've had a FreeBSD user tell me there's no problem with the recent changes. Can you download http://thilo.tjps.eu/downloads/testsleep.c and compile it with gcc -o testsleep testsleep.c Then start the program with: ./testsleep 1 wait a few seconds, note the results, then again ./testsleep 1000 and note the results. > Hz: according to xrandr 60 I'm not talking about your monitor, I am talking about your system Hz setting, or kernel Hz. It should be at least 1000Hz, which will yield a 1ms precision. You can use com_busywait of course and this will be pretty much the old behaviour. But it means that your client will unnecessarily hog 100% of your CPU, even if your framerate hits com_maxfps. Note that this is how it was before for framerates > about 100fps; my new changes fix this. But they require a granularity for the timeout of the select() system call of at least 1ms. Most major OS, including Windows and MacOSX seem to fulfill this requirement, that's why I turned this on per default. > The system is built from 12 days old development sources. Not > particularly outdated: Indeed not. > Note that all that fancy new GEM, KMS and so forth mumbo jumbo is > not available on FreeBSD. So it might be that the video drivers are > somewhat dated, since the Xorg project has stopped caring about > portability. They do not play a role in this. -- Thilo Schulz
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
