Map Boundary Extension Thread - WIC: Modern Warfare Mod for World in Conflict

Hiya All/Blahdy,

I have been ghosting in and out of WiC for a while now, but I have this lingering urge to try figure out how to extend the map bounds of World in Conflict.
I recall asking a long time ago whether this was possible but was told that it wasn't known how to do, is this something that could be investigated through python scripting and forcing it, or would it be locked away in some .dll? I am not too sure how to begin looking into this, even just to satisfy my own curiosity.

Any and all information about this would be appreciated.
Thanks,
A.

Haha I also wonder if there is a solution to this problem. I forgot why I haven't been trying before, I kept running into issues with this error on the modkit installation.

I have my install on another hardrive called "D:\Games\WiC" (This should probably be a separate thread...)

Hi,

Question #2 first:

Is your installation of WiC also registered in your Windows Registry? I believe the mod kit installer tries to find where your WiC is installed by checking the registry, and if it can't find it, you'll get that error. A clean installation of WiC should fix this problem.

Question #1:

Map boundary is an interesting topic indeed. We've been doing some research into how this works and so far we know the following:

• Each mesh tile size is fixed at around ~1500m by ~1500m approximately, though some maps are slightly different by a few numbers? (odd).. Pathfinding cannot occur outside of center mesh. This is also the maximum functional playfield.
• Smaller maps (i.e. vanilla do_Seaside, do_Riviera, etc) use smaller playfield to limit the size of the map, but all maps use statically fixed 1500 by 1500 mesh.
• Surround meshes of 8 tiles (also 1500 by 1500) are used surrounding the center mesh.
• The game could technically address playfield coordinates bigger than 1500, however unit pathfinding would not work outside of center mesh for XZ coordinates.
• During an experiment, a FLINT-based ballistic missile was fired at X and Z coordinates up to ~5,000 meters successfully (more than 3 times the range of typical wic map), however inconsistency of ground elevation on surround mesh often times may cause game crash upon landing. Also, units cannot path find in surround mesh, so only static units and FLINT missiles could operate in these distances.
• Y axis for air units does not require pathfinding, therefore can accept larger numbers. It is perfectly acceptable for FLINT missiles to fly up to extremely high altitudes, though maximum tested altitude so far is 250km height.

So, supposedly playfield mesh size could be hacked by a patch to increase it from 1500 by 1500, but the effects (stability and memory wise) is quite unknown. Lot of values in WiC are hardcoded everywhere, so changing the 1500 number could have some interesting consequences and effects, and whether existing maps would even continue to work is another question that is yet to be addressed. The big issue here is that every mesh has statically set size, so enough difference in mesh dimensions between maps may cause an exception.

I think increasing of map size is something that is technically possible, however, for purposes of WiC MW and Massgate.org modifications, we have not found sufficient benefit vs. cost ratio to spend the time researching this further. There are also meta-game considerations as well, for example, match time lengths may also need to be significantly increased to accommodate the extra playfield.

Edited by: blahdy

Heya Blahdy,

In regards to problem one it seems to not fix itself with a clean installation, is there a way to manually add a registry entry? I am using the GOG version which is probably causing some issue.

Fixed that, but cannot make an account.

Edited by: flames09

Reach out to tenerifs or better yet, go to Reddit.com and post a thread. This appears to be a Massgate database error and someone should be able to help you there.