I agree, i fired up the old 1.6 the other day and i had forgotten about the
old download status bar.
Would be nice to get this back!

On Fri, Aug 8, 2008 at 8:13 AM, Cc2iscooL <[EMAIL PROTECTED]> wrote:

> Alright, I know this is only for the select few of us who run custom
> maps on our source servers, but I'd like to see a better download bar
> for the Source2 engine.
>
> What does this mean?
>
> Remember back in the old 1.6 engine, when each file had it's own
> download bar, and you could actually tell (sort of) the filesize that
> you were downloading? Why can't we do that with the Source2 engine? It'd
> be nice if the download bar would tell you what you're downloading as
> well as displaying the size and the download status, instead of this
> silly one-bar-for-all-files-plus-extraction kinda thing that's going on
> now. If you're a server administrator and compress files on your
> webserver to .bz2, your clients see a download bar that goes halfway. If
> there's a large map (TF2 maps are getting larger and larger) we see
> clients leaving just due to the halved download bar, because the first
> half shows the overall file download progress (oh, and it doesn't care
> what the filesizes are of any custom files, so if you have two or more,
> good luck) and the second half shows the extraction and load process.
>
> So my question is...why can't we have anything to better inform the
> clients of what they're downloading and exactly how big it is? It would
> be very useful to us as server operators, I'd think, but correct me if
> I'm wrong.
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
>



-- 
--------
Chillidog Systems - Re-inventing the wheel for the sake of all humanity!
--------
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to