Enemy targets inside friendly territory
Closed this issue · 6 comments
BR Version: 0.0.310.04 (231005-061000) DCS Version: 2.8.8
Brief Description:
When generating a campaign in some missions targets are inside friendly territories or neutral territories, structures too
Expected:
I expect targets are only inside enemy territory
Mission and Template Zip:
Syria - Operation Unrelenting Clay.zip
See mission 2, 6, 8, 9, 10
Please also note this is generated from a custom situation, also included in the zip
Mission modified: N
Spawning logic is rather complex. Priority should be.
- Anywhere it will fit (objectives only)
- Not in No Spawn zones
- Relative to the front line (yes units can be behind enemy lines how far depends on the unit)
- Not in hostile border
Basically yes AI can spawn on the hostile side to represent recon or surrounded units. This most often happens in areas of relatively low spawn point density (a manual task) where the tool is forced to make do.
If you can share some screen shots that would help me look at any particularly nuts ones.
Sure, here few screens:
Understood but a whole surrounded enemy structure (or a tracking radar) in the deep of friendly territory is quite strange :)
Also happens enemies are placed outside the boundaries of the map, especially for planes but not exclusively.
Can be related to the "Static Situation" option?
Can you turn on the other map options to show the front line and units? I agree this looks rather wrong
Sure, here you are:
Static situation off, seventh mission out of ten, with the frontline seems have sense.
Is it intended to work so?
Hmm it is definitely placing objectives in the blue zone I'll look into it and see if there is a positioning bug
Ok I've found the cause and its specifically campaign missions affected. Basically between missions the objective center point is used as a hint for the next mission. This is so you don't fight in wildly different areas each time. This hint ignores borders to get most accuracy. I think it probably should not and you need SpawnAnywhere turned on for it to work.
Fix will be out in next beta