dmatt76

Ok. I got the answer from Wags:

Regarding last Viper Updates video - does anyone know what are the ACTION and CHECK OFF values in the manual bombing mode table?

I know, I'm not asking what it is. I've just noticed that if don't touch any bomb settings, the hangar will collapse in big explosion after the bomb hit. If you change AD from 0 to any other value, the hangar is OK after the bomb hit - nothing happens.

Made a few runs against hardened shelter. GBU-24 penetrates it only without touching any options on MFD. Changing arming delay even 0.25s and the target will not be destroyed. TRK included gbu24 delay bugk.trk

So, the AD for GBU-24 should be 0? I tried a few times with 1 or 2 seconds and the bomb did not destroy a hangar shelter - went through with no effect or made a crater next to a hangar. the only damage I saw so Far was when the bomb didnt follow the laser and fell down on random buildings in a city…

After last update airspeed on IHADSS shows "0" even when the chopper is speeding up forward, what velocity vector shows. Speed starts to rise above 0 with noticeable delay, after the gaining quite a lot of speed

I have checked right after the April patch. The only fix is that the shaking ends only when the rotor stops spinning and it's no longer present after reloading the flight. If a broken rotor keeps spinning even with the lowest speed, the cockpit still shakes like crazy. I don't know it if it is intended but doesn't seems realistic...

You have previous AI model of the Apache with FCR and without. Work well as just a static.

Thanks!

I was checking the TSD ->Show->THRT SHOW options, but couldn't see any difference or new symbols with VIS Shades, VIS Threats, Rings... Are they for FCR only or not implemented? Quick Guide describes them without N/I as working already....

Thanks for explaining it! Also, I think there is a bug in loadout menu. We don't have M274 training rockets, as marked in mission editor, but WP - M156

Edit OK, did more testing while in pause, and while you cant really tell the difference looking at the i-beam with M7.5 and A2.0, there is a huge difference where the rockets hit!

Exactly, so if the ranging source does not affect that, so what does it affect? What's the difference if I choose the A method and see A2.5km or choose W02 as acquistion and see 2.5KM to the source? Seems like A should be the prefered method with pilot's solo run.

I know you can set: nav range manual range auto range but after many test runs I couldn't really tell the difference between those three. i-beam seems to have its own life anyway but it is always around LOS reticle, the rockets hit somewhere around LOS reticle regardless of the setting... Is it only affecting the limits of firing because of max range (7.5km for rockets)?

I am also experiencing worse performance with PNVS. It is not a lag or anything intended to simulate how it works, just normal frame drops. Everything is fine with regular NVG goggles, but with FLIR is getting below 20fps.

No, it is not just a keybind. Apache uses brand new pilot models, so it requires a complete set of body 3d meshes and animations while on the ground. You need standing pilot and CPG, walking, etc. Maybe they add it after releasing upcoming new models of ground units...

I'm struggling too. I can make everything centered but it requires a lot of twisting head and body and the accuracy is always wrong. I did some trials and errors run and managed to get a good accuracy from gun in the middle of the reticle, but te circles in boresight were a complete mess.

OK I did some testing and it works only, when after "LASING" from JTAC I switch seats and activate Hellfires again in that seat. Then I can see on IHADSS that Hellfire got lock. If I stay in the same seat and wait, nothing changes on IHADSS, however the missile will still hit the target, but SKR acq works ony with switching seats

Thanks. So that's how it worked that one time, without touching LT button.

I'm trying to master Hellfires with JTAC. Missiles hit the targets with no problems but I can't get TADS camera on the lasing spot. I managed to get it ONCE - hit the slave button and camera went for the target - slighlty off, but still (screenshot attached). And dont know why it worked that one time. Now when I'm trying it goes all the way back, trying to look behind the chopper, in the sky, bal limit everwhere... After lasing I go with: sight - TADS acq - SKR LT - AUTO Slave Is it right or I missing something?

Made a couple of runs and: - MGRS for CM52 holding area in briefing is misspelled - should start with 0313 - not 3013 - last TGT mgrs with KNxxxx in briefing seem all wrong since CV and CA are all around? - Greeting message and text appear long after all preparations and take off - Pilot George AI can't keep altitude - gradually going down every time

I have that too -it is easy to check when you boresight the HDU. Without TrackIR or VR you need to move the camera sideways to center align with boresight. On the other hand, the CPG boresight is a bit to the right, so maybe that's how it should be.

There is a mod with ISIS and Technicals https://www.escuadron69.net/foro/index.php?%2Ftopic%2F71654-mod-isis%2F&fbclid=IwAR2yrKl-PoF-QC10rwNWtARdRaNzNV5gQN3WV20ldRPV6Iwwx6OJDwOalhM

Yes, it shows the "TO from the ground" which is as in description and basically "from a hover" what I see but still, the b. take off is confusing if you start from pushing cyclic forward. The AI Apaches in DCS t.o. with a bit of roll on the ground before lift.

Because the quoted descriptions say opposite or don't say everything. a. describes starting a hover b. describes starting from ground, unless you are supposed to go to a hover first, which is not in a description