Ptroinks

What I would also like to have (not to make this a "wish list" thread) is what we had in Falcon 4 after clicking the fly-button; the option to either start cold & dark, ready to taxi, or from the runway. I know there's a start up "cheat" (Rwin+home) to start everything up, but that takes time, even when using time acceleration.

I'd also feel like I was cheating. The AI "vision" is so much better than any player's vision would be, so It feels almost as bad as having labels on...

Absolutely! I'm really looking forward to the next patch.

I don't mind there being a random failure generator. What I DO mind, is that we can't turn it off if we want to! I am sick and tired of starting up my jet, going through all the checklists, and then have some #¤%& random failure just after take off. It doesn't exactly make me look forward to my next flight! Yes, having system failures is realistic, but pleeease, give us the ability to turn it off!

Excellent post! The IR needs some work! When rivers show up as hotter than anything else in the IR image (including vehicles and people), something is very wrong!

As I am still a noob when it comes to flying the A-10, a lot of my problems with the game comes from lack of experience and knowledge about how all the systems work. However, having successfully completed the training missions over and over again, and using what I've learned to do other missions, new problems arise. The manual is great for learning more, and it shows how things are supposed to work, but there isn't a lot of information there about what happens when we do something wrong and how to "recover" from mistakes. So before I become overwhelmed with an urge to ask the forum members about all of my problems (I do use the search engine!), I would just like to know if there is a "known issues" list anywhere. It would be very comforting to know what ED are working on to fix bugs and improve gameplay, and (at least for my part) that might save us a lot of time posting (and worrying) about issues that ED already knows about.

How do we compensate for such elevation computing errors? If you're in a sort of "search and destroy" mission, where you have a general area to look for targets, the target elevation could be significantly different from the waypoint. If there's no JTAC, does that mean you can't attack? I don't understand why a waypoint would be displayed as a point in the air. It just doesn't make any sense at all. If I'm in a mission, and I'm flying to a waypoint which is set to 5000ft, I would be screwed if There were targets around there, because my targeting computer would be calibrated to the waypoint altitude...

I think I figured it out! We can enter the data in any order we want, but if the UTM zone has to be changed, it must preferrably be done prior to entering the UTM coordinates. If we enter everything, and notice afterwards that the zone is wrong, we have to input the correct zone, and then re-enter the coordinates. I can't believe I didn't see this before... When I entered the wrong zone the very first time, the coordinate line changed to all zeroes. I noticed it, but didn't think that it mattered. So what I got, was the very correctly displayed coordinate of GG0000000000 in grid 38T :music_whistling:. Then, when I changed to the 37T zone, I got GG0000000000 in that zone (obviously!), making me think that there was some JTAC bug. Now, I'm just wondering how anyone managed to get the correct waypoint to the target in that mission. Of course, you get the JTAC data to the TAD, and that's really all you need, but it really bugged me (no pun inteded) that I couldn't get those coords right! Strange that the manual doesn't mention anything about UTM zones, though... Well, now I just feel kind of stupid, but if someone else gets the same problem, I hope they will find their way to this thread :).

Uh oh! Maybe it has to do with timing, then. I waited a little longer before I started punching in the UTM coords the last time around. I still had to change to 37T, though. I don't know if that has anything to do with where my aircraft is when I enter the data. From what I understand, the CDU "defaults" to the UTM-zone where the player spawns. I'll have to test this a little more...

@Dragon The only difference between your short (and excellent) guide and WarriorX's guide is that you're telling me to set the STEER PT knob to MISSION before I enter all the data. WarriorX tells us specifically to set that knob to FLT PLAN before entering data (so I guess I'm blaming my frustration on WarriorX ;)). And wouldn't you know it, that short item on the list apparently made all the difference! I'll test it some more to be sure, but right now, I have the target WP 3,5nm to my 3 o'clock, so I'm officially in hot :smartass::thumbup:. Just for the record, WarriorX has excellent guides that I use, and his work is invaluable to any new Hog pilot! @McVittees If your waypoint is too far away to be anywhere near a target area, you know! I guess all you have to do is to enter 37T/38T (the one you didn't use the first time) into the CDU to fix it. Edit: Oh, Dragon already answered that one...

If any of you want to take a short A-10 flight, please try the "Shooting Gallery" mission and tell me if you got those coordinates to work (or maybe you even got different coordinates! Now, that would be interesting!).

Entering 37T shortened the range to 160nm, so it's closer. I also tried adding both one and two zeros to make it GG03290668 and GG0032900668, and both coordinates were accepted and were even closer, about 50nm away. I would still like my coordinates to point to the target area, though...

