Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
(You can search the CS:GO directory with the keyword "access" and you'll be able to find the files. Note that depending on how many times you've unsuccessfully launched the tools, there may be several files that you may need to delete. Moreover to launch the tools you must search the CS:GO directory for csgocfg (which will have the CS2 game logo and will be an application) and then run it)
Upon inspecting the minidump, I find that in my case the engine is trying to query my Vulkan gfx chip and not getting a full response, then fails to set DXLevel to 120 - Vulkan claims it supports DXLevel 111, so it silent-crashes even though this system in fact has DX 12 installed.
Regular SFM balks at this Intel chip as well (unsupported video card error) as it thinks it cannot support even DX9, though this same HP15 in the AMD flavor works flawlessly (Vega 3 chip).
Interestingly, none of this is an issue if I install on a virtual machine!! The VM supplies a generic "chip" which DOES properly report the physical host's capabilities, and SFM works as it should!
So, it works on a computer it thinks it can't work on, as long as it thinks it's not working on that computer.
Brillant, Valve!!
This is what csgocfg.exe is launching the game with:
"E:\SteamLibrary\steamapps\common\Counter-Strike Global Offensive\game\bin\win64\cs2.exe" -addon s2fm -tools -steam -retail -gpuraytracing
Notice that last switch. It apparently wants to force "RTX ON" on a chip that has no raytracing. It also seems you can add switches to the command line via library settings, but you can't edit the actual command line itself.
So, I opened a command prompt in the game folder, and executed the line as it appears... CRASH as expected. Ran it again without the -gpuraytracing switch, and VOILA! It runs perfectly.
So, like OP runs the exe directly, I'm doing it with a launch shortcut so that it actually gets all the other switches properly (they're basically important housekeeping).
If someone knows how (where) to permanently edit that commandline, it would be hella sweet, so the play button works right and Steam tracks your time in-game correctly.
Hope this is helpful.
Thanks for the detailed info, seeing what was causing it explains why low end pc's can't run it.
How did you do this? I'm right in the middle of an edit and all of the sudden my Source Filmaker won't launch through workshop tools :(