Jump to content

Woxof

Members
  • Posts

    68
  • Joined

  • Last visited

Everything posted by Woxof

  1. For those following along with this thread, (since I have been utterly unable to find an answer anywhere) the solution to my problem is the ERAS function. It's one of the tabs in the ODU, and with repeated clickings will remove the targets imported into the Recall page. A new set of 10 targets can then be imported and hit, just like the first 10 were. Works like a charm. Many, many thanks to the denizens of the Razbam Harrier Discord room, who Knew.
  2. I think you guys are both saying basically the same thing. I've tried deselecting the targets in the ODU, removing the target flags (with the T01, T02 etc., on the map), and reassigning them but neither has worked. But it is a complicated process, and it's entirely possible that I'm doing something wrong in the sequence. I think I need either step by step instructions from someone Who Knows, or a link that points me to exactly where I can find the steps. As far as I can tell, the instructions for removing one set of targets and replacing it with another do not exist in printed or video form. If you guys can show me I'm wrong about that I'd appreciate it.
  3. I've been enjoying the Harrier, using it against SAMs, mostly. I go into the map and designate 10 targets (T01, T02, etc.) for the GBU-38 JDAM, import them into the airplane using Shift-K, and am having good success during the strike. The question I have is, how can I clear the target list from the Harrier after the strike, so I can designate a new batch of 10 targets and hit 'em again? I've tried several different things to get the first strike targets to clear so I can hit another set with a second strike, but the bombs seem to just hit the targets from the first strike, now empty craters, again. Help!
  4. Don't know about anyone else..... But I'm personally pining for DCS: Thud Ridge. We already have all the MiGs we'd ever need. And we have the A-4. Obviously we'd need the F-105. But the A-7 is in the pipeline, right? What about the F-8? And is the F-4 now in process a USAF or a USN type? Because while we'll get one, we'd need the other, too. We already have the KC-135. What else? Maybe an A-6 or for the later years an F-111. Heck, keep it easy and just make them AI, too. See? We're really only an airplane or two away from making it happen. Get on the case, guys.
  5. Is there an English-translated cockpit for the J-11? I've been looking and cannot find one. I was sure I saw one a while back, but I've been wrong before...
  6. From the A-10 section of the update notes " The Ejection Seat Handle will not move now if the safety pin is installed. Triple E (Eject) keyboard command is disabled by the corresponding Ejection Safety Pin now.
  7. So where's the pin, anyway? I saw in the update notes that you now need to pull the pin for the ejection seat during preflight in the A-10C so you can eject if necessary during the mission. But I have no idea where to find it. Help!
  8. It tells me where the TGP is pointed, directionally, in relation to the airplane. Distance down that sightline is inexact at best. Telling me where it's looking in relation to the airplane is not really helpful. Telling me where in relation to the potential target -- now that'd be helpful.
  9. Okay, I tried it and it's still next to useless. Whether you hit the target when you do the first designation is more or less random. If you do get lucky and end up close, great, refine the alignment, redesignate, and you're set. If not, start over. And I have no clue how you even get close when you have no idea where the damned thing is looking. Actually, that's not fair. You do have some idea, but it's vague at best. Either 1. There has to be a way to know through the HUD where the TPOD camera is pointing before you do the first designation, or, 2. The target diamond has to move around on the HUD as you move the TPOD view. Otherwise...unless there's something to this whole business that I'm missing entirely. Which is always possible.
  10. OK, that I got. I think. I'll try it out shortly, to see if I really got it or need more larnin'.
  11. Ah, this sounds promising. Thanks. Using what mechanism exactly should I "lock the ground"? Remember I'm new to doing ATG using the TGP in the Hornet. If I'm following correctly, the "locked ground" will somehow show up in the TPOD screen. Then I can slew the marker onto the desired target? Is that right? Or, are you saying the slewing will all take place on the HUD? Then the HUD sends the target location to the TPOD screen? Either way would work, of course. And either is better than the current "It's over here someplace...?"
  12. And it's the next best thing to useless against stuff like tanks. Good for surface to air radar, but I'm not always hunting them. Anything else?
  13. No TPOD icon on HUD? What is the best way to find targets on the TPOD when I can't locate them on the HUD using a TPOD view icon? There has to be a better way than "Put 'em on the A/C centerline and guess?" This cannot be how it works IRL.
  14. Here's the .trk file. LastMissionTrack.trk
  15. This happens with all aircraft. Started with the F-18. I'll get a track to you in a bit.
  16. I have a problem which, if not exactly a bug, sure feels like one. My Axis Assign button, on the Control Options screen, does not work. As in, press it and nothing at all happens. Click, no response at all. No dialog box opens, so no axes can be assigned. This is in both the Stable and Beta versions, and on all the modules I've tried. Both versions are plain vanilla, unmodifed installs. Any help would be greatly appreciated. I'm going to hold off doing a complete delete and reinstall for now, in case you want me to test anything for you.
  17. Yeah, I have a feeling it'll be a total reinstall ... which I was hoping to avoid, obviously. We'll see. It's all the modules I've tried, and both the Stable and Beta versions. I guess I will file a bug report. At least that gets a trouble ticket started. I'll hold off doing the reinstall in case DCS wants to ask about this. For now.
  18. I think you're right But I haven't got the first idea how to diagnose and (hopefully) fix it. And if nobody else has seen this sort of thing it looks like I'm waiting for something from DCS. But thanks for your help, guys. At least you were able to confirm what I suspected -- that this one was beyond me.
  19. Yes, it has worked before I was trying to assign the rudder axis to the rudder pedals. Always worked before. Now I can't assign anything to anything, because the dialog doesn't even open.
  20. Yup, first thing Absolutely ran Repair. No effect.
  21. So, should I be concerned about this? Almost 24 hours and no reply from either the player community or DCS to my previous post. NineLine, are you out there? I'd report this as a bug, but I'm not clear as to whether it amounts to one. Help, please.
  22. Yes, the one on the Control Options screen. It does NOTHING when pressed. This is using the Stable version, and the F-18, both on and offline. Any ideas? It's not working in other airplanes in the Stable version, but it's also not working in the Beta, either
  23. Warning: Actual real life flight instructor here That's not technically correct. Trim is an airspeed control, not an AOA control. In a real airplane, you can set it up in cruise, with an appropriate power setting, and trim off stick pressures. Then if you pull some power off, the airplane will pitch gently down, hands off, and descend at the trimmed speed. From there, add power, and the airplane will pitch up and climb at the trimmed speed. This behavior makes many challenging things about flying a whole lot easier, like flying instrument approaches. Having the airplane help maintain a set speed takes a big load off. Demonstrating this characteristic is something we do in training, to help the student better understand the trim-power-airspeed relationship. Now this works in light airplanes and transport-category stuff, which is where my experience is. How well it works in fast-mover jets with FBW and autotrim we'd need to ask Wags.
  24. You guys are missing the point Been there, done that. Apply this dodge, do this workaround. That's not how it's supposed to work. If they don't want to bother supporting an autostart (because real virtual pilots don't use them, right?) fine, let them say so. So far, I have not seen one word regarding this problem. The bottom line is, right now the airplane as I bought it is broken. ED needs to fix it.
  25. Now I get it when it's warm, too Just tried to start the F/A-18 at the Kerman Airport on the PG map, using the autostart, 30 degrees C (in other words, NOT cold). Got the failure. So the Hornet is now unusable for me. I refuse to spend 30 to 45 minutes of my very limited available flight time just making the engines go (that's what the engine start time amounts to, spread over 3 or 4 flights in a session, not just the one.) This is not what I paid good money for. I should clarify that yes, this is using the Beta version. I tried an autostart at -1C in the stable version (at Echo Bay on the Nevada map, should anyone inquire) and did not experience the failure. Could somebody at ED please take a look at this? Or at least respond?
×
×
  • Create New...