From the store page:

Minimum Requirements
OS: Windows 10 64bit
Processor: Intel or AMD 3.0 Ghz+ with 4 cores (e.g. Intel Core i5-6600 or AMD Ryzen 3 2200G)
Memory: 16 GB RAM
Graphics: Discreet GPU with 4 GB (e.g. Nvidia GTX 1650 Super or AMD RX 5600 XT)
DirectX: Version 11
Storage: 30 GB available ...

Well 2 minutes after asking the question I hovered over this little icon on the store page...
Question is answered right there.

I'd like to purchase this game via Matrix Store (when it's available) because I thought I read somewhere that they get more of the cut than if I were to buy it on Steam.
I want to manage the game (installation, launching and updates) from Steam though. Do I get a "Steam Code" when purchased via ...

One of the youtubers playing the game this morning pulled up the online docs in game and it shows the url:
https://docs.waveops.io/mnw/

The range circles appear off because you have "Draw units at altitude" turned on in Game Options | Map Display. This option draws planes at varying altitudes with a line to the ground (with the length of the line increasing with altitude). So the plane icon is not drawn at ground level coordinates ...

As per the tool tip, this is the range at which the unit will fall back.

Knowing something is out there is a far cry from a fire control solution.

Much, MUCH, can be said about this topic. Here's an article I found that had some interesting thoughts on Detection and Localization issues of a modern Task Force:
http://www.navweaps.com/index_tech/tech-031.php#:~:text=The ...

Maybe a points penalization (like doubling or tripling the penalty) for units killed by friendly fired would be an easy way to keep it constrained?


It's already constrained. You just don't do it. A real life Fire Control team would never consider dropping arty when there is a chance they will ...

@MauriceB, you can also filter and color-code those log messages and drop the arrivals or any other message you don't need/want. Click on the yellow triangle in a log window to open the filter menus.

Yes, one of the first things i did. It does reset to All Tags when i start another scenario but ...

That's a design choice: If we were to generate all these messages, they would completely swamp the radio net (unrealistic) and the radio log (granted, we have added message filtering to the radio log). We do create a few messages for flavor, and initial contact, but not all.


I had to laugh out ...

Is there a reason I'm not seeing any enemy Unit spotted events (like Detect, Classify, Identify) in any logs? I see a lot of messages about spotting artillery landing on me. Of all the messages I want to see, this is the most important as units can disappear from the map as fast as they popped up ...

That pictures shows spottable. i.e who can see you. So it shows the the red unit to your SE can see you. Also notice the little dot below the "S" shows that you are spotted by an enemy.

Are the labels for the preset SOP's just that, a label? Or is there internal logic (code) that affects unit behaviour besides what we see on the SOP screen.

While we're at it: If I plot a movement with multiple waypoints, is there a "orders delay" at each waypoint or is it just as fast as a single ...

I was very confused by the "Stance only", maybe it should have been called "Use Stance" or "Based on Stance"

Hmmm, I reduced the font size and it helped. The pop up (with large fonts) was slamming against the side of the screen and covering the list of units.
With a smaller font i can navigate the list still:

I like all the info that the ui is presenting to the user most of the time, but this popup in the Spotlite (F10) window gets in the way a lot. As I click thru each unit on this screen to see where it is on the map the pop up more often than not gets in the way of my "navigating" down the list. I ...

yikes, that's an obscure setting.

I was trying to get intel on the enemy units and after about 10 minutes of looking thru the numerous screens I just assumed it wasn't in the game.

... With the fix in place, the strikers dropped the targets, did not pick them up again, and proceeded to RTB.

This may now mean that unless you got some damn good 24/7 coverage of your strike targets, the strike may not launch or engage at all.


Thanks Dimitris, That makes sense in this case ...

FIXED: #17056: Log spamming '... is dropping target from its target list'

I'm still getting a lot of log spamming in the latest beta. Attached in the zip file are a couple saves.

The first one (Escort Spam) generates a lot of messages like this one
[PRC] Shield #1 (J-20B Fagin) is dropping USS ...

FifthDomain wrote: Sat Nov 22, 2025 2:34 pm Are you using the public beta or base version on steam to start with.

I copied over steam release version (could never get the public beta on steam to work for me)