Deezle

That switch was never implemented.

You can't. GBU-12s carried on the Mirage have a default lase code of 1688.

It's the HDR effect. I find it quite annoying near dusk.

Worked fine for me but with the other radio traffic it may take a little while to get through all the steps.

Dear god I hated that. About time.

Ciribob, I was playing with this script this weekend, the JTAC would find the first target and mark it no problem, after I destroyed the first it would say scanning for targets and and never find any more, mind you these targets were all in one group close to each other. Am I doing something wrong?

JDAMs are great because you can easily drop multiples in a single pass and above cloud cover, a miss is usually close enough to kill unarmored and lightly armored targets, with a tank you're definitely better off with an LGB for a direct hit.

That's the problem with building a simpit, if you want to use genuine military grade switches/ect, you're really going to pay for it.

Yes, it is Russian after all...

Because they assume you wont be mapping them for anything else with the A-10. Find the input/joystick folder in the a-10 folder and delete the two mfd luas, then you can map them however you'd like.

Assigning the GUI to the center screen used to be possible in 1.2.xx using the monitor config file. As of 1.5 if you try this it completely breaks the GUI.

Thanks for sharing. I've been wondering for a while now, are there any restrictions from a pilot pointing their TGP at Groom Lake and having a look around?

I'm telling you guys, it's the crosswind. Open any mission you have trouble with in the editor and turn the wind off and try again, the plane will go straight.

I'm quite fond of my setup.

Not a tank but you get the idea. Also [ame]https://www.youtube.com/watch?v=dQ37y0yeSgc[/ame]

lol "cheating" For what it's worth, IR cameras don't care if something is camouflaged. The DCS implementation is just a filter over the visible spectrum, nothing realistic about it.

I've not experienced this. It goes perfectly straight with no wind.

The 103 and 105 are GPS guided, they only work in CCRP and you're given a release window instead of alignment cues and an auto release, this is because the release with these doesn't have to be nearly as precise, being GPS guided. The 87 and 97 are dumb bombs and work with CCIP and CCRP. The CCRP works with alignment cues and an auto release countdown. Sounds like you're getting 103s/105s when you want 87s/97s.

Did you watch the video I posted? With the 103/105 you do not hold the pickle button and wait for a count down. You hit the button when you are within the release window, the bomb is GPS guided and will find it's target.

Thanks Andre!

Yes.

That setting is what caused the tone, thanks :thumbup: I'm using this amp and transducer. http://www.amazon.com/gp/product/B00LF5GK94?psc=1&redirect=true&ref_=oh_aui_detailpage_o07_s00 http://www.amazon.com/gp/product/B0002ZPTBI?psc=1&redirect=true&ref_=oh_aui_detailpage_o06_s00 Honestly the effects when I started using SimShaker in August felt the best for me. The landing gear effects I remember were particularly amazing. I no longer feel the distinct "CLUNK" when each of the gears lock in place, just the vibration of the gear moving. The helicopter constant vibration instead of "thump thump thump" was the most obvious change in the last update.

CCRP with the GPS guided bombs is a little different than how it works with the dumb bombs and LGBs. [ame] [/ame]

Well what's odd is I just checked another tacview from an earlier flight where I killed a T-90 in a single pass, it was hit 166 times. It was also a rear aspect pass under .7nm. Seems odd it worked that time on a tougher tank.

You can change between CCRP and CCIP on the weapon profile page. You can also do it manually with the master mode button. The 103s/105s can only be used in CCRP.