Jump to content

SaladinoSaurus

Members
  • Content Count

    14
  • Joined

  • Last visited

About SaladinoSaurus

  • Rank
    Junior Member
  • Birthday 01/01/2020

Personal Information

  • Flight Simulators
    Falcon BMS, DCS World
  • Location
    Netherlands
  • Interests
    Flight Simulation

Recent Profile Visitors

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

  1. You do realize Eagle Dynamics is modelling a General Dynamics (now Lockheed Martin) F-16CM (CM means standardized with Common Configuration Implementation Program, CCIP) Block 50 Fighting Falcon "Viper" used by the USAF/ANG from circa. 2007, right?
  2. You do realize that the USAF never even carried CFTs or Chutes... and the USAF Block 50s never carried LANTIRN either...
  3. Correct, as far as I am aware the USAF F-16s don't have the pylons wired to support smart weapons like JSOW, JDAM (and WCMD?).
  4. If you turn off the INS on the INS panel and turn it back on you will have to do an alignment again.... I don't see why this is a bug report....
  5. How much does the aircraft move? Possibly it is enough to disturb the alignment and "activate" NARF(if this is modelled), ED will need a track file though.
  6. I have done a cleanup and repair, and the exact same thing is happening. I don't think it's because it's a bug, I think it's incorrect SPI Logic. In DCS currently when making a slew difference in CCRP or EO-PREplanned and changing master mode to NAV (without pressing Cursor Zero on OSB 9) the slew differences aren't applied to all the steerpoints, or any steerpoint... in the MLU-M1 Manual I have gathered more info that it should do that, quoting this: This is from the MLU-M1 manual, PDF Page 164 (154 in the actual manual). It literally states what I said in the bug report/r
  7. First part of the bug report: In the Open Beta version of DCS (2.5.6.59398), the steerpoint/SPI logic is completely messed up, especially for the CCRP-type modes (CCRP, EO-PREplanned (PRE Submode for AGM-65s) and LADD -something not implemented yet-). I will use the CCRP submode for example, but the behavior is exactly the same for the PRE Submode for the AGM-65. When entering A-G mode (CCRP), the HUD symbology is incorrect as the Steerpoint Diamond is being shown, while the steerpoint diamond should always be occluded in the CCRP mode (aswell as EO-PREplanned and LADD) as the
  8. Setting XMT on HSD is not necessary, as this is a rotary that selects to what datalink "network" you will Transmit for example A-A info or A-G info, setting it to L16 will mean that you'll send your data over Link-16 network. This isn't modelled yet so no use in it at all
  9. In DCS in the F-16 when you command a Weapon Release in CCIP the CCIP Pipper (circle with dot in it) does not show on the location where you commanded the Weapon Release on the HUD. This is for both a normal CCIP drop and a post designate CCIP drop. It seems like this should show with some HUD footage to back it up: https://youtu.be/2uh4yMAx2UA?t=252 ^This is a Post Designate CCIP drop, with the Time Delay Cue -the solid dash- still on the steering(?) line. You can see that the CCIP Pipper is on the location where he pressed Weapon Release. This is an older HUD Scale, not the same on
  10. Posting a bug report about the VAHS Heading Scale not moving with the FPM in the following Master Modes: NAV, AAM/A-A, JETT and MSL. The A-G and DGFT mode DON'T have this behavior, explained later. In these three videos (I have timestamped the rough moments of when you can see the Heading Scale move down with the FPM(Flight Path Marker)) you can see that the Heading Scale is moving with the FPM downwards, I do understand that these F-16s are all different, but in my eyes it would make sense that the Heading Scale moves with the FPM to prevent them "going through" each other and not being ab
  11. Sorry... I am new to the forums, I just used the option that would seem to fit the most. As for the INS vs EGI question, I don't know! Ask the HAF why they didn't go all-out on the EGI, it allows for MANY, MANY more steerpoints as opposed to 127 (I am talking about 1000+, probably even 3000).
  12. An EIA is still possible with EGI and INS + GPS (AFAIK, it at least is possible with INS + GPS) equipped aircraft, it just requires you to turn set the FILTER MODE to INS, (LIST > 4 > Dobber RIGHT (SEQuence) and pressing any number on the ICP to set it to INS. This will set the KALMAN FILTER to only filter/update from the INS data it gets, not the GPS data (performing an EIA will not work when getting KALMAN filter updates), a standard EIA will increase the INS accuracy by about 40% for the first hour of the flight. The F-16 we have in DCS uses an INS panel, not EGI. I am not talkin
  13. I do! But I have been told posting pictures of the source would get me banned :(, any other way I can confirm this is correct?
  14. I know.. INS in F-16 is still WIP. It seems like you can get a status 6 with a normal GC alignment (setting INS knob to NORM and wait 8 minutes), which is actually not possible. The highest you can get with a normal GC alignment is status 10, status 6 is only possible with an EIA (Enhanced Interrupted Alignment) which requires you to move the aircraft and do lots of fancy stuff (EIA also needs atleast 4 more minutes, not 42-ish seconds). Status codes(number) with time and description (of a NORM alignment). The following might be completely wrong, I am not 100% certain as I don't have the
×
×
  • Create New...