beita

I read the whole thread, was asking about the Carl Gustav, the uniforms, the night vision equipment, and the packs because nothing was said about them. Wasn't sure if you meant texturing new uniforms or re-texturing the ones already in there. There was a post describing the new uniforms being planned, so I was wondering if you planned on doing both the new and old. The M72A6 has been included, so I was asking if the Carl Gustav would as well, as the first post says "with hopes of AT weaponry soon after". The MNVD is the err "official" name for the night vision issued, the AN/PVS-14. Sorry for not being clear on that.

Nice work. What plans do you have for equipment and weapons? CTS Ruck/small pack? AN/PVS-14s/MNVDs? New/old uniforms/boots? Carl Gustav? Would be very appreciated if you could model some of the "modern" stuff as well, not only focusing on the future equipment.

Well, it is A Friday .. any news? :)

Also can try: this && ({(_x getPos select 2) > 2} count thisList) > 0 In the condition field of the trigger. Basically, it fires if the original trigger conditions are true and if there is at least 1 unit from the trigger list under 2m altitude. Depending on what your trigger is for, you might need to change that.

Try: _str = format["Stop Vehicle %1 for inspection", i]; _btrig setTriggerStatements ["this", "pac1 = player addAction [_str, ""civc\stop.sqf"",[], 0, true, true, """", """"]; i=i+1", ""]; Easier to manage it via another variable than trying to put in 8 sets of quotes.

I just quickly tested this in the editor, for a Kamaz truck, simply put this in it's init line and it will drive without headlights: this setHit ["L svetlo", 1]; this setHit ["P svetlo", 1];

You can do it by destroying the lights on the vehicle. Use the setHit command in the init of the vehicle, you could repair them later with setHit if needed. Try: this setHit ["L svetlo", 1]; this setHit ["P svetlo", 1]; If those class names don't work, you will need to look them up in the pbo file for whatever vehicle you are looking to drive without lights.

init.sqf is run after the init lines of units as far as I know. I haven't found a way to change the group ID in the slot selection screen as of yet ...

Try in the unit's init: group this SetGroupId ["PapaBear"]; Won't show up until you have gone to briefing (when the unit init lines are run) so during slot selection you still will see 1-1-A, 1-1-B, etc. Also, can't seem to have the regular space character (" ") in the string, %20 might work, haven't tried it ...

Creative use of the setPlayable command? http://community.bistudio.com/wiki/setPlayable In the unit's init, maybe something like: id = [this] spawn {sleep 0.1; _unit = _this select 0; if (!isNull _unit) then {setPlayable _unit;};}; Not sure if this would work properly though.

Did you ever find anything out about this? In the same boat, would REALLY like to use this logic for other purposes ...

Any idea on when this might happen? I thought I read sometime in November a while ago? Nice mod by the way! Some suggestions I thought of while testing out all the units and weapons .. 1. Need some sort of sight adjustment for the Elcan optics, they become less and less useful as you move past the 200m mark. 2. Would it be possible to apply a "glow" to the tritium part of the Elcan optic (similar to the compass and watch in Arma 2)? 3. Adding the glowing cateyes from the USMC Arma 2 model would be awesome, those things are helpful when it's really dark! Keep up the good work, looking forward to a release with some CADPAT TW so the units don't look so out of place in Chernarus!

The blur when near the MGs seems overdone. Haven't been around an M2 firing, but the M240 ... yeah, maybe the very first 5 bursts you would be a little nervous or whatever, but hell, after you have been around the thing firing a lot, you don't notice it. Just another loud noise and some toasty brass.

Is that an incoming artillery sound I hear? Nice. The impact effects look better, the damage radius also seems better. Would it be possible for you to do any work on 60mm mortar rounds? They would be fantastic additions to the game, an easy platoon mobile mortar piece (rather than the 81/82mm mortar, more of a Company piece).

Yeah ... it is becoming a MASSIVE crutch. Pretty much every other form of IFF is going out the window, being taken over by the "just hold the spacebar" method. Seems like a pretty damn strong exploit to me, you can see things through houses, trees, terrain? Are you kidding me? That is a bug plain and simple.

To expand on that .. Name your LAV something, ie: "lav1". In the initialization line of each soldier you want to put in the LAV, put: this moveInCargo lav1; Alternatively, you could group the soldiers with the LAV and put the "Special" of the unit to "In Cargo", then they will start inside the vehicle. Some different behaviour can happen though when the LAV is grouped with the soldiers.

Haha, why did you even put a poll if both the responses are yes?

Unless this changed in Arma 2, there was no way to change the name of the group BEFORE the briefing. init.sqf and the init line of units is run at briefing, so you cannot change the default group names until then.

Awesome! Thanks.

Found this in one of the functions from BIS (Defense one I think): { doStop _x; sleep 0.5; _x action ["SitDown", _x]; } forEach units _group; Now, the _group variable could be replaced with the name of whatever group you want to sit down.

Yeah, I tried adding the leader of a spawned artillery group to the syncronized objects array, but, looking at how the system is initialized, that isn't going to be enough. Some scripts are run at the mission start that implement the entire artillery system. I guess I could take a longer look at the init process, but it was pretty confusing to me and I was wondering if anyone else had already figured it out ;) Name the artillery module instead of the MLRS group leader. You are supposed to use the module for the call, NOT the group leader. It depends what you want the artillery to DO. If you just want it to be a single barrage, that is different then a group that constantly picks out targets. If you want it to be player controlled, different again. Also, if you have trouble getting it to work, try using single quotes instead of double quotes. Not sure why it helps, but sometimes it does.

Little bit of a complicated question ... If I wanted to create an artillery battery when the mission is in progress, what would I have to do in order to get the group leader synced to an artillery logic? Is it possible to do after a mission has started?

The third argument doesn't HAVE to be a config file, an array of unit classes works fine. An example: _pos = getPos redfor_spawn; _skill = [0.5, 0.5]; _side = EAST; _units = ["RU_Soldier_SL", "RU_Soldier_TL", "RU_Soldier_AR", "RU_Soldier_AR", "RU_Soldier_LAT", "RU_Soldier_LAT", "RU_Soldier", "RU_Soldier"]; _newGroup = [_pos, _side, _units, [], [], _skill] call BIS_fnc_spawnGroup; Worked fine for me.

Well, in my opinion, the best feature of the Guard waypoint is the fact that the AI will actively seek and destroy ANY known enemies spotted by other groups. So, you can have AI on sentry duty spotting targets, and other AI on guard duty who will move out to destroy the targets. Makes for a very active and aggressive AI that will hunt you down.

That's the right command. Used the in-editor help (press F1 over a complete command). Try: this disableConversation true; In the init of any unit you want to not talk. EDIT: Seems to only disable the "Greeting" and conversation menu. They will still salute/address other units.