Jump to content

ice41

Members
  • Posts

    33
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Your description sounds exactly like what I noticed here.
  2. Double check you're looking for it under Axis Commands, and you have a controller or HOTAS plugged in. The axis binds aren't on the buttons table, and will not appear with just mouse+keyboard. the rdr cursor switch - up/down/left/right directions are buttons and cannot accept analog axis binding, same goes for everything not on the Axis Commands table.
  3. Sometimes after locking and unlocking one target in RWS SAM or TWS, the antenna elevation axis center position will not return the antenna to center, and one end of the maximum elevation can not be reached. In the RWS trackfile, on the first SAM lock, the altitude numbers next to the radar cursor jumps up after the lock, and the SAM scan is above the target elevation. After TMS down to unlock, I recenter the elevation axis but the radar does not return to scanning the horizon. It lowers slightly from scanning above the target to scanning at the target elevation, and it seems like the radar thinks this is the new horizon position. The same radar elevation persists on switching to A1, and the radar elevation corrects itself to the horizon when I cycle back to A6. The next lock reproduced the same behaviour. But it did not happen again on the next 2 or 3 attempts. I'm not sure what made the difference. TWS trackfile shows the same thing as the RWS track. RWSElevOffCenter.trk TWSElevOffCenter.trk
  4. You can bind rdr cursor switch to an axis in the Axis Commands table. The up/down/left/right directions are for buttons only. I'm not sure about binding it to the mouse.
  5. I'm pretty sure SAM mode also trigger a lock warning.
  6. Do you use an axis for TGP slew? If that is the case, try adding a deadzone to the slew axis.
  7. Your line for the SB 2POS looks fine to me and appears to work when I added it to Mods\aircraft\F-16C\Input\F-16C\joystick\default.lua and bound the slider button to it My DCS sees a button pressed and held down when the slider is fully forward. In the jet, slider fully forward retracts the SB and slider back deploys the SB However on the landing approach when gear is down, the SB in the F-16 does not open to the maximum unless the AFT position is held, probably a risk of SB hitting the ground. So I'm not sure if doing a 2POS SPD BRK like this is a good idea.
  8. F10 map and INS DED page shows true heading (hence THDG in the INS page) while the HUD is showing magnetic heading. The numbers should be different according to the magnetic variation.
  9. I managed to reproduce something that looks the same if my jet started with 0% fuel. Do you know for sure that there was fuel in the jet? Edit: looks like SteelFalcon beat me to it
  10. Not certain if it is the cause here. But why is ELEC only on BATT and not MAIN PWR?
  11. Any chance that DCS-ExportScript is in use? Last time I heard about TGP crashes like this was caused by that export script. Tess also has a fixed export script in the thread linked. https://forums.eagle.ru/topic/252202-missing-crash-logs-f-16cs-tgp-causes-the-game-to-crash
  12. are you using DCS-ExportScript by any chance? https://forums.eagle.ru/topic/252202-missing-crash-logs-f-16cs-tgp-causes-the-game-to-crash
  13. Include a track file preferably on a free map so others can see exactly what you're doing and verify your procedure. Without a track file other people can only make guesses as to why it's not working. A note, TMS right can be done with the radar cursor anywhere. It will transition all current Track Targets to System Target, but you must not have any System Targets. TMS up with radar cursor on a Track Target will promote only that Track Target to System Target. This can be done when you have System Targets to promote additional Track Targets to System Targets. Whether you can still do this with a Bugged Target I do not know and will need to test. A few ideas as to why it's not working. FCR is not SOI. You're seeing datalink symbols which do not distinguish between Track target and System Target. You're on the latest open beta which, when no datalink symbols are present, does not show the hollow square symbol for System Target, and instead shows a filled in white square like a Track Target. You already have a System Target, or Bugged Target.
×
×
  • Create New...