Include Hardware Acceleration
#1
Posted 08 August 2012 - 01:24 AM
27 was so gracious to develop something with such capabilities for Urban Terror and even more so when he provided the source: http://www.mydevstuf...e_Bumpy_v7a.rar I think it would help alleviate alot of the complaints the community and you (developers) face due to FPS issues.
#2
Posted 08 August 2012 - 03:41 AM
try the diRf client still lacks VBO but is faster then the Old ass ioquake version they are using https://github.com/urtdevs/diRf_client
I do have my personal build for 4.2 but its old code as well
This post has been edited by attackxie: 10 August 2012 - 07:20 AM
#7
Posted 10 August 2012 - 04:45 AM
Barbatos, on 08 August 2012 - 01:49 PM, said:
If you take out the optional auth, 4.2 demo and server side demo, there's barely any changes vs. 4.1.1. I noticed a few cvars, rambetter's drdos fix (which ioquake3 handled differently upstream anyway), increased limits to match the custom 4.1.1 clients, a few new server commands and some branding changes from ioUrT -> Quake3-UrT. Could you put out a release based on the latest ioquake3 so it fixes the other problems and add auth and server side demo back in a future release?
When you say moving to iobumpy, can you build the modular renderer so we can pick between bumpy and the standard renderer at runtime? If I run into a problem, I'd like to be able to set a cvar rather than recompiling it.
This post has been edited by undead: 10 August 2012 - 04:48 AM
#8
Posted 10 August 2012 - 07:20 AM
Frankie V, on 10 August 2012 - 03:34 AM, said:
I piss on the cornflakes of the deserving if you don't like them don't eat them
don't you have some animations to fix ... err I mean not that there is anything wrong with players flailing about like there string puppets ...
This post has been edited by attackxie: 10 August 2012 - 07:23 AM
#9
Posted 10 August 2012 - 07:24 AM
undead, on 10 August 2012 - 04:45 AM, said:
When you say moving to iobumpy, can you build the modular renderer so we can pick between bumpy and the standard renderer at runtime? If I run into a problem, I'd like to be able to set a cvar rather than recompiling it.
r_simpleshaders 0;r_glsl 0; r_vbo 0 should effectively revert
This post has been edited by attackxie: 10 August 2012 - 07:24 AM