Bug #5494

Not all terrain settings are usable as defaults

Added by sbsmac almost 6 years ago. Updated almost 6 years ago.

Status:Closed Start date:10/27/2009
Priority:Normal Due date:
Assignee:- % Done:


Target version:3.00


KadinX 20805
  1. -dlgs.h
  2. If the default value in //Terrain is replaced with any of the other values listed with a decimal setting, it does not show up when the parameters are displayed at the start of the mission. Only the 50 and 25 show up correctly. There is a good chance that the actual setting is correct in mission. But I need further evaluation this.


Updated by sbsmac almost 6 years ago

It's a limitation of ArmA2 that decimal (float) values can't be used as defaults in lobby dialogs. An alternative woudl to to try and create some 'pseudo-values'. Need to look at this...

Updated by KadinX almost 6 years ago

Since the reason for PvP scripting existance is to allow the mission designer to control most parameters from the ctfConfig.sqf and not really searching in the ctf subfolder, I think you should leave this issue alone. Call it off, for now anyway. :)

Updated by sbsmac almost 6 years ago

  • Status changed from Feedback to Closed

Will probably come out in the wash for Issue #5498

Closing this in meantime

Also available in: Atom PDF