It ♥♥♥♥♥♥♥ worked ♥♥♥♥♥♥♥♥♥ thank you

You beautiful, beautiful bastard. It worked! Thank you so much!

♥♥♥♥♥♥♥♥♥! that's actually it!

日本人プレイヤー向けに日本語も記載しておきます。

### 忙しい人向け要約
Windowsの時刻を正確な時間に同期したら直りました。

### 経緯
私の環境での症状としては、

- Air Baseには普通に入れる
- マッチングも完了する
- 機体選択もできる
- その後、実際のフィールドへ移動するタイミングで `ST3100001`
- 回線をスマホのテザリングに変更しても改善しない

という状態でした。

最初はサーバーやNAT、ルーター周りを疑っていたのですが、通信をパケットキャプチャして調べたところ、実戦用と思われるサーバーへの接続自体は正常に成立していましたため、「サーバーに接続できなくてタイムアウトしている」という単純なネットワーク障害ではありませんでした。

そこでパケット内の認証情報に含まれる時刻と、PC側のパケット記録時刻を比較すると、約2分強のズレがありました。
確認には管理者権限で起動したpowershellで以下のコマンドを利用しました。

```powershell
w32tm /stripchart /computer:time.windows.com /samples:10 /dataonly
```

自分の環境では、以下のような出力で実際の時間より2分ほど遅れていたことがわかりました。
```text
+136.358s
```

ACE COMBAT 8ではマッチ参加時にセッション用の認証情報やトークンを使っているようで、その中には発行時刻や有効期限に関係する情報があるようで、通信を確認した限りでは以下のような流れになっていると推測されます。

```text
Air Base
↓
マッチング
↓
機体選択
↓
実戦サーバーへ接続
↓
認証 / セッション情報を送信
↓
時刻の整合性を含むセッション検証
↓
失敗
↓
ST3100001
```

要するに、ゲーム側やサーバー側でパケットや認証トークンの検証が行われていて、PCの時刻が大きくズレていると、認証情報が「未来に発行されたもの」などとして扱われ、実戦セッションへの参加に失敗する可能性があります。
よって自分の場合はWindowsの時刻を正しい時刻に修正したところ、**その直後から普通にマッチへ入れるようになり、ST3100001も出なくなりました。**

### 具体的な解決手順

管理者権限のPowerShellで、

```powershell
w32tm /stripchart /computer:time.windows.com /samples:10 /dataonly
```

を実行してください。

正常なら、だいたい

```text
+0.01s
-0.02s
+0.03s
```

のように0秒付近になります。

数十秒、数分単位でズレている場合は要注意です。

### 一時的に原因確認だけしたい場合

たとえば先ほどの確認で、

```text
+136.358s
```

などの非常に大きい時刻ずれが表示された場合は、管理者PowerShellで一時的に、

```powershell
Set-Date -Date ((Get-Date).AddSeconds(136.358))
```

のように時刻を補正できます。

その後もう一度、

```powershell
w32tm /stripchart /computer:time.windows.com /samples:5 /dataonly
```

を実行し、ほぼ0秒になったことを確認します。

その状態でSteamとACE COMBAT 8を再起動してマッチへ参加してみてください。

自分の環境では、これだけで **ST3100001が解消して普通に出撃できるようになりました。**

ただしこれは一時的な修正なので、Windows Timeサービスが壊れている場合は後から正常に時刻同期できるよう修復した方がいいです。


同じ症状の人の参考になれば幸いです。

Might be a bit stupid, but where do I go to type this stuff in?

Originally posted by Frost D-44:

Might be a bit stupid, but where do I go to type this stuff in?

There are two ways you can do it.

Easy way — Windows Settings

1. Press Windows key + I to open Settings.
2. Go to Time & language → Date & time.
3. Make sure Set time automatically is turned On.
4. Make sure your Time zone is correct.
5. Scroll down and click Sync now under “Additional settings”.

After that, restart Steam and ACE COMBAT 8 and try joining a match again.

PowerShell way

If you want to check the clock difference or Windows refuses to sync:

