Bug #12407

Building placement in warfare restricted in Beta 72197+

Added by Trauma about 5 years ago. Updated about 4 years ago.

Status:Expired Start date:07/28/2010
Priority:Normal Due date:04/01/2011
Assignee:Trauma % Done:

0%

Category:Warfare
Target version:-
Affected ArmA II version:1.55.75445 First affected build:
Reproduced by another DH user:Yes First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

As of beta patch 72197 I have been much more restricted in where I can place buildings as commander in both standard Mountain warfare and Warfare BE (preferred).

I have tested this in OA on both warfare types with non-beta, beta 72197 & beta 72291.

It seems to not like inclines, buildings/factories/walls & shrubs. Obviously this is an issue on a map that consists of just that. Leaves you with little other than to build in open and mostly flat areas and spread out more than before, also fortifications can not be built near enough to buildings. Makes the bases bland, easy to find & defeat and limits the amount of areas you can build a base in.

I'm going to hazard a guess that this has something to do with the fix for dieing while driving down hills (much needed and awesome fix), if this is the case then that fix is more important imo.

T08_Base_Construction_Training.utes.7z (66.2 kB) kju, 07/28/2010 09:32


Related issues

related to ARMA2 Community Issue Tracker - Bug #7564: Construction Interface (COIN) vs. Trees Assigned 12/30/2009 12/01/2011

History

Updated by kju about 5 years ago

I assume it is more related to scripting or related changes.

Can you please test the a2 building tutorial and make a few screenshots.

Updated by Trauma about 5 years ago

I tried that construction tutorial on Utes but I found it to be very restrictive with out beta given that it start you on a hill top, I was able to build by the water, but was unable to build near the building at the runway as it was too far from start point.

I made some bases in Warfare BE 2.062 to show difference.

  • Non-Beta

http://img408.imageshack.us/img408/3333/nonbeta1.jpg

  • Beta. Could not build in the small squares and had to be central in the large squares for the others, MG nests needed more distance, sand bags around AA need more space.

http://img830.imageshack.us/img830/6480/beta1.jpg

  • Non-Beta 2

http://img203.imageshack.us/img203/2387/nonbeta2.jpg

  • Beta 2 - Was unable to build in most of the open areas and had to build factories on the roads. Could not get anything at all in the small areas.

http://img801.imageshack.us/img801/4115/beta2.jpg

Everything just needs more room that it should and used to, pretty annoying tbh.

Updated by BigDawgKS about 5 years ago

Trauma wrote:

I tried that construction tutorial on Utes but I found it to be very restrictive with out beta given that it start you on a hill top, I was able to build by the water, but was unable to build near the building at the runway as it was too far from start point.

I made some bases in Warfare BE 2.062 to show difference.

You should probably limit your testing to only BIS warfare/construction module.
Using 3rd party missions may not provide the same results.

Updated by Fireball about 5 years ago

I think this ticket should be moved to the Warfare BE project, unless you are able to replicate this with the BIS Warfare.

Updated by Trauma about 5 years ago

I have reproduced it on normal warfare as I said, the area that you are limited to in the training mission is too restrictive, when i ran into the airfield area I was too far from the set build zone.

I don't think this is a Warfare BE issue as BE uses the BIS build system and simply turning off the beta patch and building in the same version and places in Warfare BE clearly show the difference.

Updated by Fireball about 5 years ago

  • Due date changed from 08/14/2010 to 10/14/2010
  • Status changed from Feedback to Assigned
  • Assignee set to Dwarden

Cheers, just making sure.

Updated by Trauma about 5 years ago

I grabbed some quick screens on CTI Mountain Warfare on Takistan, I was unable to build a full base as I could not set supply to start high like I can in Warfare BE. I ran a persistent server and dropped in with and with out beta running, no mods of course.

Updated by kju almost 5 years ago

  • Affected ArmA II version set to 1.54.72888

Updated by kju over 4 years ago

  • Due date changed from 10/14/2010 to 02/01/2011
  • Affected ArmA II version changed from 1.54.72888 to 1.55.75445
  • Difficulty set to Not set
  • Reproduced by another DH user changed from No to Yes

Updated by kju over 4 years ago

  • Due date changed from 02/01/2011 to 04/01/2011
  • Status changed from Assigned to Feedback
  • CPU deleted (E8400)

Anyone feels like trying to tweak the script by himself?

coin_interface.sqf in \ca\modules\CoIn\data\scripts from:
  • arma2\common\modules.pbo
  • or arma2\addons\modules.pbo

Put the mission in your mission and overwrite this variable
with your path (in an addon or a mission):

BIS_WF_CoinFunction = Compile PreprocessFile "ca\modules\coin\data\scripts\coin_interface.sqf" 

Unfortunately both coin.sqf (\ca\modules\CoIn\data\scripts)
and Client_Construction.sqf (\ca\warfare2\Scripts\Client) use
a hardcoded path to the file.

In any case in the said file this code determines whether
an object may get placed or not:

//--- No Place To Build
_isFlat = (position _preview) isflatempty [
    (sizeof typeof _preview) / 2,    //--- Minimal distance from another object
    0,                //--- If 0, just check position. If >0, select new one
    0.7,                //--- Max gradient
    (sizeof typeof _preview),    //--- Gradient area
    0,                //--- 0 for restricted water, 2 for required water,
    false,                //--- True if some water can be in 25m radius
    _preview            //--- Ignored object
];

I assume Max gradient, Gradient area or
Minimal distance from another object cause the issue.

Updated by Fireball over 4 years ago

It's fixed in current versions of Warfare BE at least.

Updated by kju over 4 years ago

Cool - maybe someone can ask Benny what he did or check the source?
Maybe he modified the script himself already. :)

Updated by Fireball over 4 years ago

I think he doesn't use the Warfare module, so potentially no BIS code involved there.

Updated by zGuba about 4 years ago

  • Status changed from Feedback to Expired
  • Assignee changed from Dwarden to Trauma
  • I am using deleted (CO (A2+OA))

Also available in: Atom PDF