snippers

Nice! This is all looking really good! Really good work guys!

Just to make this a bit clearer here is a screenshot when it crosses from the field into the woodland area, in the woodland area and in the pictured area it grinds to halt (It is not the stone wall causing the issue as far as I can tell). http://i.imgur.com/p44iIEZ.jpg (846 kB) Thanks for the nice map, it is really awesome!

Great job Teriyak and Zabbi! Many thanks for this release. Looks like all the rpt errors are gone, you guys are awesome!

@Przemo Yes the github is where all the current code, work items and suggestions are logged. It is more likely that things will get noticed there rather than here. @Chairborne The only thing that should be effected is gear iirc. Until we get official word from BI on their exact intentions on parameter processing it is futile to attempt to fix.

Zabb you are my hero! Thank you so much for working on it! The video looks amazing and I loved the rainbow six music :D . Really looking forward to this!

Thanks you Zabb :D for the update and reply! Really liking this stuff! I didn't know if you knew, so I wanted to try to help. If I can help in any other way let me know!

Congratulations ACRE2 team! We have been using ACRE2 since the initial alpha/beta public releases and If your reluctant to try ACRE2 because of your experience with previous versions; I'd urge you to try this release as this release is vastly superior to all prior released versions.

Thanks for the update and for your hard work Zabb and teryaki! It is really cool to see an update to the vests. This mod has been really useful and I greatly appreciate it. These new vests are really nice! I was hoping you would fix the problem with the vests reporting lots of warnings to the Arma 3 log. This is quite frustrating as it slows down the game when the game logs these. There are many lines that are outputted, the following seems to show something is not quite right with the models. It can cause some really bad problems. Here is a small selection: 18:33:39 Warning: zabb\tacv1\ei_tac_v1.p3d:4 Error while trying to generate ST for points: 439, 438, 440 18:33:39 Warning: zabb\tacv1\ei_tac_v1.p3d:5, vertex: 125, sum of weights is 200, should be 100 18:33:43 Warning: zabb\tacv1\ei_tac_v1lcqb.p3d:1, vertex: 695, sum of weights is 200, should be 100 18:33:54 Error: zabb\tacv1\ei_tac_v1p.p3d: Opposite edge to P(200, 186) was not found - shadow geometry is not closed. Here is a much bigger part of the logs - http://pastebin.com/2sgiR1nY

Prior to Arma 3 1.44 parameters were available during preInit on the server, this is no longer the case. Technical Details can be found in this ticket: http://feedback.arma3.com/view.php?id=24007 It's upto to BI whether or not they want parameters to be available at preInit on server, it would be far nicer if they were as currently there is inconsistency in Arma 3 between the MP editor and Server behaviour. I was just in the process of finalizing an overhaul of the parameter system, I had recently written in F3, but this is broken too. The current parameter processor is also the reason backpacks don't appear in the singleplayer editor. I'll get back to it when we see what BI's response is. @skruis It is quite strange to hear that publicVariable was giving improper values. BIS_fnc_getParamValue does indeed provide a valid output, though digging through it's code it looks quite computationally expensive and opts for default values when the true value isn't known, which isn't nice if we depend the exact value. It's use may be fine, though I haven't tested to see if parameters are available during unit initializations yet, they are however available by init.sqf

This should be possible though a little complex to setup and not exactly what it was designed for. To give an idea as to how you can do it: once you have modified description.ext to have respawn at base, you'll need to setup an object with an addAction and then call something like the following to open the spectator-> [player,player,true,true,true] call f_fnc_camInit; @ACE3: Yes, Significant progress has already been made to support ACE3 in F3.

I have noticed this error as well, it seems to occur on any client that has AI except the server. I have had it while Zeusing after the start and it lasts to the end of the game. I would guess that for !isServer in preInit there is a bug, so it doesn't reach the function compilation stage.

This is quite odd as it has worked for me. As spectator you wont hear the radio comms, but you can hear the players if the camera is close them. It works by using the camera distance to the player so you need to be close. Are you also running the latest build of F3 and have you turned on ACRE2 in the mission parameters?

