haha nice one....Quote:
Originally Posted by jcap
Printable View
haha nice one....Quote:
Originally Posted by jcap
no, pretty sure its impossible.Quote:
Originally Posted by supersniper
am I wrong?
Without reversing at least half the engine, no you are not.Quote:
Originally Posted by Heathen
Fix the fact that I get 33 ping on a FUCKING LAN NETWORK AT MY HOUSE.
Think you could find a fix for us nvidia users who have to disable decals or suffer huge framerate drops?
Move your mouse closer to the receiver, buy a short cable, replace the gold on your MoBo with silver and try to circumvent Einstein's first principle of General Relativity. :v:Quote:
Originally Posted by CN3089
EDIT: Con I could look into that.
Lol no. I get 2 to 3 ping in Unreal 2k4 and then like 33 to 60 in Halo.
It's some stupid shit with the netcode I'm sure.
Some of this stuff is easily done with OS. I guess I can just release a version with those basic fixes included.
Well, some of the game updates are tied (unless modified via delagginator or the like) at 30 (or higher) game ticks (or it may have been FPS). I wouldn't be surprised if it was either: A) lying and including this watered down packet update value in the real ping (3 + 30) or B) Actually causing the pings to take that long to respond due to the time things are suppose to be updated. Just educated guesses though.Quote:
Originally Posted by CN3089
I've dedicated far more (personal) time in lower level systems and tool development to really get too deep in the Network engineering field for grade A games. However, at least this game doesn't suffer from 'WTF'isms like that in MW2. Maybe we should instead figure out a way to get IW to properly design and implement an XBL matchmaking and party interface? That or just wait for Reach and whomever ports it with Halo 3.
http://www.bungie.net/Forums/posts.aspx?postID=35242876Quote:
Originally Posted by Dwood
mybad i was thinking about that.