Sander van Rossen🇺🇦 on Nostr: Trying to run steamcmd through System.Diagnostics.Process in Unity, to run ...
Trying to run steamcmd through
System.Diagnostics.Process in Unity, to run app_info_print to get the latest buildid.
steamcmd runs that command asynchronously .. so if you run a script and call quit after "app_info_print", you won't get any data. There doesn't seem to be a way to wait for the data before calling quit.
But System.Diagnostics.Process in the dotNet version used in Unity 2022.3 seems completely broken?
Published at
2024-09-03 12:40:42Event JSON
{
"id": "a37c23ed27b05c09b73c657c7262996cb965617dfbb7071cfeb58fc7a99df00d",
"pubkey": "e062fbe72ae69ccb16a631db7dcba2221e17a897b835743d7f1c0ccd7a2ef223",
"created_at": 1725367242,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.gamedev.place/@logicalerror/113073667587046370",
"web"
],
[
"proxy",
"https://mastodon.gamedev.place/users/logicalerror/statuses/113073667587046370",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.gamedev.place/users/logicalerror/statuses/113073667587046370",
"pink.momostr"
],
[
"-"
]
],
"content": "Trying to run steamcmd through \nSystem.Diagnostics.Process in Unity, to run app_info_print to get the latest buildid.\n\nsteamcmd runs that command asynchronously .. so if you run a script and call quit after \"app_info_print\", you won't get any data. There doesn't seem to be a way to wait for the data before calling quit.\n\nBut System.Diagnostics.Process in the dotNet version used in Unity 2022.3 seems completely broken?",
"sig": "bb78d40ea2fa4352823b44aca9c92fcc6d3b2cb773623b3de221e0bdd7f347e22e520e556084b6ec75d470dfd40a5d5998f17a9a3be7ec3d04d1e6dc80b77e03"
}