Fish

How can i transfer my pilot log to the new install. (still have all the old files :) ) ??

Funny I feel exact opposite. I could not careless how the window look, but AAR is one of the unique, and most challenging features of this sim, and implemented very well. I miss it terribly..............(Well at least i can continue to hone my skills in SP missions, and AAR works good in SP.)

If you got TIR, here's a profile you might like to try out.

So if your a paid for A10 as a beta purchaser, who is entitled to get the nevada update for A10, would you then have to pay for it in BS2 I wonder?

The issue above remains, But it should be pretty easy to make a spi from the TGP, once you selected it as SOI, See point 2. from Post above, and your autolase will then work. Also you should find a way to see the TAD (along with TGP) while running in. There's invaluable SA info from that screen during weapon deployment, especially in EXP2 mode. Remember CDU stuff is repeated on the CDU screen, so you don't need that to be one of the mfcd's.

Believe i tried it both ways. But always made sure Mark point was set as the spi (with the tadpole tail). Also made sure to slave sensors to it.

Ignore my last post. Setting SPI definitely not your problem here. Tried the mission several ways. Here's what i found 1. When using Mark point as SPI (tms back long), Cannot get laser to stay on. (in manual mode it flashes a bit then constant). 2. When I make the TGP spi, (first TGP SOI), then TMS fwd long, I get manual lasing and autolase working fine. 3. With 1. above, I could hit target by constantly pressing/releasing the Laser, to keep it active for last 10 seconds. 4. In 1 above, sensors were slaved to mark points fine, since TGP moved when i changed mark point. 5. Wheather i slave all sensors (CHN FWD LONG), or just TGP to SPI (CHN AFT LONG), makes not difference to 1. above. Someone else might explain whats happening.

Have not looked at your trk yet, but will do it in a while. Might be obvious point, but in 'mark' mode, you make a mark an spi with TMS DOWN long. All (Steerpoint SPI), then slave sensors. Now when you cycle the marks, SPI's cycles also. Other spi's you make with TMS UP LONG.

Not bugged for me. Brightness. Contrast. Symbols (the green stuff, but u gotta go close to zero to see any effect). Nice cause you can set them for each page independently !!

along with some others... :thumbup: Oh hreich, you might check the following: ATC direction, QFE is normally 4 digits and decimal in middle. Believe TAD hookship mode you refer to should be HOOK-CURS (user 'hooks' their own ship). I like you list, and will add some points to my own notes. :smilewink:

hreich, Can you please include the fix by 'Speed' for the missing leading zero's on some JTAC UTM calls. http://forums.eagle.ru/showpost.php?p=1310618&postcount=36

Big +1 Also Stabilise aircraft and 'sloooooow' down. Once you hit the mav weapon envelope, clock is ticking for you to make your shot. If you don't have the aid of the tgp, or a spi, you might only be left with boresight (China left AFT short). use TMS DOWN SHORT to stabilise temporarily. if you loose target, and still time/distance, go back heads-up SOI, boresight again, (or re-slave to SPI again if its your target) then MAV SOI, and try again. If you run out of time, just break and redo the IP.

Another use of markpoints. In an unknown threat zone, i will establish a 'run in' point, and a 'break off' point as marks, at a minimum safe distance (which will be determined by the threats) from the target area, while we asses the threats and mark all targets. This i relay to my wingmen as SPI's and he/they create marks with them same as me. If close enough it can be used to launch safely stand off weapons (mav's), and break away clear of any AG threats. Also aids in flight de-confliction, if all follow the same pattern. Maybe not the right way. Buy My way..... :) You gotta just love the mark points in this sim.

Nice work, particularly the 'mode' images. You might consider highlighting what atttributes are different when SOI's are different on those pages (5,6 etc), since much of the hotas functionality is consistent through out the various SOI's.

Was replying to the original post Answer to this is at 20:50 in the video. You can see the TO-TO mode works correctly (as described in the manual) when set from the mission editor. (video 17:50 on). i.e, the CDI reflects how far you are away from the 'course line' irrespective of the course heading knob. I too had difficulty changing modes from the CDU, but was able to demonstrate TO-TO mode by selecting the attributes at the mission editor stage. (after all, the subject for the video was the CDI, not CDU !!) I too welcome the CDU functionality being improved in 1.10.

Here's the keyboard i use. Sits nicely in between stick and throttle http://www.amazon.co.uk/Keysonic-Wireless-Keyboard-Integrated-Frequency/dp/B000L10Y5E/ref=sr_1_2?ie=UTF8&qid=1319664755&sr=8-2 When i'm finished flying (virtually!), i revert back to my G15 My rig is almost the same as yours, and I got a pretty solid profile for cougar/tir/Ch pedals. You can download it from the VAC thread. PM me if you need support for it, or help with cougar.

If you change your HOOK FROM, to the BULLSEYE, and change your TAD to EXP view, and zoom into the general target location. Then when you move the cursor to any object on the map, the bottom RHS of the TAD displays the Bullseye bearing and distance, and you can get a good 'feel' for roughly where things are and what the calls may be related to. Helps greatly with situational awareness.

Awacs is @7000ft, and comes on station over the target area, not realistic. I did request picture, but not sure if I would have got the call back if i did'nt call it. From what i remember, it felt like the call was made because the AWACS was threatened by those targets, cause when i put it up higher, i could not get the call. If that makes sense.

posted in error.

Actually found out LBG's in A10 are released by default in OPTLase mode, which throws them ahead of the target giving them lots of kinetic energy for the hit. You can release in pure ballistic mode, but you have to change it in the profile page. Hope this 'un-confuses' you a little' Still lots to learn about this sim. (and thanks for kind words!)

Hi Arran, ad welcome to DCS A10 TGP is a highly 'zoomed' instrument, and at close range even zoomed out, its FOV is very small. If you can see them visually, then you are pretty close, and using the TGP to 'search' is pretty ineffective. I suggest you slew the hud cursor (with HUD SOI,) on to them, TMS FWD long to to make a SPI, then CHINA FWD LONG to slave the TGP. If you are too close, just break away and come around again. Your TGP will be looking at the place you made your SPI, and even if your targets have moved on, you can start looking for them there. Don't forget to make the TGP the SOI (sensor of interest), as its movement is much less sensitive than the hud cursor. If that's all a bit much at once, try to understand making different instruments the SOI, then make a SPI (easiest from the hud), then slave your sensors to the SPI. There's lots of stuff including videos showing this, and also guides and the manual. Here's one resource

FYI theres a dedicated VAC thread Here

I presume that you have an analog throttle, so what about num- and num+ :smilewink:

Nice Fix :thumbup: Sorry i could not check earlier, looks like someone else got there first with the 'northing' coordinate. And you checked both!! Below is example of 'easting' coordinate. (Hmm, i'm thinking E longitude, and distance in bullseye calls.....)

P546 P553 Suppose depends on definition of 'accurate'. In this context, its 'accurate' enough to get into the funnel when there's 10s left, up to a farily high altitude. I understood that CCRP attempts to compensate for the wind shift (and I accept that its not a perfect world). Interesting. How can I set this, I have only ever used CCRP for LBG's Would not have considered the LBG a weapon of choice for a road speed moving target, unless is was the newer 'dual mode' type. Not sure they are simulated in DCS. But this is probably subject for another thread.