Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Needs some work though: with those beers near the end, they don't actually start a plane wash until the plane is on deck! :megalol:
  2. I haven't uploaded the patch yet. still testing things. If what you say about the mi-8 changing stations is true, though, I'll look into that as well. I know stations 1 and 2 are reversed in the mi-8 compared to the Huey, but is it actually changing from left to right seat and vice versa whenever you release trim? Could you please upload your cts.dat file so I can try to duplicate the error?
  3. When TrackIR is paused, Hat1 maps to POV by default and trim is S3+Hat1.
  4. In addition to the Emergency Wing Sweep Handle cover (which is in now), I would like to see key commands (and perhaps axis) for the emergency wing sweep handle up, down, forward and aft.
  5. Looking further, part of the routine in releasing the trimmer is to make a Station Check to properly remap TG1. Since I added WAV to the StationCheck() routine, this has apparently made its way to helos as well. I have added an argument in the function to suppress the wav, and applied that to helo trim. Please let me know if there are other occasions where the wav file plays (other than direct station change) so I can address those routines as well.
  6. That's really weird. What you describe sounds possibly like a corrupted database. It certainly doesn't have anything to do with TARGET itself. Delete the CTS.dat file in your CTS folder (and not CTSn.dat in the DB folder), then try building a script, changing only your hardware (i.e. setting your HOTAS and head tracking). See if this populates the values where they need to go.
  7. Fellas, you may want to check out the Virtual Armed Forces. They have a few members in the PNW, including BC. This weekend they're publicly hosting one of the dynamic missions we (VAF and BVS) created, so you can jump on and see how you like the guys. We (the Black Veal Squadron) are also looking to bring people in. We fly with the VAF all the time. If you're interested in the F-14 RIO position, I'm happy to train people up as well.
  8. I can't imagine refueling without adjusting the seat height; it's the only way I can maintain sight picture on the tanker pod. What I like to do is put the HUD in cruise mode, then move the seat down so the heading tape is level with the metal sticking out on the right "prison bar." This gives me a sight picture where I can keep the pod in the forward glass and the canopy rail just touching the tanker's wing root. The graphic below is mainly to show you where I adjust the seat (i.e. where I match the heading tape with the right prison bar). This isn't a great sight picture (I'm high and behind) because I had to take my hands of the controls to do an ALT+PrintScreen.
  9. Coming from you that's high praise indeed! I know we've had a lot of fun with your missions as well. :thumbup:
  10. The UH-1 and MI-8 do not have progressive trim, so the trim hat should only be used to change stations or use POV/padlock. Use H4P (or H4U for Cougar) to do trim. You should also read the section of the User Reference on TARGET Central Position Trimmer Mode (TCPTM), which is a giant improvement over the in-game trim system, but requires that you deselect "Central Position Trimmer Mode" in DCS Options.
  11. Version 2.49a (Hotfix 1) is available. Change Log: Added S1 VR Zoom to P-47, F-86 and F-16 F-14: Added error trap for pilot LANTIRN Mode P-47: Added pylon arm/disarm twist knobs to LMFD F-86: Fixed airbrakes and misc keybindings Updated bindings since 2.49: P-47, F-16, F-86 Updated Custom Luas since 2.48: F-86
  12. Make sure you build the script from the GUI prior to launching it. What I see in the spoiler text are empty sections where there should be values populated by the database.
  13. I just noticed on the F-16 that the texture for the left shoulder has been reversed. This has obviously been introduced in a recent update. My question is whether this is temporary, or whether I should start reversing my left shoulder patches on my own textures. Here's an example of what I mean:
  14. For the comm plan, feel free to use the included graphics for your kneeboard. In general, we'll use VHF (i.e. alternate) frequencies for coordination to accommodate aircraft like the A-10 or F-16 that don't have two dual-band radios. We use UHF for ATC and AWACS/Tac Common.
  15. Full trigger is designate, but you have to hold half trigger to keep the laser on. You can also map Latch Laser to your HOTAS, which is what I recommend. It keeps the laser on until you half-trigger and release to stop firing.
  16. Save your $. :thumbup: Here you go!
  17. S1 is the button on the right side of the stick (the MMCB in the A-10C). As for the nomenclature, this can be found in the Thrustmaster folder where each controller has a PDF that shows what the names are. Assuming you have TARGET installed to the default folder under C:\Program Files (x86), the PDFs are hyperlinked in the User Reference under the section near the beginning titled "Naming Conventions." I didn't do any code changes to the F-16 or F/A-18, but VAICOM Intercom is set to DX30+DX21 (which can be keyed with S3+MSU if you use the DirectX PTT). CTS 3.0 will have dedicated, unmodified DirectX buttons for ICS and VAICOM ICS. I"ll look at the JF-17, but I need more info. Do you have SRS and/or VAICOM enabled when you run the JF-17? Also, I assume you're using the Warthog Throttle and not the Cougar TQS, right?
  18. Yeah, that sucks, and it happens when a target either notches or is on the edge of the scan zone. That's where TWS Auto helps to automatically adjust the radar to keep as many targets in the cone as possible. Personally, I'm more inclined to mark targets as friendly to take them off the shoot list than I am to mark targets as bandit. A quick IFF to make sure datalink isn't lying, then send out the foxes. I'll designate at first if I have time (or if the target isn't datalinked as well), but as long as the data is out there and I know what I'm shooting it's all good. Of course, this also assumes that the targets are coming from a hostile threat axis (i.e. "Outlaw"); any friendlies in the scan area and to paraphrase the carpenter's mantra I interrogate twice, shoot once.
  19. 2.49 is released. Change Log: Updated UH-1 and P-47 for DCS 2.5.6.53756. P-47D: Applied Water Injection indication (Warthog Throttle LED1) for all holding and locking permutations (Warthog Throttle). P-51D/I-16: Restricted WEP use to SC when Afterburner Detent not installed (Warthog Throttle). F-14: Revised context sensitive Cage/AutoThrottle to be tied to logical Gear State with TEMPO to allow Cage while gear is down. Updated Autopilot/Altitude Hold HOTAS mappings. Added doubletap hold function to VR Zoom for S1. Note: The S1 as VR Zoom on the F-14 is a trial run for what is likely to be a global routine for VR users in CTS 3.0. S1 default functions will be shifted for VR users. I intend to remove the H1U doubletap function in favor of S1. VR users please provide feedback. Known Issues: Very close to stack limits. If you receive a full stack error, report it ASAP. P-47 gun safety switch toggle does not work (module side issue) H2U set to Arm discrete command for time being. Updated bindings since 2.48: UH-1, P-47, F-14 (pilot kb)
  20. Cold Start Israel mission in 2.5.65.54046 started like this: Apologies if the screenshot is considered NSFW by some. :lol:
  21. One common mistake at first is believing that the datalink track is a contact. What you may think is a contact is in fact a datalink track. If the HAFU symbology was the underside of a shape (e.g. a V or bottom half of a diamond instead of a ^), then this was a datalink track and not a radar contact. Datalink tracks are great because they show you where to point the radar (and you can hook them to get a more precise altitude), but they are not actionable. Any radar contact will show the shape on the top half instead of the bottom half. If you don't designate friendly or hostile, the shape will be the top half of a square, and designating friendly or hostile will make the shape the top half of a circle or a ^ respectively. Ideally, the radar contact corresponds with your datalink track, so when you designate it hostile you see a full diamond (i.e. the radar half and the datalink half making one shape). Bottom line: see the datalink tracks, slew your radar until you can see radar contacts correlating with the tracks, then let the AWG-9 sort targets for you. Again, if you have a mix of friendly and hostile tracks, you will want to hook each radar contact (not datalink track) and designate them friendly/hostile to manage your target list.
  22. Version 2.5.64 is released for DCS 2.5.6.54046. I couldn't duplicate the error. It may be OBE with 2.5.64, but please let me know if you get this again.
×
×
  • Create New...