banimod / etpro / ettv forums

Any of the ETPro/ETTV developers care to comment, please?

Yeah, what arni said (although cl_allowdownload is the client-side cvar controlling downloads). Setting sv_allowDownload to "0" will disable all types of download, both in-band and http/ftp.

Topic says it all, really. Does this security vulnerability (CVE-2006-2082) occur in ETTV beta 9 as well? If so, any timeline for fixing it and releasing an update?

Thanks.

smaching succes... every match they were reset 10 times :s <My jet-lagged, overreacted rant deleted, realizing that it's not worth the effort> What actually happened was this: on Thursday and Friday we were running ETTV beta3 on both the game servers and the external hubs and slaves. This provided ...

sv_cheats shouldnt default to 1 on a slave 8) I hate to contradict happy bani, but... ./ettv.x86 +set net_ip x.x.x.x +set net_port 27960 +set com_watchdog 0 +set fs_homepath ~/et27960 +set fs_game etpro +tv connect sea.gamecloud.com&#58;27970 **** **** ... bla bla bla ... status map&#58; sw...

The buffers are okay: I'm getting no NET_SendPacket ERRORs. And as I said in my first post: the jitter happens even with just one viewer connected and CPU load is low (<15%). As to your broadcast comments: I have no idea what you're talking about. Why would I want to broadcast the Nations Cup using ...

Ahhh. Yes, you're right; I just checked. On the other hand, sv_cheats appears to default to 1 on an ETTV broadcast slave, so a viewer could just enter \r_drawfoliage 0 to remove the grass (just checked this as well and it worked). That is, if the admin didn't explicitly set sv_cheats to 0 on the ETT...

Different.

It would make for different game play.

Different is not necessarily better.

As far as I can tell, the slave servers act as mere pass-throughs of the settings that are in effect on the master. Hence, the local config of the slave has no effect on cvar enforcement.

That comment is not stupid, it is false. Anyhow, the jitter occurs irrespective of the latency between the client and the broadcast server, because it is also evident when running a broadcast server on my local PC which is connected to our hub. It might very well be dependent on the total latency be...

We've been running ETTV beta 3 for QuakeCon over the past week, and on the whole, it is performing very well. However, the viewers are experiencing some very noticeable jitter when connected to a broadcast server. Instead of seeing smooth movement and effects, everything kinda lurches ahead, intersp...

Thanks for the heads-up. Two of these jokers were indeed on the QuakeCon tourney servers, so I got their IAC outputs. Hopefully these will be useful to bani and crew. Note that ET Pro anticheat did not mark them as cheaters, nor were they kicked by PB. PB screenshots turned up as "application n...

gotenks wrote:my vote is the other way... b_ for server b_cl for client, because then they don't need a massive .cfg change

I'd say make it "b_" for server and "bc_" for client, simply because I hate cvars_with_multiple_underscores.

The exact cause of this problem is rather complex and will take a long post to describe (which I will do when I've got the time). The short version is: under certain circumstances (that is the long story), the PB GUID Auth server will tell the ET server you're connecting to that it has not received ...

As for QuakeCon: we'll probably just run with what we've got at that point in time. Any suggestions would be more than welcome! First try and grab infos from them about casting. They don't seem to be much interested by a nice worldwide broadcast :( Well, "they" is me in this case, and I c...