Jump to content

Ramsay

Members
  • Posts

    3741
  • Joined

  • Last visited

Everything posted by Ramsay

  1. Perhaps you have, a video, track or at least screen shot of your input curves might help diagnose why you are having issues. LTE (loss of tail rotor effectiveness) is a real thing, where the tail rotor has insufficient authority to compensate for large amounts of torque, crosswind, etc. Again a video/screen shot of your settings, curves and control inputs (RCtrl+Enter) would help us, help you. Note there is a known bug ATM - if you spawn with a full fuel load - reducing the fuel load (via the rearm/refuel dialog) does NOT reduce the aircrafts simulated weight.
  2. I reproduced this bug on the 4YA Syria server - not sure of the cause but it's reported.
  3. TL;DR: Helicopter's don't trim like fixed wing aircraft and crab slightly in forward flight Detail: • centered ball = in aero-dynamic trim • centered yaw string / doppler needle = in nose to tail trim Being in nose to tail trim is useful as the nose (and hence gun, rockets, etc.) is facing the direction of flight. Aero-dynamic trim is the most efficient/least draggy and preferable most of the time. Casmo explains it well in this Apache video @21:34
  4. Depends on personal preference and what you want to do with it. • Tablet gives you the correct GS (something that's been broken in the NS430 since Christmas) • OTOH the NS430 gives cross track error, ETE, etc. and has a Airport DB that gives Lat/Long that can be typed into the NADIR. The NS430 "should" be better than the NADIR if managing a flight plan with more than 9 waypoints (but ED have left the NS430 more or less unsupported), while the tablet is prettier. Pick up the Gazelle NS430 in a sale as a semi-functional cockpit decoration/instrument - but that's just me and YMMV.
  5. Note: Spawning in the A-10A slot before switching to the SA-342L was good, only crashed when I switched back from the SA-342L to the A-10A (I haven't tested all the other possible combinations - main purpose was to see if I could generate the reported crash).
  6. Reproduced a crash on the 4YA Syria Server 1. Load into SA-342L at FARP-London, Load up 4 HOT Missiles and Sand Filter, take-off/hover taxi and land 2. Select Spectator Role and check map 3. Select A-10A slot at Incirlik - DCS Crashes to desktop/triggers crash reporter 4. Steam validated all 100482 files (548.7 GB) as correct. dcs.log-20230612-204554.zip
  7. Yes, it's a limitation of DCS (grass has no collision model). AFAIK choices are 1. Don't land where there is tall grass 2. Remove the grass using a Mission Editor zone 3. Reduce/remove the grass in settings to your own personal preference
  8. The tablet uses GPS, so is only available in missions dated after march 1994
  9. Where do you get this information ? AFAIK the control positions have been tuned using SME feedback and US Flight Test Data which show the cyclic aft and slightly left of center (50%) in a hover (0 knots) in both IGE (3-5 ft) and OGE (75-100 ft)
  10. You may be better off reporting NS430 bugs in the "DCS: Tech & Terrain>DCS: NS430" sub-forum as the NS430 module is developed by Eagle Dynamics https://forum.dcs.world/forum/306-bugs-and-problems/ ED's moderators can then add your report to their internal bug tracker or ask for further details as req'ed. (note the NS430 seems low down on ED's priority list, so I wouldn't expect a quick fix).
  11. Normandy 2.0 is "keyless", so doesn't have a CD key. What does the Steam DLC manager show is installed ? This is how it looks for me Normandy 2 is listed in the Mission Editor as "Normandy" and maintains compatibility for owners who haven't upgraded (they miss out on high detail London/Paris textures, etc.). Were you expecting to see "Normandy 2.0" listed separately or can you not access Normandy at all ? The original "Normandy 1944" (AKA 1.5) area, now has the same detailing and textures as Normandy 2.0 You will only notice the difference after upgrading to 2.0 when flying/spawning outside the original boundaries i.e. Gravesend after upgrading to 2.0. is more detailed. This is a good "before" and "after" post demonstrating a successful Normandy 2.0 Licence "Upgrade"
  12. This is from discord but note PC are endeavoring to get reference images/diagrams of the real and what we have *may* change (the current sight is based off the UK version). I haven't tested the reticles myself.
  13. We really need a short track or video of what you are doing - have you checked out Chuck's AV-8B Guide to see if you've missed anything obvious ? https://chucksguides.com/aircraft/dcs/av-8b/ You are likely doing something wrong as lasing and dropping GBU-12's was trouble free. Tested using GBU-12's in DCS Open Beta Multi-thread 2.8.5.40170
  14. No, there are L, M and Mini-gun variants. The old L and Mistral variants are now combined in the new "L" version and are now determined by their "loadout" The new "L" can also carry HOT missiles or FN HMP400 .50 cal gun pods. The "M" is the only version with a night vision camera and laser range finder, so still has an important role in night missions, etc.
  15. My understanding is that shared buttons/keys between pilot and co-pilot are improved but the copilot needs to press buttons (i.e. for NADIR data entry) at a slower/steady pace than normal (i.e. press/hold/release) to avoid multicrew network desync on keydown/keyup "events". How much control Polychop have over sync issues and how much is on ED/DCS is unknown, so we'll need to wait for the update before forming an opinion. IMHO, your loss - I find the Gazelle's positives outway it's negatives most of the time but you're always entitled to your opinion, however as PC have clearly put a lot of work into this "FREE" update - it seems poor manners to throw shade on the update before even trying it. YMMV.
  16. The trouble is the old flight model has been broken for a while, just because people adjusted to it's faults (the engine has been under performing since DCS 1.5.6) , didn't make it "right". IMHO once ED have fine tuned engine, transmission and torque output to realistic figures and the DCS Huey can pass a realistic "hover check" at different altitudes and weights, they will have a much stronger foundation to tune the flight model (if that is their plan).
  17. It's a complete module, however as it's been heavily reworked to meet AdA requirements, some of the training and campaign missions still need to be updated. IMHO although it's not the most competitive for PvP, it's one of the best DCS modules available.
  18. However it doesn't match the diagrams, etc. found in the 2002 Tac Manual Vol 1. AFAIK Razbam are consulting with SME's to confirm the correct ASL behaviour.
  19. The ASL likely displaces from the designation diamond by a fixed amount when it's correcting for wind. That's not what we see in DCS where the distance between ASL and target diamond changes with the FPM/aircraft heading.
  20. It can be flown as a single person from the front. AFAIK you only "need" to enter the WSO's seat to turn on the TGP, laser, counter measure program and similar. Initially the EA module won't support multi-crew 100% (still WIP) or have an AI WSO, though it's planned to add one later in development.
  21. That was my understanding as well but I'm no SME when it comes to OFP H6.2
  22. Negative, Auto doesn't work ATM i.e. as it only triggers the first release pulse (sometimes 2) and only one (or 2) bomb drops out of a stick of 6, etc. So • AUTO QTY 6, MULTI 6, INT 15 (x10) will drop all 6 bombs at once while • AUTO QTY 6, MULTI 1, INT 15 (x10) only drops the first (and sometimes second ?) bomb of a stick of 6 AFAIK Razbam are aware of the bug via discord but are focused on the Strike Eagle ATM. Interval spacing does work but requires a "fudge" factor i.e. I use INT 15 x10 for 130' (40m) target spacing As CCIP ripples are working, they can be used to confirm if the release settings, spacing, etc, are correct but only when the Reflected Cue isn't in the HUD. Tested using Mk-82, Mk-82 Snakeye and Mk-20 Rockeyes, DCS Open Beta Multi-thread 2.8.5.40170
  23. I believe how the fall line is drawn in the HUD is a separate issue (design choice? ) to the auto release pulse failing to increment i.e. auto used to work.
  24. If you are using CCRP, the release parameters are very tight (IIRC +/-5 mil ) and the flight path marker needs to be on (or very close to) the azimuth steering line when the release cue reaches the FPM (otherwise the bomb(s) won't drop). Release angle 45° gives you the cues for a "optional" 45° loft and instead of a single release cue, we now get a release "staple" and 2 cues that look a lot like the "in range" cue for dropping GPS guided JDAMs, etc. but that work differently (it's changed from the LGB and dumb bomb HUD illustrations in the official manual and Chuck's Guide). • prior to line reaching FPM and top of staple - depress and hold weapon consent/release • top of staple - FPM flashes --> time to start climbing (mil power, smooth 4G pullup) @ 45°, keeping the FPM on the azimuth steering line (AFAIK actioning the climb is optional and the system will release the bomb(s) regardless - provided pickle button is held and FPM is kept on the ASL) • once the system calculates the release will hit the target - bomb(s) auto release, FPM flashes a second time (this may or may not be near the bottom of the staple - which is the release cue for level fight) Wags Loft Video also applies to CCRP LGBs, etc. weapons releases. IIRC the release parameters for dropping LGBs, etc. used to be more permissive but ED received info that SOP was to use tighter release constraints (perhaps to avoid collateral damage, etc.). In the DCS A-10C, we have the option to change release constraints i.e. to the 3-9 line - unfortunately we don't get that (menu?) in the F-16C.
  25. CCIP ripple is working but for now, you must avoid the CCIP -> Auto conversion i.e. dropping while HUD has the CCIP Reflected Cue (horizontal line) symbology. Tested using Open Beta Multi-thread 2.8.5.40170 Mk-82SE, QTY 6, MULTI 1, INT 15 (x10) You can enter 100' using the ODU and the mechanical counter will display 10 (x10). Only one bomb dropping out of a stick of 6, is typical of the current Auto/CCRP bug when using CCIP while the CCIP Reflected Cue is displayed.
×
×
  • Create New...