1. Press Windows key + X.
2. Select Terminal (Admin).
3. Click Yes when Windows asks for administrator permission.

On most Windows 11 PCs this opens PowerShell automatically.

Then paste this and press Enter:

w32tm /stripchart /computer:time.windows.com /samples:10 /dataonly

This checks how far your PC clock is from the real network time.

Something close to this is fine:

+0.01s
-0.02s
+0.03s

Mine was showing around:

+136.358s

so my PC was more than 2 minutes behind, which was enough to cause ST3100001.

You can also try forcing Windows to synchronize:

w32tm /resync /force

If it says that the Windows Time service isn’t running, use:

Set-Service -Name W32Time -StartupType Manual
Start-Service W32Time

and then try:

w32tm /resync /force

again.

Another quick way to open an administrator PowerShell is:

Press Windows key → type PowerShell → press Ctrl + Shift + Enter

Then click Yes.

Once the clock is synchronized, completely close Steam and ACE COMBAT 8, reopen them, and try the match again.

In my case, correcting the Windows clock immediately fixed ST3100001.

Absolute legend. Thanks, mate!

Originally posted by GoryoDog:

Originally posted by Frost D-44:

Might be a bit stupid, but where do I go to type this stuff in?

There are two ways you can do it.

Easy way — Windows Settings

1. Press Windows key + I to open Settings.
2. Go to Time & language → Date & time.
3. Make sure Set time automatically is turned On.
4. Make sure your Time zone is correct.
5. Scroll down and click Sync now under “Additional settings”.

After that, restart Steam and ACE COMBAT 8 and try joining a match again.

PowerShell way

If you want to check the clock difference or Windows refuses to sync:

1. Press Windows key + X.
2. Select Terminal (Admin).
3. Click Yes when Windows asks for administrator permission.

On most Windows 11 PCs this opens PowerShell automatically.

Then paste this and press Enter:

w32tm /stripchart /computer:time.windows.com /samples:10 /dataonly

This checks how far your PC clock is from the real network time.

Something close to this is fine:

+0.01s
-0.02s
+0.03s

Mine was showing around:

+136.358s

so my PC was more than 2 minutes behind, which was enough to cause ST3100001.

You can also try forcing Windows to synchronize:

w32tm /resync /force

If it says that the Windows Time service isn’t running, use:

Set-Service -Name W32Time -StartupType Manual
Start-Service W32Time

and then try:

w32tm /resync /force

again.

Another quick way to open an administrator PowerShell is:

Press Windows key → type PowerShell → press Ctrl + Shift + Enter

Then click Yes.

Once the clock is synchronized, completely close Steam and ACE COMBAT 8, reopen them, and try the match again.

In my case, correcting the Windows clock immediately fixed ST3100001.

You can also right-click the clock at the bottom right > Adjust date and time > 'Sync now' under 'Sync your clock'

Thanks for adding that.

Thanks for the info! I had also figured while i was in powershell that i might as well use the following commands also to look for messed up windows sturffs and attempt an automatic fix to those issues as well (both can be used at the same time)....

sfc /scannow
dism /online /cleanup-image /restorehealth

too late already got banned for a day

Doesnt work, keep having error code ST-3200001 right at launch with it telling me it's optimizing shaders

Originally posted by Kenny:

Doesnt work, keep having error code ST-3200001 right at launch with it telling me it's optimizing shaders

its for ST-3100001, not ST-3200001

Originally posted by GoryoDog:

Originally posted by Kenny:

Doesnt work, keep having error code ST-3200001 right at launch with it telling me it's optimizing shaders

its for ST-3100001, not ST-3200001

still should of worked xD i can't find anywhere on how to fix it it's really annoying after waiting so long for a legendary title again to have this kind of launch quality almost discareful

Originally posted by Kenny:

Doesnt work, keep having error code ST-3200001 right at launch with it telling me it's optimizing shaders

Are you playing on Linux? This particular error seems to be related to it and unless the devs work on a patch to specifically enable Linux support, we're SOL.
I'll wait for any development across the week and if something changes for the real launch of the game, if nothing happens I'll have to setup a Windows dual boot....