Steve 161st

Yep - we're seeing the same thing - sometime giant trenches while they are still in the process of being dug

Brilliant idea and functionality! Apologies for asking this and not trying it and finding out (not at my PC at the moment) but do the empty magazines keep the same 'mass' as full magazines? (As far as I'm aware, a magazine of a certain class always has the same 'mass' in ARMA regardless of how many rounds are in the magazine.) Given ARMA's inventory system is supposed to be a hybrid of weight and size, it's hard to know exactly what the 'right' thing to do is here, but the fact it links so heavily to the stamina system, makes it seem fairer if it would be possible to lower the 'mass' of the empty magazines...

Awesome work. Thank you so much for bringing this to the A3 community

Love this as a mod! As a suggestion for future improvements, do you think it would be possible to be able to bind some hotkeys to the pace count bead interactions to save having to navigate through the ACE menu?

Has anyone else noticed a return of the invincible AI with the last update to the medical system? One thing we noticed with the new medical system was AI could be hit in the limbs with entire mag dumps and would rarely die or even lose consciousness. We tweaked away at settings until we found something that seemed much more balanced/realistic. However, since the last update, our tweaked settings no longer work if the hit limb is either arm. We can now mag dump 7.62x51 at point blank range into AI's arms putting them in severe pain with fractures and multiple serious injuries but they never lose consciousness unless they struggle to bandage themselves up before bleeding out. (Wounds to legs still behave as expected) What makes this particularly problematic is that many weapon stances mean a lot of the target's torso is covered from the front by either the weapon or the left arm. Given the AI seems to have no reaction to getting injured (no flinching etc.) unless it dies or loses consciousness, this can result in 'terminator' like AI as their weapon deflects or front arm soaks up huge amounts of incoming fire to the torso and the AI is still able to fire back, it seems, as accurately as normal. Having spent quite a long time tweaking the new medical system to get a balance our group likes, this seems to be a large step backwards so I was interested to see if others have experience similar issues? One interesting thing that suggests this might be a bug is that in the ACE3 Virtual Arsenal, arm wounds no longer show up on the AI. (I.e. an arm never changes colour to yellow/red etc. unlike other body parts.)

I think JD Wang makes a good point there. Have a read of the CF_BAI thread as that specifically attempts to deal with the AI spotting and reactions, especially at greater ranges. From what I remember of the discussion, AI in the vanilla game have surprisingly short spotting distances when not in the alert state (300m ish). The distance from which they can spot you is also binary - i.e. 1m over the threshold and they will never spot you, 1m closer and the maths to spot you works normally. We too, run Lambs and CF_BAI and find this a good combination. They can also be combined with VCOM but you might find you need more tweaking of parameters to get the balance you want when running all 3.

@Blutze Thanks for your reply. I should have followed up to say that we discovered what the error was regarding this behaviour. It was one of my unit's custom scripts that was destroying the 'fired' event handler off which the initial bullet's trajectory is determined using ACE3 scopes. So entirely our fault and certainly no issues with ACE3!

OK - apologies..... the error statements are not linked to breaking ACE3 scopes. That was part of our own code that happened to run at very similar times to the CF_BAI events. The errors do stop us from running the detect module though (which is a shame as the concept of it is awesome) due to hideous spamming of the server .rpt file.

Has anyone else had issues with ACE3 Scope adjustments stopping working part the way into a mission? It seems to revert back to Vanilla scope adjustment despite force turret adjustment being set to on. So always starts working but something mid mission seems to revert it back to Vanilla. To clarify, the tumblers still 'animate' showing adjustments but the weapon always seems to be zeroed to a very short distance - which seems to be the vanilla zero distance. I.e. the ACE3 scope settings have no effect at all..

One thing we've noticed in multi player (and I suspect is also there in single player) is an error which I suspect is relating to the AI spotting. Here's an extract from the .rpt log: 18:55:21 [CF_BAI] (detect) LOG: Vision tests: [[0,0,"aiFacing"]] 18:55:21 [CF_BAI] (detect) LOG: Original probability 0 adjust probability 0 18:55:21 Error in expression <x select 0; _probability = _probability * _testProb; } forEach _visionTests; pr> 18:55:21 Error position: <* _testProb; } forEach _visionTests; pr> 18:55:21 Error *: Type String, expected Number,Not a Number 18:55:21 File x\CF_BAI\addons\detect\fnc_determineKnowsAbout.sqf..., line 10 18:55:21 [CF_BAI] (detect) LOG: Vision tests: [[0.062381,0.062381,"distance"],[0.223383,0.223383,"aiFacing"],[1,1,"raycast"],[0.5,1,"stance"],[0.5,1,"playerMovement"],[1,1,"playerFoliage"],["CF_BAI_detect_aivision_safe_chance",1,"awareness"],[0.75,0.75,"bino"],[0.5,0.5,"optics"],[0.25,0.25,"nightVision"],[0.44,1,"spotTime"],[0.5,0.5,"dayNight"],[1,1,"rain"],[1,1,"fog"]] Over the course of the evening, the server log gets quite large with repeats of this error. One other really nasty side effect (other than the large .rpt file,) is that once this error has occurred ACE3 Scopes no longer has any effect. So although the sight barrels still adjust in clicks, the scope always behaves as if it has zero elevation and windage adjustment. We turned the Detection module off on our server this evening and have not had a repeat of the ACE3 Scopes breaking so are fairly convinced this error somehow causes it. Actually, the only way to stop this error is to remove CF-BAI completely. Disabling the detection module did not fix it. I will do more testing to see if it is conflicting with other mods or whether just ACE3, CBA and CF_BAI result in this error

