![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#4 | |
Warfaresims
Join Date: Nov 2002
Posts: 299
Downloads: 2
Uploads: 0
|
![]() Quote:
The only area of H2/3's model actually affected by weather is sonar. (And sonar modelling had so many problems that the inclusion of weather was small consolation). Effect on visual sensors - none (not even day & night difference!!!). Effect of e.g. rain on IR sensors - none. Clouds hiding aircraft - nope. Clouds & fog blocking LGBs - nope. Weather & sea state affecting ships: none. Nothing. Nada. In contrast: Command actually models these things. Visibility varies not simply by day and night but by actual time of day (different ranges at e.g. dawn, noon & dusk). Rain drastically reduces visual, IR and laser sensors depending on its intensity. Clouds can block both visual/IR sensor and things like LGB illumination. Even some radar frequency ranges are affected by rain. Rain and increased sea state can also mess up sonar surface ducting and CZ propagation (it does not affect deep-to-deep sonar detections, as in RL). Furthermore, heavy sea state drastically affects the accuracy of gunfire and other unguided weapons on ships - the smaller the ship, the more severe the effect. And more. In addition: in H2/3 the scenario author has no control at all over weather. Let's say you want to make a Falklands scenario, with appropriately dark pissy weather, and the wonderful weather engine decides it's warm and sunny in the area - tough luck, you can't do anything (not that it would matter much, considering that only sonar is affected by the weather) . Command OTOH lets you fully customize the weather properties to suit your area of interest _and_ also change them later on the course of the scenario via easy and powerful scripting. And what's more, these properties _actually matter_. Which is why many scen authors use them. Advantage: COMMAND ![]() |
|
![]() |
![]() |
|
|