安装 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(越南语)
Українська(乌克兰语)
报告翻译问题



Otherwise you should really be asking in the Steamworks discussion not here, but generally you can pass environment variable directly into your exe when you compile.
I downloaded the 4.22 updated SSL files and put them in my build but it didn't work.
My project is blueprint only.
"but generally you can pass environment variable directly into your exe when you compile."
Can you tell me how pls? Apologies for wrong board.
You should really ask here
In short you have to write the code to handle each launch parameter you want your game to handle. It won't just happen auto-magically. And in this case you'd have to write additional code to take your value and run it against the windows command prompt.
And it might just be easier to detect if the user is running a 10th gen CPU and just run the command in an if statement to side step the user having to fiddle with launch parameters that maybe don't need to be launch parameters.
"it might just be easier to detect if the user is running a 10th gen CPU and just run the command in an if statement to side step the user having to fiddle with launch parameters that maybe don't need to be launch parameters."