Optimized .exe; builds of ioq3 engine
With GoogleTranslate, Bumpy, dmaHD, iKALiZER, Raw Mouse, Bug Fixes, ..
#981
Posted 03 August 2010 - 12:33 AM
"autodownloading was not initalized. /cl_curllib library is needed"
if i give the command /cl_cURLLib
it sais
"cl_curllib" is "libcurl.so.4" default "libcurl-3.dll"
i didnt change it, but changing it to the default works fine... hmm anyone tried to download a map with the build yet?
#982
Posted 03 August 2010 - 12:55 AM
--
It could probably use a more 'chaos'-friendly way, i.e. 'even if it doesn't find it, try the default ones'.
--
Ye. I think this can be done.
--
done. now cURL is more forgiving if its lib is not found, it will attempt the defaults before giving up (libcurl-3.dll and libcurl-4.dll on windows, libcurl.dylib on mac, libcurl.so.4 and libcurl.so.3 on other unix).
This post has been edited by mitsubishi: 03 August 2010 - 02:27 AM
- Optimized exe; builds of ioq3 engine for urt With GoogleTranslate, Bumpy, dmaHD, iKALiZER, Raw Mouse, Bug Fixes, ..
- Networking, lag meter, and gaming consistency guide
#984
Posted 04 August 2010 - 08:05 PM
Still trying to find what is causing my rendering problems. I have narrowed it down to urt minimizing, there
is about 5% chance of that corrupting any further 3D rendering (be it OpenGL or DX). At first I have
suspected faulty card or drivers, but after a week of testing, I found no problems. UrT is only program
that causes this problem, to fix it I have to reset GFX card HW (PC suspend to ram is enough).
Used old version of iourt exe without minimize/win key handling and it worked fine, so would like to
disable this feature in latest ioq3 as well to confirm it.
#985
Posted 04 August 2010 - 09:39 PM
--
See also /minimize. It explicitly minimizes without the alt-tab utility. It can be bound to keys.
This post has been edited by mitsubishi: 04 August 2010 - 09:42 PM
- Optimized exe; builds of ioq3 engine for urt With GoogleTranslate, Bumpy, dmaHD, iKALiZER, Raw Mouse, Bug Fixes, ..
- Networking, lag meter, and gaming consistency guide
#987
Posted 05 August 2010 - 05:49 AM
I have tried the latest 64bit/32bit/32bit vanilla versions, all have the same issue.
running win7 64bit, intel q6600 with an ATI 5850 (catalyst 10.4 >> the newer catalyst versions caused all kinds of graphical errors in urt, but 10.4 runs fine)
I've tried running as admin, compatibility mode, 32bit/16bit color. event viewer has no errors. Always just a black screen with no mouse cursor.
I've searched this thread and also at http://www.www0.org/...r_urt#Downloads but am not seeing others reporting this problem.
Any help would be greatly appreciated.
#988
Posted 06 August 2010 - 02:13 AM
Microsecond Definition support; it potentially increases efficiency of the engine and makes it possible to use any integer on com_maxfps; /sysMicroGranularity.
It's a rather experimental feature that might potentially do little to be usually noticeable. The theory is that better granularity of timing, microseconds instead of milliseconds, might increase efficiency of the engine. An interesting outcome is that currently it's used to throttle FPS with com_maxfps in finer granularity. As a byproduct, that makes it able to throttle on any integer since it's not restricted by 1000/integer anymore. It's also used scaled on milliseconds calculations though that was already what was being done for UNIX.
UNIX support of it is also in.
The var can be changed 'live'.
This post has been edited by mitsubishi: 06 August 2010 - 02:41 PM
- Optimized exe; builds of ioq3 engine for urt With GoogleTranslate, Bumpy, dmaHD, iKALiZER, Raw Mouse, Bug Fixes, ..
- Networking, lag meter, and gaming consistency guide
#989
Posted 06 August 2010 - 04:20 AM
#990
Posted 06 August 2010 - 06:25 AM
Quote
Now, when setting com_maxfps to presumably take advantage of the above information, keep in mind that FPS (visual and internal, same thing) is limited to values of 1000msec divided by an integer; this is because the engine measures frametimes using millisecond integers. So you can either set 125 FPS (1000/8), 111.11 (1000/9), 100, 90.9, 83.3, 76.9, 71.4, 66.6, 62.5, 58.82, etc. (without any rounding up.)
Quote
Notice that the ceiling of the var is being rounded up internally in an unintuitive fashion: com_maxfps 84 goes to 90.090.. while 83 stays to 83.333...
i.e. com_maxfps 84 gives effectively 30.30.. packets per second since it puts effective max fps to 90.91.. while the correct value would be 83 to get 41.666.. since that is the com_maxfps value that will give an effective max fps of 83.333 which we'd want for lowering networking latency with the cl_maxpackets ceiling available.
So with the microsecond support it would be possible to use 84fps without the rounding up on 42pps.
sysMicroGranularity 1 or 0 to test it, as mitsu said it works on the fly.
Quote
hopefully. :-)
Quote