tech_op2000

You are certainly correct about the TEDAC mode. If your sight select is set to Gunner sight, the laser wont work you must be set to TADS as Sight. Your Acquisition source should be fine being anything, just as long as the pilot isn't desynced into believing it is slaved when the CPG sees it as un-slaved. I'm glad you got it working better!

I had my other PLT/CPG in discord stream his view. it quickly became apparent that almost all of the relevant settings needed to fire a hellfire had the potential to desync. Then it was just a matter of developing a method to detect each desync and a method to sync it back up while flying. My friends and I haven't found any surefire way to get around the weapon loadout desync in the air(just have to land and rearm) and no surefire way to get around the TADS slave desync. The rest were pretty easy to find a workaround for once we knew they were happening.

It's possible, there may be a minimum time for the account to gain that access.

I believe you are dragging them to the wrong spot. Try the green area here. If you drag it to outside of the reply box, it will do the download thing.

you can just drag the track file into a message here on the forum

That or apparently there is a helicopter server called BSD, Black Shark Den.

If you trim the cyclic way forward with the trimmer, it will actually limit how much aft travel you have available. It may be necessary to initially pull it back a ways, retrim, then pull back more. This can be easily observed in the controls overlay RCTRL+ENTER. Pull it up, then add full forward cyclic on the ground and retrim. now pull full aft and see how far the controls indicator moves.

First, what does BSD stand for? If hellfires are missing their target, there are many different factors that could be at play: There is major desync in this first release of the apache in multiplayer. The pilot is the host of the aircraft, so what the pilot sees is what is actually going to happen, not the CPG! For now, always have the pilot backup what the CPG is doing. Have the Pilot pull up TADS Video and observe what is happening. If the pilot doesn't see the laser is firing or doesn't see that the missile has a laser track, it isn't going to hit the target. If the pilot sees that the TADS isn't lined up with the target, the Hellfire will miss. -Here are a few steps to take at the start of every flight: 1. pilot pull up WPN Page 2. Pilot set laser codes and missile channels, CPG confirm. 3. CPG "weapon select switch" to missiles. 4. Pilot select VID->TADS->TADS 5. pilot enable master arm, and ground override if doing this on the ground, CPG confirm same state of master arm 6. CPG cycle between RF and SAL mode on Missile page 1 or two times then set to SAL, CPG cycle WPN->UTIL->LASER multiple times, then set to On 7. CPG aim TADS at ground in front of the heli where the missile seeker could see laser. Fire laser, check for missile seeker track, Pilot confirm on TADS Video. (If no laser or no missile track on Pilot Video, CPG cycle laser on UTIL and cycle RF/SAL. Cycle Laser Trigger. then retest) Once you have established good missile tracking of CPG laser, you are now set to go engage targets. -During engagement, Pilot should always check video to see if it is tracking what the CPG is doing, I have encountered these problems: CPG enabled LMC and although he is on target, Pilot sees drift. (turn off LMC) CPG fires laser, but PIlot does not see laser firing( recycle laser trigger) Missile doesn't see laser( reselect code and missile channel)(sometimes cycle RF/SAL) CPG sees deslaved TADS but Pilot sees Slaved TADS( cycle slave button, cycle ACQ source, have pilot take TADS as NVS sensor, This one I have had trouble clearing up, often the cpg and pilot just get stuck with opposite slave state) -PIlot should check after missile is fired that he still sees laser is on. If not, command CPG to cycle laser trigger. Missile should reacquire the laser and track. -Some users have reported missiles spinning like crazy when they are spectated in F6 view. perhaps if the pilot is the one that spectates them. It seems from another bug I've seen that there are issues with the heli if the pilot is not in F1 cockpit view. - I would suggest never using the default A code in multiplayer, 1688 is the default code for many aircraft and JTACs in missions. If someone else or an AI JTAC is on that code in the same area, who knows where those missiles might go. Try the above tips out and let us know how it goes. Remember that much of that is to do with desync problems and will hopefully only need to be done temporarily until a patch fixes the desync.

that is correct. If you were to hold pressure against the stick, then tap it to center on a new spot, it would instantly change in force and cause a bit of a jerk of the control. If you held it before moving off its position, you would have no additional force fighting you as you move the stick. This would make it easier to move, and remove any force bumps you would get otherwise.

as gunner, i would recommend mapping the tedac handgrip weapon selector, and tedac weapon trigger. this will mean you dont have to worry about trigger guard. for firing the gun as cpg a few things have to align, master arm must be on, (in multiplayer this means the pilot and gunner must both see master arm on, due to desync) tads as sight source gun selected the gun must be in a position where it can fire, if you see a message right above your high action display that may clue you in to what is out of limits Elevation limit- gun cant look that far up or down Azimuth Limit - gun cant look that far to the side BAL limit- the gun cant shoot that far Man range will tell the gun how far you think the target is away, when not lasing If you lase and fire, the gun will use the laser range.

