strtok

I have a dell 30" at work and it's sometimes difficult to play games on it because of the high resolution. If you go for it, make sure you have plenty of space between you and the screen :) You'll also probably want to increase mouse pointer speed.

I thought this was going to be a "where's waldo" joke at first.

I didn't use the wrong ordinance, because I didn't have a chance to use any ordinance :) I think Lane is correct. My targets are being hit quickly by the other AI. The problem is that they attack every target the JTAC gives me until nothing is left :)

I've been using the fast mission generator lately on medium or hard difficulty and what I find is that the JTAC seems to give me -and- other AIs the same targets. Once I have a target I have about 30 seconds until the AI takes it out and I get the "abort abort abort". On one of the last missions I tried, I had about 4-5 attempts at this until the JTAC had no further tasking. Am I doing something wrong ?:)

Is it possible to raise landing priority with ATC? I've had a few times now during one of the campaign missions where I've been shot up pretty good, and have multiple system failures or engines out. I'll make it back to base, only to have the ATC tell me to orbit. Shouldn't I get priority ?:)

Still not sure what caused this, but uninstalling the saitek software and re-installing the X52 driver and the Saitek software seemed to fix it.

I've been using SJackBauer's X52 profile on dcs a-10 for a while, and it's worked wonderfully. Last night I installed the Saitek combat rudder pedals, and although my flight stick still works partially in game, I've found: 1. The X52 profile to map the ministick to the slew buttons no longer works, even though I have the A10 profile selected in the systray profile selector 2. Coolie right no longer seems to be able to select the right MFCD as SOI? Selecting the left MFCD seems to work, as well as selecting HUD soi from the stick. 3. The slider doesn't seem to send the N and B keys anymore. I have two systray icons now for Saitek. One for the X52 and one for the Rudders. Is it possible they're conflicting somehow? I have no profile selected for the rudders, and I have SJackBauer's selected for the X52. Because the major problems are the mini stick and slider not producing the right keypresses, it makes me think that the profile isn't being set correctly in the Saitek tool. This doesn't really explain not being able to set right MFCD SOI though. Any thoughts?

I have the same experience holding TMS forward long in the TAD. At this point I usually create a mark point instead. I feel like there's very little feedback that the SPI has been created.

I've done a few missions now of the first campaign, and while I can eventually find out where the action is, I don't think I've quite got the handle of the JTAC communication. I know when the JTAC reads off the briefing, I can manually enter in the 2 letter + 6 number location into the CDU and create a new waypoint. Is this necessary? Is there a waypoint included in the JTAC data? After the upload, I have a small red triangle/diamondish looking symbol on my TAD. It doesn't seem to be a new waypoint, however. What is the correct process? Thanks! --strtok