Thanks Evro for yet another epic release! Have you thought about maybe doing the UNO faction or just a few things from it? Or at least some UN reskins for the Mi8/M113 and other vehicles and a UN helmet? This would be really awesome to see and would give some new gameplay options!

The 117F requires a large amount amount of inventory space and should only fit in rucksacks, you can test if the player has enough space with the following: _hasSpace = player canAdd "ACRE_PRC117F";

Great stuff, Thanks for the release :)! Sorry for the nitpicking but, thought you might appreciate being made of aware of the following: I noticed that when you shoot the hueys with a MX rifle that a brown dust cloud appears if you hit the any of the helicopters on the side, most other vehicles in arma are configured (like the littlebird) are configured to give out a smaller greyish colour that better represents the metal rather than the dirt. It was quite noticable as I poured in machinegun fire into a huey.

Great job Burnes, The challenger update is nice! I noticed one slight problem with it, in the gunner seat the display with the green outline is slightly bugged, the rotation for the turret is displayed on the incorrect side of the tank e.g. if you turn the turn turret left it will appear as turned to the right on the display.

Thanks for the patch :), I am still pretty hyped about this. The rpt errors for when you select the M3 MAAWS are now fixed :D! Based on your changelog your probably appear of the rpt errors that still appear when firing (using the Virtual Arsenal here), wish I had a clue about how to fix them! But I thought it would be wise to post. 9:03:51 Error in expression <speedX> 9:03:51 Error position: <speedX> 9:03:51 Error Undefined variable in expression: speedx 9:03:51 Error in expression <speedY> 9:03:51 Error position: <speedY> 9:03:51 Error Undefined variable in expression: speedy 9:03:51 Error in expression <speedZ> 9:03:51 Error position: <speedZ> 9:03:51 Error Undefined variable in expression: speedz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmoke1Jet.moveVelocity 9:03:51 Error in expression <positionX> 9:03:51 Error position: <positionX> 9:03:51 Error Undefined variable in expression: positionx 9:03:51 Error in expression <positionY> 9:03:51 Error position: <positionY> 9:03:51 Error Undefined variable in expression: positiony 9:03:51 Error in expression <positionZ> 9:03:51 Error position: <positionZ> 9:03:51 Error Undefined variable in expression: positionz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmoke1Jet.position 9:03:51 Error during evaluation of expression _moveVelocity in ExhaustSmoke1Jet 9:03:51 Error during evaluation of expression _position in ExhaustSmoke1Jet 9:03:51 Error in expression <speedX> 9:03:51 Error position: <speedX> 9:03:51 Error Undefined variable in expression: speedx 9:03:51 Error in expression <speedY> 9:03:51 Error position: <speedY> 9:03:51 Error Undefined variable in expression: speedy 9:03:51 Error in expression <speedZ> 9:03:51 Error position: <speedZ> 9:03:51 Error Undefined variable in expression: speedz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmoke1JetM.moveVelocity 9:03:51 Error in expression <positionX> 9:03:51 Error position: <positionX> 9:03:51 Error Undefined variable in expression: positionx 9:03:51 Error in expression <positionY> 9:03:51 Error position: <positionY> 9:03:51 Error Undefined variable in expression: positiony 9:03:51 Error in expression <positionZ> 9:03:51 Error position: <positionZ> 9:03:51 Error Undefined variable in expression: positionz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmoke1JetM.position 9:03:51 Error during evaluation of expression _moveVelocity in ExhaustSmoke1JetM 9:03:51 Error during evaluation of expression _position in ExhaustSmoke1JetM 9:03:51 Error in expression <speedX> 9:03:51 Error position: <speedX> 9:03:51 Error Undefined variable in expression: speedx 9:03:51 Error in expression <speedY> 9:03:51 Error position: <speedY> 9:03:51 Error Undefined variable in expression: speedy 9:03:51 Error in expression <speedZ> 9:03:51 Error position: <speedZ> 9:03:51 Error Undefined variable in expression: speedz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmoke1JetL.moveVelocity 9:03:51 Error in expression <positionX> 9:03:51 Error position: <positionX> 9:03:51 Error Undefined variable in expression: positionx 9:03:51 Error in expression <positionY> 9:03:51 Error position: <positionY> 9:03:51 Error Undefined variable in expression: positiony 9:03:51 Error in expression <positionZ> 9:03:51 Error position: <positionZ> 9:03:51 Error Undefined variable in expression: positionz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmoke1JetL.position 9:03:51 Error during evaluation of expression _moveVelocity in ExhaustSmoke1JetL 9:03:51 Error during evaluation of expression _position in ExhaustSmoke1JetL 9:03:51 Error in expression <speedX * 0.8> 9:03:51 Error position: <speedX * 0.8> 9:03:51 Error Undefined variable in expression: speedx 9:03:51 Error in expression <speedY * 0.8> 9:03:51 Error position: <speedY * 0.8> 9:03:51 Error Undefined variable in expression: speedy 9:03:51 Error in expression <speedZ * 0.8> 9:03:51 Error position: <speedZ * 0.8> 9:03:51 Error Undefined variable in expression: speedz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmokeRefractPlane.moveVelocity 9:03:51 Error in expression <positionX> 9:03:51 Error position: <positionX> 9:03:51 Error Undefined variable in expression: positionx 9:03:51 Error in expression <positionY> 9:03:51 Error position: <positionY> 9:03:51 Error Undefined variable in expression: positiony 9:03:51 Error in expression <positionZ> 9:03:51 Error position: <positionZ> 9:03:51 Error Undefined variable in expression: positionz 9:03:51 Error during compilation of bin\config.bin/CfgCloudlets/ExhaustSmokeRefractPlane.position 9:03:51 Error during evaluation of expression _moveVelocity in ExhaustSmokeRefractPlane 9:03:51 Error during evaluation of expression _position in ExhaustSmokeRefractPlane Keep up the great work fellas!

