World in conflict soviet assault crash to desktop series#

World in conflict soviet assault crash to desktop series#

Let's review the gun flash visibility across all night scenarios, all /cygdrive/c/Documents and Settings/Robert/My Documents/Games/Matrix Games/CS/devel/Campaign Series scn files, where is the gun flash visibility set? Nowhere! Beginning with 2.02, for now, we have assigned a standard gun flash visibility of 6 hexes. It may vary, as the scenario designer specifies. In 2.0* and later scenarios, night visibility is no longer fixed at 1 (or 2, if the Variable Visibility optional rule is in effect). For newer 2.0* scenarios, Dynamic Visibility is specified as, for example: That is for older, legacy pre 2.0* legacy scenarios. Gun flash visibility (also for illuminated hexes, with wrecks in them) differs scenario by scenario, according to the designer's specifications, as set in the. Standard night visibility is 1 hex, or occasionally 2, if the Variable Visibility optional rule is in effect.

(The 6 & 8 indicate each side's star shell count.) The red line, first number, indicates that this is a night scenario. The blue line, the fourth line, is where you see the (gun flash) visibility. scn /cygdrive/f/Games/Matrix Games/John Tiller's Campaign Series 2.01 SUPPORT/Rising Sun Look for Visibility as the last number in the fourth line of the. So too 'Visibility 17' in the Hex Info Box. In Rising Sun 1.04, if you launch the Tenaru.scn, the Scenario Briefing dialog indicates 'Visibility Night (17)'. The 'Visibility' window of Scenario display (Hot Key I) also states if Night rules are in effect and the maximum visibility that a gun flash can be seen. You will see where Night Visibility is 1 (unless Variable Visibility).Ī set-piece scenario that takes place at night will be so noted in the introduction to that battle, just prior to the recommended side (example: 'Tenaru, 7km ESE of Lunga Point, Guadalcanal: NIGHT '). The more we looked, the more issues we saw. In a perverse sort of way, I'm kind of happy to discover the 2.01 night visibility bug, because it forced us to look more closely at night scenarios. That so many of us all overlooked the night visibility bug for so long - I think that demonstrates my second point. The great majority of East Front and West Front were developed before Rising Sun's release. Why, compared to EF & WF, are there so many night scenarios in RS? It's because night scenarios were introduced to the series with the release of Rising Sun. Out of 102 stock RS scenarios, 17 are night scenarios - a considerably higher percentage than for EF or WF. Out of 222 stock WF scenarios, just 15 are night scenarios. Out of 206 stock EF scenarios, only 16 are night scenarios. The rules for night scenarios are rather obscure. I think I understand better why that may be so:

I was dismayed by the bug, but equally dismayed (astonished even) that nobody - not I, not the Dev Team, not even the great mass of players - observed or reported the bug since February's 2.00 release (and for me and the Dev Team, even earlier). Please look elsewhere for details.)įirst reported at The Blitz, the night visibility bug(s) in effect lifted the usual 1-hex night visibility restriction and had night visibility functioning as if it were daytime. (In the 2.02 Update, there are several data fixes, and much new content. In the 2.02 Update, the only EXE changes are these:įor new scenarios, the default, hard-coded GFV (gun flash visibility) is now 6. No, we need to focus on new game development now. For various reasons, we are being conservative with the JTCS changes, fixing what really needs fixing, but holding back on the non-essentials and/or the stuff with the potential to break things, hence requiring lots of testing. You might know that, soon, we will be releasing a JTCS 2.02 bug-fix update.