jamesf1

Well, I saw a lot of people were looking for a stance indicator for first-person view, so I thought I'd throw something together. It should work fine, I've had a number of guys from my squad test it, but the usual disclaimers apply - your mileage may vary :) It's possible it'll screw up in some situations, given it relies almost entirely upon animation names (and I suppose it's possible that BIS may not be 100% consistent in their naming). It should be all signed and good to go - the .bikey is included. I've also not tested anything other than 1920x1080 on the normal UI size... but I've utilised safeZones properly, so it should be fine (if it's not, I'll fix it :p). Features: Shows your stance in first-person mode. Highlights stances that hinder your movement in yellow (in this case, low prone and high prone). Displays stance-based lean status, too! It's a stance indicator... what more do you want? Video: (v1.0 demonstrated) 6HYnBL8OQhI Download: [HMM] Stance Indicator v1.1 (5kb - .zip) (and here it is as a direct link, if CoralCDN is being slow) Requires @CBA_A3. See this thread for info on that :) Changelog: v1.1 Now highlights main stance separately. Stance-based lean states are supported/indicated. v1.0 Initial release. Installation: Extract the @HMM_StanceIndicator folder from this archive into your Arma 3 folder. Load Arma 3, go to Options > Expansions. Click on @HMM_StanceIndicator in the list and click Enable (make sure to also do @CBA_A3, too). Thanks: To the HMM Squad folks for testing :) ShackTac Fireteam HUD for inspiration for the show/hide UI logic. License: Usage of the HMM Stance Indicator is predicated upon your agreement to the following: All files included are the property of the original author. HMM Stance Indicator may not be modified, included in other mods (in whole or in part), or used for any commercial/military purposes without prior permission from the author. Redistribution is permitted only if the original archive is unmodified and it is distributed free of charge. This mod may not be ported to any other game, including any variation of the Arma series, without prior permission from the author.

Apologies for the delay in updating - the past few weeks have been hectic (RL) weeks for me :) The next version is almost ready to release, but I'm going to hold off until the stance command change from the dev branch makes it to the main branch... just in case there are any other similar changes that could break it. At the moment, the problems some of you are experiencing are due to the dev branch command returning different results. At the moment, the next version includes: Updated (v2) server/client keys. UI now fades out when in a "normal" stance (i.e. the 'middle' stances). UI now indicates when you're unable to move due to an injury (by use of canStand only, currently). I've yet to do the config options for sizing/positioning, but will hopefullly have them done for the release :)

Excellent idea. In the version currently undergoing testing, the stance turns red (instead of white) when (canStand player) is false - that seems to be the best solution at the moment :)

This refers to the stance-based leaning. Using Ctrl+A or Ctrl+D when in Crouch or Standing puts you into a "step lean", which is indicated :) The traditional Arma leaning (using Q/E by default) isn't indicated in the UI, because even from first person, it's fairly easy to identify your position, due to the view rotation that comes with it (the step-leans keep your view level). Saw this mentioned earlier in the thread, it's the next thing I'll add as soon as I get some time :) I'll look for a way to make this configurable along with the UI size - never really delved into supporting configuration options in mods. Nice catch, will fix :) The primary reason was that you can easily see your stance in third-person view, but it's almost impossible to know what stance you're in from a first-person perspective (unless you're actively tracking, or looking down at your soldier model, which is completely impractical whilst fighting).

I'll take a look into either making a smaller version as well, or a config to allow people to choose a size :)

I've posted a new version (v1.1) - see the first post for an updated download link :) Changes: Now highlights main stance separately. Stance-based lean states are supported/indicated.

Yeah, I've been trying to work out a sensible way to differentiate between the three 'major' stances - the problem with shapes at the corner of your view is that they have to be fairly significantly sized (simply reorientating the blocks doesn't aid that, from my testing). I'll try a few options and see if I can come up with something sensible - maybe highlighting the respective character on the left hand side, that is associated with the current stance :)

