Does this happen with CS? I believe this is because TFC doesn't support the new VGUI2 style text printing interface and the old interface had a weird timing dependency on setting text colours. The change to the VGUI2 font printing (required for Asiatic languages and for higher screen resolutions) removed this timing requirement but may have made mods running with the old interface sensitive to incorrect colors.
We don't have a timetable for updating TFC of HLDM at this time, I will have a look if there is another solution. For other mods you should always call gEngfuncs.pfnDrawSetTextColor() before doing any engine string printing. - Alfred > -----Original Message----- > From: Digital Widget Support [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 18, 2003 8:12 AM > To: [EMAIL PROTECTED] > Subject: Strange behavior of Steam HUD say text? > > I've noticed some strange behavior of HUD say text under Steam/TFC. > Specifically, say text (ClientPrint, whether it be from > StatsMe, AdminMod, > C-D, etc) seems to be affected by the presence of other HUD > messages (like > an AM csay, or UTIL_ShowMessage). > > Say text will fade out in sync with existing HUD messages, > and then snap > back to the appropriate color once the HUD message disappears. This is > decidedly different from pre-Steam, where say text was not a > TTF and did not > react in any way other HUD elements. (In fact, the only way > to change the > say text color was with a client side con_color call). > > Below are screenshots identifying the problem. Anyone else > experiencing > this? Any way to get say text to stay stable? It's quite > disconcerting to > have text fade to gray while you're trying to read it. > > http://www.100acrebloodbath.com/misc/hud_problem.htm > > Thanks, > Buzz > > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
