Jump to content

jcagle

members
  • Content Count

    787
  • Joined

  • Last visited

  • Days Won

    1

jcagle last won the day on February 15 2016

jcagle had the most liked content!

Community Reputation

180 Excellent

4 Followers

About jcagle

  • Rank
    Privat Pilot - SEP

Recent Profile Visitors

5703 profile views
  1. Everything dfw said was spot-on, just a little more background. The spoilers are electrically driven, while the rest of the control surfaces are hydraulically driven. This means the spoilers have unusual deflection schedules (and rates) since they can be programmed/computer driven. On the ground, only the inboard spoilers deflect to prevent the electric drive system from overheating. With flaps down, inboard and outboard deflect for a controls check prior to take-off, and they operate normally with weight off wheels.
  2. The IP addresses need to be entered before starting the sim. By default, go to your Start Menu, then Aerosoft F-14 Extend -> F-14 Shared Cockpit Configuration If the shortcut was not added for some reason: Go the selected installation directory: <user selected path>/Aerosoft/Aerosoft F-14 Extended/Gauges Open "AS F-14 Shared Cockpit Configuration.exe"
  3. I can answer at least the installer and TacPack portion of this thread. Externally installed add-ons is the direction that LM is pushing, though different development groups have adapted the methods to various degrees. Prepar3D v3 is just as capable of reading externally installed add-ons as v4, but it wasn't until the 64-bit version came out that it really caught developers attention (E.g. A2A, FSDG). We worked with VRS to get the external installation functional within v4 and v3, but it meant that an update to the TacPack was required for v3. The last I heard, the v3 update of the TacPack to allow external add-ons (and recognize the Kitty Hawk) was going to be released at or after their v4 version. If that hasn't happened, it certainly explains why the loadout manager and KItty Hawk aren't working. I can ping the folks at VRS and see when the update is planned. My guess is that it's a little ways out since P3Dv4.2 was released and they are probably working on it's compatibility patch for the TacPack as a whole. In the interim, I would suggest running the F-14 in P3Dv3 with TacPack turned off. I've also brought up the installer issue with Aerosoft to see if it can be squared away so that the v3 files are placed in the correct directories.
  4. Have you checked the Mini-HUD [Shift+1] to make sure that you're in Zone 5 and not 4? If there was a throttle calibration issue, it could be that the final detent is not being recognized.
  5. Well that's one person fixed, and working with Starbuck over PM. Will post here if anything is learned that affects users as a whole.
  6. I'm a little confused, though maybe this is just bad memory. - When you say that the Nose Strut won't kneel all the way down...does that mean is starts to kneel and then stops? - I don't recall releasing a hotfix for this problem? Can you please describe the problem in more detail? E.g. Are you (first) trying to compress the gear with the VC switch Nose Strut - Kneel, or are you simply pressing toggling the Take-off assistance ARM keypress [Shift+I] and letting the gear compress while it attaches? The default test flight that I use is a carrier flight, so I've literally performed hundreds (if not low end thousands) of CAT launches with the F-14. The only memory I can really pull up on this, is that the an carrier is an AI vehicle and if the frame rates are low or unstable then it can cause bouncing between the F-14 and the carrier that really causes problems with the CAT attachment.
  7. The ramp movement that affects the location of the shockwaves is quite small, so the difference between subsonic and transonic ramp positions is easy to miss [first image]. Larger actuations of the ramps happens gradually from transonic to the very high end of mach limits [second image]. Faster actuation (i.e. larger displacements and lower Mach) would starve the engines of air and have a notable impact on thrust.
  8. The transonic effects on the altimeter and VSI were modeled on Mach ranges, frequencies, and magnitudes provided by an F-14 driver who flew multiple tours and had front and back seat flight experience. He also provided similar input for perturbations from the refueling probe (which are notably smaller if I can remember correctly). It seems it’s a quirk of the airframe.
  9. I believe those are all present, this is the list from the lua file itself: -- 270 RIO Stick Input Inc -- 271 RIO Stick Input Dec -- 272 RIO Stick DDD Cursor -- 273 RIO Stick TID Cursor -- 274 RIO Stick Radar Slew -- 275 RIO Stick FLIR Slew -- 280 TV Mode Knob (CLOCKWISE) -- 281 TV Mode Knob (COUNTER-CLOCKWISE) -- 282 TV Mode Knob TCS -- 283 TV Mode Knob A/C Stab -- 284 TV Mode Knob ATTK -- 285 TV Mode Knob GRND Stab -- 286 TV/IR FOV Wide -- 287 TV/IR FOV Narrow -- 288 TV/IR FOV Toggle
  10. Sure, they've been added at the top of the post
  11. Wait, that actually makes sense, I had the 2D windows flipped in my head. [Shift+8] is the FLIR window for TacPack.....it must not be Prepar3D compatible. Will disable that panel in a future update.
  12. Okay, LANTIRN checklists posted here
  13. Checklists for AI targets are listed below. Steps that vary from Land Targets are bolded to emphasize the commonality of the checklists. AI Targets (AIR or Ground) Pilot Seat 0) Configure main flight controls (e.g. set AP if desired) 1) HUD Mode → A/G or A/A (match to target) [Note #1] 2) VDI Mode → TV 3) Master-Arm → ON [Note #2] RIO Seat 4) Switch joystick to rear seat (CRTL+F) 5) Rio Stick → IR/TV 6) FOV → WIDE 7) IR/TV Mode → GND Stab or A/C STAB (as desired) 8) Contrast & Bright → Desired 9) WPN TYPE → MATCH ORDNANCE 10) Coarse Target Select → RIO Stick 11) FOV → Narrow 12) Fine Target Select → RIO Stick 13) G1000 MFD Select → Single Pull (Initiates IR lock/track) [Note #3] 14) VRS Trigger → Single Pull (assigned key or button) ** Target selected ** **G1000 MFD Select [Key] will de-select target** **Land Light Home [Key] will de-select target and reset LANTIRN position** 15) VRS Pickle → Single Pull (assigned key or button) ** TREL = 0 AND LANTIRN BRG = 0 ** ** Fine-adjust RIO stick inputs will NOT update guidance until impact** Pilot Seat 16) Switch joystick to Front seat (CRTL+F) 17) Dive to keep LANTIRN seeker within FLIR mask ** Due to tracking limits within the VRS TacPack, you must dive maintain a track on an AI target ** -------------------------------------------------------------------------------------------------------------------- Note #1 A Target's type is decided by the "Weight on Wheels" criteria. E.g. An aircraft is not an airborne target until wheel are off the ground. Note #2 It is not possible to guide ordnance toward airborne targets (for hopefully obvious reasons). However, the LANTIRN can track them just as well as ground targets. Note #3 With a Land Target, the IR lock/track is applied passively when the RIO stick is returned to center
  14. Hello All, As requested, here is an unofficial checklist to drop and guide ordnance with the LANTIRN. You can download these checklists here: Vol 2 - Checklists.pdf Setup - Use payload manager to install desired payload (GBU-12, GBU-10, GBU-31, or EMPTY) - If the payload selected on the ground is empty, the LANTIRN will operate in training mode (after take-off) and simulate a drop using the exact same proc as with live ordnance Land Targets (i.e. patch of dirt) Pilot Seat 0) Configure main flight controls (e.g. set AP if desired) 1) HUD Mode → A/G 2) VDI Mode → TV 3) Master-Arm → ON [Note #1] RIO Seat 4) Switch joystick to rear seat (CRTL+F) [Note #2] 5) Rio Stick → IR/TV 6) FOV → WIDE 7) IR/TV Mode → ATTK 8) Contrast & Bright → Desired 9) WPN TYPE → MATCH ORDNANCE 10) Coarse Target Select → RIO Stick 11) FOV → Narrow 12) Fine Target Select → RIO Stick 13) VRS Trigger → Single Pull (assigned key or button) ** Target selected ** **G1000 MFD Select [Key] will de-select target** **Land Light Home [Key] will de-select target and reset LANTIRN position** 14) VRS Pickle → Single Pull (assigned key or button) [Note #3] ** TREL = 0 AND LANTIRN BRG = 0 ** ** Fine-adjust RIO stick inputs will update guidance until impact** -------------------------------------------------------------------------------------------------------------------- Note #1 Master Arm → ON is at Step 3 for continuity in checklist flow between front-seat and back-seat. In practice, the the Master Arm can be set on immediately prior to the ordnance drop (just prior to Step 14), it has no effect on the LANTIRN's operation. Note #2 I prefer to use a hardware joystick, which requires switching control away from the front-seat. However, the landing light directional keys work in single player to control the RIO stick. It is therefore possible to control the flight stick and the RIO stick simultaneously. Note #3 If the GBU does not appear to strike the target, the tool TacView is very useful in determining what happened. More than once in testing, an hit to a static (non-ai) target that did not render visually in the simulation what an actual hit.
  15. Hello Peter, Answers to your questions: 1. No idea on this, I have not experienced this before 2. Okay, it's changed in the manuals for the next time they are uploaded 3. If I can remember correctly, sometimes is takes a sim restart for the smoke effects to turn off. I've always flown with them off (for the same reason on the ground). 4. The SimObjects directory is the back-up location of the manuals, since people are bound to be in there is adding a livery. The main location of the manuals should be in Prepar3D main/ecosystem/Aerosoft, additionally there should be a shortcut to the manuals in the Windows start menu under "Aerosoft F-14" along with the link to the IP config for shared cockpit. From what I understand the ecosystem directory is the common location for all Aerosoft's manuals in Prepar3Dv4.
×
×
  • Create New...