Wouldn't know :p I value my keyboard too highly :D I'll take your word for it... just this once :eek:

You'll be needing this:

Friends?! What are those? :p In all seriousness... that's not a bad idea. Now I just need to find one of these 'friends' you speak of :icon_mrgreen:

No, they didn't. The GTA4 port wasn't brilliant, I'll give you that, but it was fine with an X360 controller (at least, that's how I played it on my PC). I'd just rather have LA Noire on PC than fork out £160 for an X360, plus the game price... just for the one game. :rolleyes:

This is the one title tempting me to find the money to pick up an X360 - but I wonder if Rockstar will play the usual game of porting it to PC a year down the line? Decisions, decisions :D

This should work. Create a GameLogic, and put this in its init: chair = "FoldChair_with_Cargo" createVehicle (getPosATL this); chair setPosATL (getPosATL this); char setDir (getDir this) Then, move the GameLogic where you want the chair to appear, and rotate the GameLogic to change the chair's orientation. When you move up to the chair (often the back gets better results than the front), you'll get an option to 'get in chair as cargo' :)

Using createVehicle you can spawn a "FoldChair_with_Cargo" that can do just that.

If you delete existing groups, they are no longer counted towards the limit. The limit is more '144 active groups per side'. Your method of deleting will work, but it's usually advisable to give a 10-15s delay before deleting the group (to ensure it's completely empty).

I rarely post outside of the Editing forum... but felt compelled to give my feedback on PMC. It must be said, though, as much as I'm a supporter of BIS, I'm a little disappointed this time around. As many others, I have tedious stuttering in the in-game videos (and no, nothing more than your 'normal' set of codecs... no virus/security software running, etc.); there are no new MP or SP scenarios (other than the armoury); the campaign has proved a bug-fest (e.g. I spent about 30 minutes running all over Zargabad, looking for a single AI who was stuck on/in a wall, that I had to kill to move on); the map is nothing worth writing home about; my frame-rate has plummeted (with the patch or DLC, who knows); and I just generally feel like far less effort went into it than BAF (with which I was thoroughly impressed). :( I'm not here to deride BIS, far from it, but regardless of my level of support (which has been high, and over years), I won't be touching the next DLC unless it returns to BAF-quality.

endMission

I was more referring to parameter value selection rather than parameter listing. I think the latter looks fine, but the former just has a lot of space to the left and right side. I think it'd be better if you could change the values on the parameter list screen (such as via a drop-down, or arrow selections... we now have enough space for that - don't know how viable it is in-engine, though). My day job is working with/designing user interfaces - so perhaps I'm just a little more critical than most :icon_rolleyes: In either case, I don't think it's bad, I just don't think it's as good as it could be. And please don't mistake my feedback for ungratefulness, I'm very grateful for the continual work you guys at BIS put into these games :) Edit: For clarification, I voted "not good" because some of the aspects of the interface just aren't that good (mostly pointed out by kylania)... but, that's not to say that I don't believe they can be improved, or that I think any effort thus far is wasted... far from it! :)

Couldn't have said it better, and voted accordingly. I can see the need for some improvement to the UI in terms of available space, etc. but the new idea is just a bit over the top (an entire screen for a parameter? :rolleyes:). Not trying to sound ungrateful, but I think a compromise between this new idea and the old system is needed.

46 is the primary display :)

Untested, but perhaps visibleMap does the job?

Uhh... Mando Heliroute? In my experience, you can get a chopper to land pretty much anywhere with it :)

_all = nearestObjects [player, ["All"], [color=red][b]2000[/b][/color]]; _helis = nearestObjects [player, ["Helicopter"], [color=red][b]2000[/b][/color]]; _notHelis = _all - _helis;

Fair enough - many thanks for adding the feature :)

Haha. I was merely wondering whether there was a particular argument for "_forEachIndex" - as you say, it's hardly of any great consequence in the grand scheme of things :)