TCR_Smacky

Per my post about launchers above, I found out this is related to the whole NVG/Bino/Laser/Accessory issue. If I have the binos/rangefinders in their slot in inventory and ACE running, then they won't lock on. If I don't have ACE running OR I have ACE running, but my bino slot is not in use (empty) then I can lock on without an issue.

Has anyone seen an issue with getting various launchers to lock on? In testing and working with all the updates last night we found that none of the AA and only a few of the AT launchers would lock on. With Arma 3 1.52 & ACE 3.3.2.0 > Lock on worked as expected With Arma 3 1.54 & ACE 3.3.2.0 > Lock on worked as expected With Arma 3 1.54 & ACE 3.4.0.0 > Problems with all AA and most AT launchers getting launch on I have not yet been able to specifically related it to ACE itself....working on that part, but want to see if anyone has had similar problems.

I can't say exactly what the .dll do (as I am not on the ACE3 team). However, I can say they do not need to be uploaded to the server. They are client side only.

I found another strange issue and I looked through the change log, but don't think I see something related to this. Only when I have ACE enabled do I see this issue. When I get out of a vehicle or land after parachuting, if I am carrying any sort of binoculars (binos, range finders, etc), I will switch from my weapon to the item in the bino slot. If I test by turning off ACE and do the same thing I stay with my weapon and don't switch.

I found an issue with night vision. With the ace_nightvision.pbo in place if I sight up (ADS) with my weapons, the night vision turns off. If I lower my weapon again they come back on. This appears to be pervasive against all NVGs with the ace_nightvision.pbo in place (not just the ace NVGs). If I remove it, the NVGs stay on once turned on whether I sight up or normal stance.

Make sure you update CBA to the latest release. I had the same issue until I updated CBA.

Thanks, zbug. Just updated my post with this info to help others. I read through more of the thread and tested and found this. Appreciate the feedback and really enjoy this mission. We just started testing .914 last night and like it a lot. Keep up the good work and thank you again. zbug - "Make sure the revive parameter is set to "disable" so the ACE revive can work properly. If that's already the case then maybe people who play with ACE will be able to help"

EDIT: Reading through the whole thread and doing some testing I found what will allow the ACE medical to work. If I disable the FAR Revive when initializing the mission ACE3 Medical works as expected. Just wanted to pass it on in case anyone is interested. Perhaps this has been covered before, but running into an issue with ACE3 and this mission. Specifically, the medical self interaction. On our server we run ACE3, cTab and some other mods. I noticed that if I am hit by fire or otherwise injured, when I use the ACE3 self interaction to treat myself it does not show any color for where or what or severity of what is injured. Additionally, it doesn't seem to have any impact to banage or use morphine. What's even more add is if I fire a launcher (like a SMAW) and get hit by my own back black, the damage shows (my torso will show yellow, I will get blood splatter on the screen and the effects of pain will so). If I treat myself for this it works as I would expect (the torso shows yellow, but after treatment it shows white, the blood spatter disappears and the pain effects go away). I have tested in other one shot missions and some of the default Arma 3 multi-play/coop missions in ACE3 medical appears to work as expected. If this known? Is there something (a config, something in the mission PBO, etc) I need to change? Other than that we really love this mission. We run it as the default on our server and look forward to the additional improvements you have planned. Thanks!