We have an update ready!
This fix could solve issues for anyone who is currently unable to run MilOps, or should communicate why your system is not supported.
For people that have no issue we recommend to stay on the "standard" distribution branch. This fix will not improve performance or do anything beyond what is stated below.
To enable the fix, make sure to activate the "Beta update branch":
- In your Steam-client, right-click on "Military Operations: Benchmark" in your library
- Select "properties" at the bottom of the popup menu
- Select the "BETAS" tab in the dialog that opens
- Select "beta - Beta" from the list-box
- Force an update by exiting the client and restarting it. In the MilOps "Credits" on the main menu screen, the version should now say: 20.3.1
This fix contains:
- A solution for many users that have a system that should be able to run MilOps but suffered from the "Shutting down" issue
- Early detection of unsupported systems so the reason for an early shutdown is shown.
- A driver version check. When your driver is too old, the user is requested to perform an update of the system's graphics driver.
- Detection of systems that can run MilOps but have an unsupported GPU activated (modern laptops are prone to this issue)
- Several other resolved OpenCL related issues
Other tips to prevent/resolve problems:
- Windows 10 keeps your graphics drivers up-to-date, but never installs OpenCL. Make sure to do a manual driver update.
- Make absolutely sure you don't have the Intel Integrated graphics enabled. It is not supported!
- If you know your system should be able to run MilOps, but keeps complaining about an unsupported system, post a help request on the support forum.
- The support page on our website contains more detailed information on how to update drivers and resolve issues.