Awesome news :)! Once again this is fantastic work and one of the best launchers from any mods. This video of some swedish soldiers firing the Gustav on a training range may serve as a good reference for a blackblast effect. Also there is a noticeable different sound here when firing, but that doesn't personally bother me. Great work, I am really looking forward to playing with this and your future work :)!

Here is a bug report: Post equipping, but selecting the the Gustav, several errors appear in the RPT (I am only using this mod and CBA): 12:24:40 Error in expression <(density interpolate [0.98,0.981,-1,1])> 12:24:40 Error position: <density interpolate [0.98,0.981,-1,1])> 12:24:40 Error Undefined variable in expression: density 12:24:40 Error during compilation of bin\config.bin/RocketBackEffectsNLAW/RocketBackfire1.enabled 12:24:40 Error in expression <-speedX/30> 12:24:40 Error position: <speedX/30> 12:24:40 Error Undefined variable in expression: speedx 12:24:40 Error in expression <-speedY/30> 12:24:40 Error position: <speedY/30> 12:24:40 Error Undefined variable in expression: speedy 12:24:40 Error in expression <-speedZ/30> 12:24:40 Error position: <speedZ/30> 12:24:40 Error Undefined variable in expression: speedz 12:24:40 Error during compilation of bin\config.bin/CfgCloudlets/RocketBackfireNLAW.moveVelocity 12:24:40 Error during evaluation of expression _moveVelocity in RocketBackfireNLAW 12:24:40 Error in expression <(density interpolate [0.98,0.981,-1,1])> 12:24:40 Error position: <density interpolate [0.98,0.981,-1,1])> 12:24:40 Error Undefined variable in expression: density 12:24:40 Error during compilation of bin\config.bin/RocketBackEffectsNLAW/RocketBacksmoke1.enabled 12:24:40 Error in expression <-speedX/4> 12:24:40 Error position: <speedX/4> 12:24:40 Error Undefined variable in expression: speedx 12:24:40 Error in expression <-speedY/4> 12:24:40 Error position: <speedY/4> 12:24:40 Error Undefined variable in expression: speedy 12:24:40 Error in expression <-speedZ/4> 12:24:40 Error position: <speedZ/4> 12:24:40 Error Undefined variable in expression: speedz 12:24:40 Error during compilation of bin\config.bin/CfgCloudlets/RocketBacksmokeNLAW.moveVelocity 12:24:40 Error during evaluation of expression _moveVelocity in RocketBacksmokeNLAW 12:24:40 Error during evaluation of expression _enabled 12:24:40 Error during evaluation of expression _enabled Firing then produces more rpt output 12:26:18 Error in expression <speedX> 12:26:18 Error position: <speedX> 12:26:18 Error Undefined variable in expression: speedx 12:26:18 Error in expression <speedY> 12:26:18 Error position: <speedY> 12:26:18 Error Undefined variable in expression: speedy 12:26:18 Error in expression <speedZ> 12:26:18 Error position: <speedZ> 12:26:18 Error Undefined variable in expression: speedz ... (There is more but don't want to clog this up)

This is awesome, great job! It looks great and functions well! Thanks for releasing this I was testing this in the virtual arsenal and noticed that the iron sight is slightly offcenter, I had to aim the iron-sight slightly to the left to hit the guy at 100m. This adjustment was approximately the same width as the vertical metal bit in the sight). The zeroing works perfectly with the scope though! I believe you are already planning to add the Smoke/Ilumination rounds but if your interested in an addition optic to the M3. The FCS12 is a new fairly modern sight that I believe the Swedish military are now using with the M3. It's key advantage is a built in laser ranger finder.

