latearrival

Hi Buffallo This thread might help you (within the context of ATC and landing): http://forums.eagle.ru/showthread.php?t=70922&highlight=pattern+altitude If there's any specific ATC instruction that you need to help with, just post a quote of it back here in this thread...

I bought a HOTAS first, then TrackIR. If you bought a cheaper HOTAS (e.g Saitek or CH Products) perhaps you could buy both at the same time?!

Are you sure your throttle is calibrated correctly? You can press Right Ctrl + Enter to see if any virtual throttle is being applied when your physical throttle is pulled all the way back.

Try this: 1. Display a mav on the right MFCD and the TGP on the left. 2. Make the TGP the SOI (Coolie hat left long). 3. Make the TGP designate the SPI (TMS up/fwd long). 4. Slave all sensors to the SPI (China hat right long). 5. Slew the TGP - you will see the mav seeker move on the right MFCD as you move the TGP as shown on the right.

Welcome to the forums! I'm in a near identical demographic to you, except I grew up with the Sinclair ZX Spectrum rather than the Commodore 64 (My first flight sim was Nightflight, which required a massive 16K to run. The "night" bit was because the only thing you could see out the 'cockpit' was a few pixels to mark the runway!). Anyway, to your question -I have no interest in (real) flying, planes of any type or the military. Most of the technical references to real life stuff here on these forums goes over my head. However, I have dabbled with sims in the past (Combat Flight Simulator, FSX, Falcon 4 AF) and, following a multi-year break, I stumbled across this magnificent sim by chance. The first time I sat in the cockpit and started her up, hearing everything coming to life, I was hooked...

Yes. But just to be sure, did you check properties using Adobe Reader not Windows Explorer?

Hi Ned You can use either of these methods to find the target: JTAC entry via UFC: http://www.youtube.com/user/emtguf#p/u/7/mcJ8mlMF7qg JTAC entry via TAD: http://www.youtube.com/user/emtguf#p/u/5/pFH0epMjPWU And a thread describing the same: http://forums.eagle.ru/showthread.php?t=74097&highlight=jtac+ufc

Good question Malkin. The pdf version that I have been referring to has a Created and Modified date of 1 April 2011 (Adobe Reader/File/Properties). There are no references to version dates within the document itself that I could find. ED - it would be great to have a version date on the first page or two of the manual, especially given that the forums are full of references to page numbers that are already, or will one day, become incorrect.

There is training available on this within the sim - Training/Combat Employment/Air to Air. Good luck!

Here's mine. All information from the manual, with some holes plugged from globalsecurity, so I'm sure it will contain some inaccuracies and errors. Please everyone shout out and tell me how I can make it better/more accurate.

OK, having gone to the source I wasn't quite right about this. Both systems use varying configurations of lights. However, the principle stands - VASI pretty much says 'above', 'below', 'on' glide path. PAPA says 'above', 'a little above', 'on', 'a little below', 'below'.

I'm not sure about how they are in-sim, but in real life they're both lighting systems that provide guidance for final approach. They both tell you if you're above or below the glide path. PAPI is slightly superior to VASI because there are more lights, enabling the PAPI system to also tell you if you are a little high or a little low. I *think* the VASI system is made up of two sets of lights - one white and one red. PAPI is four sets of lights - two white and two red. Could be wrong on this.

Track Replay Enhancer 1.1 Change Log Preliminary "LateArrival's Track Replay Enhancer" 1.1 Change Log (regardless of your actual performance, your track replay will automatically be enhanced to impress your friends, your fellow simmers, and of course, the ladies). SUBJECT TO CHANGE. In other words, new items may be added, some items may be removed, or some items may be modified. This list is not in stone. - Reduce 'hunt and peck' time needed to find buttons in the cockpit. - Make it look like you know what you're doing with the CDU. - Increase perceived situational awareness (find targets without flying randomly around for hours). - Increase aerial refueling success rate from 0% to 100% (slider). - Increase crosswind landing success rate from 0% to 100% (slider). - Make all unguided bombs land in the same field as the target. - Smooth out zig-zagging down the runway upon take-off (low, medium, high smoothing options). (All options will be automatically applied to anyone viewing your track who has more posts than you in the DCS forum and/or a higher reputation power).

I have something built into my version of the sim that stops anyone from viewing my tracks whose skill level is significantly above mine. It stops me from looking bad ;)

