Jump to content

Ramsay

Members
  • Posts

    3620
  • Joined

  • Last visited

Everything posted by Ramsay

  1. The DCS NS430 can be switched between True and Magnetic - however it's bugged on the Caucasus map and so you should use True bearings in the NS430's default "Magnetic" setting. Note - although the NS430 can draw an OBS course line as required (on a North Up map), OBS lateral/cross track guidance is broken and guides a "Direct To" path to the selected navigation point (rather than to the OBS course line). Unfortunately the DCS NS430 is both limited in features and buggy - so you are not making mistakes - rather you are finding/learning workarounds. While the NS430 looks "pretty", for practical purposes - you should focus on learning how to make best use of the accurately modelled flight instruments (wherever possible) in DCS's full fidelity modules and use the NS430 for cross checks and situational awareness.
  2. AFAIK this is intended - SOP in older OFP's was to set waypoint altitudes at ground level and the elevation data is used for "height above target" calculations, overfly position updates, etc. i.e. • GPS/Barometric Altitude - Waypoint Elevation = Height Above Target • Waypoint Elevation + Radar Altimeter (at time of overfly update) = Aircraft Altitude DMT TV/ARBS and TPOD use range, angle and LOS rate to calculate the slant range/angle directly - and hence a more accurate height above target bombing solution. Not sure how much (if any) of this is modelled in DCS or if/how RL digital elevation data is used beyond the planning stage in OFP H6.2
  3. It's also worth mentioning - 1. The Notes: • Departure Proc. section says "fly RWY Hdg to 2,500ft", the Real life SID is to climb to 2,700 ft before making a right turn i.e. to approx 1,000ft AGL) • Arrival Proc. section says "Cleared ILS 09", it should say "Cleared ILS 07" 2. The runway headings on the chart are given in true - most western charts and the F-15E use magnetic i.e. the F-15E's course is set to 64°M when landing at Kobuleti RWY 07. • Tbilisi RWY 13R - 122°M (128°T) • Kobuleti RWY 07 - 64°M (70°T) Tested F-15E Quickstart Mission --> "F-15E - Caucasus - IMC Flight.miz", DCS Open Beta Multi-thread 2.8.8.43704
  4. Ramsay

    Engine Start Order

    I believe* the Aux tank is symmetrical (i.e. mirrored on the right side), in the workbook it's labelled "Tank 1 Aux Tank", it's piped to/through the Right Engine Feed Tank i.e. the tank behind it, perhaps that's where the "Right Aux" label comes from ? * Block diagrams show Tank 1 + Aux as symmetrical, however isometric views in the workbook only show the perspective from the LH side, so I can't be 100% certain. I'm using the terms from the 1998 F-15E Student Workbook for the Fuel System where "Tank 1 Aux Tank" is labelled as such - however for the purpose of the workbook's fuel line schematics Tank 1 and the Aux Tank are treated as one unit (so it's not documented in detail). Unfortunately I can't post diagrams from the workbook (I tried) as the information is more recent than 1980 and the workbooks don't include "public distribution" notices.
  5. Ramsay

    Engine Start Order

    • Item 6 is "Tank 1" and includes "Tank 1 Aux Tank" as part of it. This "Haynes" F-15 diagram is likely the best I can do without directly referring to a F-15E Student "Workbook". • Item 5 is the Right Engine Feed Tank (Tank 2) • Items 3 and 2 are the Left Engine Feed Tank (Tank 3A and 3B) Source
  6. Early WIP from 3 years ago @2:00:33
  7. Deephack's Mirage Tutorials are recent and up to date.
  8. No, it's still there - It's shown by default when loaded with cannon, rockets or mistral missiles and hidden when unarmed or carrying HOT3 missiles. To show/hide the gun sight in the SA342L, there is a clickable "hot spot" near the top of the windscreen (displays a green double arrow and a tool tip when moused over).
  9. That's just the way DCS works, expect to need more HD space when Heatblur's F-4, ED's CH-47, etc., etc. is added.
  10. I haven't tested it in VR myself - but this video @25:21 suggests it works fine in VR.
  11. Re @toro 6's bug report - as far as I can tell USR waypoints are working as they always have i.e. I've just recreated and flown this Grim Reaper NS430 example in the Gazelle SA342L creating waypoints using the NS430 map cursor and/or NS430 waypoint data entry. Comments • User waypoints are still particular about their naming i.e. 0001, 0002, 0011, etc. are trouble free but IIRC names like A, AA, TGT, etc. are problematic. However this may be working as designed. • The 2D NS430 popup didn't click and drag or scale like it used to but that may be due to WIP VR compatibility changes. • The NS430 since (January) is still reporting the WRONG GROUND SPEED in both Knots and KM/hr settings Tested using DCS Open Beta Multi-thread 2.8.8.43704
  12. Can you share a short track ? Are you sure the 1500 ft burst altitude profile has applied correctly ? https://forum.dcs.world/topic/330898-cbu-didnt-burstdet-trk-file/?do=findComment&comment=5263837
  13. AFAIK Eagle Dynamics are now responsible for weapon performance in DCS and act as arbiters for what is/is not considered "realistic". • You'll likely need to give feedback to them, including short tracks, .acmi or videos demonstrating against which targets/aspects you believe the mistral is under performing. • IIRC there are know issues vs AI helicopters due to their simplified (health bar) damage model and aggressive (perhaps unrealistic) use of flares. A success rate of 92% during training says nothing of how well it rejects flares or it's battlefield success rate (just that it functioned well and the troops who used it were well trained).
  14. 2x Empty CFTs = 4,386 lbs 2x Full (with ~9500 lbs fuel) CFTs = 13,738 lbs Note there are "minor" differences in weight between F100-PW-220 and 229 versions, so these values are approximate.
  15. Yes. The RL F-15E Flight Manual (1993) gives the "basic weight" plus crew as • Without CFTs = 33,500 lbs • With CFTs = 37,500 lbs (to the nearest 500 lbs)
  16. With TPOD HOTAS Mode selected (SSS double tap) Pressing NWS/Undesignate (usually once or twice), will undesignate whatever you've targeted and cycle the TPOD to the HUD velocity vector - you can then fly to place the velocity vector on a target and designate/ground stabilise using TDC depress.
  17. Unfortunately it's not unusual for tracks not to replay "exactly" as they are a recording of your inputs, actions, etc. - your bug may be difficult to track down if it's not easy to repeat. This is how your track played on my PC ... as said, if I took control of your track - I simply had to wait to get in range for the IRMAV to "lock" onto a ground object and I could press the pickle button. Have you setup a dead zone for your TDC axis as, IIRC any drift on the TDC will break the IRMAV target lock ?
  18. Thanks for the track file - what I see ? TL;DR: You attempted to lock a target at too greater distance for the IRMAV seeker, without a valid lock, the IRMAV wouldn't fire until you got closer. Detail: 1. You attempt to lock the IRMAV at ~15nm (using the LH MFD) - as the cross hairs fail to close (i.e. lock), it fails to launch. 2. You switch to using DMT-TV (RH MFD) and attempt to designate, while still closing distance on the target. 3. At 10.2nm, the IRMAV cross hairs reappear, perhaps because it senses a lockable target or a sensor slew. 4. You switch to IRMAV mode again and the IRMAV was able to lock on a railway telegraph pole and you fire. 5. The telegraph pole is hit by IRMAV and a passing train is hit by splash damage 6. The DCS Debrief screen shows the IRMAV was shot at the railway telegraph pole Taking control of your track, I simply needed to close the distance to the target area to lock and fire the IRMAV at 7.1 nm Adding a waypoint near the telegraph pole, I locked one of the nearby buildings at 8.9nm with the IRMAV alone. What did you expect ?
  19. AFAIK Razbam's Mirage 2000C with M53-P2 engine, RDI radar and Matra Super 530D missiles entered service in 1987. IMHO removing NVG filters, digital radio, etc. won't help to increase it's inclusion as most "cold war" servers model the early cold war for balance/fun and the M-2000C is simply superior to older aircraft like the F1, MiG-21, MiG-19, etc. With the F1 and (planned) Kfir Mirage from other 3rd party devs, there's likely already enough cold war options, YMMV.
  20. IRMAV locked and fired ok, when I tested using a "simple" air spawn mission, do you have a short track file ?
  21. Campaign progress is saved in "Saved Games\DCS\MissionEditor\logbook.lua" If the file is deleted or the campaign path/file name changes - progress can be lost. If due to a path/file name change - logbook.lua can sometimes be edited to match the new location. For paid DLC the campaign path name will be something like "./Mods/campaigns/FA-18C Raven One/Raven One.cmp" While for user [save games folder] campaigns, the drive letter is also part the path i.e. "C:/Users/Ramsay/Saved Games/DCS/Missions/Campaigns/en/FA-18C TopGun Release by florenceSSD/TopGun .cmp"
  22. DCS Open Beta Multi-thread 2.8.8.43704 FA-18C Radar Helicopter Test at 80nm.trk
  23. AGM-65H and AGM-65D aren't in the USMC AV-8B's inventory, they use AGM-65E/E2 LMAV and AGM-65F IRMAV versions. The RL USMC AV-8B Master Flight Syllabus Guide make no mention of ripple firing Mavericks. AFAIK to quickly fire on two targets (in a modern scenario) - you'd create TOO mark points or target points and switch between them. I suspect the F-16C's ability to lock separate IRMAV targets per station and ripple fire is an older technique that pre-dates the AV-8B's TPOD (~2004). As said, AFAIK there's no documentation of the AV-8B ripple firing IRMAV's.
  24. TL;DR: CAS = ON is for normal flight, CAS = OFF is a fall-back mode. IIRC CAS trims for 1G and damps pitch oscillations among other things, on initial release the DCS F-15E showed some undesirable pitch oscillations after take off and CAS was tuned to behave in a better (more realistic) way. My understanding is that CAS is why the F-15E has "fly by wire" like flight and doesn't require lots of trim adjustment. AFAIK, turning off CAS is most noticeable by the amount addition trim adjustments needed to maintain level flight, etc. at different speeds/altitudes but I haven't tested this in DCS. Before the CAS fix, users reported that CAS=OFF helped fix the undesired pitch oscillations - so it would seem that the CAS reversion/ fall back mode used to work. It is (if not more so), as explained, AFAIK the DCS F-15E CAS control logic was partly responsible for causing pitch oscillations after take off and required tuning. Flight model/system tuning during early access is an iterative process and to be expected. Detail: https://www.f15sim.com/operation/f15_yaw_control.html
×
×
  • Create New...