BinaryMan

Because he has proposed something different and I agree with cyruz. There should be no user input for headless client functionality at all. No script, no module, no editor change, or mission config change. It should just be handled by engine automatically. Headless client needs to be developed so its functionally better than the game currently is or abandoned. Being able to not use a feature which makes the game better or having to enable a feature which makes the game better is stupid.

You most likely do not have the most recent CBA or do not have it enabled. CBA now has a key binding system that allows modders to register keybinds through one system. It also allows users/players to change keybinds for all CBA registered keybinds through one easily accessible interface in the game controls menu. You can read more about it here: https://dev.withsix.com/projects/cca/wiki/Keybinding

Floating trash pile on altis at: [3923.36,12721,0.0010376]

Are you on an AMD graphics card? I've been getting this in game with my amd 280x. I've also been getting it in insurgency as well (Only on certain maps). Perhaps its amd's fault?

You haven't seen my post yet. :mad: jk A note on aiming deadzone. it appears that weapon movement inside of an aiming deadzone doesn't inflict any aiming penalty.

I realise my first post might not have been very clear, in this following post I hope to make my ideas more clear: I think the advanced flight model would be easier for keyboard and mouse users if collective up and down changed collective at a constant speed instead of a non-linear one. Currently tapping collective up or down does almost nothing. Collective up and down go from doing almost nothing for the first quarter to half second to moving quickly in a short span of time, which is really hard to use. By changing collective up and down to a constant movement speed it is easier to slowly engage or disengage the rotor blades. Currently the non-linear speed in which collective up and down proceed at makes this very difficult. In fact, multiple long presses of these collective up/down keys cause a nasty "stair case" effect. "stair case" effect explained in more detail: A simple maneuver like flaring for speed reduction (at constant altitude) becomes hard with a keyboard and mouse with non-linear collective change. During a flare it is almost always necessary to reduce the collective over a period of time. Holding down the collective down key is almost always too much, while pressing the key multiple times does not elicit enough collective change. What ends up happening is the collective is moving to fast during certain parts of the flare and to slowly during other parts when the key is pressed multiple times over the entire flare. This too little, then too much, then too little, etc... collective change is the nasty "stair case" effect. By changing collective up and down a linear movement speed it becomes possible to slowly or quickly disengage the rotor blades by either tapping the key at a slow rate, fast rate, or holding the key down for maximum traversal. My proposed solution to the current problem of collective change is the following: Make collective up and down keys change collective by a constant rate of change. Add 2 more key binding: Collective quarter step up/quarter step down. This will immediately change the collective up or down by 25% Reasoning behind the Collective quarter step up/quarter step down is that it is sometimes necessary to quickly change the collective by a large amount, these two bindings preserve that. Default keybindings (US keyboard): constant collective up: "Q" constant collective down: "Z" Quarter collective step up "Shift + Q" Quarter collective step down "Shift + Z" It will most likely be important to experiment with 1/3 collective step up/step down. or other such values as 1/5 maybe even 1/6 or 1/2. In addition to this quarter collective step up/down might need to happen over a period of short time to reduce the immediate load the step brings on the rotor. It would also be nice if you could add keybindings for constant turn left/right for ground vehicles. Currently you can get some "stair case" effect causing under steering followed by over steering.

I think the advanced flight model would be easier for keyboard and mouse users if collective raise was linear instead of quadratic or whatever it is right now. Collective up and down go from doing nothing for the first half second to moving really quickly, which is really hard to use effectively. Even when binding collective analog to something silly like trackIR forward/Back, it suddenly becomes 10 times easier. It would also be nice if you could do the same thing with turn left turn right in ground vehicles.

I think he is talking about an addon specifically for single player use.

I feel like you didn't read the entire post

You've done it again Tao. GREAT JOB I like the changes to the grenade launchers and hand grenades the most! I only have one concern and it regards the fragmentation system: If the fragmentation system only direct fragments at object like people and cars would it be easy to, in some cases, use that to detect where enemies are? Just a thought, if you could get back to me with a reply that would be great. Recoil changes are amazing too, Also hit effects... really everything. just wow

I think the update is great, new weapon sway is amazing, fatigue system rewards specialized loads outs with a goal in mind. Keep it up BIS you're definitely on the right track here!

Taosensai is a boss! keep up the good work

Overall I like the new weapon sway mechanics. I only have 2 problems with it, neither of which involve how the sway works but just the amount. 1. Impact of small damage on sway is a bit too much 2. Induced sway due to movement speed is high Great work bis!

Top right click on the box that says game spy, should switch to the steam master server. :DDD :))) ?!?! ^.^ >.>

I'm on stable currently, I meant it as the ai are good!

I can't complete the combined arms showcase :( Good work fabrizio! :D

The three round burst on the m16A4 has no recoil. Other than that amazing mod! I was waiting for someone to part the smaw into arma 3 :D

Not sure if this has been found or discussed before. It appears that BIS_fnc_addStackedEventHandler and BIS_fnc_removeStackedEventHandler when using "onMapSingleClick" will remove your ability to set a personal way point on the map. Steps to reproduce: Load an empty mission in mission editor and place a soldier unit Note that you can set a personal way point with shift click Press escape and Local exec this: "["Blah", "onMapSingleClick", "hint str time"] call BIS_fnc_addStackedEventHandler;" Note that you can no longer set a personal way point Press excape and Local exec this: "["Blah", "onMapSingleClick"] call BIS_fnc_removeStackedEventHandler;" Note that you can no longer set a personal way point. (it does remove the event correctly) Is anyone else getting this? I'm getting this on the stable branch at the moment. Could anyone with dev branch downloaded or someone with a faster internet connection than me verify if this is still a bug?

What was the addon that was causing the problem? Just curious.

The free look is like that in vanilla arma 3. It is not an effect of tmr alternate. I can't reproduce the rate of fire issue you experience.

I've been trying to make a very simple addon for an hour or so, and I can't figure out what I've been doing wrong. I do have community base addons installed. Here are my 2 files: blah.sqf: while {true} do { hint "blah"; sleep 1; }; bny_Arma3mod.cpp: class CfgMods { class BNY_Arma3mod { dir = "BNY_Arma3mod"; name = "A mod"; picture = ""; hidPicture = "true"; hideName = "true"; actionName = "website" action = ""; }; }; class Extended_PostInit_EventHandlers { SLX_Arma3mod_postinit = "[] execVM '\blah.sqf'"; }; Is any of this wrong? Or am I making the pbo incorrectly?

do you have the latest version of the mod?

I come and check this thread every day for new updates. Feels great, love the recoil compensation.

I've had that problem before too. I found that the behavior was sporadic. Just a few questions: 1. What range were you using the PCML at? 2. Did it work fine in the training mission? 3. Does it function the same when looking down the scope vs using the on screen reticle?

I'm having the same problem with regard to the rounds hitting right of the prescribed hit point indicated on the your new overlay optics. Here is a photo for you convenience. http://steamcommunity.com/sharedfiles/filedetails/?id=173835933 As you can see the whole graphic is off center. Resolution 1920x1080 interface size small aspect ratio 16:9 my 3d sampling is also at 100% Though I will say I was skeptical about the optics, this preview is great. I am loving the optics!