Jump to content

Razor18

Members
  • Posts

    1948
  • Joined

  • Last visited

Everything posted by Razor18

  1. Have you ever tried to put the Controls indicator on screen to see if and how the in game controls (in your case the throttle) follow your physical controller inputs? I think it would be a good starting point...
  2. Using the proper radios (COMM1 or COMM2) AND the proper frequency?...
  3. RIght, I was referring to earlier post here about land based TACANs. Should have quoted the post to be specific.
  4. I encountered this once, it turned out it was another TACAN within range, on the same channel, interfering. Might be different in this case, but worth looking at nonetheless...
  5. Try it without. I don't think it has any influence...
  6. If you don't climb after each duel back up to at least Angels 15 before committing again, he will always hit the drink when he tries to nose down for speed. Stupid as it is, but that's all AI can do atm
  7. I don't think guys this has anything to do with the original bug report. If you think your issue is a bug too, maybe it would worth it reporting it in a separate Bug topic, as probably the solution is also totally different, but definitely worth to take a look at too? Regards
  8. Hi Bignewy, any tally about the date of the next update at the usual place?: Patch status
  9. Go to Options / Controls. Select F-18 Sim. In the next field to the right, select "Axis commands". Below in the big window scroll down to Thrust Left. In this line go to your throttle column (see column header). In that field press RIGHT mouse button (NOT the left one). From the pop up menu choose "Add combo". It will look for input, so move your left throttle up and down, until it recognizes it. Do the same thing with right throttle. Go in game, check if throttles moves forward when you push yours forward. If not, go back to the same place, bring up again pop up menu with right mouse button (or simply highlight the line and then at the bottom press "Axis tune"), and check the "Reverse" box. Reading the manual would also be beneficial. This is not a game in any regard, and learning curve will be steep, but very rewarding. One must have patience to learn, or he should rather go play War Thunder or some plug-and-play eye candy arcade game.
  10. Sorry then, probably misunderstood. Pressing Finish suppose to put all (incl. new) commands onto your clipoard for insertion. And the Keyword Collection group must be consolidated in the Profile edit window.
  11. I think if you had ever went through the manual, or at least throught the first steps, you would know what was meant. Please open VAICOM manual, then press Ctrl F and type in the top right search window: finish steps.
  12. Yeah, I even forgot it is in the RL plane. I had to look it up...
  13. I'm afraid it has nothing to do with restarting (which means pressing finish button on one of the VAICOM control page tabs, don't remember which now. YOu will find it in the VAICOM manual, or in a pop up window in VAICOM after perssing mentioned Finish button. Back to the original question, I also have Comms menu popping up for no apparent reason. I did not investigated so deep yet, but my culprit is rather the Voice Attack listening window, that usually picks up words sometimes you didn't even say at all. Some said it is some wrong joystick assignment, but I don't think so, as this one I checked several times. I think it can be some "ghost" words, but as I said, didn't spend so much time investigating. Not sure I understand what you mean... You only need to re-edit commands (copy-paste bla bla) after a VAICOM update AFAIK, DCS update do not touch Voice Attack or VAICOM I guess...
  14. Is it present in the RL Hornet?
  15. Sorry, what I meant was Auto Throttle Controll in Approach mode.
  16. It depends on your speed and the amount of angle you need to turn for the new heading. I usually use "heading select" switch to start the turn, as many miles earlier, as much hundreds of knots I'm flying. So, flying 300 KTS I start turning 3 mileas earlier, if the turn is around 50-90 degrees (left or right). If the turn is a shallow one, less than 50 degrees left or right, then 2 miles is enough. If it is a sharp turn, meaning more than 90 degrees left or right, then I start is as early as 4-5 miles from waypoint, to remain on the "inside" of the route legs.
  17. How can I have a pilots body visible in a first place?... EDIT: Disregard, found it RShift P (if available for the modul)
  18. Hay Glyn, will that be Supercarrier-based? Can't wait for it...
  19. Might be a bug, but bigger surface contacts (ships) were definitely visible with or without NVG. Interestingly, on the 2nd or 3rd try, from miles out I finally discovered the two groups of fastmovers, when wingman reported "Contact", but only WITHOUT NVG, seeing two small group of about 8-10 tiny lights in both groups in the darkness. But then as I came closer, the lights disappeared into total darkness, contrary to what I expected to be more visible as I'm coming close. So, definintely some kind of a lighting bug.
  20. Dang, it was a 1.5 hours long mission from Raven One, not sure how long in size the track could be. How can I retrieve the track, if I didn't fly another one since? Edit: found it, 69 MB... geee... I suppose I can not trim it down somehow? Or it would loose it's point then anyways? EDIT: made a track by simply starting a SC Case III recovery, find attached. Totally the same things happened. But the track did not recorded any communications. I used Voice Attack and VAICOM, and went smoothly in game, dunno why not recording in the track. However if you simply start the same SC CASE III recovery mission (Persian Gulf), all you need to do is calling Marshal, and you can see what happens. By the way altimeter callout is also off by 0.01, because I guess Marshal should say altimeter 29.92, but she said 29.93 instead. I reported it in the F-18 bug topic, together with a fuel state and altitude being also off. "Angels 16.5", when altimeter shows 16040, and "state 10.3", when fuel qty is in fact 10150. readback.trk
  21. Hi, in a Case III recovery player's readback is totally off, dunno if it is Hornet bug or Supercarrier bug, sorry, if wrong place here. Reporting in to Marshall, and giving my bearing, distance, (altitude?),and fuel state, Marshall gives me instructions: "...expect final bearing 164, altimeter 29.88, Marshal on Mother's 344 radial, DME 23, Angels 8. Expected approach time is :41" "My" auto-readback to Marshall: "Marshal, 403, DME, angels 24.5, expected approach time 0, approach button 15" Marshall replies: "Redback correct", altough no DME number repeated, Angels 24.5 is my present altitude, and expected approach time is not 0. Am I missing something, or carrier to F-18 comms still W.I.P.?
  22. Does ICLS work now w/ full flaps too? Some months ago Grim Reaper said in his YT video ICLS only works in "half flap" yet.
  23. Thanks, I was just surprised/confused seeing that on UFC the first time a few days ago. Hopefully some clarification comes out soon...
  24. I assume due to the new IFF function alright, but is there any information about this two options selectable by pressing IFF button on the UFC? Thanks
×
×
  • Create New...