Unable to spawn any VC and NVA infantry red groups in SOG Prarie Fire, using this command:
BG100 = [getPos EDEF, side BG1, (BG100 = [getPos EDEF, side BG1, (configfile >> "CfgGroups" >> "East" >> "VN_VC" >> "vn_o_group_men_vc" >> "vn_o_group_men_vc_01"),[],[],[],[],[],180] call BIS_fnc_spawnGroup;
Aircraft won't spawn as well.
I make my own single player scenarios and I use the above command extensively to distribute newly spawned red units.
EDEF is a simple object placed on the map by hand. BG1 is a red commander present on the terrain, also placed by hand.
See command above. The reference to the group (configfile >> "CfgGroups" >> "East" >> "VN_VC" >> "vn_o_group_men_vc" >> "vn_o_group_men_vc_01) comes directly from config viewer.
(Also, there are no entries in the editor for many corresponding viet nam ground groups which appear in config viewer.)
Disregard. Found the cong entries in the editor.
Still won't spawn.
I have found the issue. Using BIS_fnc_spawnGroup it creates an error on line 160 when using this command with the configfile entry. The issue is the fact that the config entry is different on the unit placement positions for the SOG groups. See below for OPF_F:
configfile >> "CfgGroups" >> "East" >> "OPF_F" >> "Infantry" >> "OIA_InfSentry" >> "Unit1"
position[] = {5,-2,0};Then for the an SOG group:
configfile >> "CfgGroups" >> "East" >> "VN_VC" >> "vn_o_group_men_vc" >> "vn_o_group_men_vc_01" >> "unit_1"
position[] = {0,"(-1*5)",0};As you can see the position in the SOG groups config files uses a string within the position. I am not sure why this is different. Either way I recon the configs need to be altered, or the BIS_fnc_spawnGroup needs to change to compile format that line of code. The code on line 160 of the BIS_fnc_spawnGroup is as follows:
_itemPos = [(_pos select 0) + (_relPos select 0), (_pos select 1) + (_relPos select 1)];
to fix it change that line of code to:
_itemPos = call compile format ["[(_pos select 0) + (_relPos select 0), (_pos select 1) + %1]", (_relPos select 1)];
That worked for me when I compiled my own version of that function with those changes. and it still works for all other config enteries for BIS vanilla groups.
@badanov - just create your own function for now, that will allow you to keep playing until it is fixed.
Hope this is of use.
Hope this is of use.
It's not. I use the above standard on minimum 15 single player scenarios on a wide variety of terrains. It makes zero sense to me to compile in a change that would affect the other 15 in unpredictable ways.
I wait for the fix.
If you make the change as I said and call your own function, just copy the BIS function and change that line, when the fix comes, it is just a case of find and replace the function name within your scripts. Just do it for the one mission. It doesn't affect the function in any other way, other than to make it compatible for the config entries for PF and also still works as normal for the vanilla units. I don't see how this cannot help?
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Hello,
We've picked up your issue and the fix has been implemented in the last S.O.G. update. Thanks for helping us making the game better!
In the unfortunate event that (part of) the issue persists, please open a new ticket and include a link to this one.
Best Regards,
Bob Murphy