Ramsay
Members-
Posts
3750 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Ramsay
-
I've updated the link to the accompanying Krymsk diagram (must have broken when the forums were upgraded). Mission Briefing Unfortunately the 2.5.3 track file doesn't playback correctly all the way to the landing and the weather/lighting is a little different in DCS 2.7.10 but you should be able to hit "ESC" and "take control" none the less.
-
What RL pilots report aren't subjective "feelings", rather they are objective "observations" - i.e. in RL they'll use 40% throttle (in DCS 60%) to taxi, in a dive DCS picks up too much speed, in a climb DCS bleeds too much speed, at speed "x" they - use left rudder, ball is centered, use right rudder, etc. I forget all the details of the Yak's FM issues and would need to refer back to a none English video and run it's transcript though google again (IIRC he speculated engine torque was over-modelled), however going into such detail would be flogging a dead horse as AFAIK it was reported in both the English and Russian forums and the Yak just doesn't have sufficient priority. There was some tuning done for flaps drag (a couple of years ago), so I'm not sure on it's current status. For the general FM - the main issue I still see is rudder behaviour where with a fixed trim tab "tuned" for a set cruise speed i.e. 210 kph, we should be using left rudder for take off, centered pedals/ball at cruise speed and right rudder when faster but that's not what we see in DCS. Perhaps one day the Yak's rudder trim adjustment will work in special options but I'm guessing that's the best we can hope for.
-
Possibly but the linked RL Yak-52 pilot's comparison isn't the only one (there are another 2 owners of the real, that say similar things). As a sim pilot, I've never flown a RL Yak-52, so find it's flight model "reasonable", however RL pilot's scan their controls and instruments and note throttle/rpm needed, etc. as more/less throttle, etc. than usual can be an indication of something wrong/missed i.e. gear/flaps not down, etc. Flying in DCS, RL pilots have quickly noticed discrepancies between the Yak-52's real behaviour and DCS. Paraphrasing what one Yak-52 owner/DCS player said, unlike a F-16, etc. with a "civil aircraft" there are a lot more DCS players who have flown the real and ED can't handwave flight model issues away and get a pass. He then praised the DCS Yak-52 for the bits it got right but had bought it mostly to support ED and encourage them to fix it's problems/make similar aircraft. IMHO the DCS Yak-52 has never had the resources for it FM to be finished to a high quality and seems to be mostly running on systems ported from DCS's WWII warbirds, it may keep it cheap but from the comments of RL pilots of the Yak-52, it's been at the expense of accuracy.
-
Yes, using symbolic links, though aircraft are pretty small and maps take up the most space i.e. Caucasus=15GB, Mariana=13GB (with the largest Syria=60GB) Here I'm using symlinks to put most of DCS's maps on a second 1TB SSD so they don't fill up my 1TB NVMe root drive IIRC you want leave at least 10-25% free space on each drive for performance and longevity
-
A blade strike i.e. Wags likely hit a tree branch.
-
They are not, you chose your range source - Nav (distance from waypoint), Auto (radar altitude + LOS angle), manual (as set i.e. 1500m), TADS/Coop (CPG locks and lases target ?) or radar lock (just guessing at this one). Obviously you don't use all five at once as they'd likely give different ranges i.e. the waypoint isn't near the target. In Wags first video (IIRC) he used Nav (distance from WP02) for his first attack run and the TADS/Coop (via George) for his second run.
-
Sort of, as I understand it ... 1. Place LOS indicator on target 2. Manoeuvre helicopter so I-Beam is horizontally aligned with the 'LOS on Target' indicator 3. Fly straight and adjust pitch/wait until the LOS indicator is within the I-Beam's limits ( I-beam turns from dashed to solid, showing the rocket pods can articulate i.e. track the target's pitch) 4. Wait until within range, (Auto, manual, nav source, TADS or radar) 5. Shoot, adjust, shoot again ...
-
Yes, it'll be in a future DCS patch (in the same way the western/Cyprus addition was).
-
There should be a F-5E folder in both locations • CoreMods/aircraft/F-5E for AI and MP aircraft, default liveries, etc. • Mods/aircraft/F-3E for the player cockpit, flight model, default mission files, etc. AFAIK even players who don't own the F-5E should have the CoreMods folder, so it sounds like you have a corrupt DCS install and need to do a "repair" https://www.digitalcombatsimulator.com/en/support/faq/repair/ Note: If running the Steam DCS version, you should instead go into Steam > select "DCS World" properties > Local Files > Verify Integrity of game files ... This is what you should see If you continue to have issues after "repairing" your DCS install, please attach your Saved Games\DCS\Logs\dcs.log file as it may contain important clues to help diagnose the problem.
-
The MGRS coordinates of WP02 in the video are 37S DA 9694 0433 and the nearest base to that location is the Tal Siman military base i.e. north of Raqqa and part of the Syria map's free eastern expansion. This is a picture of the base/runway without the barriers, tents, vehicles, etc. that Wags placed around it's ramp area. More detail on the eastern expansion of the Syria map is here https://forums.eagle.ru/topic/239806-syria-preview/?do=findComment&comment=4897988
-
Correct, the NS430's VHF radios aren't useful/usable. Stick to using the Gazelle's UHF/VHF radios.
-
It depends, I've enjoyed learning to use the NADIR, etc. and the NS430 offers a chance to do things differently (plus it sort of looks cool) i.e. it's another tool in the Gazelle's toolbox. As the NS430 can't drive the aircraft's native systems/HSI/ADF, ideally the NS430 and NADIR should be used together. However YMMV, especially if not familiar with both. Here the bearing to WP1 is 34°M and is confirmed by the HSI course needle. The NS430 confirms the aircraft is flying a 33°M ground track i.e. heading direct to WP1 but both Desired Track (51°) and Bearing (40°) are showing TRUE/F10 map values instead of their Magnetic equivalents. NS430 Bearing (40°T) - MagVar (6°E) = HSI Course needle (34°M). While annoying that not even the most basic NS430 bugs have been fixed, I still find it easier to scan/read the NS430 than step through NADIR parameters/look down while flying nap of the earth. I own all the NS430 modules but the Gazelle's NS430 is the only one I'm planning to make regular use of, so I guess it's doing something right (ergonomics ?), despite the flaws in the base NS430's logic/programming, YMMV.
-
@oznckr The F10 map ruler measures Vaziani RWY 31's TRUE heading as 315°T. The F-16's HSI and HUD are showing the MAGNETIC heading 309°M This is correct as the Magnetic Variation for that location and date is approx. 6°E MagVar = TRUE - MAGNETIC = 315° - 309° = +6° How to check DCS's MagVar for a particular Date/Location using the F-16C's DED Magnetic = 309°M
-
I'm hardly a dedicated DCS Gazelle pilot but have used the Garmin GNS430 trainer and used the GNS430 (and similar) in other simulators. Positives The DCS NS430 is a nice dashboard decoration and adds things such as • low resolution moving map, • Direct to, • route cross track error • Imperial measurements (useful when flying in mixed formation) • Holds more than 9 waypoints (unlike the NADIR) Personally, I also find it helps maintain focus when flying nap of earth and avoid CFIG on longer (+1 hr) flights but YMMV. In general, I don't find the NS430 adds much function over that of the Gazelle's base equipment, rather it at best offers alterative ways of achieving the same things. Which is easier depends on how familiar you are with the "Garmin" way of doing things and/or using the Gazelle's native systems. Negatives DCS's NS430 seems to have much less fidelity to the "Real" GNS430, than the NADIR but detailed info on the "Real" NADIR is sparse. The main thing that stop the Gazelle's NS430 from being considered a "serious/high fidelity" module are all inherited from the limited base NS430 module and it's many broken/missing features. • The NS430 isn't integrated with aircraft systems • The NS430 VHF com radios don't work i.e. for ATC • OBS radial adjustment doesn't work i.e. cross track to follow a VOR radial or line up for a runway approach • Desired Track is 6° out on the Caucasus map • The moving map is 6° out (MVAR ?) in Caucasus and Nevada maps (you learn that a WP directly ahead will appear slightly to the right on the map) • The NS430's magnetic bearings = F10 map/True and selecting True adds another error i.e. Batumi RWY 31 which is 300°M/306°T in DCS, reads 304°M/311°T • etc., etc. Because of the above, I only recommend buying the DCS NS430 on sale and warn it's not suitable for learning to use the real GNS430 (IMHO it's best used by players who only have a perfunctory interest in the real GNS430 or those familiar enough with the *real* device not to be confused by the gamified NS430).
-
Blade damage model is way too forgiving.
Ramsay replied to DmitriKozlowsky's topic in Bugs and Problems
-
Blade damage model is way too forgiving.
Ramsay replied to DmitriKozlowsky's topic in Bugs and Problems
I think the dev's would need to see proof as the only Gazelle main rotor strikes I could find involved lose of control/other major damage. Here a AW139 grazed a cliff face and lost 70-80mm of blade and returned to base with minor vibration. http://aerossurance.com/helicopters/alps-aw139-sar-blade-strike/ here another AW139 struck tree branches and suffered similar tip damage https://www.avfoil.com/helicopter/atsb-releases-preliminary-report-into-aw139-main-rotor-blade-strike/ and here a SA350 struck a bush while hover taxiing, and damaged the main rotor tip caps. https://www.atsb.gov.au/publications/investigation_reports/2017/aair/ao-2017-074/ -
A common suggestion is to :- * Type "cmd" in windows search, right click on "Command Prompt" and run as an administrator. sfc scans your registry for errors and dism compares your windows libraries against windows update Comment It's a "health check" and something I often find myself doing when Steam starts acting "funny" (i.e. game updates keeping asking to be installed), after a Windows 10 update.
-
solved How set metrics in units setting to keep metrics in my device?
Ramsay replied to pepin1234's topic in DCS: NS 430
I think you misunderstand what @Mentos is asking for, the NS430 defaults to Imperial units and there is no way to save NS430 user settings/preferences between flights. The NS430 does not take into account DCS's Options>Gameplay units configuration. Here I have chosen Metric and the L-39 is using Metric instruments (as is the F10 map's ruler, etc.). However the NS430 uses knots, nautical miles and feet until changed via NS430's in game Aux > Units page. Tested DCS Open Beta 2.7.10.19473 -
Disabling Inlet Covers and Ladder for "Takeoff from the ground?"
Ramsay replied to CrimsonCommissar's topic in JF-17 Thunder
No issue contacting the ground crew and asking them to remove the ladders, rearm, etc., I'm guessing you've missed something ? Placed an invisible "Helicopter" FARP with a selection of appropriate "service" vehicles for radio/ATC, rearming and fuelling (fire truck is cosmetic IIRC) and all worked as expected. Tested DCS Open Beta 2.7.10.19473 -
There are two "Approved for public release; distribution unlimited" reports from 1979 that I can think of that match your description. • A-10 GAU-8 (6 passes) Low Angle Firings Versus Individual Soviet Tanks, 36722041.pdf • A-10 GAU-8 (10 passes) Low Angle Firings Versus Simulated Soviet Tank Company, a522397.pdf
-
Yes, this is an air spawn and uses active pause, I • Lase 1st truck, • Fire BRM-1 (laser timer displays), destroy tuck, • wait 3 minutes to avoid over heating (LSR still blinks as it's ranging), • repeat for a 2nd truck • wait 3 minutes to avoid over heating (LSR still blinks as it's ranging), the laser fails after ~12:30 minutes (LSR stops ranging/blinking) just as I'm getting ready to fire at 3rd truck. • I fire a BRM-1 but the MFD's LSD laser timer doesn't display, the missile misses, as does a second (just to make sure). Track recorded/tested using DCS Open Beta 2.7.10.19402 JF-17 Laser fails after 12 minutes, 2_7_10_19402.trk
-
Great. You'll need to set Channel 01 on the Green VHF/UHF Radio and use the "Coms" or "Green Radio Menu" Button You'll need to re-trim your aircraft for your approach speed/AoA (160-180 knots) or use the auto-pilot. You should then be able to control your descent mostly using small throttle movements. Obviously if the AoA increases too much (i.e. starts stalling), etc. you'll want/need to take control and smooth out any phugoids, etc. before re-trimming When landing, I usually place the velocity chevrons near the top of the two brackets or land on the faster side as it's easy to bleed off speed quickly if you allow the AoA to increase and the speed drop too much - obviously with practice/good control, flying with the velocity chevrons in the brackets gives you lower speeds and a shorter landing distance. Here is a short video demonstrating me flying "Training Mission 4 - ILS Landing at Batumi", after about 24 hrs youtube should add auto-translated sub-titles for your preferred language.
-
I am pleased to say I eventually convinced Steam Support to make a exception in my case and refund my 3rd of Jan 2022 purchase. Rebuying under the new App ID 1882810 installed the missing DLC manifest to Steam\steamapps\appmanifest_223750.acf and the missing files/folder were installed. At least the problem seems limited to the old App ID, however it's definitely worth fixing the old Steam App ID and manifest as the problem (missing files) will effect anyone who bought the NS430 Gazelle Plug-in on Steam between 6th Nov 2021 and 26th Jan 2022. Note: The link to the old Steam "NS430 Gazelle plug-in" store page was somewhat broken but could be reached via the main Steam NS430 page - so although the number of owners is likely small, there is at least one other owner who left a review.
-
Mini-gun variant = Special forces variant to provide suppressive fire (at night ?) Facebook video from Armée de Terre https://www.facebook.com/watch/?v=281867828964985 Google Translate (for those who don't like Facebook) "Groupement Aéromobilité de la Section Technique de l’Armée de Terre added 26 new photos. 25 July at 07:00 · You picked up the picture of the gazelle with the machine gun. Here are some additional elements on the work done by le. To respond to a need expressed by the 4th rhfs, Airbus has integrated a mitrailleuse machine gun in port from the gazelle helicopter. This 6-Gauge Rotary machine gun has a firing rate of 3000 strokes per minute. After an evaluation of the implementation (ground and flight in Valencia areas) and the maintenance of this new weapons system, the brand team organized, in collaboration with the 4th rhfs, a campaign From Sunday 5 to Friday, 10 February 2017, on the site of captieux. This campaign allowed: Evaluate the implementation of day and night gatling with jvn; Validate coordination within the crew and associated employment procedures; Define the safety rules related to the use of this weapon; To validate the different firing configurations. The ten shooting sequences (seven days and three nights, 30 rounds fired) were carried out without incident." Mistral variant = a real thing, works with teams of other helicopters to provide self-defence against other helicopters, etc. There's documentation of M's and L's working in groups for Desert Storm (1991) with a special forces CSAR transport helicopter providing support. Four French Gazelles were equipped with Mistrals by Matra for the Gulf War. They never fired in anger. The Mistral Gazelle officially entered French service in 1996 after 9 years of development. https://www.flightglobal.com/mistral-armed-gazelles-enter-french-service/6585.article Photographic walk-around of a Gazelle Mistral http://www.primeportal.net/hangar/ulrich_wrede/sa342l1_gazelle_fr/ IRL = Yes, in DCS = not AFAIK. For ED's helicopters it's a Mission Editor option (rather than loadout change) and changes the IR signature (fitting Mi-8 suppressor 0.5 --> 0.3). The small, single engine Gazelle already has a low IR value in DCS (0.2). IIRC, the dev(s) said the DCS exhaust heat shield reduces power, as well as adding extra weight.
-
I've rolled back and verified DCS "Stable" (2.7.9.18080) on Steam and the 'NS430_SA342' folder is still missing - so it looks to be a Steam, rather than Stable/Open Beta, issue. Steam has refused to refund* my 3rd Jan 2022 "NS430 Gazelle" purchase as it includes a product with 2,615 hours played ( ~109 days). * In order to buy the "NS432 Gazelle plug-in" using the new App ID 1882810 Lets hope ED can sort out the issue, as otherwise it looks like I might be buying a 3rd copy of the "NS432 Gazelle plug-in" in the next Steam Sale