It's not just you that got confused! It took me months before I realised that the SPI moves as the TGP sensor moves. Until then, I thought that making the SPI with TMS Forward Long created the SPI at that specific point, after which you could move the TGP without moving the SPI. This is not what seems to happen in the sim, at least with the TGP. I think that "Set Sensor as SPI" is a better description for TMS Forward Long, than "Make SPI".

OP was Alexrey. I think we're all in agreement in this thread. Happy with the answer Alexrey?

That's not what I meant Iceman. I've never created a track before, but here's my first one - hopefully showing what I said in my post above, just with the TGP on the left MFCD and the mav on the right. moving_spi.trk

I think this is a really important concept that is not obvious from RTFM or STFF (searching forum). The SPI does move, for all intents and purposes, as you move the sensor that is designating it. I'm pretty sure that if you display a mav on the left mfcd and the tgp on the right, make the tgp the soi, make the tgp designate the spi, slave all sensors to the spi, and then slew the tgp, you will see the mav seeker move on the left mfcd - the spi is moving.

A-10C profile for CH Products Fighterstick HOTAS Here's an A-10C profile for the CH Products Fighterstick, Throttle & Pedals. The profile was originally built by Ken "531 Ghost" King and has been modified by myself. Points to note: To use this profile you need "A-10C.map" and "DCS_Warthog.cmc" to be in the same folder (see the zip file). There are no scripts in this profile and CH modes are not used. All assigned HOTAS commands work as at v1.1.0.8. There may be unused commands in the CMC file that no longer work due to changes in the sim. Button 4 on the throttle is used as the shift key. In the print-outs of the profile I've used a simple convention in the button labels where a single button does multiple jobs: "<" means the command to the right of the "<" is executed after a long press (e.g. China Forward Long = Slave all to SPI). "/" means the command to the right of the "/' is executed when the shift key (Button 4 on the throttle) is held at the same time. In Guns mode, hold shift and the trigger to stabilise the aircraft (first stage), then release the shift button to fire. This has been accomplished by using DX mode as suggested by Ruggbutt and Bob Church at http://www.ch-hangar.com. "Up" on the throttle POV switch is mapped to non-ED software - Push to Talk for VAC / Push to Talk for Teamspeak (TS). The POV switch on the joystick, when used with the shift key, is used for TrackIR commands (TIR). A10C profile for CH HOTAS.zip

My understanding is the latter.

A warm welcome to you zoomzoomers6 - the community here is amazing and the sim is brilliant. You won't regret your purchasing decision. I'm relatively new to the the A10C too, coming, like you, from FSX. The best tips I have are: 1. Read the manual BUT realise (which I didn't) that the first half (to page 412) is like a reference guide. The second half, (once you understand all acronyms!) is more of a how-to guide and is much more user friendly. 2. The CDU and MFCD sections in the manual are particularly long, detailed and frightening - someone with more knowledge than me might be able to point out what you can safely ignore (for now) and what to read sooner rather than later. 3. FSX might not have taught you about the litany of acronyms in this sim (e.g. TGP, TAD, MFCD, SOI, SPI, CMS, TMS, DMS) and other confusing terms (Pinky Switch and China Hat I'm thinking of you!). Learn what these are as soon as possible. If they were called things like map (TAD), camera (TGP) and monitor (MFCD) the learning curve would be less daunting! 4. There's lots of great videos on YouTube. Checkout the channels of ExcessiveHeadspace, wagmatt and tigerpwrr for starters. 5. If you don't understand something, search in this forum first and then don't be afraid to ask for help if your search was fruitless. I've never seen anyone abused on these forums. Good luck!

That's pretty much how I've been using it, e.g. I attack a target that's near my current location by using the TGP to make that target the SPI, slaving all to that SPI (China Hat Forward Long) and launching a mav at it. With the steerpoint being at the next area of interest, I then slave the TGP to that steerpoint (China Hat Aft Long) and start searching for targets at that location. Rinse and repeat.

My mistake. Thanks for pointing that out Boulund :)

I'm very happy that v1.1.0.9 means I can have a nice sharp cockpit again. But I thought we'd established here that the problem wasn't a 32 bit vs 64 bit thing? http://forums.eagle.ru/showthread.php?t=74828&page=17&highlight=blurrie I run 64 bit Windows, have a half decent system, run at 1280x1024, and I have to have textures set to medium to avoid/minimise stutters.

Great idea sledgeweb. Just visited with my Android and it looks nice and clean (apart from those ads ;) ). Good job. If you could replicate the 'gold standard' of checklists, Paulrkii's (http://forums.eagle.ru/showthread.php?t=74949&highlight=checklist), it would truly be something special.