Jump to content

ultraking

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by ultraking

  1. It's not a bug. You need to create a binding for the "target designate fwd". You move up and down the bomb line, and then press that button to put the caret over the target.

     

    I've done it many times and it works as described.

     

    Just to make sure we are on the same page, I have submitted a screenshot. This is the button that I have designated on my stick and have tried numerous times to make work with no success.

     

    https://imgur.com/a/Y0MBvhj

     

    Is this the binding you are talking about? If so, it does not work for me. It DOES work however for PAL in A/A mode so I know the keybind itself works. Keep in mind, just because it works for you doesn't mean it isn't bugged for someone else. Especially at this stage of release.

  2. Bailey, one more issue. I can get chief to connect the ground power but not the air supply. I am trying to use "Chief, Hook us up". It will turn on ground power but never mentions air. I have also tried "Chief, connect the air" and no joy. All my keyboard commands are default and I have unbound F11 and F12. Any idea?

  3. Quote from the manual :

     

    To designate a target the pilot steers the aircraft in azimuth to place the target along the BFL. Then
    UP/DN
    on the target designate switch on the left wall of the pilot cockpit is used to slew the target designator along the BFL until it overlays the target. At that point
    the target is designated by pressing the target designate switch to DES
    .

     

    After designation the target designation diamond becomes stabilized to the designated position on the ground and the AN/AWG-9 is slewed to it for range measurements. The BFL now remains overlaying the designated target while the store impact point pipper and aircraft velocity vector continues to follow aircraft movements. In addition the HUD now displays the upper and lower solution cues on the BFL.

     

    So, in essence :

    1. you steer to align the Bomb Fall Line with your target
    2. you press DMS forward or DMS aft to move the caret on the Bomb Fall Line and place it on your target
    3. you press DMS right to ground stabilize the caret over your target
    4. you fly a standard CCRP approach and maintain the Weapons Release button pressed to drop the bomb

    Except it doesn't work for me or one of the other guys I play with. I have checked all the bindings and can slew up and down all day long but it will not designate/stabilize. I guess this must be another bug.

  4. Ok so here is a question. I was doing one of the missions that is included with the cat. It's a mission to blow up an Iranian Nuke Plant. Three waypoints, an IP and an ST, using Jester. I was flying and made WP 1-3 no problem. Once we got to WP 3 I told Jester to switch to IP to start the attack run. He complied (I jumped in the back later and verified) but at that point my nav information went away. I was still in cruise mode. I had him switch to the ST (Surface target), again he did, and again no nav cues at all. I still had my switch set to "Destination". Am I missing something? How do you navigate to the final attack steerpoint if the cues go away. Is it a glitch or is there something I need to know....

     

    It was pretty frustrating to travel almost 200 miles and not even be able to take a shot at the target.

  5. This has started happening more frequently and I was wondering if anyone else on here has had an experience with this or know how to fix it? Sometimes when I play DCS, either single player or multiplayer, the games sounds and voices sound higher pitched, almost like hitting fast forward on a VCR or Alvin and the Chipmunks. The actual game play does not seem to be affected. It happened last night on a MP server. It was high pitch for almost 10 minutes, then all at once it went back to normal for no discernible reason. The game is still playable in this state but it is highly annoying. If I wanted to be high pitched I would just breathe some helium!!!! Thanks for the help.

  6. I have a trick for this on my x52 pro. I use the bands on the small throttle slider to map LCtrl+Lwin to it. I set slider all the way down to not press that key combo. Middle 90% is deadspace. Top of the slider makes it hold down LCTRL+LWIN so I can use the keyboard to type. Once I finish my keyboard entry I just slide it back down to the bottom and everything goes back to normal. It works like a champ. Please send me a PM if that didn't make sense and I will try and explain it a little better.

  7. Hey guys, the project has been somewhat slower but is very much alive. We're in process of building M07 and soon will start recording the VOs for it (again more than 300) :) Doughboy is busy writing the script for the other. Research also takes some time, as we want the info we are giving you 100% accurate. It will take time, but we will get there!

     

    If you would like any other people for VO's I would be willing to help out, for free of course. If you are interested just send me a PM here. Great work!!

  8. We just retested missions 2 and 3 and they played fine in the current DCS World released version.

     

    Make sure you set your radio to 124.000 when instructed to after takeoff.

     

    Let me ask you this. Is there a height trigger as well? It doesn't seem like he starts talking until I go down and start making gun runs. Could that have something to do with it?

  9. Yeah, I tried DCS repair and also reinstalled the campaign, video drivers are totally up to date and it still had the very late trigger for the instructional VO. I was able to finish mission 3 and will move on to 4. Ill let you know if it does it on that one as well. Thanks!

  10. Hi Sabre, I have decided to go back and restart the TTQ Campaign since it had been a while since I had played it. I restarted the campaign, which ran flawlessly a couple of months ago. Now on mission 2 and mission 3 (so far) the timings for the VO is completely off. The long briefing from Saber that normally starts before waypoint 2 doesn't start until way later when you start talking to JTAC Uzi, which turns into a huge mess of trying to communicate with the JTAC with Saber droning on in the background. I have updated my drivers and completely reinstalled the campaign and it does the same thing. I have made sure that I am right on the waypoint lines and hit every steerpoint on the nose. Do you have any other suggestions? I would really love to move forward and finish this amazing campaign.

    Thanks!!!

×
×
  • Create New...