Jump to content

Florence201

DLC Campaign Creators
  • Posts

    923
  • Joined

  • Last visited

Everything posted by Florence201

  1. If you get too far out of the "slot", boomer will tell you to Return Pre-Contact as a help to get stable again
  2. PM me and I’ll shoot you the table file I have
  3. It’s done by mouse button
  4. Strictly speaking VHF is 118-225, UHF is 225-399.975 low VHF is 30-80 and as pointed out, COMM2 will do Low VHF freqs
  5. Reset by pulling the knob out
  6. If you can find the forum to write this question, you skipped past the “Viper mini updates” entry that has a lot of how to videos
  7. Testing has proven greater ranges than depicted here. M0.9 and 30000’ will give you 35nm range. Going higher then increases this
  8. If you wait for the tracking radar then you’re in range with HAS
  9. The tables are already set with 80% of the systems in it. You only add/customise what’s not there
  10. New version 2.4 uploaded
  11. Ah the bashing of the virtual Sqn. Are we not talking about a virtual game??? I guess my “Virtual” Sqn found a way to improvise, adapt and overcome the current limitations with a newly delivered EA capability, rather than declare the game “Unplayable”.
  12. POS mode we have currently is for saturating the tgt area as strikers ingress. You are expecting MEZ penetration and therefore SAMs to transmit. Lob HARMs in POS mode to clear a path. They won’t work if SAMs don’t go active
  13. Y’all are getting way too hung up over this. Yes, it’s needed I grant you that. But “unplayable” is wrong. I’ve passed the BVR Trg sortie in my virtual Sqn with the Viper BE limitation
  14. Then learn...........
  15. When loading the jet (doesn't matter with what), ME and in game re-arm window do not display the same weight. In game Rearm window is consistently 1300lbs under weight for the same loadout. This is not affected by spawning a clean jet and adding loadout, or spawning a loaded jet. The weight calculation in the rearm window does not take into account the suspension equipment and is therefore off compared to the weight shown in the ME Reproduce: 1. Remove all stores, racks and pylons 2. Arm a single bomb on a random wing station 3. Remove store but LEAVE pylon attached
  16. In rl, they will pass datalink tracks for points, or EW fixes ref BE
  17. You can do a NORM align just ensure you hit Enter on ICP for Lat/along and Alt. Flashing ALIGN in HUD will occur after about 8minutes. Then turn NAV. You can switch DL on at any time (I power on as I put INS into NORM). Zoom out HSD Rng to check for DL tracks
  18. Not a viper specific issue and has been reported as correct by rl boom operators.
  19. So, why not try and narrow down what’s happening. My suggestion (as I did when reporting mobile SAMs problem). 1. Fresh mission. Test against SA11 2. Replace SA11 with a different system. Test 3, Rinse and repeat for all systems 4. Post trk files supporting results found
  20. Battery on and UHF radio on
  21. If it’s not showing video whilst in A-G, switch it to SBY then back to A-G
  22. The FCR page incorrectly displays Aspect Angle. Seems to be more prevalent when you are Right. AA appears to be displayed ref bandit tail (correct), incrementing clockwise (correct if left) but going past 180 without showing L/R, as it just continues to increase. FCR displays 20 instead of 16R, 22 instead of 14R. Trk file attached this is on 2.5.6.59625OB Viper AA.trk
  23. POS RUK mode searches within 20nm of a Steerpoint and thus actually takes that into account. This range is “less” when firing as it could potentially have further to fly to go past the SP. it will dive for a target once the programmed radar is active
  24. Can you add bookmarks to an already finalised TV file for debriefing purposes?
×
×
  • Create New...