Ramsay
-
Posts
3630 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ramsay
-
-
10 hours ago, Mateo said:
What is right and what is wrong?
Both the Real F15E and Razbam DCS manuals say the front CMD pinky switch moves vertically - as you say, the switch animation appears to be forward/aft which is wrong.
Tested in DCS 2.9.4.53707
-
1
-
-
1 hour ago, HawkEXO said:
Anyone else having INS issues?
The HSI NADIR needle in the SA-342L is broken ATM i.e. it doesn't point to the selected waypoint as it should.
https://forum.dcs.world/topic/347051-nadir-waypoint-issues/?do=findComment&comment=5415678
AFAIK the Gazelle's NADIR is working correctly in the M1 and Minigun versions.
-
@DragonSoulkin Currently there are 3 Gazelle versions that are flyable by the player
• SA342M
• SA342L
• SA342MinigunThe 4th (AI only) version - SA342Mistral is kept for backwards compatibility with older missions that used the old Mistral version as an AI opponent.
(Players can now load Mistrals on the L and there is no longer the need for a separate version ).
Here is an example of the Gazelle's kneeboard folder names that are required to have custom pages in all 3 player flyable versions.
-
5 hours ago, Olly2282 said:
Just wondering if anyone else has been having issues with the 10th April 2024 update regarding NADIR waypoints?
I can confirm the HSI "NADIR Double Arrow" no longer points to the correct WP azimuth.
Switching the NADIR's Parameter Selector to TPS/CAP (WP Estimated Time / Heading) - the NADIR's WP heading reads correctly, so the fault is with the HSI needle.
F10 Map Overview.
I also confirmed the HSI's Waypoint needle was incorrect in a Caucasus Mission with zero wind.
As reported here, the NADIR needle bug only appears to effect the SA-342L version.
-
1
-
-
1 hour ago, skypickle said:
is there any indicator on the dash that autohover is engaged?
Below the main panel starter and pump switches are the ALV (hover) and CVS (slaved) lamps which are yellow when armed and green once active/in parameters.
1 hour ago, skypickle said:... when I move to copilot's seat, everything goes awry.
The slaved autopilot will try to track the periscope/Viviane sight which moves with helicopter body unless ground stabilized
• for the L use the "Periscope Command Box" Stabilization toggle
• for the M, the Viviane sight will ground stabilize after it's first manual slewBecause of these issues, it's probably best to switch to the co-pilot seat first (with same control/axis settings as the pilot) and setup the Viviane/Periscope, before engaging the Hover and Slave modes.
AFAIK the current autopilot Hover and Slave modes are still WIP due to the Gazelle's new/more accurate flight model.
-
2
-
-
22 hours ago, Tiger-II said:
... the manual states time-to-climb to 40000 ft takes 7.5 minutes.
Which manual is that, I don't see a 40,000 ft climb listed in the DCS MB-339A Flight Manual ?
22 hours ago, Tiger-II said:... Is that from brakes release or starting in flight from sea level?
Climb rates in the Real MB-339A Instrument and Navigation flight planning section assume a 12 minutes taxi, take-off and level acceleration prior to initiating the climb (i.e. 80 kg fuel burned).
Starting with 2x pilots, a clean configuration and full internal fuel (half full wing tip tanks), the RL manual gives a 30,000 ft climb @ 38 NM / 7.5 minutes / 222 kg additional fuel burned.
The DCS MB-339A Flight Manual (Page 26) shows a Climb to 30,000ft performance spec. of 7.1 minutes (so is perhaps without filled wing tip tanks).
When testing, I found the real MB-339A flight planning tables worked well enough for DCS i.e. climb distance/time +/- 15% and fuel used covered by the 200 kg planning reserve.
-
1 hour ago, Aoi Kaze said:
What do you think?
"dcs-20240320.log" still has too small of a page file - DCS/Windows is likely running out of memory.
Quote2024-03-20 11:46:37.368 INFO APP (Main): CPU cores: 8, threads: 16, System RAM: 65462 MB, Pagefile: 512 MB
-
21 minutes ago, peachpossum said:
Has this issue been fixed yet? I'm having significant problems with the vertical axis TDC slewing of the IRMV seeker.
AFAIK not really - as the issue comes from still having a input on the opposite axis (i.e. a slight input on horizontal axis can cause the vertical axis to "stick").
It can be "fixed" by setting a axis dead zone (size depends on how much drift/jitter the other axis has).
Here is an example of my Winwing TDC axis setup, which is a compromise for sensitivity vs slew speed - YMMV.
Similar thread Re:TPOD slewing
-
1 hour ago, Suffer_Player said:
I can't repair after I damge my mig19, am I missed something?
What makes you think you've damaged your MiG-19, when I watch your replay - the ground crew rearm and place/remove wheel chocks as requested.
They also acknowledge your repair request with a "copy", AFAIK when there's no repair timer, there's nothing to repair.
-
1
-
-
1 hour ago, Mootmoot said:
... do you think i'm just poor , or maybe i have to buy a rudder pedal to manage the gazelle( i'm actually using the twist of my Gladiator NXT) ?
I flew for several years using the twist axis of a MS FFB2 Joystick - so flying the Gazelle is possible with your setup.
Starting out - it took me around 12-18 hrs of practicing hover taxiing around airfields, etc. to get comfortable coming from the Huey, etc.
My son started flying DCS helicopters in the Gazelle, so while it's not the easiest to start out with due to it's sensitive controls, it's certainly possible.
Note that different loadouts, fuel weights and versions i.e. M, L, etc. can have an effect on how easy it is to fly.
1 hour ago, Mootmoot said:i've tried the gazelle with the free trial ,but unfortunately i've never exceeded the cold start , i just spend my time to crash my bird at take off
...
i managed to fly with the ka 50 without difficulty , but for this one it's just frustating...If you haven't already - I suggest starting with air spawns and getting comfortable with it in flight and only then moving on to the more difficult aspects of hovering, take off, etc. that IMHO require time and patience similar to A2A refuelling in fixed wing aircraft (you can sort of "cheat" as a newbie - and use a quick "jump" to get into the air and worry about landings later).
1 hour ago, Mootmoot said:... i think they should have relase a training mission for the take-off
Perhaps this tutorial from deephack will help ?
-
1 hour ago, richskinns said:
Have continual issues with auto pilot not functioning. Failed to work so I reinstalled the F1 module and it worked well for several missions.
However then abruptly stopped working (auto pilot lights fail to light up).
Not sure why things have changed - taking control of your track, I could engage the Autopilot Modes/Lamps, once I reset the Autopilot using the
• Autopilot disengage lever (Control Stick paddle switch)
Tested DCS Multi-thread Preview 2.9.3.51704
F1EE auto pilot works after AP disengage lever rpt richskinns.trk
-
14 hours ago, Jenrick said:
First off can any provide just a general overview of the autopilot/stabilization system for the Gas?
AFAIK the pilot's desired SAS attitude and heading is set using the same cyclic button as magnetic brake.
The SA342 SAS receives inputs from
• Heading - Gyromagnetic compass
• Pitch & Roll - Primary ADI
• Altitude/Speed Hold sub-modes - Barometric Altitude/IAS from the Air Data Module
• Air Speed above/below 90km/h (49 knots) - Badin Switch
• Pilot control input - Pitch, Roll and Yaw linkage micro-switchesHeading is maintained with the SAS Yaw channel below 90 km/h IAS and switches to using the Roll channel when above 90 km/h IAS
A French 1970 SA342 Historic Flight Manual is available from www.alat
Section 1.7 describes the Autopilot and starts on page 65.
-
1
-
-
1 hour ago, DerRedMax said:
Is there an ETA on when the flight director is going to be functional?
There's no ETA but IFE Duke posted this on their discord last week
QuoteThe flight director is almost finished, we are optimising the algorithm. We have been busy with the tornado project for msfs to include the TVTAB functionalities, but next week we will back to work again on DCS MB339 and G91.
So work is in progress.
-
On 3/4/2024 at 9:03 AM, GrEaSeLiTeNiN said:
It wouldn't have been an issue if the Gazelle didn't die from 1-2 secs of just a slight fuel lever movement. Not sure why that is though.
The Engine shuts down with the FUEL LEVER if the "Starter" switch is in the middle ARRET/OFF position.
When in flight - the "Starter" switch should be UP i.e. in the MARCHE/ON/RUN position.
Currently the Gazelle spawns with the "Starter" switch in the incorrect ARRET/OFF position, so it needs moving to MARCHE when selecting an air spawned or hot started Gazelle.
-
1
-
1
-
-
9 hours ago, sarumax said:
The prob is with the Laser mavs not the IR
Problems firing the 2nd E2 Laser Maverick are usually due not cycling it's cage/uncage button.
There seems to be a bug where the 2nd E2 LMav retains the status of the first and is "sort of" uncaged (has good HUD symbology, etc.), but isn't.
-
8 hours ago, sarumax said:
What a piece of crap 2024 I'm only able to fire 1 mav and then for the rest I can not uncage anymore always the same with razbam
TL;DR:
If you want help, rather than just venting your frustration, please start a new thread with a short track/video of your firing procedure.
A common error is, after the 1st IR Mav is fired - the system switches to "INS Mode" and SSS Forward Short is required to reselect IRMV to lock/fire the 2nd IR Maverick.
Detail:
Here is an earlier post I made describing firing IR Mavs and errors to watch out for.
https://forum.dcs.world/topic/324103-help-with-ir-mavs/?do=findComment&comment=5199684
This video from Deephack may also help
As will Chuck's AV-8B Guide - Part 10 Weapons & Armament - Sections 2.7 and 2.8
-
1
-
-
42 minutes ago, Brisse said:
I don't see any failure states or anything applied to the aircraft in the mission editor so I wonder if those missions are somehow bugged.
They are, originally the missions worked as intended and Kobuleti's active runway and ILS was RWY 07.
DCS's chosen runway direction has become particularly unpredictable when dealing with light head/tail winds (1-6 knot), hence the issue with these older missions.
21 minutes ago, Brisse said:So it's a feature, not a bug.
No, the problem with ATC appeared with DCS 2.5.0 but seems to have a very low priority with ED as it's not combat related.
There is the promise of an ATC future rework but it seems to be focused on new voice lines, etc. rather than simple functionality.
21 minutes ago, Brisse said:A tiny bit frustrating though, that the instant action missions can't be used for setting up an ILS approach.
Yes, it's unfortunate players need to learn the mission editor and adjust the wind in a copy of the training mission or create their own versions.
-
2
-
-
3 hours ago, J3ST3R said:
... is this due to a limitation with DCS rather than the actual jet?
No, it is a real limitation and how the weapons are carried i.e. an example of GBU-12's on one side and AIM-7's on the other over Iraq in 1999.
-
1
-
-
22 minutes ago, J3ST3R said:
Recently listened to a 10 percent true podcast with starbaby (ex SE wso) and he said they used to regularly carry ...
Surely they only way you can carry all that is to have the gbu10s and Aim7s on the lower CFTs? Is there other any way you can have this load out?
They did and the asymmetric loadout is valid in DCS.
-
2
-
-
10 hours ago, DimSim said:
It appears all the missions I'm having trouble with arm the player craft with AGM-65E, not the E2/L variant. I'm guessing this is the cause and those missions need to be updated to support self lase?
TL;DR:
Correct, the mission loadouts need to be updated to carry the E2/L version.
Detail:
The AGM-65E cannot be self lased and represents an "earlier" Harrier software/missile combination which could not lase from the launching aircraft.
The AV-8B's E2/L variant in DCS represents a newer software/hardware combination (perhaps ~2012 when the centre pylon was wired to accept the TPOD?) that could self lase i.e. switching from TPOD to LMav E2/L didn't switch off the TPOD's laser.
On 7/7/2021 at 12:29 AM, RAZBAM_ELMO said:The AGM-65E will have its implementation improved with the addition of limitations linked to the TPOD integration. The TPOD video can’t be displayed at the same time as the Maverick video, this is true for the AGM-65F and the AGM-65E. Since when the TPOD is not displayed, the HOTAS controls reverts to its default settings and the AGM-65 is a lock-on before launch (LOBL) type of weapon, the missile can’t be guided by the launching aircraft. The AGM-65E2 goes around this limitation because it can be uncaged and launched from the TPOD page, or the TPOD video can be switched to the MAV video momentarily. We will also implement a particularity of the E2 that it can lock on the TPOD laser source if the laser is fired before the missile is uncaged and the TPOD is loaded on station 4
https://forum.dcs.world/topic/276694-announcement-regarding-agm-65-maverick-loads/
See Chuck's AV-8B Guide Part 10 "Weapons & Armament" (page 227 and section 2.8, etc.) for more detail of how to employ the AGM-65E and AGM-65E2 variants in DCS.
-
2
-
1
-
-
On 3/1/2024 at 10:24 AM, DimSim said:
Perhaps this is the bug Ramsey mentions?
Not, exactly - IIRC I've always been able to fire the first E2 Laser Maverick, it's the follow Maverick that can have issues i.e.
2nd E2 Laser Maverick appears to have "good" HUD and MFD lock symbology (but it's likely a residual system state from the 1st missile fired)
Although the 2nd E2 Laser Maverick's X is steady on both the HUD and MFD, the MFD is missing the LMav's "crosshairs"
Cycling the Maverick cage/uncage button fixes the missing MFD LMAV symbology and allows the 2nd LMav to be fired successfully
These screenshots were taken over a year ago and AFAIK nothing has changed re: Maverick behaviour.
Note: In this case a JTAC "lase" was provided by a CTLD autolase script and YMMV when using the TPOD to self lase.
-
1 hour ago, fencible said:
How did you find out about these changes?
Read the initial Polychop post.
-
14 minutes ago, Estamel_Ter said:
I've tried to strictly follow the launch procedure written in manual but it just won't work.So I think the only problem is with the pickle button.
Is this a bug or something?
I was firing IR Mavs yesterday without issue, so it's unlikely to be a bug, can you share a short track file demonstrating the issue.
-
1 hour ago, zlm63682 said:
Does that mean we will have no way to identify which AA threats are currently locking on us if there are multiple of them?
My understanding is that -
• NEW locks generate a warning tone and the identified threat aircraft symbology should flash/blink for 5 seconds on the TEWS.
• The previous behaviour, where a circle was drawn on the TEWS aircraft that was locking us up, was unrealistic.I haven't tested this in game.
.jpg.ed705efeb84e27f77e25959e6d9a033e.jpg)
.JPG.58dd58c05b65dd56ed27979da06be7ba.JPG)
Which Version Is Which (And Flyable) For Kneeboards/Skins
in SA-342M Gazelle
Posted
Correct.