Jump to content

Home Fries

Members
 View Profile  See their activity

  • Posts

    3515

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by Home Fries

  1. Home Fries
    Thanks for the report. I just compared the modified keyboard default.lua with the latest version (it was not updated in 2.7.5) and I couldn't see anything that should cause this issue. Doesn't mean this isn't the issue, just means that I can't see it. ' Now that we have a new patch, could you please backup the existing default.lua and try restoring that to see if it works. There were a lot of changes between the 2.7.3 and 2.7.4 versions of the files. Also, the issue may be something in your saved games\dcs folder if it is crashing the second time you use it. Does restoring the original default.lua fix the issue? I'll hold off on the 2.7.5 hotfix until we can get this issue sorted.
  2. Home Fries
    2.57 Hotfix 5 is up. This fixes the AV-8B issue with the MFD buttons being offset by five positions. You will need to load the 2.57e versions of the AV-8B diff.luas.
  3. Home Fries
    For the F/A-18, the engine start/stop are key macros assigned to the Warthog throttle stops. Buttons 30-32 should be entered as modifiers, and Button 29 is used for VR Zoom and Wheel brakes. As long as the F/A-18 profile is loaded, this should be how it works. The DirectX profile is the simple catch-all profile that just assigns the "normal" DirectX buttons to the HOTAS buttons, and can be used to create your own profile for something that doesn't yet have a dedicated profile (e.g. CE II, Hind).
  4. Home Fries
    Is this for the DirectX profile, or is this occurring in a specific aircraft profile?
  5. Home Fries
    With VR, S3+S1 will do the NWS button. This is the convention on a few of the modules (and will likely be a standard convention in CTS 3.0). You can look at the HTML documentation to see the substitutions.
  6. Home Fries
    TAS is what is shown in F10, and you can expect differences in TAS and IAS/CAS the higher altitude you go and the more your weather deviates from standard temperature and pressure. Of the four major types of airspeed, Indicated and Calibrated Airspeed (IAS/CAS) are almost equivalent. CAS is IAS with adjustments for pitot-static errors, and is generally within a knot or two of IAS. IAS/CAS is simply a measure of airflow over the wing, and is useful to the pilot to stay within the performance envelope. True Airspeed (TAS) is simply the speed of the aircraft going through the mass of air regardless of wind. TAS is useful for navigation in order to determine the winds (or to determine track and groundspeed if you know the winds and are not using an INS/GPS). Groundspeed (GS) is the speed of the aircraft over the ground. It is quite simply TAS+/- the wind component of the aircraft heading. In no wind, GS = TAS. In most INS/GPS systems, GS is determined by the navigation system, then compared with a TAS computed by a flight computer to determine the winds. So looking at the picture: We have the aircraft on a ~043 heading, which is the same as the 10kt wind vector creating a 10kt headwind (rounding up the 9.5kt wind component). IAS shows 250, and GS shows 245. With a 10kt headwind, TAS should be 255. With the aircraft near sea level (can't see the altimeter, but the aircraft is below the ILS needles and therefore below glideslope), we can assume that IAS is within a knot or 2 of CAS and CAS is roughly equivalent to TAS. This indicates a possible three knot discrepancy between TAS and IAS/CAS, which isn't that out of whack, especially considering the lag in pitot-static dependent gauges like speed, baro altimeter, and VSI.
  7. Home Fries
    Earlier versions may be "simpler," but not necessarily easier to model. Take for example the A-6A vs. the A-6E. The A-6E (I'm including the TRAM/SWIP in this discussion) could carry the PGMs and had solid state equipment (just one integrated radar), while the A model was limited to dumb bombs and the AGM-45, had two separate radars, and had a drum computer (the thing that Willem DaFoe was kicking when the bombing computer went down in FOTI, and yes, kicking the drum was a valid troubleshooting method). If we want to go with simple development, I imagine it would be a lot easier to model the E systems with the single radar and solid state equipment. Having to model the two radars and the interlocks/interconnects, as well as the drum computer would likely be much more difficult. When it came to the pilot's VDI, the drum computer was so slow that the pilot looked less at the altitude AGL, but rather the rate of change of the altitude AGL. Personally, I would be happy with an A-6E with a base loadout to begin with. You still get the 90% experience of the A model, albeit with a faster DIANE processor and no pilot radar repeater since it's no longer two radars.
  8. Home Fries
    2.57 Hotfix 4 is up. This addresses compatibility with the AV-8B in DCS 2.7.4 and updates the database. You will need to import new AV-8B diff.lua files and apply the new Controls LUA mod if you have been using it. You may also need to re-select the MiG-15 in your CTS modules database. Note: if you use CTS Legacy for DCS 1.5.8, please update as that database has been updated as well.
  9. Home Fries
    Version 2.7.40 is updated for DCS 2.7.4.9847.
  10. Home Fries
    I'm aware of the issue, but I'm out of town until Sunday. I'll address the issue when I return and will post again when the server is up. EDIT: Server is back up.
  11. Home Fries
    With programs like LOTATC working with Modes 1 and 3 being set in DCS jets (allowing specific IFF combinations to automatically ID aircraft to controllers), being able to assign an IFF code for Modes 1 and 3 as a single pilot on a multiplayer server is becoming a useful feature. Ideally, I would love to see the option to change Mode 1 and Mode 3 IFF from the front seat. If not a Jester wheel command, then perhaps a way to change it on the kneeboard similar to the LGB laser code. Additionally, being able to set the defaults in the mission editor would also go a long way to allow mission designers to assign custom IFF codes to each aircraft, which could then be assigned additional details for LOTATC. Right now, single pilots in MP are out of luck. Anything to allow IFF mode assignment from the front seat would be quite welcome.
  12. Home Fries
    If I'm flying as RIO, I like to use DP as Bullseye. It's more intuitive and wieldy than NAVGRID; I can just switch to MAN to read my current B/E position and/or use point to point navigation to figure out where a B/E call is in relation to my jet.
  13. Home Fries
    Thank you. This is the best way to go.
  14. Home Fries
    I was wondering if there is an option in AIRIO to have Jester select the MAN position on the DEST switch. This corresponds to the Defended Point (DP) waypoint, and could be very useful for things like setting DP as Bullseye and having your B/E position on call. If there isn't, are there any plans to add "Navigate DP" or similar commands to AIRIO?
  15. Home Fries
    True. One RIO I served with preferred the B to the D because of the slightly better performance. The engines and airframes are near-identical, but the avionics in the D ate into the thrust to weight ratio.
  16. Home Fries
    Once the Tomcat was known to be on the chopping block, NAVAIR didn't put money into upgrades (with possible exception of the Sparrowhawk HUD, which we didn't have). The B's we deployed with in 2000 were very similar to what we have in game, albeit with PTID instead of the fishbowl. We also had the 40k LANTIRN, but that was about it. The D model is a different beast altogether.
  17. Home Fries
    2.57 Hotfix 3 is up for 2.7.3 compatibility. Only affects the AV-8B, and only if you use the custom controller Lua fiies.
  18. Home Fries
    BuNos are unique, they're just not specific to airframes. For instance, you could have 123456 on a Tomcat and 123457 on an A-6. Usually you see them grouped together by airframe type because a number of airframes will leave the factory at once, and they will get sequential BuNos. But you will never see the same BuNo on different airframes.
  19. Home Fries
    2.57 Hotfix 2 is up for 2.7.2 compatibility. Change Log: MiG-21: Fixed SPO-10 lighting toggle M2000C: Added Radar modes to MFD3 and Warthog Throttle Updated buttons and keys for 2.7.2 Updated bindings since 2.57a: M2000C, MiG-21 Updated Custom Luas since 2.57a: AV-8B, F-14
  20. Home Fries
    Mission 2 is a cinematic. No briefing required.
  21. Home Fries
    The Hind profile may take some time, as I'm dealing with RL issues right now. I'm working on getting an update out for the 2.7.2 changes, but I need to do a number of things before I can tackle the Hind. EDIT: in the meantime, please feel free to set up the Standard DirectX profile for a helicopter with retractable gear (the options are in CTS). You can then make your own assignments and still use some of the same conventions I've been using (such as the Button 30-32 modifiers, gear cycling, reversed collective, etc.).
  22. Home Fries
    Very nice! Hopefully ED takes note and applies your json/Roughmets to DCS.
  23. Home Fries
    I second the recommendation for the M2000C. It has A/A and A/G capability, fairly simple systems, and "set and forget" switchology for the most part. The autopilot is the most robust in the game, and the HUD is intuitive. Additionally, BD's campaign that comes with the module is part tutorial. The M2000 is a great way to learn high fidelity systems (set up the autopilot, then play with the cockpit), and it's a lot of fun to fly.
  24. Home Fries
    The A-10C II works the same way as the A-10C I, so there shouldn't be any issues. Regarding the throttle issues, what specifically is happening? Do you use the afterburner detent and if so, did you enable it in the CTS settings?
  25. Home Fries
    Back then, politically incorrect callsigns were more the norm than the exception!
×
×
  • Create New...