Jump to content

TomCatMucDe

Members
  • Posts

    2084
  • Joined

  • Last visited

Everything posted by TomCatMucDe

  1. The RIO must select the stores to be jettison from his seat. By default nothing is selected. I am not sure if you can do it with Jester, I believe you can. It does work with a human RIO though.
  2. agreed. There is still a lot on the plate. Even many the existing features need a lot of correction
  3. as said by the others, this is not a bug. The aircraft really acts like this. The cover engages ACM and allows you to quickly jettison the stores that the RIO selects in his seat.
  4. alright then! thanks for this amazing level of fidelity and attention to details!!
  5. I have encountered an issue with engines not responding anymore and being stuck at certain RPM. On the way back from a mission, I was critically low on fuel and at Mach 1.4 roughly (escaping scrmbled Floggers), I iddled the throttles but the engines continued in their high regime and didnt repond at all. The throttle in the pit does indeed move and go until idle, but the RPM, Fuel Flow etc... dont move at all. When I got lower and my airspeed went down, suddenly the engines responded. attached the track of the long mission. The issue happens towards the end. Thanks and happy new year!
  6. Hi Nineline, sure here is a track based on the instant action BVR 8v8. as you can see; Step1: go to TWS Step 2: Slew the TDC left or right Step 3: go back to RWS There you will see that the RWS is not centered anymore, even when you go 140deg AZ TWS AZ messes up RWS AZ.trk
  7. Hi NineLine, This behavior is easily reproducible, if you go in TWS and go back to RWS the antenna will not be centered anymore and the radar will always be looking of to the right or to the left in the previous TWS Azimuth location. Even when you go to 140 Azimuth, the radar will not be centered. Sent from my SM-G975F using Tapatalk
  8. FYI. On the bug reporting subforum, the devs confirmed that the current implementation is correct and follow the real aircraft. Sent from my SM-G975F using Tapatalk
  9. Alright then ! Thanks for the follow up! Sent from my SM-G975F using Tapatalk
  10. Nah, I don't get butthurt on forums :) you are again derailing the thread. Ciao. Sent from my SM-G975F using Tapatalk
  11. Thanks Wicked! I have the impression is that sometimes I can't get the second contact to be fully red (system file) I'll test again if I still see the issue. Yesterday it didn't happen again. Sent from my SM-G975F using Tapatalk
  12. You are polluting the thread. You said twice that you were leaving ... Sent from my SM-G975F using Tapatalk
  13. I never asked for the hornet to follow true by default, but if you select the option on the HSI, it should follow true, which it does, only the AP doesn't which as you say is probably a bug. Sent from my SM-G975F using Tapatalk
  14. You really don't get it... Sometimes, I can't have a second system target and therefore I can't bug him. When this issue occurs I have only one system target that I can designate, the other remains a track file that is not buggable. I can TMS up on him and he would never become a system file to be bugged. Your contribution was not helping. Thanks and bye. Sent from my SM-G975F using Tapatalk
  15. To the other forum users, let me clarify my post: Does it happen to you to fail to upgrade a second track file to a system target once you have one already system target? Sent from my SM-G975F using Tapatalk
  16. Just don't be stubborn. I know how TWS works, I used it for years BMS and I used it for a couple of weeks in DCS. However sometimes, I can't get to bug the secondary Target and can't designate him. Most of the time it does work. Thank you for your contribution nevertheless. Sent from my SM-G975F using Tapatalk
  17. Ah I see what you mean, I think you misunderstood me. My point is once I have a primary bugged, sometimes I can't bug a secondary at all, TMS Up on him does nothing. To make sure that the second target is actually correctly seen, I unbug the primary and try to bug the second target, that indeed works, he becomes primary. So he is "buggable". It's only a test somehow. Sent from my SM-G975F using Tapatalk
  18. Thanks for the heads-up, but my opening post wasn't about comparing what Western aircrafts use in flying. It's about a functionality that is probably bugged. Sent from my SM-G975F using Tapatalk
  19. Hey Flamin_Squirrel, I didn't write to the pentagone to ask them to change to true north or magnetic north. I wrote to ED to correct a possible bug in their module... I suspect that like the real aircraft you can indeed change the heading to true north, but it's weird that only the tape changes but not the other systems like the auto pilot. Your comment about Western aircraft in real is a bit out of topic, nobody argued about how it is done in real. Fact is that AWACS and F15 use true north heading, for this reason I want to be in sync with them.and chose also true north. No more, no less. Sent from my SM-G975F using Tapatalk
  20. Of course not. I think you didn't understand my post. I can't bug the second target manually by placing the TDC over it and hit TMS up. If you think that's wrong, you should read about TWS or watch wags video on YouTube. Sent from my SM-G975F using Tapatalk
  21. is it only me or sometimes you cant bug the second target in TWS? I see the issue relatively often, both targets are within the scan azimuth and elevation limits. If I unlock the first target, I can bug the second target as primary
  22. You said if there is an option to switch to true heading it's a bug. What's your source that this option doesn't exist ? Sent from my SM-G975F using Tapatalk
  23. Interesting? Why ? It's not like this in the real aircraft, it isn't in any modern jet as far as I know. Sent from my SM-G975F using Tapatalk
×
×
  • Create New...