Jump to content

Limaro

Members
  • Posts

    286
  • Joined

  • Last visited

Everything posted by Limaro

  1. Totally agree!!!
  2. Oh yes, in the other mission it works!
  3. Looks like it works for HSI, but nothing on ADI. And I also hear no beeping or background noise. EDIT: made video,
  4. I've tried the quick start mission A10C II night landing in Caucasus. There you have to land in Kobuleti i guess, the ILS is 111.30. But setting this up, and switching on has no effect. also tarce 67X remains dead in my case.
  5. Hi, did with the last oder second last update with A10C or A10C II change using of ILS or TACAN? Somehow I dont get them to work any more. Also in the A10C landing tutorial the ILS does not seam to lead to any effect doing all by instructions (it's on right frequency and switched on) Limaro EDIT: Corrected to TACAN, sorry cannot change Title...
  6. Sehr schade. Aber vielen Dank für die klare Antwort :)
  7. Hallo zusammen, kann man wenn man zu zweit im Multiplayer fliegt, der eine A10, der andere F18, sich irgendwie gegenseitig im Datalink sehen? Im konkreten plate ich aus der A10 aus jemanden in der F18 zu hooken. Gruß Limaro
  8. Ok, that's what I wanted to know:thumbup:
  9. But what and when would be the commication about the assigned stack?
  10. Hi, after some time of landing on the carrier I wanted to know how it works with the stacks in case 1 landing. I guess i've understood it in general. However, in the manual I don't find the part in the comms, where marshal tells me, which stack I should wait on, and also I tried to set up a game with douzends of F/A18 landing to force the need of stacks - but it just does not happen to change. The only thing is, that I do net get the Charlie signal when arriving. Do I miss something?
  11. that was the one I tried to point out :smartass:
  12. oh wow, thats a funny timing. thanks.:thumbup: Side note and maybe question to ED: I am wonderung how the decision are made to make this behaviour switching from one function to another. Particulary because there is a real plane with a real "how it works" as template.
  13. Hi, IIRC the TGP "resetted" to look forward again, when pressing China Hat Aft short. Now, the Laser search is starting. How can I let the tgp look into default direction again?
  14. Here is my contribution:
  15. Generally I prefer the F/A 18, but . I would say A10C anyway because it would fit best in the collection of what you already have. (Have to mention that beside I only now F/A 18, not the Harrier.) Maybe you should now only decide the order of modules to buy ;)
  16. I was testing VR. And I agree on your dogfight-issue. But once, putting on also by headset with still mounted TrackIR - TrackIR took over control of the view. However, it was not that smooth as usual. But maybe there is a way to switch of the VR for such a case.:huh: To the thing of "hitting" the buttons with the mouse. I have some side buttons on the mouse, and added the "precision-button" on it. So whenever I need to click I could fastly switch it on and again off.:thumbup:
  17. Thanks you were right. a lot of things were messed up. Commands suddenly there multiple times over category "General" and "GUI Layer". Strange, that there is not a "replace" warning, when assining.
  18. Hi, did the way how to create mark points change? I cannot create/see them with the Open Beta. The Release seams to work. Regards
  19. I have the impression this is caused, wenn mission starts at night, and later on, at day, the comms are messed up.
  20. I read some pages of the whishlist, and found many COMM-related things. Maybe the following idea was already mention somewhen, but as I consider this easy to implement, I hope it gets a bit more focus - or gets developed secretly hiding any feature-dev-workflow :smilewink:. Idea: COMM selector cursor to easily select and jump through the comm options - Assignable to keys or buttons of a HOTAS. It would reduce significantly the need take hands off the hotas to the mouse or keyboard. Example (please forgive me my use of paint) :
  21. Ah now I understand. So it's kind of mode, where my stick movements are ignored, but also the AP is not active. Is this good for anything? Any situation? @ randomTOTENI now also see it on the DDI. This was a quite unexpected behaviour for me. Thanks for your clearifications! :thumbup:
  22. I've uploaded a video that shows the issue as you can see in the controls view (bottom left) at some point I am making a lot of movings, but the plane does not react (as if autopilot is on). But the altitude is not kept in the same moment. Then, when suddenly the plane moves, I pressed the button to disable it on my hotas.
  23. Hi, I em experiancing something in the Open Beta since some time, which I cannot explain. And I cannot remember having that in the release version (2.5.5.???) a) Sometimes, when activating the barometric altitude keeping autopilot, the two dots don't appear. So it seams it is not active. b) Other times, when it's active (and there are the two dots) - they disappread suddenly - without me doing anything unusual. When this happens, the plane starts changing altitude. But when that happens and I try to steer, I feel that the Autopilot is still active as I have to steer a lot until it reacts (Or I can deactivate it by button). I have this quite often. Autopilot on - BALT not marked active, altitude changes anyway. What is the reason for that, and what can I do to keep autopilot active?
  24. I see. Not it's workingm using 110.90. Dont know what I did wrong presiously. But now I am still consued as I am missing is the Glide Slope. The Localizer seems to work, but the other. Is this normal for some airports?
×
×
  • Create New...