arteedecco

Odd because that is what makes it work. Otherwise I don't get the asterisks next to the OSBs on the MFCDS and cannot load mission data.

I was running into this problem and would have to restart my avionics power-on checklist. What I determined to work (can someone explain why?) is (with engines running) flip both of the following to ON: 1. CDI Power Switch; and 2. EGI Power Switch then immediately turn the following to ON / TEST: 1. CICU 2. JRS 3. IFFCC It must have to do with timing, but could it be a bug? Reason being, I know that the DTS UPLOAD COMPLETE message has been showing but no asterisk appeared next to any of the MFCD OSBs, including LOAD ALL. You can press it all day long and get nowhere. I will have to double-check for the IFCC NOT READY message but I am fairly certain it isn't showing. The problems seem to be if you follow the BETA 2 manual for startup (Set Up Auxiliary Avionics Panel (AAP), p. 424) and switch the CDI and EGI to ON with just the APU running then get both engines up and running, then switch the CICU, JRS, and IFFCC to ON / TEST (starting p. 431). I also never see mention in the manual to use the MFCD to LOAD ALL. Any thoughts?

Lol... Thomasew... looks like we had the same prob, just coming to it from different angles. Guess it would be nice to have a little more discussion on this in the manual. http://forums.eagle.ru/showthread.php?t=60929

Ah, didn't know about the "M". I'm assuming that masking is sometimes occurring even if I can't actually see any of the aircraft in the image, which is why I can't get it into AREA / TARGET tracking mode even when the image appears unobstructed?

I've noticed some issues with navigation concerning lines showing up between waypoints on the TAD and auto-sequencing between points. On the Auxiliary Avionics Panel (AAP) [located on the right console just below the CDU] the STEER PT select dial can be set to FLT PLAN, MARK, or MISSION. I was a little confused as to the setting to use during various phases of flight, so I thought I'd write it out here in case anyone else was confused. For some reason I got it in my head that during startup, once the system is ALIGN you should put it in "MISSION" mode since you are about to fly a mission. However, this didn't seem to work the way I wanted it to. I was expecting to have lines connecting all of the waypoints of the programmed mission. Instead, what I saw was simply the waypoint box for whichever waypoint I had set as the current steerpoint. The simple (and correct) solution is to simply put the STR POINT switch into FLT PLAN mode.... giving the desired functionality. I then ran into another annoyance that I wasn't expecting, but makes sense after review. Sometimes while flying a mission I didn't want the nav system to automatically cycle to the next waypoint in the flight plan as I crossed over the previous one. This was especially problematic when you have slaved all to SPI and have designated the steerpoint as the SPI, while using the slaved TGP to search for targets in the area around the steerpoint. It is very annoying and disorienting to fly over a steerpoint, looking carefully for targets only to have the current steerpoint change every time you pass over. Again... user error. This is basically good testimony for why it is important to understand the systems of the aircraft; how they work and why they do what they do. The solutions to this are simple: 1. On the CDU, click the Function Select Key (FSK) for the FLIGHT PLAN MENU page, "FPM", click the Line Select Key (LSK) along the left-hand side of the CDU next to the active flight plan to toggle from AUTO to MANUAL sequencing between waypoints. >> This will make it so that the system will not automatically sequence your steerpoint to the next waypoint of the active flight plan every time you fly over it (helps when you're remaining at a particular waypoint) 2. Flip the STR POINT switch to MISSION mode as you near the desired steerpoint >> This will keep the system focused on the currently selected steerpoint until you select another one and will clear the TAD of all other waypoints and connecting lines. NOTE: MISSION will cycle through all waypoints of the mission database, which could be a bit much if you have a bunch entered into the system. Also, keep in mind that if you have designated MARK points that you are working with it may be a better solution to switch the STR POINT switch to MARK 3. After the TGP has slewed over the current steerpoint, make the TGP MFCD the SOI and then make the TGP the SPI >> This will *not* keep the system from auto sequencing steerpoints to the next waypoint in the active flight plan (if STR POINT switch on AAP is set to FLT PLAN), but it will keep your TGP from zooming off to look at the next waypoint when it automatically becomes the active steerpoint Overall, it seems that SOI / SPI is one of the most important, tricky, and error prone areas of the whole A-10c (advanced avionics / targeting) learning curve. Glad they highlighted it in the manual (wise). I am still looking for the best way to locate threats quickly without resorting to low passes over an area, looking for tracer rounds! The TGP seems to currently have terrible target acquisition capability unless there is already smoke from burning vehicles in an area, marker smoke, or a waypoint from JTAC that you can hook via the TAD. Guess it just goes back to the "good ole days" of being a FAC when you had to rely on whatever intel you had, comms w/ ground pounders in the area, and being "smart." I do have to say I am really happy w/ the AI gunners and SAM modeling. They are good enough to where you had better not get lazy, but not snipers who kill you on the first shot every time (like Arma2). I really like watching the SAMs come off the launchers and come after me. With the jamming pod active and some maneuvering it is possible to live through the experience. On the other hand... flying directly at a SAM while trying to gain Maverick lock under 3 miles is a good way to get shot down. Neat! I do have to say that I am looking forward to enhancements to the TGP including making the "focus" functionality actually work. Can anyone shed any light on the TGP tracking modes? I have been unable to comprehend how the system decides when it should be able to move into AREA and even POINT tracking modes? Seems to do with distance to the target and maybe with the gimbaling of the TGP optics, but I just can't seem to tell when / why it will track an area / point. Seems like you have to be in pretty close before it will switch to those modes. Thanks everyone! i am so stoked on this simulation and this community! Keep posting! Arteedecco

Go-around : Make it part of your flow (mental shortlist - "checklist") to retract speedbrakes completely >> as soon as your nose is above the horizon you're full throttle and cleaning the aircraft up (gear, flaps, brakes) Descent : You need to stabilize your descent anyhow, meaning you should have time for a quick shoulder check / outside view check (F2...peek...F1) One thing that may help is to get used to motor speed on the speedbrakes, for deploying in descents w/out having to peek. Practice on the ground during preflight.