oldy41

I keep getting these errors, too. Nearly every mission, I believe it is triggered by first contact.

Yes, it tends to become a bit tedious when assaulting a village with more than a few houses, having to wait while your squadmates clear them one after the other. A move or regroup command should override that behavior. ("Come on everybody, now stop pillaging those empty houses and let's all go back to work. It's not like there is anything expensive inside, anyway... not even any furniture...")

@nkenny Great work! I just replayed some of my own very simple sandbox-missions, clearing towns against a few AI teams. The experience was completely new and so much richer, since your mod really adds a new dimension to the game: Before I started to realize I better REALLY should watch those windows opfor AI had already mopped up my whole team. From positions inside buildings, which the AI had decided to man completely on its own, without any modifications to the mission code. 👍👏

Absolutely impressive! 👍

And keep in mind: " If you hurry it ain't a hobby!"

Maybe you missed that post 😉 I think it sheds some light on the problem with static animations.

@snkman: I think I found another subtle little glitch: - I set up an opfor camp for indulging myself sneaking in on unsuspecting enemies. - One of the groups in the camp is made to sit down on the ground using BIS_fnc_ambientAnimCombat. In particular: { [_x, "SIT_LOW"] call BIS_fnc_ambientAnimCombat} forEach units grp_1 => As soon as that group begins to chill on the ground, their comrades in the other opfor groups seem to get upset about their lazy behavior and come running from all sides with weapons ready. They barely refrain from killing their sitting fellows, but keep running around the sitting group for a while, not knowing what to do :). And, worst of all, they are alarmed now before registering a single real enemy. I believe this is caused by some specifics of BIS_fnc_ambientAnimCombat: This function always seems to spawn some blufor entities for displaying the animation, while hiding the original units. TCL opfor AI then probably registers those spawned blue entities (whatever they are) as threats. Maybe you can add a check in your code to prevent such entities from being registered as blufor units? This is really not high prio, but it keeps breaking my little mission. I tried working around it for a while, but to no avail. Many thanks A.

This may very well be a problem related to how the RHS vehicles are configed. And of course I totally understand if you do not want to spend time investigating sophisticated issues with 3rd party mods, but this might still be interesting: One of the classes affected is rhsgref_BRDM2_HQ_msv. It is a variant of the BRDM2 wheeled APC, which RHS chooses to categorize as an MRAP. It has no 'real' turret, but an open hatch with an MG. The unit is stand-alone with no waypoints. As soon as the action gets near (idk what exactly is the trigger) the complete crew disembarks and engages by foot.

I noted the same for some APCs from RHS: It was some Russian APC manned (per default) with a driver and a machine gunner. (I will try to look up its class later.) Both driver and gunner immediately abandon their vehicle as soon as the mission starts. Maybe something is broken in the TCL code for deciding, whether a vehicle is damaged or the like?

@tpw: Being one of those not in favour of player suppression allow me to urgently suggest not to forget a switch for that new feature 🙂

The problem is I shredded the scenario configuration, which would show the effect while fiddling around and trying to simplify it 😖 I'll try to rebuild it.

I repeated my tests, and could nail it down a bit more, but it looks like the conditions leading to the effect I described are more complex. So I think you can ignore that problem, as it should not be too prominent in missions. Just for the records: The effect I described seems to be related both - the presence of the Opfor AI infantry watching group. - and the setup of the surroundings (i.e. positioning of view blocks) (???) Both removing the watching infantry group as well as rearranging the view blocks did remove the effect. (I am a bit confused here, cause I cannot imagine how the removal of some view blocks, which are never blocking LOS for any of the involved units can play a role here, but that may just be a trick of the engine...) So, now I am just going off to have fun with the mod! 😀

@snkman: I have just tested the new version and must say: It is impressive! 👏 🤗 The most immersive firefights ever, and without the superhumanly exact knowledge of AI about yout position. This really feels 'real' now! However (how I hate to be a nag) I think there is still a small bug in your routine for decreasing AI knowledge about the player (and sorry for the lengthy description): I used my "counter-APC" test setup mentioned earlier as a testbed: - An Opfor AI APC without fuel behind a huge viewblock between the player and the APC. - The whole APC and its turret initially facing away from the player. - An Opfor AI infantry group to the other side of the player of initially 6 units. => The APC turret does NOT rotate towards the player, even after the player is seen by the Opfor infantry. (Fine!) => After engaging the AI infantry and reducing their strength to 3 still no visible reaction form the APC. (Fine with me, though the shots would probably have been heard IRL.) Player then sneaking to a side of the view block to gain LOS of the APC. Player then putting a few rifle shots at the APC. => The APC reacts. Its turret turns towards the player. (Fine!) Player now rushes behind view block again. => APC turret is still watching the position where it had last seen the player. (Great!!!) Player now moves to the other end of the view block to sneak the APC from its other side. => APC still watching the first LOS. (Great!) Player now shooting at the APC again with the rifle. Now something funny happens: => The APC quickly reacts, but its turret rotates towards the new player position for about a second only, then rotates back to its previous position watching the outdated LOS. This behavior is repeated several times. The APC cannot manage to complete turret rotation to face the current player position, but is always forced to rotate back again. I suspect the routine for decreasing the knowledge about the initial player sighting might still be active, and interferring with the new threat? Renewing the outdated knowledge or renewing the "watch direction" command or something like that every few seconds? But let me emphasize again, that the new version is still fantastic! Many thanks for all the efforts you are investing in this mod!

@pognivet: If this was meant as an encouragement to the mod team it probably failed utterly 🙄 Personally I enjoy this mod very much, and I prefer high quality content over a huge number of low resolution assets. So @FoW team: Take your time, but please keep supporting this wonderful mod!

@snkman: That sounds good. Do we need a new version for this setting to work? And could you please explain the new parameter a bit? (Like how it is converted to seconds till AI oblivion or the like?) Many thanks!