Jump to content

ice41

Members
  • Content Count

    17
  • Joined

  • Last visited

About ice41

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I think you're confusing datalink symbols with normal TWS Symbols a solid red triangle is a datalink track correlated with onboard sensors like the radar any correlated datalink tracks will override the normal TWS symbols normal TWS symbols are a small solid square for raw search returns a big solid square for Track Targets a big hollow square for System Targets and a big hollow square with a circle around it for Bugged Target when datalink is present, hollow red/green symbols are only datalink tracks and not seen by your own radar TWS
  2. I don't use Streamdeck but from what I can find, Saved Games\DCS\Scripts should have a DCS-ExportScript folder inside DCS-ExportScript there should be ExportsModules folder inside ExportsModules there should be a F-16C_50.lua replace this file with Tess's F-16C_50.lua and that should be all you need to do to not crash
  3. Something is moving your plane after the canopy closed, like really strong gusts of wind. I think that's affecting the alignment.
  4. This seems to be new to 2.7 since I never noticed problems rearming previously. one example of reproduction steps F-16 set to take off from parking hot, default empty loadout rearm to put 120C on stations 1,3,7,9 AIM9X on stations 2,8 enter and leave dogfight mode after rearm completes rearm to put 120C on all stations 1,2,3,7,8,9 after rearm completes, enter dogfight mode and DCS hangs I noticed DCS only hangs if there are 120C on stations on the inboard side of AIM9 stations for example, the game does not hang if stations 3,7 were untou
  5. The oval on the HMD implies they are using ACM Bore with the helmet sight. As far as I know, the radar transmit conditions in ACM is still incomplete/inaccurate. I've heard that holding TMS up is suppose to have the radar follow the HMD but not transmit, and then releasing TMS up will turn on the radar to lock whatever's in the radar beam. and entering ACM mode is suppose to place the radar in a no transmit state until a search mode is picked using the TMS. Both of these are currently not implemented. As a workaround for now, I remember doing either holdi
  6. Uncage is not a must. Move the seeker diamond over the target for a good tone and press weapon release is enough. Uncage helps if you aren't looking perfectly at the target or aren't tracking the target perfectly with your HMD. More reliable because the tone means the missile sees a thing that it can track, it does not guarantee this thing is the target that you want. Flares near the target is one possibility that comes to mind. I don't remember if you can get a 9M tone looking at the sun.
  7. symbols for datalink tracks override the usual symbols in TWS I've not seen any Unknown or Suspect datalink tracks so this is for Hostile tracks only hollow icons are datalink tracks that your radar does not see white dot shows up for radar returns that do not have a track file yet the hollow icon becomes filled in when TWS builds a Track target and the Track target matches a datalink track with datalink tracks visible on the FCR, System target does not have any visible difference than a Track target. Only difference is the radar cursor will magnetize and stick
  8. How steady is your plane when you release the missile? I noticed an uncaged seeker can't keep up with the target if I roll my plane too quickly, especially if the offbore angle is high. I've seen some of my high offbore shots go ballistic off the rail if I was rolling when I launched even if I had a good tone the moment I pressed release.
  9. ice41

    F16 FCR

    detection ranges are a lot better for targets flying directly at you compared to targets flying away from you 15nm for a target flying directly away does not seem too unusual. whether this range is accurate to real life, I'm not qualified to say.
  10. the current F16 INS in DCS will start alignment with SALT set to the barometric altimeter value, and SALT can be changed by the barometric pressure knob on the altimeter during alignment. I noticed that when an alignment completes and the knob is turned from ALIGN to NAV, the SALT will magically be synced to the actual altitude reported in the external view info bar regardless of the value used for alignment. The odd SALT value in the screenshot is most likely an effect of the inproper alignment procedure. wptmd7675 I took a look at your original trackfil
  11. ED's Viper manual page 188 says "It is a three-position switch that overrides any mode except emergency jettison." in reference to the dogfight/missile override switch. If selective jettison is considered to be a master mode, then the current implemented behaviour is intentional.
  12. Did you verify your coordinates? After a full shutdown at a different airport, my stored heading alignment has my original spawn point's coordinates and heading.
  13. Do you do the full 8 minute INS alignment and enter in the correct GPS coordinates after you repair?
  14. I've ran into this once before and thought it was bad luck. Just messed around to find why it happens. This only happens in A3 or A1. Bars and TWS/RWS doesn't seem to matter. When the scan is about to bounce off the right side azimuth line, slew the cursor to the left to drag the azimuth limit. Time the slew correctly and the radar gets stuck. When it gets stuck, a quick slew to the right can fix it. The radar seem to only get stuck on the right side. If I attempt the same thing on the left side, I can see the bars looping as I slew to the right but it never gets stuck when I sto
  15. The bomb fall line and the TGP location never matched for me until I realized the target box needs to be slewed with HUD as SOI, and then switch to TGP SOI to refine the Point/Area track. I don't have the map for the track so I'm wondering if this is what's happening? Start with TGP SOI and hit TMS down to CZ and recenter TGP on the target box. DMS Up for HUD SOI and slew around until a target comes up on the TGP, and then TGP SOI and switch to point/area track to track the target. The CCRP target won't be exactly on the target, but I found this to be close enough that the laser can corr
×
×
  • Create New...