Wolfenswan

In some vehicles, such as the newly added Huron or the Ghosthawk, the crew has access to a GPS and map when in specific slots, even if they don't have either in their inventory. This includes the "fire from vehicle" turrets, no matter if they are disabled or not. Is there a way to disable this feature?

Possible 1.44 bug Hi all, 1.44 seems to have changed something about the way parameters are initialized. This is def. breaking backpack assignment and might affect other things as well. We don't know if this is a deliberate change by BI or a bug. Until either them or we provide a fix you can enforce a backpack loadout, as described here. Edit: You can also execute this code from a small server-side addon's config.cpp to force f_param_backpacks to 1 and get backpacks to appear properly: class Extended_PreInit_EventHandlers { class FA_preInit { serverinit = "f_param_backpacks = 1; publicVariable 'f_param_backpacks';" }; }; The addon only needs to be run on the server and requires CBA.

Careless does help but is undesirable, as it'll always enable the AI's light and enforce other unwanted behavior.

Since the latest update (possibly including 0.9.21) I've noticed AI controlled transport helicopters being very timid, breaking off any attempt to land if they are engaged by a lone infantry. Before that (and with vanilla AI) I could get them to land reliably even under fire by disabling their "Target"/"Autotarget" AI and setting allowFleeing to 0. Any idea what could have caused this?

You can call the function to initiate spectator directly: [player,player,true,true,true] call f_fnc_camInit; That would force-activate the spectator camera even if the player is still alive. Attach it to e.g. a flagpost as an action and players should be able to activate spectator script on their own whim. What do you mean by paratroopers? Paradrops for players can be enabled by using the mapClickTeleport component and setting the height variable to a value of over 0. We're currently thinking of whether we should start to pre-implement some AI functionalities but that's not decided yet. If we do, we might also consider AI paratroopers.

Depends on what you need. F3 provides the Framework for MP adversarials and coops but doesn't include any scripts to spawn AI. In init.sqf just add f_param_caching = 800; (for example) before [40] spawn f_fnc_cInit; Can you clarify what you mean? ACRE1 or ACRE2?

I think this is an issue with TFAR and how it handles spectators. I know that what you described works fine in ACRE2. It should be possible by force open the dialog/display. Unfortunately displays are a bit of a pain so we'll delay this one. But what does work (awkward though) iirc. is as ZEUS remote controlling a unit and opening the briefing there.

Does beside the BIKI entry any documentation for this exist? I'm mostly interested if priority is ascending or descending (direct has priority 0 for example) and what sound3D does (not mentioned on the BIKI and only set for direct). Also, which affect these values (if any) have on VON.

Yes and no, but as I couldn't reproduce it within a few tries I can't say for sure if it might have happened before without me noticing.

I saw AI heading to cover and starting to "twitch" very rapidly from left to right, changing their doWatch. It's quite possible that it's caused by vanilla behavior but just wanted to mention it here, in case other's see this behavior to with 0.9.20. It look a bit like the "stuck AI" bug seen in the 1.43 dev branch but afaik that one has been fixed.

Server and myself were running the latest official CBA release RC4, not the dev version of RC6 currently available. If Zriel says they're not seeing those errors pop up, I'll assume it's caused by the older CBA version and will make the switch asap. But why are the functions called for AI not local to the player?

Seeing more errors now, again on dedicated server but as a normal client: Both client and server are running the same version. The errors do not appear in the server's RPM.

Getting the following error in 0.9.19 on 1.42 stable. I have not seen this error in 1.42 RC using 0.9.19: Appears only when creating units as ZEUS on a dedicated server.

Given that the AGM team has merged with the ACE3 team I'd say it's safe to assume that we'll aim to support ACE3 eventually. But that all depends on the first release and how desirable it'll be to switch to ACE3 in it's early state.

Not sure what you mean, we don't add anything directly. But by default F3 enables the debug console for logged-in admins, which also enables the init window when editing units as ZEUS.

Which vehicle currently allow turned out position turrets? I noticed it doesn't work with the T-100 for example.

No objection to either of you. Maybe we'll get the barrel changing in the Assistant Gunner DLC ;)

Different perspective: for myself I appreciate the addition of a unique and powerful MMG which sets the dedicated MMG attachment apart from the ARs in the fire team. I'm not sure how to resolve this, wouldn't mind a reduction of the burst RPM but I wouldn't want to see it removed completely either.

For the number crunchers, here's a dump of the 1.42RC config (excluding vehicles) as a google spreadsheet.

Since 1.40 we've been noticing a significant effect on sFPS from spectator. This will be fixed in the next release of F3 (within days of 1.42 should everything go to plan) but for now we can offer this simple hotfix: Updating sqf (preferable method) In f/spect/f_camInit.sqf Modify line 41: _newUnit enableSimulationGlobal false; Debug console (on-the fly method) Once there's a signifcant drop of sFPS, execute {_x enableSimulationGlobal false} forEach (allMissionObjects "VirtualCurator_F") in the debug console, server-side.

Care to elaborate why?

I've written a small server-side addon/script to add bipods for players in older missions which use a gear assignment script (removing attachments without considering bipods). I won't have time to test it extensively in MP before the eight of April, but if people here are running MP in dev and want to try it, I'd appreciate it. The easiest way would be to simply run this code (without the //comments) from debug console (server exec) after a mission has started. The code only checks for the unit class or F3 assign gear type, not the weapon itself. I could add the latter too but if it's really necessary.

This ticket (Legacy 7.62x51 ammo does not work in Zafir) has been assigned for a while but nothing came of it as of yet. Would be good to know if the fix will make it into 1.42 as otherwise I'd start writing a workaround addon.

But isn't that kinda the point, that AI mount statics to replace a dead gunner? :P

Noticed in latest ASR_AI3: - AI mount vehicle turrets even if the vehicle is locked - AI mount vehicle turrets even if their ammo is empty I assume line 6 in fnc_getInWeapons needs to be: _weapons = [getposATL _leader, vehicles, 100, {_x emptypositions "Gunner" > 0 && (locked _x != 2) && (ammo _x > 0) && !(_x isKindOf "Plane")}] call FUNC(getNearest);