Storm of War: Battle over Britain...

[He111]

Originally Posted by KG26_Alpha

Hmm

The mods need to sticky this with an appropriate title for those who need the information without having to read all of Olegs interview.

Doug: Some people in the flight sim community are concerned about the future and well-being of Storm of War: Battle of Britain claiming it has been in development much longer than they expected, so there must be something wrong. Can you put their mind at ease and say that Storm of War: Battle of Britain's future is bright, and there is not a reason to be concerned for the project?

Oleg: First, a reminder that IL-2 Sturmovik was in development for over 4 years before it was released. Then many years of modifications and adding new features in add-ons followed. Without the right engine design to allow modifications in the beginning of the IL-2 project, we would never have seen the IL-2 series come to life. But keep in mind IL-2 Sturmovik was only one title.

The Storm of War series engine and the first product, Storm of War: Battle of Britain is many times more complex than the engine in the IL-2 series. Also, the content itself is in some cases a hundred times more complex than in the IL-2 series. And that is not all. We have added new features into the Storm of War series engine that will give Storm of War a long, long life. Maybe even longer than the IL-2 series engine. We are building for the "next level" of quality and features. This takes much more time in development than it takes for one product title. Another benefit of having the Storm of War series engine — we will have 1-1.5 years production time for each follow-up title. Future titles from the Storm of War series will see the market with much less time in development compared to the initial release of the Storm of War series engine and the first series title, Storm of War: Battle of Britain.

I wonder if they're having memory issues with SOW, as most PC's only have a 32 bit OS and can only address about 3G memory. Empire totol war had this issue and they needed to rewrite their EXE to address 64 data space. i'm no guru but apparently it extends addressable memory to 3.5G.

Of course having a 64 OS solves this issue.

h