Jump to content

Anti Tank Ditch


CharlieB

Recommended Posts

  • Members

Why not place dragon teeth, really. This is crazy.

Heck, you could also use some of those concrete "Bremer walls". If you use half height, defenders can still shoot over them. Abusing emplacements for this is bad for the frame rate, bad for future compatibility of such scenarios, etc.

 

I understand that there is a need for excavated obstacles, and you'll get them, once that the new terrain engine has been successfully implemented. Once that it is there we'll start working on dynamic terrain, and that would include the ability to dig trenches of any size.

Link to comment
Share on other sites

5 minutes ago, CharlieB said:

good point.  the Maps are now embedded into the scenario are they not?

 

Yes, but it will mean the scenario file is bigger than a purely Mission Editor based implementation.

 

This will be more evident in the new terrain model - at least as its currently planned to be implemented.

Link to comment
Share on other sites

26 minutes ago, CharlieB said:

Nuc?

 

Well unless its a massive fortification (West Wall, etc.) then the amount of engineering effort would limit the length of the obstacle belt.

 

So you should be able to go around - of course that might be the intent of the obstacle though. :) 

 

Edited by Gibsonm
Typo
Link to comment
Share on other sites

  • Members
18 minutes ago, Gibsonm said:

it will mean the scenario file is bigger than a purely Mission Editor based implementation.

 

This will be more evident in the new terrain model - at least as its currently planned to be implemented.

 

a) currently, it's not. A "wadi" terrain type is only that, a tile like water, except that no water surface is rendered (and that vehicle engines don't stall by driving into them. As each terrain map is ALWAYS embedded in the scenario, this doesn't make a scenario larger.

 

b) Wadis will be discontinued in future versions. We'll still support them when importing legacy scenarios and legacy maps of course, but the option to mark a terrain type as a wadi will be replaced by a functionality to simply dig them into the terrain profile. Functionally they are then identical to any other trench, except a different cross-section profile, of course. For the moment however they would be a quite legitimate way to visualize an anti- tank trench.

 

What you lose however is the ability for the exercising students to set the trench during the planning stage. Rather, the mission designer needs to create a scenario based on a copy of the intended map (in anticipation of the students later setting the location of the obstacle); then adjust the terrain map according to where the students indicate that they want to have the AT ditch; then perform a map refresh on the scenario, and finally distributing/publishing the scenario file for the exercise. So, you lose a bit of flexibility

 

c) The new terrain model will be implemented in a way to retain this flexibility in map adjustment for scenarios by introducing "delta maps"; maps will be organized in folders, "map packages", which contain the immutable base map ("immutable" as in you'd need to save it as a different base map before you can make major changes to it), and files that describe just the modifications to the original map; in addition there would be other files that belong to the map data preprocessing (computationally/memory intensive operations that are stored, so that they need not be done every time that you load a map - like navmesh generation).

You could have several different of these delta maps in a single map package (but no deltas of deltas; that would quickly become a recursive nightmare). The scenario would then specify WHICH delta map were to be applied to the base map; if the local copy of the map package doesn't contain the required delta map, the host could then pass on just the missing delta map to the client. That way the amount of data transfer can be minimized.

Link to comment
Share on other sites

On 10/20/2016 at 8:47 AM, Ssnake said:

I understand that there is a need for excavated obstacles, and you'll get them, once that the new terrain engine has been successfully implemented. Once that it is there we'll start working on dynamic terrain, and that would include the ability to dig trenches of any size.

Sweet, spider holes, trenches and improved positions for the foot mobiles will be an awesome addition.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...