I guess this is just another "user error" thread, but I just don't understand what I could possibly be doing wrong here :mad:. I'm trying to fly the Shooting Gallery mission. I take off and contact JTAC, who gives me the 9-line. The coordinates are UTM (two letters and six digits), and in this case, they are GG329668. I'm following WarriorXs UTM guide to the letter, and it all works great, until I find out that the coordinate I entered, is 850 miles away. What am I doing wrong? I restarted the mission a couple of times just to see if that would give me some reasonable coordinates, but I get the same every time. So if the coordinates are OK, is there some switch or setting that I don't remember (I have WarriorXs guide printed out, so I know I'm not skipping anything there) that has to be set before I can get the coordinates to work?

Hmm... Could it be that the grass already has some small friction bug in it, and if the nose wheel on the A-10 suddenly "dips" below the runway textures and "touches" the grass below (My guess is that runway\taxiway textures are placed on top of grass), the sudden friction will tear the nose gear clean off. I mean, it wouldn't even take "super glue grass" to do that. The runway and the grass have different friction values assigned to them in some way (the grass obviously having a higher value), and when the nose wheel comes down a runway doing 100+ kts and suddenly hits grass, the outcome is obvious. If my explanation is correct, that is :).

Do A-10s have extremely fragile nose gears? I was taking off from Beslan (Smerch Hunt mission), and just as I was pulling back on the stick to take off, there was a loud bang, and the nose pitched up violently. The screenshots show my A-10 just before my nose gear "exploded", the instant it happened, and then how much it made the aircraft pitch up. Is this some kind of bug?

"Waypoint line select keys, R5, R7 and R9. Used to delete or overwrite flight plan waypoints" What does R5, R7 and R9 mean??? Edit: How did this double post end up here???

"Waypoint line select keys, R5, R7 and R9. Used to delete or overwrite flight plan waypoints" What does R5, R7 and R9 mean???

My question regarding this, is why an A-10 pilot would have to use FUNC+SEL rocker to select a waypoint, when so many other inputs to the DSMS pages are done by just entering a number from the UFC and then clicking the appropriate OSB on the MFCD. Obviously there's a reason for it, I just would like to know why the DSMS needs that specific kind of input to that specific input.

I figured out how to use the TACAN now :). I don't know what I did wrong the first time (hearing the tacan morse code, but needle not pointing towards the tanker), but now I know how to do it right! Thanks a lot for all your help!

Bearing pointer 1 (which is supposed to point to the steerpoint) moves clockwise around the HSI (endless loop) while the course deviation indicator on the course arrow tries to keep up (telling me I'm too far to the left, then the right, and so on). I let bearing pointer 2 (which is supposed to point to the TACAN transmitter) lead me to wherever it was pointing at, and when the pointer turned 180 degrees (and I was at my "destination"), I was over some forest with no buildings. Maybe there's a bug there. I don't know... I hope my english was good enough to explain that... Edit: I don't know if this picture illustrates it better. Maybe it will just confuse you more :).

I don't know what I did, but I got the TACAN to work :). I don't use the course needle though (which would only work if I wanted to approach the tanker from a certain bearing), but now one needle points towards the TACAN transmitter, and the other towards my current waypoint! Excellent! But that last .trk file I posted; what the heck is going on there? Again, look at the HSI needles... About the question in my first post regarding the Mavericks, do any of you experience the same, or am I doing something else wrong? :)

I tried all of the TACAN modes. I got range information to "something" about 40 miles away (Edit: sorry! The range info I got, appeared only when I clicked the ILS button adjacent to the TCN button). I guess I'll have to figure out what that was. Something weird happened when I tried it just now, though. Take a look at the needles on my HSI in the short replay I attached. In the meantime, the NWS button to reset the refuel light to "ready" worked, but it seems I'll need to get a good HOTAS to be able to maintain proper level flight and speed. BTW, what do you guys use? Thrustmaster or Saitek? The HOTAS Warthog looks a little big to be placed on a desk, so the stick seems to end up too high to be comfortable to use (if you know what I mean). refueling2.trk

I turned all the HSI knobs, but nothing changed. I'm going to try that again, though, in case I missed something. I didn't press the NWS button after disconnecting, so that explains that :). I guess drilling the start up procedure will make it easier (Never thought about the bleed air and main supply. When should I engage those?). I'm off to try again! I'll report back :).

I've been flying simulators on my PC for over 10 years now (a proud flight sim nerd, you might say :joystick:), but I'm new to the Warthog, and I have a few questions that hopefully will be embarrassingly easy to answer: -TACAN: I was trying to find a tanker with TACAN, which seemed impossible to accomplish. I switched to the correct channel (1X in this case), turned the TACAN knob to A/A REC, and press TCN on the navigation mode select panel. The needle on my HSI immediately points "somewhere", indicating it's recieving a TACAN signal, and I can hear the morse code. The problem is that the HSI needle is pointing in a completely different direction than towards the tanker. At first, I thought the needle was "stuck" in some way, but it points to the same heading when I turn. I made a refueling training mission in the editor, so there are no other aircraft on the map except me and the tanker. What could be wrong here? Probably user error, me being new to this sim, but what could I be doing wrong? -AGM-65 D/G: Locking on to a target with any maverick is easy, but I'm having problems breaking lock with the D and G versions. With the EO seeker versions, I can just slew away from whatever the seeker locked on to and try again, but when the infrared locks on to something, it's completely stuck on the target. To break lock, I have to slave it to boresight or SPI, which makes it time consuming to reaquire my targets. -Refueling: I had a reeealy weird experience trying to refuel, but instead of a long story, I'll just attach the track file. Be prepared to ctrl+z a lot! Why won't the refueling boom connect? And how the heck did the tanker manage to suddenly go into a steep dive and crash at the end? -Checklist confusion: (Yes, I know this question has a few threads in here...) The checklists I printed from the manual are different from the procedure used in the ramp start training mission, and I've seen a lot of different user made checklists for ramp start, and now I'm just confused. Isn't there ONE checklist that can be used for EVERY ramp start to get the systems up and running in the right order? If I follow the checklist in the manual to the letter, I get a few caution lights and alerts, and when I'm done, I'm far from ready to taxi :cry:. I hope someone will take the time to give me a few answers. refueling-wtf.trk