Jump to content

Forest Rat

Members
  • Posts

    144
  • Joined

  • Last visited

Everything posted by Forest Rat

  1. My guess would be because when you alt+tab out you lose HDR ... unless they fixed that this patch.
  2. Most, if not all of our A-10 pilots wear ear plugs... can't speak for cockpit noise but it can be deafening on the comm when they crank the volume.
  3. Yeah, that's a shame. I didn't think it'd be possible, but it's something that has always bothered me so I figured I'd ask.
  4. I'm guessing you don't fly with a lot of weather, do you?
  5. I fly in ALT+F1 view a lot but I really hate not having the "tint"... especially on high noon missions. Does anyone know if it's possible?
  6. w00t! :pilotfly: My laptop wouldn't know what to do with a 7800 GTX so if Maler or Cobra has a use for it it's all theirs!
  7. China Hat Forward Long - Default Key Binding "V" Slave All to SPI – Upon command, all active sensors will track the current SPI. If a slaved sensor can no longer track the SPI, it will either track the last known position or return to boresight. This can happen if the SPI source is changed or a SPI tagged TAD symbol is changed. However, a sensor can be set individually to track a different target/object but the remaining sensors will maintain track on the SPI. Then TMS forward short to "lock on".
  8. He was the FAC. ;)
  9. Tusks of Rage Here's my contribution. :joystick: Flown and partly rendered on my Ideapad Y560 with a Logitech Wingman joystick. i7 1.73GHz, 4GB ram, Radeon 5700 mobile. Some of the shots were FRAPS'd at 1/4 speed and then sped up in Sony Vegas due to the abysmal frame rate. The others were done by my brother back in the states. While it's currently not in the cards to upgrade my peripherals this is a great opportunity for me. I've gotten to know and love my Wingman stick but her days are numbered. Thanks and good luck to everyone.
  10. How would one do this with a group of Helos?
  11. I seriously wish you could rewind tracks....
  12. That picture would be of a LAU-88 ... not a TER.
  13. Sure thing - prior to takeoff radio weapons and tell them to drop station 2,3,4,6,8,9 and 10 pylons. Make sure they chrome the muzzle clamp while they're at it. Oh, I almost forgot about the chaff/flare panels. Get the drill... you're gonna be waiting a while. Maybe ED could model a demo bird ....
  14. It would be nice if the following key bindings were added to slew: Up Right. Up Left. Down Right. Down Left. With a standard 8-way hat switch on most sub $100 joysticks it's currently impossible to bind diagonal slew directions to the hat (without 3rd party software). For an example, the bindings for view look include the needed 8 bindings. (Current View Configuration) Whereas slew only has 4 (Current Slew Configuration) You're able to slew diagonally with the keyboard by pushing both directions at the same time, but since you can't do this on a hat the bindings are needed.
  15. Well, I was going for a solution that didn't involve 3rd party software.
  16. The footage looks like it's from Combat Hammer .... Same as this video: "The weapons testing program, known as Combat Hammer, is part of the Air Force's ongoing effort to test weapons systems in training missions that also prepare air crews for upcoming deployments."
  17. I'm well aware... I was simply posting an example of how the slew key bindings should be.
  18. Going off of this video I'd say it's *safe* to say the equipment is capable of slewing diagonally. http://www.youtube.com/watch?v=GMW__1HZ5zQ
  19. Yes .... whether the real HOTAS slew allows diagonal movement would need to be confirmed. Diagonal movement is currently allowed if you use the keyboard and press both directions at once. *shrug*
  20. Does anyone else feel there should be 8 key bindings for slew? With an 8-way hat switch the norm on almost every joystick it would be nice to be able to slew the TGP diagonally (without having to use the keyboard). It could be the same configuration as the view bindings. :joystick: (Current View Configuration) (Current Slew Configuration)
  21. I've tried every possible configuration and this is the only one that worked for me... At my "holding" waypoint I have: 1. Run Script (trigger.setUserFlag(999,true)) 2. FAC - Assign Group ("T-55") It wouldn't work with the script unless I put the FAC task after the script. Odd. :) On a side note, even when I set the FAC - Engage Group as an en-route task he still stopped all FAC function during a "hold". Thanks again.
  22. Yes, he does. I've confirmed this by making the same waypoint that he holds at the final waypoint ... so naturally, he stops without the hold command reports Type-2 in effect as opposed to no tasking available.
  23. Well, I've got a new problem now. While he holds he stops functioning as a FAC and won't give me any targets until the "hold" is released. Anyone know a workaround?
×
×
  • Create New...