Druid_

Are you sure that its the smoke effects causing you frame rate problems? Most modern graphics cards can render smoke with little FPS loss if done correctly IIRC.

I can post my shoulder rotator cuff surgery next tuesday if you like

yes it will. The other seat can be occupied by an AI pilot/gunner & you will be able to switch seats.

Don't use notepad, it will cause problems! Download Notepad++

Aye, that it is laddie. If you like your malts then you might like Op Lagavulin which is aging in the cask waiting for patch 0.9 to be released. EDIT: Unfortunately patch 1.1.09 removed an awful lot of lua script capability which was used extensively throughout of Op Lagavulin. I believe this will be remedied in the next patch 1.1.10 so rather than hack it to poeces I will sit on it until the next patch. I hope its worth the wait.

For the JTAC to transmit target position on datalink he has to have EPRLS in the advanced options of the GUI. Beware only certain units have this capability e.g. A10c, Humvee, MRLS. Having said that I have replaced a FAC once when the previous just didn't work for some unfathomable reason. Frustrating to say the least ...

When the JTAC will tell you the relative position of other threats in his brief. e.g. SA-13 5nm NE (IIRC). You just have to go looking for them with your TGP. Using the offset page on your CDU you can even plot that approx position, display it on your TAD then start scanning the area with your tgp

in 1.1.0.8. I have found this not to be the case with an AFAC so be wary when mission building. Even the priority system doesn't seem to work with airborne or ground based FACs. I have tested with AFACs, stationary FACs & mobile FACs and found the whole system does NOT work as advertised I'm afraid. So be ready for mixed results with the JTAC system. Hopefully it will be better in 09 patch.

If you do that 6 of em will fall short. You should aim at the middle of the target area.

I think this is because they aren't fixing the lag associated with ACTIVATE GROUP. Now if they fixed that I'd be well happy. In the meantime though this will help.

takes me back a few years. I wonder if I still have the cardboard cockpit stashed away somewhere.

Nope, I create a group, formate them how I want then create a Template. Later when I want to use that template again its not there in the drop down list. Maybe I need to do a reinstall. Check yours first though if you don't mind.

Disregard above post. I was just mucking about with templates myself & for some reason after creating about four they do NOT appear in the drop down list of available templates. They have disappeared into the ether never to be found again. In the GUI trigger actions they are there, just can't select em in Create Template icon menu. Weird. anyone any ideas or another ME bug?

Here's how to enter BULLSEYE offsets into the CDU via the UFC. 1. Select CDU on right MFD 2. On UFC press (FUNC) once then (4 OFST) 3. Change INIT POSIT to BULLSEYE on MFD CDU page by pressing FUNC once & press SEL rocker - / down Once 4. Rotate STEER PT Dial on AAP to MISSION 5. When you receive a Bullseye call e.g 146/36 ....a. On UFC enter 146036 (Note the use of extra zero in front of 36) ....b. Press OSB 8 MH/DIS ....c. Press OSB 9 to display the information as indicated Waypoint. 6. Select NEW Bullseye created WP in HUD (STEER+- or HOTAS). Note: The entered Bullseye bearing will change once entered, this is due to Mag Variation & is correct. (absolutely no credit necessary for this as I'm sure its in some official manual somewhere, I didn't invent it & have absolutely no Ego to stoke.)

I have used two different methods for the vehicles. 1. Correct 2. Correct (the zone has nothing to do with what STOPS where) 3. It sets off trigger as it enters zone (it doesnt stop in zone) If you didnt use flags then it wouldnt be achievable as shown. A flag is a boolean, i.e. it can be true or false. In a programming language flags are usually alphanumeric e.g. x . In the DCS MissionEditor flags are numbers. So each number can be true or false. You can utilise these to good effect when constructing a mission. Google boolean flags as see some explanations if your still not sure.

just select it in GUI Templates & press the X next to it ?

A quick mission example. First take a look at the trigger actions in the ME GUI. then .. click on each unit -> ADVANCED -> click on HOLD (HOLD is an option accessed from PERFORM TASK menu.) HOLD has a Condition & STOP Condition. Click on STOP CONDITION on Unit#2 you will see I have ticked flag and set number to 1 (unit#1 just has HOLD without any conditions as we are using GROUP RESUME in trigger actions) In the GUI Trigger actions you will see I set the flag to 1 when unit#1 entered a trigger zone. Hope thats clear. hold_move_on_trigger.miz

or MISSION START -- RANDOM(100) -- groupname AI OFF ONCE -- flag number true -- groupname AI ON however the units will be dim until they start moving (i.e. they will not defend themselves or engage enemy). If you want them to stay active then use HOLD command (in advanced tab) as Speed mentioned with condition STOP on flag. (btw flag must be between 0-100 in this case), or use HOLD without any conditions and in triggers use ONCE -- flag number true -- GROUP RESUME groupname

Heli's are a major pain in the a*se in A10c if you ask me. When activated they cause ridiculous lag and as you have found out they are buggy as hell.

Read with interest. Have to say though why is it that people assume the reason a company went bankrupt/stopped trading etc was due to the inclusion of a DC in their software? I would say there were a hundred other reasons & quite likely the inclusion of a DC is way down the list. But then I too am making an assumption here, in reality only the MDs and Directors of aforementioned companies know for sure.

The reason for the 40x40 map is due to the limitations of the leadwerks engine that they are using for development. Richard 'Flex' will be looking towards a newer engine & incorporating other engine technologies (e.g. he has just purchased a Grome3 license). The main stumbling block is financing. They intend to release a working version on the Helo along with a U.S. based firing range & terrain map first to finance further development whilst he works on the DC and the Afghan map. He then intends to release further modules to Combat Helo in the form of new Heli's the first being the ch47. The MP will be Coop only. The Apache will be 2 player coop or 1 player + 1 AI. Richard is immensely knowledgable of the pc games industry & has a canny knack of knowing what works & what doesn't. I wish him well with this project. It is definately shaping up v nicely.

yep that checkbox hasn't worked since beta. As long as you just uncheck it the once it should work even though its ticked again next time you check it. Confusing eh! I usually set flags to true when I want to do something though as opposed to the other way around. Makes it easier when debugging if you stick to one method.

Given the amount of changes in this changelog & if it doesnt break too much then maybe they will have a little time to look at MP Comms, i.e. JTAC,AI, F10 Menu. Whilst also working on BS intergration. At least .. I hope so.

Hmmn yep looks like you could be right there Shagrat. The only thing is you might find the travel (full left to full right + fwd to back) may well be a lot less in aircraft than you have with extended WH. The last picture might show full right aileron. Difficult to know for sure. Could always mimc this with DCS curves though I suppose.

Now this is starting to sound very interesting. Wish I had to the time to contribute. ^ I really couldn't agree more.