>Q4 have hitboxes, just like Q3 sorry, if I misunderstood you, but Q3 had no projectile hitboxes. look at g_missile.c: G_RunMissile and you will see, that the collision-detection is a trace, no hitbox. The G_RunMissile code uses the equivalent of Q3 "bounding boxes" in that it does a trac...

The question arises (again): why not stick to what worked before? The projectile hit detection in Q3 was perfect. Doom 3 is a different engine that does this (and many other things) differently than Q3 did. It's also somewhat tricky, because its not like anything with D3/Q4's proejctile collision i...

well I guess he is talking about something else.. this problem I think we are talking about has to do with the boundingboxes of the rockets. I tried making them smaller, and voillat: it worked. I guess he just misunderstood, like I did the first time. He says on the 2nd page of that thread that the...

Finally found SyncErrors post at ESR : The rocket hitting the wall when aiming 1 pixel away from it has nothing to do with the rockets hitbox. It has to do with the origin of the projectile. In D3 and Q4 it shoots from the players origin whereas in Q3 it shot from a distance just in front of the pl...

and I'm not sure if its worth the time (as I don't know if the majority really wants it). I'm sure the majority thinks it sucks that when they're hiding behind a wall and want to fire a rocket or nade, with the croshair a few pixels away from the wall, they shoot themselves in the face (or the nade...

4days wrote:

FragaGeddon wrote:So Raven made the game, does this mean that id is patching their crap?

the engine is id's, so i guess most of the crucial work on the patch would be theirs regardless of who made the assets.

No, wrong.

Kills don't get written to the console in my game - they only appear as little messages in the top right corner. Maybe you haven't checked the console for them - or maybe you're using a cvar/setting we don't know about? The code in idMultiplayerGame::ReceiveDeathMessage() calls Printf(), so it SHOU...

dynerman, settng logfile to 1 will write console output to a text file, sure, aber it will NOT contain the game action as it was in q3. Only messages about players connecting are logged. Look at my other thread in programming discussion for more information about this. This seems very odd - logfile...

To answer Fjoggen's (and other's) questions This stats dump is just a dump of extra end-game summary statistics kept (basically the end-game scoreboard stuff) - it's not a log of the gameplay action. Logging every item picked up to a file would be very intensive ont he server. This is different from...

Add-on paks is the way to do custom content like you describe. I'll look into the voting issue, but I'm not sure how much can be done with that since the whole point of add-on paks is not loading them until they're used.

Pure black isn't possible, check out ui_hitscanTint

Hitboxes are the only weapon hit detection used in MP. There's no finer collision resolution.

It's the rate the server sends out snapshots. The higher you set it, the more snapshots have to be constructed on the server, which means more CPU utilization. You'll also need more bandwidth to handle the extra traffic.

spookmineer wrote:What's the difference between a demo and a netdemo? Is there difference in filesize, what resembles Q3demo.dm68 the most?

Regular demos are render dumps of gameplay. Net demos just record user input and re-simulate the game based on that input.

The demo_scale cvar should control netDemo playback speed.