Jump to content


  • Posts

  • Joined

  • Last visited

About Mikaa

  • Birthday 12/12/1991

Recent Profile Visitors

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

  1. I'm not quite sure what more information needs to be given. As @TEOMOOSE wrote, the T.O. GR1F-16CJ-1 states that +/- 100 feet can be maintained up to FL400 PA utilizing pitch commands up to +2.0 Gz. Both the HDG SEL and STRG SEL roll modes command a maximum of 30 degrees bank, which is ~+1.15 G, which gives the AP an additional +0.85G to maintain altitude in turns (up to 15 degrees alpha mind you, at which point the AP should disengage). The only mention of inaccuracies in ALT HOLD mode are in the transonic region (due to shock errors in CADC input) as well as attempting engagement beyond +/-2000 fpm; and even then, the AP should attempt to maintain the given altitude within the -.5/+2.0 pitch command limits, it's just noted that the intended altitude may not be captured.
  2. First off, I'm sure alot of this is WIP, and may already be reported internally, but I've noticed that when utilizing Mode 1, the Hornet consistently seems to be landing short. I tested both a no-wind scenario where the carrier is making wind at 27 kts, as well as with a carrier speed of 20 kts, with 10 kts of headwind along the final bearing (total ~30 kts down the angled deck). At first, I thought it was user error, or I disconnected something, but then I noticed that it only seems to deviate in-close when the burble comes into effect. It's looking like the ATC can't keep up, chops the power for the slight updraft, and then can't catch up in time to recover from the sink. Meanwhile the coupled A/P attempts to compensate by pitching for the glidepath. With no-wind, it consistently hits the 1 wire, and over the limited testing I've done, any amount of wind beyond 1-2 kts results in landing short of the wires and subsequent hook-skip bolter. This wasn't apparent during Wags' showcase videos (burble may not have been implemented yet), and although not a perfect system, I don't think it should have this quite large deviation, especially towards striking the back of the deck. This issue aside, I'm really digging the ACLS system as well as all the other SC updates! Edit: I forgot to mention that I also tried a slow repair, without success. F-18C ACLS Mode 1 Burble - 10 kts Wind Final Bearing.trk F-18C ACLS Mode 1 Burble - No Wind.trk F-18 ACLS Test.miz
  3. Push D/L again. It's just a nested menu now.
  4. Only FM bugs I can think of are a few little tweaks like the AOA shift when crossing the deck (3PTS EGIW), the lack of FBW assisted lateral stability with gear down and flaps full, and some high alpha tendencies, like the pirouette maneuver that ED is currently investigating. AFAIK the rest of the envelope is dang close to the RL charts for the 402's.
  5. I’m guessing this also means that none of the Hornet ACLS functionality will be possible with the Forrestal either? Seems like a shame considering the amount of work that went into it. I do appreciate passing on the feedback to the team. I can also understand if they initially release its full functionality for the SC, while considering the best way to add the basics to the other carriers down the road.
  6. This may also be waiting on the mission planner/DTC implementation. For now there’s some workarounds to assist in employing certain laser based weapons.
  7. Apologies if this is already reported. I couldn't find anything specific to this when searching the forums. While spending time looking at another TACAN-ism (the TOD discussion) I came across this bug when utilizing the CPL function of the Autopilot in conjunction with a TACAN station. While in Mag HDG Mode (under the Data, A/C submenu), the aircraft does not properly track to the waypoint, despite the HUD and HSI heading information as well as the HUD Great Circle Steering Cue indicating correctly. This however, does not appear to be an issue when the HSI is switched to True Heading Mode. When in TRUE HDG, the autopilot correctly tracks toward the station (seemingly within a degree or so of the HUD indication). Additionally, the HSI bearing information changes for Waypoints when swapping between Mag and True HDG modes, but it does not change for the TACAN information - I believe this should reflect the current units (Mag or True, whichever is selected under the Data, A/C submenu). Next, I attempted to see if a manually selected course would track TO/FROM the station along a selected radial using the CRS rocker and CSEL. Both the HSI and HUD CDI cues are incorrect in True HDG, even if the course is manually slewed to center over the a/c's current radial (which should prompt it to capture and track to the station). This also doesn't match the HSI indications of the course line. The True Heading mode seems to have conflicting information as it eventually will violently roll towards the full scale CDI needle (TAC BLIM) but then rolls in the opposite direction, as if to track an incorrect radial. This cyclical error pattern is endless while in True HDG mode, regardless of the radial chosen. Mag HDG as far as I can tell, seems to be operating somewhat correctly, however it often will develop a significant bank angle while attempting to track the selected radial, or will begin to oscillate laterally in an attempt to correct for drift. Something may be amiss, but it is difficult to tell without further investigation. As a sanity check, I conducted this same test utilizing Waypoints instead of TACAN with the same Freeflight Instant Action in Nevada. I just boxed the waypoint for Nellis (WP 5) and conducted the same checks. This seems to be working as intended from my cursory run through. True/Mag swap works correctly, with correct indications on HUD and HSI, as does the selection and tracking of a manually selected course in both True and Mag. At present I feel this is only a TACAN issue. Reproduceable on other maps, however the errors are most apparent on NTTR due to the high degree of Mag Variation. Please let me know if you need more tracks. F-18C TACAN CPL Bug.trk
  8. The only way I can reliably hit with high drags with any cross wind is to offset the target about 1/4 to 1/3 the way to the side towards the ASL, and then as the ASL slides in, hold pickle, adjust to hit the ASL right with the release cue and hope the timing is right. It's a bit aggravating. Or just don't use high drags at all... which is a shame.
  9. It only seems to do it somewhat accurately with slicks (most likely because the low TOF means less correction needed). With high drags, you seem to end up chasing the ASL at the last moment. Something isn't right, but with low-ish winds you can compensate or chase the ASL enough to accommodate it. Not sure what's exactly going on.
  10. I've also noticed that it's offcenter in 2D when messing around without TrackIR enabled.
  11. Thanks for your feedback. The plot thickens… I also fly the other sim, and have had no issues with my TM gear in terms of roll response. Hopefully someone well versed in the FLCS can shed some light on what might be causing this. just spitballing, but could it be that some of the FBW gain filters are being accidentally applied more than once? Either way, I’m out of my depth for this aircraft, however it anecdotally seems a bit sluggish when roll is initially commanded.
  12. I wonder if it would be easier for ED to implement a modified curve for non-FSSB users (which is the majority of us), similar to the central trimmer mode options for Helos (or F-5). That way those who have a replica Viper Force Sense stick can use realistic the breakout forces and gains, but the rest of us with physically moving sticks can still have a similarly snappy Viper out of the box. Just a thought.
  13. I don't disagree that at this stage it's relatively a low priority task (as most of the flight envelope is already quite accurate), however the NFM-000 is pretty specific on high alpha handling qualities, and the stated attainable (instantaneous and sustained) alpha IRL is just not possible with the current flight model, especially when attempting a pirouette. I don't see this as subjective at all, but I do realize that it's not a priority and can take a lot of work to fine tune. Maybe now that the Viper FM has been updated, and seems to be much more representative of it's RL capabilities, there will be some devs available to have another look at the Hornet. Edit: Perfect, thanks for the update!
  14. Does this mean that there will not be any further changes to the pirouette logic and high alpha pitch authority capabilities, as referenced in the bug report marked "investigating"? Or has this already been rectified, and implementation is pending the next patch?
  15. This. If the STRG SEL was in fact just a simple homing autopilot, it would never be used IRL due to significant wind drift, and pilots would just use the HDG function to track to the desired steerpoint by referencing the tadpole and vv cues and collocating them manually. Just because the F-16 autopilot is incapable of intercepting a specific HSI selected course to a steerpoint does not mean it doesn’t have the capability to compensate for wind drift and track (read steer) directly to the selected steerpoint. I really hope this is looked at again.
  • Create New...