Optimized .exe; builds of ioq3 engine
With GoogleTranslate, Bumpy, dmaHD, iKALiZER, Raw Mouse, Bug Fixes, ..
#53
Posted 23 November 2009 - 03:33 AM
Well Cooked Nade Burgers, on 23 November 2009 - 02:09 AM, said:
Now that would be sexy
#54
Posted 23 November 2009 - 11:02 AM
edit: I tried to fix the code available for ikalizer but now it kicks on the ikalizer library which is closed source.
btw a very small update happened yesterday which I didn't mention ('cause it'd be very unimportant for most); the meter's 'dynamic arrays'(pointers) get refilled with memory less often so there should be some minuscule performance increase with them on for calling realloc() less often; remember of course if absolute best fps is needed it's best to turn off all 2d meters (such as these and lagometer) since if they are not shown they are mostly not calculated internally either; expect though small or no noticeable difference.
This post has been edited by mitsubishi: 23 November 2009 - 03:13 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
#55
Posted 24 November 2009 - 12:09 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
#57
Posted 24 November 2009 - 03:07 AM
After the mighty inclusion of cl_utradio now Stopwatch!
It's of milliseconds accuracy, details on its use are on the 1st post under its image.
At first I thought of using the "real" clock of the OS to set its timer - to avoid /timescale having an effect on it - but then I realized timescale having an effect on it is precisely why it should be set on q3 clock. It's more relevant to gameplay that way and it's still equivalent to real time on timescale 1 anyway.
This post has been edited by mitsubishi: 24 November 2009 - 03:36 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
#59
Posted 24 November 2009 - 07:31 AM
I found something that could help to solve one of the problems with all ioquake3 versions that are out at the moment(Iobumpy/iKALiZER/and your optimized version).
They come all with the old default size limitation
#define MAX_CMD_BUFFER 16384
but with the original UrT.exe we had
#define MAX_CMD_BUFFER 65536
my config is actually 64,0 KB (65.536 Bytes) I cuttet it down to 6kb and it startet working with your build.
here is a link with the old default 16kb you have to change it to the 64kb but look if there is a newer/better version.
This post has been edited by ObScUrE: 24 November 2009 - 07:35 AM
Quote
#60
Posted 24 November 2009 - 10:44 AM
ObScUrE, on 24 November 2009 - 07:31 AM, said:
I found something that could help to solve one of the problems with all ioquake3 versions that are out at the moment(Iobumpy/iKALiZER/and your optimized version).
They come all with the old default size limitation
#define MAX_CMD_BUFFER 16384
but with the original UrT.exe we had
#define MAX_CMD_BUFFER 65536
my config is actually 64,0 KB (65.536 Bytes) I cuttet it down to 6kb and it startet working with your build.
here is a link with the old default 16kb you have to change it to the 64kb but look if there is a newer/better version.
ok I changed it to 131072 (about 128KB); tell me if everything's fine with it.
(the filename(zip) is same so if you downloaded it recently, refresh browser's cache)
Well Cooked Nade Burgers, on 24 November 2009 - 07:26 AM, said:
good idea
This post has been edited by mitsubishi: 24 November 2009 - 11:11 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