安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
I'm also happy to host Co-op multiplayer servers for the older games.
- While I am away don't set PagedPool over 328MB, or NonPagedPool over 176MB. These figures are 70% of the maximums for a ***32-bit Windows*** system, rounded (down) to the nearest 4MB "boundary".
- 192MB should be large enough in either case anyway.
- Windows x64 has a 128GB limit for each, and doesn't have the same sorts of problems, even when executing 32-bit applications.
I only just upgraded to Steam Client Beta, and I had to manually turn the Shift+Tab : Enable Steam Community in Game back on, so I am trying turning it off (and WinRAR has finished for now).
[Sometimes I think the 'bugs' come looking for me].
Some people call it CoD5, maybe because it is like CoD3 (for a console, but not).
You will probobly see some new maps come around sometime or rather, they havent made any anouncements about that yet.
https://support.steampowered.com/kb_article.php?ref=4166-TYSC-9690
See: http://en.wikipedia.org/wiki/Data_Execution_Prevention
Either set it to essential Windows programs & services only, or setup a DEP exclusion for (example path shown):
C:\Games\Valve Steam\steamapps\<steam username>\half-life blue shift\hl.exe
It may be related to having lots of RAM, then downgrading the RAM, it may be related to having had too many different video drivers installed (Omega, nVidia WHQL, nVidia Beta, LV2G, etc), and it may be related to nVidia cards that use TurboCache (part system memory, part VRAM).
The cause will be harder to find out than the solution (for once). Which I for one am not going to complain about.
However, I am running an AMD/ATI Radeon series card and have never experienced this problem for myself. Only time will tell for sure though, although Spoonfire seams quite happy with the fix.
I may publish a .reg file somewhere that fixes it. It is recommended to have 1 GB of RAM or more when applying this 'fix' though.
If I publish a .reg file, I shall also publish a .reg undo file (obviously enough).
incase you do not understand what i am talking about here is a small description "first you a playing "say" css you play for ten minuts then the game crashes to your desktop displaying "cmesh lockindexbuffer or somthing similer" you then say wtf call steam and they say its ur system if ur dumb u buy a new computer but if ur smart u ask about how you can solve this issue. first all you have to do is increase your pool memory or somthing i am hopeing Tabris 'Ice' McSars will post on this soon because it has worked a charm. and when he does look out!.
With the console enabled, enter this command:
mat_max_worldmesh_vertices
It especially applies to: Day of Defeat: Source, Portal, Episode Two or Team Fortress 2.
The default is most likely 65536, but lowering it to 1024 my assist in reducing your crashes significantly.
Of course there is always the -DXLEVEL 81 launch option too.