bonesvf103

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

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

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

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

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

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

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

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

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

What does it mean when they say "octopus" and "no alibis"? v6, boNes

I noticed this error in my VAICOM Pro window. VAICOM Pro appears to work fine though...am I missing something and not know about it? "The VoiceAttack Sounds folder does not exist ('C:\Program Files (x86)\VoiceAttack\Sounds'). Please go into the Options page and choose a folder that exists." Thanks! v6, boNes

The first flight of the F-14 was 50 years ago today. Happy birthday, baby...! v6, boNes

Thanks. Does this mean we have to wait until the next patch to see the fix, or is it being pushed to us? How does this work? v6, boNes

Well there was Hoser Sartapa... v6, boNes

I'm glad I saw this thread....after the update I thought I was going crazy. The Tomcat was just bleeding energy so much in turns it was frustrating to think I was doing it wrong. I also found that in a nose down attitude, with full burner, that she barely accelerated in general. And this was clean. I out 2 Sidewinders on and it was worse. I'm glad HB has seen this thread and are checking things out. In the meantime I guess I'll fly other missions or something else. v6, boNes

I was just about to ask this, I am really hoping so! v6, boNes

Hello, How do you change the name that is displayed in the missions list? When I add a mission to the folder, and I search for it in the missions menu, I find it but it has a different title. I don't think it did that before... Thanks. v6, boNes

Yup, looks to have worked, thanks! v6, boNes

I’ll try that, thanks. oh and I don’t have any warbirds. The other aircraft were the Tomcat, Hornet, and Falcon. v6, boNes

Lately I've been noticing that the rudders are fluttering. For instance, if I am trying to steer my aircraft I hit the rudder but nothing happens. When I look down at the rudders in the aircraft, the graphic representation of it shows it's "fluttering", rapidly flipping back and forth then it stops, then it starts again. It does this in any aircraft i fly. I'm using Logitech's rudders (goes with the X56). After a few minutes it seems to stop fluttering but may come back again. I'm trying to figure out a fix because it has cost me an aircraft or two when I land. It causes skidding. I also tried using the twist in my joystick to use the rudders and it did the same thing. So it makes me think something in DCS is up, not the rudder or stick itself. In the DCS axis assign, this fluttering does not show up. The bands are stable and move left and right as they should. Any ideas? v6, boNes

OK, will try that...didn't ask him for DF IIRC. Thanks! v6, boNes

Ah good to know. But it should be ok with the ones at the airbases in DCS then right? v6, boNes

I had read in Chucks guide that the ADF in the front seat wasn’t working....so I guess that is it then, huh? v6, boNes

yeah I have had to too but luckily turning and pulling was enough to get it to come down, nothing more critical than that. I know about that but it always maxes out before the horizon when I try to adjust it.

How do you mean bending the tab up? v6, boNes