Erik,

I am very glad to see that you not only appreciate the effort those of
us that have reported bugs put in, but that you plan to do this with
SDKs as well. It can only help you really, and obviously it is :)

I noticed something about a release of the new UI soon (this week?). I
would say that's a bad idea, there are many more bugs to be worked out.
Not to mention almost every "fix" is pregnant with insects, that you
should give us a chance to ID and for you to abort them before they harm
the general population ;-)

-Smurf

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Erik Johnson
Sent: Tue 11 October 2005 18:18
To: [email protected]
Subject: RE: [hlcoders] Steam UI Update

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
This is something we're definitely thinking about given the success of
the UI beta.

We're going to try this out with the upcoming SDK release as
well, which
is a week or two off.

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Benjamin
Davison
Sent: Tuesday, October 11, 2005 8:54 AM
To: [email protected]
Subject: Re: [hlcoders] Steam UI Update



--
[ Picked text/plain from multipart/alternative ]
I think this has been a resounding success, valve probably would not
have
found all these bugs before releasing the update.

Now this got me thinking, what if this optional command was
extended to
the
actual engine? It would certainly help valve to prevent another patch
like
the 9/30 patch.

Say for example, there is a normal 'source engine.gcf' which we would
launch
normally and there would be a 'source engine beta.gcf' which we would
launch
our mods and valve games on the launch properties like -betaengine.

This would help us the MOD community test for breaking
changes and if we
started having problems that valve couldnt produce with their Q&A
process.

What do you guys think?



_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders

Reply via email to