Jump to content

AvroLanc

Members
  • Posts

    1322
  • Joined

  • Last visited

Posts posted by AvroLanc

  1. Hi,

    At some point a bug has cropped in where the LASE TIME REMINDER/INDICATOR on the TGP MFD is removed from view when the last LGB in the current program is dropped.

    This obviously prevents the AUTO LASE logic to kick in at your set ALAS time, and also if manual lasing, the MLAS reminder is absent when this happens.

    In my track the first of 4 bombs is dropped in STEP and the MLAS/ALAS indication is correct. I.e it remains. 

    In the 2nd pass I dropped the 3 remaining weapons and the MLAS/ALAS goes away. Forcing me to manual lase at 10 seconds TIMPACT, AUTOLASE would never kicked in if I had that selected.

    In the past, the MLAS/ALAS logic remained until the weapon had impacted, even if it was your last LGB.

    It's a VR track, but you can still view the issue.

    Thanks.

    F-15 LASE TIME.trk

  2. If any new weapons are to be added, going with the 'variety' argument,  I'd go with Maverick first. As the only Forward Firing AG weapon, they'd offer some different gameplay options and they are relatively simple. Otherwise, no, I think working on GBU-15/AGM-130 and Sniper etc right now would be a massive mistake. They'd take up a huge amount of dev time and the long term foundation of the module would suffer. 

  3. I posted the following list in the official discord as a way to inform and guide discussion on the future of the F-15E and the features that still need to be done. Hopefully RB are aware of all.

    ''F-15E Unofficial Roadmap

    In an attempt to be constructive I suggest that we as a user base put together a list of new features and improvements that we might reasonably like to see in the module. RB's current 'roadmap' is very barebones and contains only big headline features in a very broad and generalised sense. Something more detailed is required, similar to what ED have done with Hornet, Viper, Apache etc. There was some talk of starting this yesterday, and I'll get the ball rolling.


    Note, this is not intended as a entitled or 'demanding' wish list, but as a collection of features still to be expected. No one is expecting a 1:1 recreation of the SE, this is a list of additions and improvements we might reasonably expect for a high fidelity module in DCS,  especially when compared to it's competing modules. Note that almost all of the features below have very similar equivalents in modules such as the Hornet, Viper, Tomcat and RB's own Mirage.


    Nor should this become a mere minor bug list, that can be a separate thing. 

    -HUD A/G
    --Enable TDC slewing of the TD diamond when IN CMD of the HUD
    --Add a working AG Gun reticle with AGR and LAS ranging as options.
    --Add the AG Reticle Range bar for AGR and LAS ranges when valid
    --Add the Pull-Up Cue and the F,D and M pull-up cue conditions. (Frag, Dud or MRA setting)
    --Add the Pattern Steering Line (PSL) command steering bar when a PSL has been designated on the AG radar. 
    --Add the 25 mil small reticle display as an option, selectable on the HUD repeater page.
    --Add pilot laser fire when IN CMD of Hud. (see below)

    - HUD A/A
    --Add/improve the Gunsight GDS and FNL calculations.
    --Add the 'Degrees till break lock' readout above the waterline symbol when in expanded azimuth radar mode.
    --Add IFF cues on STT or PDT TD box when valid
    --Add the target locator line (This may be suite dependant?)

    -HUD General
    --Add NAVFLIR Snaplook and Look-in-to-Turn features. Logic for offsetting display in boresight is already there.....
    --Add HUD Caged Velocity Vector.

    -- Add HUD PROG page and HUD decluttering feature.

    -TSD
    --Add the range marks and distance from centreline marks
    --Add the RBM radar search pattern footprint
    --Add the AG radar cursor position
    --Add the HRM patch map cue (footprint)
    --Add the TGP IR cue (solid and broken, dot for track etc)
    --Add ability to take CMD and cue the HRM or TPOD position and track state from the TSD.
    --Enable the PP and Steerpoint 'look ahead' feature.
    --Add the Ground Speed and Bank angle function for curved flight path turn radius prediction. Important for TFR.
    --Add the PDT or STT AA target symbol.
    --Add ability to display 'Avoidance Areas' (essentially threat rings) as defined in Mission Editor.


    -LANTIRN TGT IR / TPOD
    --Add dynamic Point Track box (symbology) for proper point tracking.
    --Improve the designation logic. There should be no LOS 'jump' when designating.
    --Improve/correct CDES behaviour. Track State boxed, no manual slew, etc.
    --Enable digital laser range readout above 8.2 nm, should be up to approx 13.4nm.
    --Enable manual level and gain control.
    --Add AA modes. Simple slaved to STT or PDT would suffice for now.
    --Add ability for pilot to fire TPOD laser for ranging when IN CMD of HUD (and not TPOD) and TPOD slaved to TD diamond.


    -A/G and Nav Logic
    --Fix MN and INS, non GPS functions. MN and INS are still too buggy and can't be trusted. Drift rate too high etc.
    --Finish the AUTO HAT logic. Improve LASER AGR SYSG hierarchy and selection logic.
    --Add MANUAL HAT. Add HRM, PASS and RALT as ranging options with correct conditions and usage cases. (Admittedly low priority).
    --Add the WIND MODEL with corresponding MFD page for capture and entry.
    --Add MANUAL Bombing mode. Both MAN FF and MAN RET mode should be added, along with the Reticle Depression entry on the AG DEL page. Other modules have this even if only 0.69% of users practice it.
    --HUD ILS bars should be command steering bars and not just Localiser and Glideslope repeaters.


    -UFC
    --Add the missing Data page 2 functions:
    ---TOT, Time on Target function with corresponding HUD command velocity wiper.
    ---Fuel at next Steerpoint 
    ---Lookahead ETE/ETA and TOT/TOA functions
    --Correct the logic and display of GPWS audio and add HUD GPWS pull up arrow.
    --Zero Point Designation feature for the truly sadistic.
    --Add Overfly and HUD position updating procedure.


    -WEAPONS
    --GBU-24 / Paveway 3 HUD displays and improvements. Model a correct PW3 LAR bracket display with ED's current MODE 1 (and sorta 2) flight model. Correct the TIMPACT time calculation for both AUTO and DIR.
    --Add Desired Ground Range DGR entry for PW3.
    --Improve MK20 Rockeye fuzing to have PRI and OPTION rather than TIME and HEIGHT. PRI is 1.2s and OPT 4s.
    --Improve BLU-107 ballistics calculation.
    --Smart Weapons page:
    ---Add the 'Un-Target' feature
    ---Add RPL QTY release feature
    ---Add EDIT FUZE once ED has completed new fuzing simulation.
    ---Add JSOW and WCMD burst height settings.

    -RADAR
    --Add FLOOD mode for SARH shots.
    --Add visual launch mode for AMRAAM
    --Add SBR mode for AIM-9.
    --Add TWS Sort mode.

    --Add missile flyout cue to vector stalks (dots and crosses)

    -TEWS/ICS
    --Add some basic ICS Jammer functionality. Use ED's Viper as an example of basic Noise Jamming and also Self-Protection track breaking modes.
    --Add Semi-Auto and Auto Chaff and Flare dispensing.
    --Add Mission Specific CMD dispensing function.

    -SOUNDS
    --Add updated AB sounds

    -FLIGHT MODEL and ENGINES
    --Add correct Windmill Airstart without JFS
    --Anything else critical here? 

    -3D MODEL
    --Add NVG on pilot models
    --Add visible Chaff and Flare expenditure in buckets.

    *****(almost everything above should come before what comes below, others may disagree)*****


    -NEW WEAPONS
    --AGM-65D/H/K/G Maverick. Model correct LANTIRN auto target handoff logic and HOTAS controls, ties in well with a corrected CDES mode. (Not sure if LITENING and SNIPER have this feature)
    --WCMD, probably soonish.
    --GBU-15 and AGM-130C. Bit of a complex rabbit hole. We all want it, but needs to be done well. 
    --GBU-28, GBU-27. Would add little to game until PW3 logic is adapted for flight path & ballistics of GBU-28 AND we get valid targets for GBU-28 in DCS world.
    --SDB. Someday.

    --SIT page and Link 16 Functions.
    ---Again a rabbit hole. Someone else may fill in details but: PPLI's, AWACS and Flight&Donor targets, Markpoint sharing, JDAM/IAM LARs and cues. Etc.

    --CTU's 
    ---Too far away to worry about detail at the moment but JHMCS, Aim-9X, SNIPER, Digital UFC''

    • Like 11
    • Thanks 2
  4. It used to be the case that NEVER would a NAV Designation (Sequencing to a target point in AG master mode) overwrite a RADAR/HRM designation.

    A NAV designation should have the lowest priority and should not overwrite, even if manually sequenced on the UFC, if you already have a RADAR designation made.

    However, a recent change now allows this.

    Now, if you make a HRM/RADAR designation with your Pre-target steerpoint selected i.e. IP (SP2 in my track) and then transition to AG master mode, and then subsequently select your target point (SP 3. in my track) to match up the DATA&HUD cues, it creates a NAV designation which overwrites. This is a big problem since it renders all your radar work invalid.

    Please see track.

    F-15 RDR DES OVERWRITE.trk

    • Like 2
  5. A bug since the FCR patch, it now seems that the CPG's NAV range (NX.X etc) is not updating when slaving to a TSD selected ACQ source.

    The problem only occurs after using a LASER range with that ACQ source. I.e. You select, either by CAQ or COORD page, a Point ACQ source and select 'Slave'. The NAV range now correctly says NX.X. If you now use the laser to get a laser range the range readout displays the laser range, however reselecting SLAVE should slave the TADS back to the point and reselect your NX.X nav range......which it does not.......the laser range remains.

    You can get the Nav range back by re-selecting the ACQ point, or selecting a different one etc. But the way it worked in the past was slaving reset to the NAV range.

    Maybe the changes introduced with the FCR introduced a bug in the logic.

    See track. Thanks.

     

    Nav Range Slaving.trk

    • Like 1
  6. A new bug seems to have appeared in BOB UP IHADSS mode. 

    When engaged the BOB UP mode should show a reference heading carrot on the heading tape (at a fixed heading at which you engaged BOB UP mode on).....which it does, but then this heading carrot responds weirdly to aircraft movement......

    It seems the heading reference is commanding a positional/translational change rather than just a fixed heading ref. It moves left and right along the heading tape with only VERY small aircraft translations. It's almost commanding a turn back to the BOB UP box centre, which it should not do.

    When engaged in AP Position Hold mode, the ref carrot stays fixed - obviously because the aircraft position is not moving.

    Please see track, excuse sloppy flying, it's easier in VR.

    BOB up heading.trk

  7. At the moment when setting up a combat jettison program, CBT 1 and CBT 2, the set program does not display in the centre of the main PACS base page. Looking at the available public docs and photos, the Jett programs should be displayed in the centre of the PACS page.

    Which makes sense, for easy reference, rather than hiding away on the Com Jett subpage.

    Please see images.

    PACS Jett.png

    PACS Jett 2.png

    PACS Jett 3.png

  8. 12 hours ago, TheGhostOfDefi said:

    Will there later be the possibility to set prioritization about which targets to engage? For example "Dont Prio targets near a Shot Mark" or "Prio Wheeled vehicles"?

    Right now im pretty sure there is nothing like that.

    I dont mean the Prio by movement.

    There's already a few tools, but not in the exact way you want. You can set PF or NFZ as already suggested, but this is a little time consuming as requires some prep. Best option in the long run though.

    Otherwise you can easily select/cycle the next FCR target with the NTS button. You also use the cursor on the FCR screen to select your desired NTS target. 

    Automatically disregarding SHOT marks wouldn't be practical. SHOT locations are saved as LOCATIONS and not targets. The missile itself may have not found the target and attacked another near by, leaving the intended target alive etc. 'SHOT AT' are for awareness only.

  9. No, there’s no way of doing this in RL.

    You have the ability to save all target locations as you already describe.
     

    I guess the problem in real life is that FCR information can get stale real quick. The TSD symbols even dim after 5s for moving and 30 secs for stationary. Detected targets are designed to be acted on quickly. What is a column of armor in one location could be a column of trucks 3 mins later. You can already store a location and make a mental note that it was a platoon sized unit of tracked vehicles, but you’ll want to rescan to engage anyway.

     

  10. As of December update, when the TADS is slaved to any acquisition source, the dashed CUED LOS RETICLE in the TEDAC is now missing. Also, two errant cued los dots are displayed.....

    The Cued LOS Reticle and dots are still correctly displayed in the video page and IHADSS. Again, just the TEDAC TADS display is incorrect.

    Note, the actual slaving still works fine.

    Thanks.

    ACQ Cross TEDAC.trk

    • Like 1
  11. As of the December Update the TEDAC display is now missing the TADS Sensor Select Status. I.e When TADS is selected the TEDAC should show 'FLIR' or 'TV' in the upper left......it does not anymore.

    The label is correctly still present in the video repeater and the IHADDS weapon symbology. It's just the TEDAC that's bad.

    Also, I believe when the DTV is selected it should show 'DTV' and not just 'TV'.......if the reference docs are to be trusted. This is been incorrect since EA release, but just thought I'd point it out now.

    Thanks.

    TEDAC Label.trk

  12. 33 minutes ago, Hoirtel said:

    FCR worked well for me as pilot, one thing I am not sure if is if hellfires can be rippled? The ripple.ootion seems to only be available when the pilots helmet is selected as the site, once fcr is selected there are less options. Assume this is correct but not quite sure why or what the difference would be. I know bit of a gamer thing to do, you can fire them with gap of 2-3 seconds in between, but not sure what the ripple mode does for the pilots helmet. 

    Ripple mode is a specific mode for the Laser missile, which alternates laser codes. It does not apply to the RF missile.
    However, you can ‘ripple’ the RF missiles as fast as you can pull the tigger. You’ll notice the NTS (FCR next to shoot) target will automatically cycle to the next target every time you shoot a RF missile.
    You can ripple all 16 in this way. Just be sure to use PF zones to limit/prioritise the target area of interest. 

  13. 22 minutes ago, felixx75 said:

    AFAIK the docs only says, that CDES does not work, if you are slewing the pod. In the moment the slewing stops, the new position becomes the new designated target. The doc says nothing about an established point track in conjunction with CDES... 🤔

    I will be back home tomorrow, then I will test it. 🙂

    There would be very little point in having CDES if it didn’t work with a track mode……

  14. 33 minutes ago, Poptart said:

    You're welcome to post a track. That's not how it works in DCS. That's also not what it says in the docs.

    Yeah. I made it clear that it may be modelled wrong in DCS. It’s still WIP, and I’ve not done enough testing with CDES. 

    My description was correct though. What doc are you referring to? I’m using RL SE workbooks. The game manual is still WIP too. 

    • Like 1
  15. 1 hour ago, Poptart said:

    CDES is irrelevant in this situation. CDES and an active point track are incompatible options. If you designate too early, your ASL will be off by the time you arrive at the bomb drop point. If you're high enough, the bomb will track. If not the bomb will miss. Currently there is no way to adjust the bomb drop point for movement.

    This is not true. CDES and a track (point or area) are REQUIRED together for CDES to work. You also need active laser ranging (or HRM or PASS ranging methods (Not implemented)).

    When CDES and a Track mode are selected, and you're laser ranging and you have made previous TPOD designation, the designation point SHOULD follow the TPOD line of sight (i.e track LOS). Any TDC input will stop CDES.

    If this isn't how it works at the moment then it's bugged/WIP. 

    • Like 1
    • Thanks 1
  16. All CBU are suffering from multiple issues at the moment. SPIN for -87s doesn’t seem to be modelled and the MK-20 have incorrect fuze settings. 

    The ballistics seem to be wrong if you set a burst altitude above 1200ft. And the dispense/coverage areas are completely different to other aircraft with similar settings. 

    Hoping they get some attention soon. 

  17. There's a designation bug when in CDIP mode and the CDIP pipper is NOT HUD limited. If you attempt to drop bombs (in this case Mk-82) with a Ripple QTY more than 1 and with the CDIP bomb impact point within the HUD FOV  then a bogus designation is made at a great distance from the expected designation (at the impact point). (In this case 360nm, but I've seen other figures like 160nm).

    When dropping a RPL QTY>1 when the CDIP pipper is pegged at the bottom of the HUD (i.e impact point is below HUD FOV and you see a TREL figure displayed, then the designation is made correctly.

    Also note that any STEP drops are correct, whether HUD limited or not.

    Thanks.

    F15 CDIP HUD.trk

    • Like 2
  18. 2 hours ago, Rainmaker said:

    The pickle button will auto designate at the point of the CDIP pipper. In Auto, its done via TDC when caged to the VV. Working correctly, just could be more elaborately worded in the manual. 
     

     

    Related to CDIP designations….there’s a CDIP bug where any drop with a RPL QTY more than 1 will create a bogus designation approx 160nm away. Single drops I.e STEP will correctly place a designation at the CDIP impact point.

    Is this known to dev team? I’ll do a report and track later if not……

  19. On 6/24/2023 at 8:06 PM, Tholozor said:

    The new fuze options are WIP and currently don't do anything, selection is irrelevant at this time.

    That’s not quite true. The various function delays (I.e impact delays) do actually work. Not that you need to weaponeer anything in DCS but a 0.25 delay, for example, is noticeable. 

  20. 9 hours ago, admiki said:

    I never get big box. Only LOBL NORMAL on HAD.

    I believe the missile does 3 LOBL attempts of 3 seconds each. So after a max of 9 seconds you’ll get either a LOBL BOX and RF MSL TRACK or a NO AQUIRE if the seeker can’t find the LOBL target. 

    • Thanks 1
×
×
  • Create New...