Jump to content

bonesvf103

Members
  • Posts

    1275
  • Joined

  • Last visited

Everything posted by bonesvf103

  1. OK for the round counter. But I did select gun on the weapons selector (left that detail out). I had AA mode on, "G" was in the HUD, master arm was on (cover and switch). TRhe first time I flew trigger opull spit out around 50 rounds then was empty. The second time I flew the mission the gun was just plain empty right off the bat, no rounds fired. Could it be if the counter is set to 0 that the gun won't fire? Then again, it wouldn't explain why it fired that short burst the first time I flew the mission. v6, boNes
  2. I flew the first engagement against Gator from the Zone V campaign. I did one short burst of the gun and i was empty! Afterwards i opened the mission in the editor. It does say the gun is loaded 100%. So i restart the mission. This time i look right at the gun rounds counter and it says 0! I also looked at the HUD and it says 0. I called ground crew for rearm. The aircraft is clean except stations 3,4,5,6 are Xd out. The gun says 100%. To further test, I take off. Master arm on, AA mode selected, pull trigger... Nothing. The bird is completely empty. How weird is that? Especially since it says 100% in the mission file and on rearm, and the first time i flew it it shot off like 50 rounds and then was empty and now this time it didn't have any at all v6, boNes
  3. Couple of radio questions: 1. If there is an ATC with one of the lower frequencies in the FM band such as 74.0 and I tune it with the -182, no one seems to hear me. If I tune their alternate AM band, then they do. Are these lower frequencies not working? 2. If the mission file is written with easy comms and your profile is set for real comms, when you fly the mission, will the comms default to easy or realistic? Thanks v6, boNes
  4. Yeah, it was kinda dicey seeing that missile head right at my face! v6, boNes
  5. You can do it pretty much by using VAICOM Pro. I have been able to tell Jester, "Radio Frequency 118 decimal 0" and he will say "roger" and then I will see in my VHF/UHF2 repeater on the right side of the cockpit the frequency being changed. He can also do TACAN ("TACAN mode transmit," "TACAN freq X-ray 018" and he will tune his TACAN.) There's a way to have VAICOM Pro do button as well, but I haven't been able to get it to have Jester do it. I'm sure there's a way I just honestly only started trying to figure that out today. v6, boNes PS was a little late..saw that you had VAICOM Pro. What was the matter with it?
  6. Thanks, I stumbled across them using a search engine, heh. v6, boNes
  7. This is pretty easily find using the hotas software (i have x56). Is there anyway to extract the pages from the kneeboard? I can't find the files. In fact i can't even find the campaign files (I'm on steam version) Also where are those fictional skins located? v6, boNes
  8. Yeah over the past few months I've noticed that this happens randomly where you have to reset it. Same with the launch bar being down. v6, boNes
  9. Looking at a TacView from a previous test, looks like the surviving F-4s beamed the missile initially then came back on course. The beam may have broken lock. But then the bandits turned to face the Phoenixes afterwards andsince the Phoenixes were pitbull, you would think they would have acquired or re-acquired the bandits, but the bandits sailed right past them., parallel to their course. v6, boNes
  10. If you are referring to my report, I have a track, a TacView, and video. Tracks are larger than 5 MB so I'm not sure how to get around the 5 MB limit here on the DCS forum. Also of note is that I was firing against F-4 Phantom II "drones" so I don't know if the mission writer made them smart enough to use CM or not. I also designated all of the TWS-A contacts as hostile so that the WCS will definitely adjust the TWS to properly focus on them and keep the target "weight" centroid for best radar coverage. Target size was also set to "normal". Test 1 at 70 miles Test 2 at 36 miles. Excuse the crash, I was busy monitoring the Phoenix missiles to pay attention to threats. See video description for time codes. v6, boNes
  11. OK, I ran a test and used GMT and locked the SA-15 with the IMAV. BUT..I got down real low, waited until I was really close, maybe about 6 miles or less, and then fired, which was dicey because the SA-15 shot first and after I did, I had to break to beam it and chaff like crazy (also had the jammer on). The missile successfully killed the SA-15. He MAY have gotten a shot off to kill the Maverick but he missed. The 3 remaining convoy vehicles were tanks and APCs so they were easy to mop up afterwards. v6, boNes
  12. OK I ran another test. I had solid TWS-A locks on the 6 targets, they were all falshing that I was in launch zone. I waited until they were around 36 miles before firing. All Phoenixes went pitbull, but only 1 hit. Compare this to when I fired at them at 70 miles and got 4 hits. I watched 5 Phoenixes fly right by, one of them flew right by a bandit without even maneuvering, the other ones went into the ground. Something doesn't seem right. v6, boNes
  13. You know, I noticed this too. AFter the update before last, they worked really well. Now, recently, not so. I shot 6 Phoenixes on targets that were no more than 40 miles away, all locked with TWS-A and had gone pitbull and only 2-4 hit. v6, boNes
  14. Maybe in the past since I wasn't using GMT and was using the TPOD, I got in closer than I did with the GMT and thus he couldn't shoot them down. AS a test I will run the mission again but forego the GMT and use just the TPOD. v6, boNes
  15. I have that poster on my wall, but it says "National Air and Space Museum Smithsonian Institution, Washington DC" on it. v6, boNes
  16. It was just a simple practice mission that I downloaded from the DCS user site, hence why it was just me wiping them out. I was able to complete it every time for months until the SA-15 suddenly woke up and decided to start shooting down my Mavericks. v6, boNes
  17. Yes I was going to say that about the GBU-38...my target was in a moving convoy, so GPS weapons wouldn't do in this mission. Also what I meant about planning ahead was planning how to keep my weapons from being shot down. So far shooting Mavericks at it has been the only thing that works, but it leaves me short of finishing off the rest of the convoy (gun isn't really effective against the APCs and tanks with it). Before Skynet woke up the SA-15s, I used to be able to wipe out the whole convoy. v6, boNes
  18. OK, thanks. Wow. I guess I'm more bewildered now that that this system suddenly just "woke up" after never even trying to shoot down my Mavericks before all these months or years. Was there a recent update to the SA-15 to make them actually activate this function? It's almost as Skynet suddenly became self aware. So how does one plan accordingly for this? The only way I was able to kill it was to shoot 2 Mavericks at ti...but then I don't have enough Mavericks for the remaining targets. Thanks! v6, boNes
  19. I was playing a mission that I have had a for a few months now that used the TPOD along with MAVE and IMAVs. When the GMT radar came out, I tried the same mission but used the GMT instead. It went fine. But a few days later when I tried it again, the SA-15 shot down the IMAV. I had never seen anything let alone an SA-15 shoot down a Maverick before, and it just suddenly happened. But then I flew the mission 2 or 3 times afterwards and it kept happening. Is it possible that an SA-15 can do this to an IMAV? And how come all of a sudden even though I flew the mission the same way it suddenly started doing this? I'm baffled. Any thoughts? v6, boNes
  20. Thank you so much for fixing the AOA indexer brightmess! OMG, I've been waiting forever for that I gave up hope. I'm now back to trapping well, thanks again! v6, boNes
  21. Yes, I've read the manual over and over about this but it wasn't really sinking in because the way it is presented is a bit confusing as it doesn't in this excerpt specify for TWS-A or TWS-M. I actually had to try it myself to really fully grasp what was going on and see what happens under different settings. So I'm clear now, thanks. My new question is this: I get that the range of PDS is 110 miles and RWS and TWS is 90--but I would think that the datalink would still show contacts beyond that--So how come when I have the radar at 200 miles and the AWACS is calling that the bandit is 150 miles away right in front of my nose in TWS, I don't see a DL contact in my TID? I have the DL on, the right freq, the correct switches, and the DL button by the HCU on. v6, boNes
  22. Ok thanks. for #3...ok, so what if your are in TWS M and you are at 20 deg, 4 bar and then you change the azimuth to 65...what will happen. It will stay 20/4? v6, boNes
  23. If you have the azimuth setting at say 40, in the TID, the diagonal lines radiating out from the bottom represent a total of 40 degrees, or 20 deg on either side of your nose, right? Next, the notion of TWS only does 20 az 4 bar or 40 az 2 bar. It seems that the only time this applies is when I’m in TWS-M. Is that right? Because it seems when I have it on TWS-A, it doesn’t matter where I have the knobs set, the system chooses 20 az 4 Bar or 40 az 2 bar as needed to keep all contacts in the scan. when in TWS-M, if I put her in 20 az, 4 bar then changed the bar, it then defaults to just 20/4, right? If I then changed it to 40 az but kept the bars at 4, then would it just default to 40/2 or to 20/4? I ask because I seem to get varying results but I’m sure there a plausible explanation for it. Thanks! v6, boNes
  24. If you have the azimuth setting at say 40, in the TID, the diagonal lines radiating out from the bottom represent a total of 40 degrees, or 20 deg on either side of your nose, right? Next, the notion of TWS only does 20 az 4 bar or 40 az 2 bar. It seems that the only time this applies is when I’m in TWS-M. Is that right? Because it seems when I have it on TWS-A, it doesn’t matter where I have the knobs set, the system chooses 20 az 4 Bar or 40 az 2 bar as needed to keep all contacts in the scan. when in TWS-M, if I put her in 20 az, 4 bar then changed the bar, it then defaults to just 20/4, right? If I then changed it to 40 az but kept the bars at 4, then would it just default to 40/2 or to 20/4? I ask because I seem to get varying results but I’m sure there a plausible explanation for it. Thanks! v6, boNes
  25. What does it mean when they say "octopus" and "no alibis"? v6, boNes
×
×
  • Create New...