uri_ba

Headspace, Just saw you posted a new version (1.0.1-8b). 10x for the quick adjustments :)

TARS won't even recognize the release version of TS3 as and existing TS3

I assume it would be compriable with TS3 rc2 as well?

Any News Headspace? I'm Dying down here :)

Just get the chepest stick you can find, say logitek attack 3 or similar. Even second hand.

And F-16 doesn't have a small payload? As long as you don't loiter for CAS which F/A-18 isn't the ideal plane for that (nor F16). you go in, drop 2 or 4 MK83 or 84 and bug out. if you have fuel you maintain CAP somewhere till you are bingo. from Falcon I can tell you that a normal sortie is 60 to 90 minutes aloft. (up to two hours with Ramp time). it's not the four hours, I ran out of ammo before I ran out of gas, you get in A-10

I use F12 with shift, alt and ctrl as modifiers for persision, pause and center. With No issues.

If I know the airodrom alt I just dial in the correct MSL and QNH shows up. No need for math that might cause errors

Ppersonal files are saved to a folder outside the installation folder. So it should be safe. It's in "my saved games" or something similar

SA-11s are bastards.. (BUK). they have a Snow-drift radar but destroying it only degrades the battery's detection ability (significatly), but each launcher has it's own radar, and can still track and hit you. so take a very carefull look around even after you get the SD. SA-6s (KUB) are easier. you the the Fire radar (straight flush), which is easily identified from 20+ clicks via the TGP. but once you hit it the battery is completely dead. I've flown with the 74th and getting those SA11s you have to be in the weeds. but I've dealt with SA-6 on the 1VFW server, and from some reason it doesn't engage you till you are well withing MAV envelope. (I was @ 20kft straight and level, jammer off)

CBU105s at "tossable". problem is that the pickle is very long and the window is sometime too small after the pull up. you need to watch for the carrot to cross the 9 oclock going up to the 12. that's the pull cue. once the MAN release shows up only then you can start pressing the pickle. I wonder in in RL pickle pressed before you reach the basket as accepted once inside it.

once a custom modifier has been assigned you cannot use it as a normal key. so setting up your trigger as a modifier for example would be a bad idea. I know it's a bit OT. But in my opinion (and aircraft designers) HOTAS should include the things needed the most and frankly, "right engine start", "canopy close", "APU gen ON", "landing gears", "flaps" and even "eject" don't fall IMHO under this category. in short, In my eyes, all the functions you use only once or twice during flight shouldn't be on the HOTAS, as they are not in RL.

looks good, only problem is the amount of PTT releases on the JTAC talks. JTAC sentence should be one transmission, not cut into so many separate comms. I assume you have changed the default "end of transmission" sound the the radio click. and it's ED that have put all of the "EOL" in that. but still, it's too much. love the gunfire sounds in the JTAC background :)

nope check out the change log http://www.digitalcombatsimulator.com/en/downloads/patches/dcs-wh_patch_1.1.0.7_en/

great job, but I'm not sure that you have survived if the terrain was less rugged or the Mig29 human.. we would never know how we will survive the DCS battle field once FC2 would be compatible. only time will tell..

And you might want to add cabin fire, smoke in cockpit and high alt ejection. And because all of that your mic is inside the mask, so radio comms too... But not all fighter jets fly with o2. during shows, the blue angles fly without a mask with a boom mic. On the ther hand, they also fly with a 40 lbs spring to have the nose constantly pitch down, and eithout a g-suitt.

He problem is that the line passes just east of betumi (less then 15km) so alot of missions in that area will pose a problem. There is the map available for download. I would suggest to print, even at low res the area, betumi to north of kobaleti, and bold out the grids, and the 37/38 grids seperation (43E if i recall correctly) that would help avoiding confusion. I'm currently working on making the Printed map "air worthy" but that would be on a separate thread when it'll be ready

so far, BS and FC2 are compatible. I don't see a difference between WH and BS in realism. AFAIK, BS will get a compatibility patch with WH later this year, but no strict timeline exists yet, WH need some more ironing (that was from an interview with WAGS in one of the sites). once BS and HW are compatible, according to the same interview, FC2 compatibility would be considered. problem is that with every DCS module, FC2 would have more advantage due to system simplicity. you can see it now with A10A vs A10C. life are much simpler in FC2. (but it's so much less effective)

You can't really document EVERYTHING it will be too much. Manual is 600+ pages as is. You need to document the basics, and refer people to real deal manuals if they wan't more. Besides, you always have the wiki that goes far deeper then the manual. (And the real deal of course)

Flash light could be nice. Say, ctrl+shift+f turn on a small lighten area arround the mouse pointer. In addition, if flash light is turned on the rest should go dark for a while, like the sun does but for longer period, to mimic the lost of night vision (the natural one)

I know it's not the same thing. but still http://www.youtube.com/watch?v=f0ttcyIJPm4 in addition, latest skirmishes in the ME has given us some additional views on FLIR at work. I think those are UAVs cams mostly. but FLIR looks the same anyway. if you look carefully, you can even see a cigarette bud thrown to the side at one point first clips of footage looks like day TADS of an Apache, but the rest seems to be LIGHTNING I or LANTIRN FLIR through a cloud I think that youtube is filled with those. giving us all the FLIR imagery we need :)

in RL you can't change Laser code in the bombs in flight (nor fuses). they require to physically change things on the bomb. (maybe Paveway III is different) but laser pointers can change their codes on the fly. so when checking in with JTAC, after you receive the order to engage with LGBs, you need to specify the weapon code, so the JTAC would be able to paint the target with the right code for your bombs (assuming you don't lase yourself)

yes, of course, if the clouds are less then say 3/8 you can maneuver between them. but I understood his intention as overcast (or worst, night and you can't see the clouds blocking the LOS of the pod). Personally, I would prefer to look for the target from a rough location, and not "copy and paste" from a text message I don't know how fast it will disappear. so unless you get it Data linked (and even then you double check with the pod) I want to be "eyes on target". I think it was back in 2003, I've heard about a blue-on-blue incident in Afghanistan, I don't remember the details, nor had any knowing if it really happened so regard it as such. JTAC was transmitting target location to an aircraft. the data was programmed to the JDAM and it was dropped. Unfortunately, he had just swapped batteries in his GPS-target-finder-gizmo, and failed to notice that the coods he transmitted were "self".

Best option is to have the Target acquired via TGP, refine the target coods (set SPI to the TGP) an drop a JDAM on it. please note, that because you can't lase the target you can't get accurate range and you use the TGP for an approximate location. so you need to use AREA mode and lock it on the base of the wall facing you. that will minimize the error (you will actually target the ground below the roof). LGB are useless because of the clouds, so does the laser designation or IR pointing from JTAC.

Mouse wheel scroll up and down. middle mouse button to select. I think all modern HOTAS systems have the mouse scrolll stuck on somewhere, isn't it? and it's much less "complicated" then actually move the mouse to the comm area.