I think you'll find there's a new setting with advanced bandages that allow you to decide whether wounds re-open. By default, it's set to 'no' so there's no need to stitch a wound that can't re-open. Have a look through all the settings - you'll find what you want.

We're talking about limping coming back on a fully bandaged, fully stitched, fully splinted player. So the effect is almost like the splints falling off when using ADV-Splint. However, with that system, you could re-split the wound where as if this what is happening under ACE, the option to re-splint does not exist. (Fully aware of the limping on open wound setting - big fan of all the new ACE medical system settings!) That said, it could be interesting trying 'limping on open wound' being turned off to see if the bug only occurs when it's enabled.

We've seen this a fair few times now. Most of the occurrences seem to be after splinting and stitching the wound when the patient is fairly heavily wounded in other body parts as well. Often when the player takes more damage after the splint&stitch, the ''walking wounded' effect is removed, returning the player to normal, so we're fairly sure it's a bug but haven't repeatably re-produced it yet.

Agree with the above. Default settings were not to our group's liking but it's SOOO customisable, we're starting to home in on something we really like. The only thing we have seen a lot of is AI not reacting to being shot - if the shots that hit them are not instantly fatal/cause unconsciousness, they are able to continue to shoot what seems to be fairly accurately while taking several rounds. (They start bandaging up once the firefight has finished though.) Players normally twitch/react when being hit so can't continue to return fire while being hit. This seems to give the AI an unfair advantage. I think this is related to the ACE medical but am not 100% sure. I don't remember it being such an issue with the old ACE medical system (but could be wrong) and I've not played Vanilla in a long time but I always remember AI twitching a little when being shot so disturbing their firing somewhat.

It's still in the GREF mod. It's just a skin change

Thanks for the explanation!

Try this:

Luckily, I grabbed a screenshot at the time: Hope this helps.

Tried this mod for the first time a short while ago and absolutely love what it adds! We may have found one bug thought. We think the issues was with one building not correctly finding its damage model so when we were inside it and it got damaged, the game glitched like mad until we were all ejected from the building and the damaged building was not enterable. It was the Restaurant building in Cherno that we had this issue with. We could not replicate it with other buildings - i.e. on deliberately damaging them, the correct model appeared and people were not spat out of the building.

When looking at the settings available in game for CF_BAI Detect, there are two values available for each state. E.g. Player Visibility - Standing Chance AND Player Visibility - Standing Knowledge Presumably the first of these is how much the player's stance (standing in this case) affects the likelihood of being spotted. But what does the second value do and how does it affect game play? Many thanks

Anyone else noticed a significant frame drop with the latest version of JSRS? A test with no other items on the map with and without JSRS seems to cause a 5-10fps drop for me. I've not done this test with the previous version of JSRS but all my group do seem to have noticed a drop since the latest version released so I thought it would be worth testing.

Well said!

Spot on, da12thMonkey! 3D sights need short, large diameter bodies to make work with ARMA. (Or a new PIP technique!) I would love to have done the low power short dot magnifications in 3D and switched to 2D for the higher powers but it wasn't possible for all the reasons da12thMonkey describes. With regards to magnification, I just felt the S&B sights would be overpowered compared to vanilla sights / other game assets if I used BI conventions so to keep things in balance, chose to do the WFOV technique for zoom levels. And having to use 2D sight techniques for every zoom resulted in the slightly odd low power/wide angle zoom to replicate what the players are used to as an 'un-zoomed' image. So I would definitely NOT claim what I am doing is more correct than Toadie. (In fact I'd say I was 'wrong' - I just did not want to abuse game mechanics / make imbalanced equipment with my mods.) Toadie's stuff is awesome (as is da12thMonkey's) and much more complete than my mods. Their work inspired me to have a go at mod making. Looking forward to whatever they decide to make next!

The issue I discovered with the Performance Binary breaking the MicroDGR GPS seems to be back with the latest update to ARMA. Anyone else got this issue?

Rolling back from the Arma3 performance binary to the stable branch seems to have fixed this issue...