In the apache, the stick is held in position with magnets at the desired location. holding the trim button turns them off so the stick can move freely. Letting go of the trim turns them back on with the new center position being where the button was released.

on the WPN page or TSD, on the right bottom. you will see ACQ. click it, then select whatever source you would like. Casmo Has a great video on this that he just released. It is from the Gunner's perspective, but much of the ACQ info is similar for the pilot. Some notes not covered there - The pilot will always see his ACQ source. -The gunner will only see it if he slaves his sight with the slave button

As Pilot, the dashed cross (cued line of sight reticle) is your acquisition source. To see where George is pointing the TADS you want to set TADS as your source.

I was not able to reproduce what you are describing here. I am flying at night as gunner: 1. NVS Mode to Norm 2. BRT rocker down to remove TADS Video from IHADSS sight. 3. NVS switch to off. 4. Sight select Switch to TADS (I now have tads control and no tads video in my sight. I am then able to set any acquisition source like normal including GHS

@NineLine I had synchronize controls off during my initial tests. I performed the test again with synchronize cockpit controls on. Same behavior. If in any view other than internal view (F1). the AUTOSTART and AUTOSTOP fails to recognize the APU On. Do you observe this behavior if you go to an external view during an autostart or stop and are in an external view when it tries to turn on the APU?

exactly!

W N Z are artificial zooms to the screen. as opposed to the actual zoom of the sensor, which is controlled by the CPG

It is due to Georges coding. When he has searched for targets and waiting for you to select one, he does a far out zoom, once you give him a target to track, he goes to a far zoomed in view. Probably not too much could be done on the player's side right now, other than get a player CPG.

Edit: Frostycab beat me too it. George can not do LOBL and LO or HI. Since it is the same direction on the hat, you may be switching to LOBL-DIR. (Lock on Before Launch). He also can not go from LOAL(Lock on After Launch) to LOBL if he is set to LO or HI to switch to LOBL, do RIGHT long until TRAJ is DIR, then Right short until LOBL is selected, to go to LOAL LO or HIGH do right short until LOAL is selected, Then Right Long until LO or Hi is selected

AH-64D_IA_CAUC_Ghost_FARP.miz Here is that mission with the only changes being, in trigger intro, text changed: MRGS -> MGRS added MM to the coord.

the main desync your referring to there is the pilot not registering that the cpg as enabled the laser on the WPN->UTIL page. Occasionally this can also be the Pilot not registering that the laser trigger has been depressed, but in my experience it has almost always been the first one. If the CPG has messed with the Laser Code or Missile channels, there could be a desync there aswell. for now, you can do a few things to sync it up. 1. if your messing with the channels and codes, have the pilot do it by pressing MSL on his WPN page. Or at least have him confirm that the changes you made actually took effect. 2. Have Pilot pull up Tads video with Tads symbology on a screen, VID->TADS on right->TADS on top 3. Fire Laser and have pilot report if he sees a lase, If not, go to WPN -> UTIL as cpg and cycle the laser in the left bottom off then back on 4, then Lase again. 5. Repeat steps 3 and 4 until the pilot sees the laser on his tads feed at the same time as the CPG. (it is not uncommon during this phase for the pilot to see the laser on when the cpg fires it with the WPN->UTIL->LASER option off.) 6. select a missile and aim your tads in front and within about 8km then try to lase and see if you get a lock. If not, repeat step 1 and maybe step 3 until you do. It is important to think that anything the CPG does right now could be desynced with the PLT, so all things the CPG does should be verified on PLT displays whenever possible. The desyncs I have encountered have been: Weapon Loadout, Master Arm, Laser UTIL, Laser Firing, LMC Track, Slave, Laser Code, Laser Channel, Hellfire Channel, Door open/closed, Direct To Waypoint, IHADSS Mode(i.e. transition/cruise/hover/bobup) just to name a few. The only one I have not been able to mitigate in the air was the weapon loadout one, that required landing and rearming. The rest I could sync up by just toggling them a few times, in some cases having the PLT toggle it at the same time as the CPG when able.

@BIGNEWYI have duplicated DotChuckles report. If I hold full left rudder when attempting to start engine #2, it has a hung start. this also Happens if collective is up during start, but does not happen if cyclic is fully to one side or back. In the following very short track I demonstrate it failing to start with full rudder, then starting with rudder neutral. Further test had it happening about 75 percent rudder and with me holding the rudder or by pressing the trimmer and having it hold the rudder in. Additionally at the end of the track I demonstrate a potential bug with the parking brake. Set by pushing toe brakes then pulling out handle and releasing brakes. then just tap brakes and parking brake gets disabled even though the lever is still out. Rudder start fail and parking brake.trk

Is that with the left most category set to "General" or set to "AH-64D Pilot" For it to work while flying as pilot in the apache, the main group must be AH-64D Pilot, and the control to bind is called "Info Bar -TOGGLE COORDINATE INITS"

did you go to external view during the failed shudown. and did you not go to external view during the successful startup, and shutdown?