Jump to content

Mo410

Members
  • Posts

    58
  • Joined

  • Last visited

Everything posted by Mo410

  1. That's the CIT operating status, try turning your CIT off and see - it may still be a bug.
  2. Undes/NWS should cancel AACQ - I don't think I have every used AACQ in TWS, so probably the same deal. Also going through Boresight should cancel it as well.
  3. You don't, it is just one of those short cuts that can be done. I never found it particularly useful, just use the trim switch.
  4. It should be IN TEST if you push FCS and hold the consent switch, since you are commanding it. If you just push FCS without the consent switch, it should be RESTART, self test (SF TEST) is not something you would expect for an FCS I-BIT where you have asked it.
  5. Just for clarity, the AOA probe on the right side of the aircraft used to be identical to the left side, but it would get snagged in the refueling basket. They changed the design to a less intrusive design and it does indeed rotate the full amount. The probes measure their rotation, the aircraft compares what it thinks it should be and uses a blended answer unless you manually select a probe (like you would in the event of damage to one). The original question is about selecting a Memory Inspect Unit/Address on the Bit page and inputting the value that would correspond being trimmed to 8.1 degrees AOA with full flaps and gear down, provided you didn't change the trim manually once set - Navy guys would remember the numbers. A short cut method would be to trim full nose up in Auto flaps prior to the break and then it would be pretty close. Not sure if this last bit is working in DCS, trim always seemed a bit off, as it seems you are always trimmed upon gear down, where in reality you need about 3 seconds of aft trim to get in the ball park once gear and flaps are selected.
  6. So I would expect any lock out of an auto acq mode, including gun, boresight, or AACQ to immediately dump everything except the track it is try to lock. Upon exiting STT after entering from an ACM mode, including AACQ, I would not expect to see any track files immediately, but would expect the Link / interrogator tracks to reappear shortly afterwards for link, and after a CIT hit (not in this case though). Radar tracks would return as the radar processed them. The looped gif is a bit difficult to interpret. I'm on the fence if AACQ should behave this way since it is very rarely used at all, it may be a bug - what is shown is how it would work from an ACM mode.
  7. He used AACQ to get the lock, I would expect the radar to operate as depicted. A normal STT command, should retain any trackfiles until they age out. And it likely changed from OFP to OFP. I haven't tried it without AACQ, so maybe have a look and see if it still clears it out.
  8. RAID is for when you are unsure of the numbers in a group and want the radar to use some of its processing power to try and figure out if there are more targets in the location of the L&S. EXP is simply an expanded view of what you have. So if you have the contacts you want to shoot in TWS and they are closely spaced: shoot the L&S, hit expand, enjoy a zoomed in view as you step to the next target to verify it stepped correctly and shoot again. What is supposed to happen with EXP is that as you shoot in EXP, it automatically exits EXP and returns you to the scale you entered EXP in. If you need to let the radar do some work, TWS RAID to get your track files and then shoot both. It won't automatically exit RAID, so you should do so in order maintain SA on the radar azimuth. Both are similar, just different uses- if you have it all sorted, EXP to make sure it steps correctly on closely spaced track files, if you need to break the targets out, RAID until you have your targets.
  9. When the HMD is turned on, the radar and seeker FOV are slaved to the HMD line of sight if AIM-9 and HACQ are selected (just using this particular scenario). The pilot can uncage the seeker on the target using cage/uncage or let the radar lock the target and then the seeker will begin to track the radar's target provided a few things are met - but in general, it tracks it. The pilot can then cage (one push) the seeker back to his/her HMD and the seeker will track the HMD LOS while the radar tracks the target until uncaged on another target or if no target in the seeker FOV, an uncage will send it back to the radar's target and attempt to track. At no point does the HMD radar acq circle or AIM-9 seeker snap forward to the HUD and back to 'normal' boresight when the HMD LOS is calculated to be through the HUD or 'blanked'. It works like you think it should work, and the seeker LOS is controlled by the cage/uncage button when there is a track. Current implementation is incorrect, not necessarily a bug.
  10. Not necessarily, not at 400 knots. It will be bleeding quickly, and you may, depending on your technique, go below the airspeed required to achieve the maximum G. Any rolling moment will reduce the G available as part of the limiter. Start at a higher speed, 430 - 480 and you should be able to attain it within about a second and change.
  11. More for a hot start, where you go cutoff at day, 45 percent, and since you are required to motor the engine for two mins, you need to wait until it is below 30 percent before engaging the crank switch.
  12. No, its pretty finicky near the edges of the mapping of the cockpit. I would say it is pretty close. The only thing that would be better is if they fixed the centering that happens when you have your LOS in the HUD. The radar and seeker should always remain slaved to the HMD LOS, even when looking through the HUD. If this was the case, I think the annoyance would be reduced. There are still a few symbology issues.
  13. Correct, and your Checklist page should tell you your gross weight.
  14. No limit to cranking, just don't engage it above 30% RPM or you risk a shear of the ATS, not sure if this is modeled, unlikely is my guess. Just air until the APU runs out of fuel.
  15. No, just add power and climb away. Once climbing, clean up. You will be trimmed for on speed, which is fine for the climb out.
  16. Laser codes remain changeable and do not depend on master mode selection. That being said, this is more of a pod interface thing so nothing is absolute there. But why not make them changeable since they clearly are here.
  17. You need to debox ACM (PB7) to regain control of where the TDC goes, otherwise the aircraft wants to keep providing ACM modes to you.
  18. Yes unless you select trigger laser, then it remains armed. Used to be an overheat issue with some pods, but no longer with the newer ones, but the logic remains. Always do MALT check, master arm, A/G mode, Laser, TDC assigned to correct display.
  19. My impression with my actual IPD set, it feels pretty close. IL-2 always seemed a bit small, but DCS is close enough for me.
  20. Laser codes can definitely be set on the ground or air, both LST and LTD, same with IR marker and IR marker pattern. The UFC just has LTD above LST, and entry is fairly straight forward, colonize and enter the code and the Enter. Codes range from 1111 to 1688, with only 1511-1688 being useful for LGBs, the lower codes - I believe - are more suited for helo's and their weapons. This is to say you could set something lower than 1511, but it would be impractical, and I have never seen it tasked or used - not sure exactly what <1511 is used for, never had the chance to use it - it definitely accepted the input. Laser codes are mission critical, so it must be set prior to takeoff to minimize risk of error, and even still there are errors in codes and IR marker / Trg laser. Similar to A/A radar presets, which have now been fixed.
  21. A/G gun symbology is always shown when selected on the stores page first. The radar will range through the pipper when suitably below the horizon and display AGR, even if there is a designation. Priority is to range through the gunsight even if the TDC is elsewhere (like the FLIR).
  22. I think the more pressing concern is that the CCIP cross is present with a designated waypoint. This should not possible for bombs, and needs to be fixed. If there is a designation, there is no CCIP cross, CCIP mode acts like AUTO until undesignated, at which point it reverts to CCIP. This seems to happen when you cycle the mode from AUTO to CCIP with a designation, but could happen at other times, such as when the FLIR is tracking and you undesignate. The FLIR continues to track when it should go into a stabilized snow plow.
  23. Try turning the blanking off, you may prefer it, just need to look under the HMD symbols when looking through the HUD.
  24. It works the same with the exception that the AIM-9 reticle (if selected) and the radar boresight never center when looking through the HUD, they continue to be slaved to the HMD line of sight. Otherwise pretty close.
×
×
  • Create New...