Important Notice for Modders re future OB2.0 update

[Joel Billings]

For those of you that have modded scenarios, if you haven't already, you should lock your generic data files in your modded scenarios before you get the next update after 1.02.52. The changes due to the new OB file are huge and would require massive rework to your units in any scenario. There are also map changes that you will probably want to avoid as well in any scenario you've already built. You can selectively update some of the other generic data files in your scenarios if you want once you see the list of changes. The key is to lock your generic files in your modded scenarios before you get the next update. The release of the next public beta is still weeks away, but I wanted to start spreading the news now so you aren't caught by surprise.

[Joel Billings]

I'm just bumping this up as we're getting very close to the release of the next WitE2 update as a public beta, and it includes the OB 2.0 files. Matrix has the files, so unless something new and major comes up in the next few days, it will probably be out within the next week or so. Be sure to lock generic data in your modded scenarios before you update.

[Nazcatraz]

WIll the Steam beta comes out at the same time as the Matrix beta?

Once I start a campaign with the beta, will my OB2 save carry over when the official update releases? Like, if I start a 1941 campaign with the beta, I can just continue playing when the official update arrives with the new OB intact right? I ask this because you guys said that the OB2 update will only work when starting a new campaign with the new update. But since this update will have 2 phases (beta and official). Will It affect savegames at all?

Thank you for all your hard works!

[Joel Billings]

First, yes, the Steam beta will come out at the same time as the Matrix update. At this point they will likely be available by the end of this week. Second, whenever you start the game, it locks in all the data at that point. So you will have that data throughout your game. If we make changes to the data later on, you will not see those changes until you start a new game. If we change the code, usually bug fixes, than you will get the benefit of the code changes.

[Nazcatraz]

The beta could come out at the end of this week? No way! Let's gooo!

[Wild]

Excellent news!

[antwniago]

Will/can the database size for aircraft (1,023 rows) and AOGs (475 rows) be increased in the new version ?

[Joch1955]

great news, looking forward to it.

[Joel Billings]

Will/can the database size for aircraft (1,023 rows) and AOGs (475 rows) be increased in the new version ?

There are no plans to increase them. Are you running into limitations? What are you trying to add?

[antwniago]

Thanks for getting back to me, Obviously I have no idea whether it is a complex issue to increase them in size, an impact on the game or whether many people are after such a change but I just thought I would ask as it would be nice to have the space when modding to keep everything in one location and also both databases are small compared to the others.

Database Rows
Units 16383
Air Groups 4095
AOG 475
Locations 8191
Leaders 4095
TOE 4095
Ground E 4095
AIRCRAFT 1023
Device 2047
When adding in Bulgaria from 1941 and putting Finland, NCMD and NMD units on map the only AOGs usable are the gaps between the existing ones rather than having room to add in new AOGs

For a German invasion of Yugoslavia/Greece scenario the same issue (I try not to delete out existing things in case of issues and usually just set delay to 250)

Adding in the Yug/Gre and earlier model Ger/Ita aircraft leaving some space at the end of chasis for any possible future changes all remaining space has gone. Also have been looking at adding in Nor/Den aircraft as the game makers have already done with Bel/Gre/Neth/Pol.

[Joel Billings]

Pavel's first take on this is that it's not possible to expand the aircraft slots, but it might be possible to expand the AOG slots in the future.

[DarkHorse2]

Currently, I believe that WITE2 has a limit of 32 elements within a unit (and TOE_OB).

That has been a major source of distress for those working with TOE updates and enhancements.

Why not just expand it to 64? I don't see this being an issue on performance as those elements are stored in a continguous block of memory and are directly accessible and would have an access complexity of O(1).

Additionally, it would barely be noticable as far as increasing demands on system resources. I doubt players would be the wiser.

This would make a lot of people happy.

[Joel Billings]

I'm pretty sure this was discussed with Pavel and unfortunately was ruled out as not possible.