!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

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

5751 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. 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
  5. Sure, they've been added at the top of the post
  6. 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
  7. 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.
  8. It's time to Call the Ball for the F-14 Extended v3, and before release we wanted to set out appropriate expectations for the updated package: Important Notes - The update is free for all existing owners of the F-14 Extended - The file structure has been redesigned for the newest versions of Prepar3D, and is only available for P3D v3 and v4 - In single seat option, the package is fully compatible with TacPack (P3Dv4) out of the box, Kitty Hawk and all. Special thanks to VRS for working so quickly to make this happen Shared Cockpit - Shared cockpit is the major new feature of the F-14 Extended v3 (aside from P3Dv4 compatibility), and special thanks to Jon Bleeker at MilViz for making this a reality - Please read the attached instructions below or your first hop as a RIO will likely have connection issues - Shared cockpit is mostly compatible with TacPack. All major functions work, but both the Pilot and RIO have separate payloads. We are working with VRS to try and find a solution - The F-14 uses many custom variables, and we tried to 'accident' proof the cockpit as much as possible, but it is not prankster proof. E.g., It is not possible for the RIO to operate the flaps, throttles, etc. It is possible for the RIO to use the mouse to flip switches in the front seat. Setup Note - Shared Cockpit.pdf Improvements - All models of the F-14 recompiled in P3Dv4 native format - Aircraft exterior lighting has been improved to not only be more authentic in color and signal, but to also make use of light cast available in P3Dv4 (image below) - GPS track (patch of dirt) for the LANTIRN has been reworked such that all inputs are ground relative rather than aircraft relative. This should make inputs from the RIO stick more controlled and precise - Subtle improvements for the TCS system, particularly in the PLM radar mode - Almost all of the controls had to be split and sorted to handle the implementation of shared cockpit; improvements (to single player operation) were made when possible. This was mainly in consistency of control input and custom sounds. Image: New exterior lights with light cast Limitations We have tried to make improvements on the Kitty Hawk's FLOLS lights, however, the issue appears to be in the way P3D renders light effects. As the ship is further and further away from the F-14, the visual model of the FLOLS board is rendered as being physically in-front of the light effects (image below). This can be overcome to some extent by offsetting the position of the effects, however, at some distance the board always obstructs the light effect. We have supplied a selection of effects so you can choose the offset that fits your flying style: 0.2nm visibility - Light effects true to light bulbs 0.4nm visibility - Light effects offset 2ft from bulbs 0.7nm visibility - Light effects offset 5ft from bulbs 1.1nm visibility - Light effects offset 10ft from bulbs - The lights are located in the Main F-14 installation under Aerosoft F-14 Extended\Aerosoft\F-14A\Alt FLOLS Lights - To install, copy/paste the desired effects into the Aerosoft F-14 Extended\Aerosoft directory Image: As the F-14 is further and further from the carrier, the visual model of the FLOLS board will eventually be rendered in front of the light effects
  9. TacPack is not presently compatible with P3Dv3.X, only v2.5. In theory the F-14 Extended will be compatible with TacPack v3.X when that version is released...but we won't know until then. It is fully compatible with the P3Dv2.5 version of TacPack, even including P3D's pseudo-IR video feeds for the LANTIRN.
  10. Thanks all for the kind words! - For the throttle issues, please start a support thread. Would be great to know you sim version and that the instructions from Vol.3 page 3 are being followed. - Mathijs will hopefully have an answer to the 3rd party shops question, I'm purely on the development side
  11. While I can't speak for the other concerns, I can address the rate of climb. We did not use NASA data for anything related to thrust; that data was pulled directly from the flight manual (which was actually quite good). Unfortunately, I think this is a case where I can't confirm the problem. I tried to setup a similar flight, with centerline tank with a 50% total fuel load. This put the aircraft at a gross weight of 9,950lb. In the attached picture you'll see a bunch of numbers, and I'll do my best to point out the ones of interest. (Yellow Box) - I have 237Gal of Fuel. Half of 252 Gal of internal fuel plus half of a 150Gal external tank would be 201Gal, so I'm running a little heavy, (Magenta Box) - This tallies up for a gross weight of 9,943lbs (Red Box) - You'll see my climb speed is 128KIAS. Climb matrix is this: Sea Level (0 Drag) 134KIAS, 5,000ft (0 Drag) 129; Sea Level (50 Drag) 127KIAS, 5,000ft (0 Drag) 123. I'm at roughly 2,350ft with centerline tank, which gives me a drag index of 14. Interpolating the above, and the recommended climb speed is 129KIAS. So I'm pretty close to where I should be (and undeniably nerdy). (Blue Box) - I'm running at 1,713ft-lbs of torque on Engine 1 and a little more on Engine 2, but still less than the 1,878ft-lbs rated at military thrust. (Red Box) - My climb speed is ~2,120ft/min (Brown box) - I have a Newtonian (NET) thrust of 39lbs (Think F=m*a), which means I'm accelerating very, very slowly. All added up; I'm a little heavy with the weight and little low on the power delivery, but still pretty close to your rated 2,300fpm. So, I would that hopefully all you need is a restart and the problem should heal itself. However, it is worth noting for the non OV-10 pilots reading this, that as the weight goes up with a full fuel load, this number will drop noticeably.
  12. Thank you for the kind words. This is probably the most rewarding accomplishment that I could hope to achieve as a developer. I hope it continues to live up to your standards, and please don't hesitate to throw out some suggestions (particularly related to the flight mechanics) if they arise.
  13. I'm sorry I was wasn't clear, I meant you should read it now. I'm awful about reading manuals for any product I buy.
  14. Landing can be a bit challenging, especially is you drop below the recommended final approach speed of 100KIAS. You should definitely read the threads pinned at the top of this forum about some of the unusual flight characteristics of the Bronco. Low-Speed http://forum.aerosoft.com/index.php/topic/50970-bronco-advance-flight-mechanics-low-speed-flying-characteristics/ Adverse and pro-verse yaw http://forum.aerosoft.com/index.php/topic/50981-bronco-advance-flight-mechanics-adverse-and-pro-verse-yaw/
×
×
  • Create New...