Thanks for the feedback Chairborne and chat on steam! I have made an issue on the F3 github: https://github.com/ferstaberinde/F3/issues/524 and I some have ideas as to what has caused it. I'll see about seeing if can propose a fix ASAP.

Thanks for the new release Deltagamer :D! Really nice to see the fixes and woodland variants, your hardwork on these is greatly appreciated! Minor Issue: The textures of the 'addon' items on top look quite low resolution (pictured). The front set of attached items, do slightly reduce the visibility of the driver while turned out, but I have no idea if this is something the US military would do. The rear cargo 'addons' also would block the rear top hatches from being used. http://i.imgur.com/ODWxg7g.jpg (413 kB) Here are some things that I think would really be the icing on the cake, I believe you already mentioned you had plans for some of them: Picture in picture displays/ability for driver to use interior LOD without having to turnout/use fixed camera would be epic (working speedometer would be great if this was implemented)! Making the driver experience better/viewpoint less fixed helps to lower potential boredom due to lack of situational awareness. Being really pedantic here but Perhaps making the first cargo seat (the one the first passenger will take) the one the left side, directly behind the driver as this is the closest seat to the crew and the most useful for a squad leader to occupy as with a range based VOIP system like ACRE it would allow the squad leader better direct comms with the driver and a little bit of visibility towards those PIP screens. Animated openable rear door :D!

Once again thanks for the updates :)! So after having a few sessions with the latest release with ~20-40 players our present problems are the following: Clients remaining muted at mission end - workaround is a global call to set spectator before calling end mission. Occasionally a client when talking on the radio will keep transmitting constant radio beeping (the sound when a radio transmission starts), we keep seeing this one time and time again for different people and is quite frustrating as it holds up the radionet and it is hard to make out what is being said. There were also some reports of some players not being able to hear others on the radio when terrain and range shouldn't be an issue, but I don't know how to reproduce this. I'll see if I can get a reproducible case or at least better document it. As a side note we do use several mods but I don't believe any would mess with ACRE2. If there is anyway we can provide better information on the issues let me know.

I don't think this has been mentioned before, but the Russian helmets (6B27M and 6B28M) offer a great deal of damage absorption, stopping several rounds of various calibers. I am not sure if this is realistic but this has become a balancing issue for PvP missions for us. Is this behaviour intended?

http://feedback.arma3.com/view.php?id=19964 This can be closed, as it is fixed in 1.32