kuIoodporny

I had a little trouble creating hotfix, so I can only hope so :rolleyes:

The AT problem is my fault. I left maxControlRange set to non-zero values, thus AI thought it was firing guided missiles. I've restored this in CCP, now AI shouldn't do this kind of crazy stuff anymore.

You should consider working on UV so you can fit 2048x2048 textures. 4096 may be overkill and I believe they should be used only as source files, while for best performance 2048x2048 textures should be used ingame.

A hint: sounds, like tons of other stock content config, can be inherited. No need to turn defensive on such non-issue.

There's still something to work with, for example optics configs - but overall great job WR5.

I guess the ACE mod wouldn't hesitate to adopt these babies. ;)

It's not about reloading weapon's magazine or changing weapon's reload time permanently. This command changes weapon state between "just fired" (1) and "ready to fire" (0), relatively to cyclic rate of fire (reloadTime). So, for instance you can make Fired EH which would reduce reload time of given weapon by half because it's executed every time weapon fires. Or, setting reloadtime to 0.5 in constant loop would make weapon appear jammed.

New steering gained some issues recently: https://dev-heaven.net/issues/35558

I think my aimpoints prototype can be of use. https://dev-heaven.net/issues/5290 https://dev-heaven.net/attachments/13745/zgb_aimpoints.7z

If we are at inventory improvements, please consider following ticket: https://dev-heaven.net/issues/23430

Great! Looks like somebody took good example of Jagged Alliance ;)

Lovely new functions!!! Please don't stop ;)

Things I have recalled from reviewing the scripting command requests on CIT: camera param get commands https://dev-heaven.net/issues/30458 visiblePositionATL and visiblePositionASL https://dev-heaven.net/issues/29553 & ASL variants of several useful commands https://dev-heaven.net/issues/24468

Basically I need leaning angle. Returning camera direction and position ASL would also be helpful. torsoVectorUp unit or weaponVectorUp -> like vectorUp, but only for leaning part of unit's body or unit's weapon selection in real world coordinates. cameraDir -> camera direction vector cameraPos/cameraPosASL -> camera position ASL

Ha! Great job with eyepos and aimpos! ... if we get up vector of upper part of player's body, I'd be able to fully implement scripted reflex sights. Just EOTechs need the up vector ;)

Awesome. Wish there was more documentation of new functions out of box, but otherwise - BI, I love you

Frigging awesome. Now, to the N++!

shshsh Nou, don't hint BI to turn into zombie games. :) Wonder about count of unique players connecting to Arma every day/week or so.

Yup, it's already fair that you can lase and shoot hovering helicopters. IRL it'd be waste trying to use Hellfire against anything faster than usual ground vehicle

Some ideas for such mission (mostly for cutscenes, intros - pick 2 or 3): - drinking vodka (or stronger stuff) with friends - doing nasty stuff while drunk f.e. driving bike, losing control, passing out and falling when driven too far away from road, while trying to resolve task f.e. "get from Stary Sobor to Novy Sobor using old bike" - race against time and police - challenging bullies / bullying wimps from school, incl. city mayor - doing Postal 2 like tasks: buying food, visiting church etc. - feeding animals, ranting wife, , walking dog...- CWR Kozlice if player chooses force solution, collecting evidence to make police help you

What about negative values? :P

Congrats man! Looking forward to Julkat :)

You will need to create extra sounds and configs for 3rd party mods, but I will supply the documentation and examples for that.

In theory we can set up as many custom conditions and soundsets as possible, however we wouldn't be able to deliver the mod before A3 then.

The Dslyecxi's ticket about making the ability to look up/down while driving optional, I find it very reasonable: https://dev-heaven.net/issues/28632 Personally, I love the changes (for me it's very intuitive and OFP-nostalgic), but as we can see many players have various issues with that. Ideally, the "camera deadzone" area would also be customizable, so player can decide if he wants zero deadzone or let the cursor roam the screen freely. == @PELHAM: Have You thrown the dump files at CIT to let BI prevent the CTD from occuring in the future?