Leviathan667

the roll tendency might be due to wind speed and direction?

This thread has been extremely helpful. Though, the ALTERNATE FLAPS code does not work with my Warthog throttle when I paste it in the default.lua file in the L39C joystick subdirectory. However, it works like a charm when I paste it in the Throttle - HOTAS Warthog.lua.

Bug: Mk-82 bombs fall short of (computer pilot) crosshair Can I reproduce it 100%: yes How to reproduce/ description: flew the mission 4 or 5 times. Attacked the target from different directions. Same result. Note: target is in the middle of a valley Step1:Ask Jester to Select ordnance (got 8* Mk-82), arm nose fuse, select ripple settings (4 bombs at 25m intervals). Cptr pilot mode is already enabled Step2: Head toward ST waypoint. Climb to 12k ASL approx., dive towards the target. Pickle when the crosshair is over the target Result: 4 bombs fall but they hit the ground a few dozen meters before the target. See video DCS Version: open beta 2.5.6.49798 System Specs: Ryzen 7 1800x GTX 1080 16GB RAM SSD 512 Gb OS: Win10 Peripherals: Joystick: Warthog Throttle: Warthog Pedals: MFG Others: None Headtracker: TIR5 Mission File: see attachment Log: sorry forgot to save it. But would be useless with the F-14 as it is impossible to repeat a mission with the logs. If need be, I’ll try the mission again and save it Video/ Screenshots: see link to two video showing my last two attempts 1st attempt: 2nd attempt: Mods: Tacview F-14 1989 Georgian Civil War Campaign 1- Strike on the Loyalists_SUPERCARRIER.miz

Hello, I find that landing the F-14 on the carrier in single player mission "Debridging the Inguri" is extremely difficullt (and I suspect it should not be undertaken according to the following parameters IRL). Heading on final is 33° So ship BRC should be 47° There's a 239° wind blowing at 15 kts (7m/s) So the wind is blowing from behind when on final approach and is pushing the plane to the right. Turbulence is 10.5 ft/s (3.2 m/s). I don't know how severe it is as I am illiterate in the matter. At this level of turbulence, the plane is hardly controllable at low speed. The plane's attitude constantly changes and the effect is dramatic. On speed AoA cannot be maintained for more than a few secs in level flight. When rolling the plane at low speed, there's a constant struggle to maintain the angle of roll. It is extremely difficult to steer the plane precisely towards the carrier deck. The slightest correction to the heading causes the plane to swing laterally by 5-15° and loose alot of altitude. In these circumstances, would aircraft still be allowed to land on a carrier or would they be redirected toward an airfield? If the plane would be directed to land on the carrier, would it be required to do a case I or a case III trap? Wouldn't the carrier be facing the wind to ease the recovery of her aircraft?

Following and engagement with 2 Mirages (Normandy map DACT), my plane has been hit by a Magic II missile. HYD PRESS caution light went on (it is indicating pressure in either engine hydraulic pump is below 2,100 psi) Pressure in the Combined hydraulic went to 0 Pressure in the flight hydraulic system remained at about 3000 psi On my way back to land on the carrier, I tried to lower my gear to no avail. Same thing with the flaps. The wing sweep remained steady at about 56° even when I tried to manually change it to 25°. I did switch the hydraulic transfer pump to shutoff, but to no discernible effect, following the manual: Next, I toyed with the emergency flight hydraulic pump in both low and high modes. Nothing changed. The hydraulic pressure indicator showed them both to be off, no matter what. But I could still steer the plane with great ease and increase/decrease throttle on the engines too (did not try the reheat). I find this to be odd because I could not supply pressure to the secondary systems such as the flaps and the, landing gear. Is there something more I should have done? The debriefing screen did not mention the hydraulic system had been hit.

A for Jester À or RAlt+À or RCtrl+À for the comms menu

I have a canadian french qwerty keyboard. Not sure if it makes a difference?

Hi, I've just been trying to land on the carrier with an asymetric loadout that made the plane behave erratically. The loadout was 1 x AIM-9M and 1 x AIM-7M, both on the right side of the plane. The gun ammo were mostly spent. Fuel stood at about 2.9k. Atm pressure was 29.95 hg. The plane had a strong tendency to lean right which I would correct using the stick (no trim). Overall, at low speeds, it was difficult to steer the plane. So I made larger loops after the first bolter in order to give myself more time to stabilize the plane when on the glideslope. After three attempts with incresingly large loops, I almost made it to the deck. But the plane suddenly lost alot of altitute just prior to touch down. I have been wondering: IRL, would the pilot do the case I overhead landing pattern before landing (in VFR) when the plane is so destabilised? Would the pilot trim the plane in order to try to stabilise it horizontally and proceed as usual with the landing pattern? Would the pilot use the ACL system? Anything else I did not think about? Also, I am having issues assessing the "real" BRC of the carrier. Whether I follow the one in the briefing (I was flying the Tomcat campaign) or the one on the F10 map, I am always off by a few degrees. Even If I correct using the local mar var. Did anyone figure it out?

Hi, Just got VA installed with Bailey's voice commands. It's working well when I talk to the ground crew but not to Jester. Besides opening the wheel, no matter what command I voice out, JEster will switch to a waypoint. Did anyone encounter the same issues and how did you fix it? VA did recognize most of my voice commands.

I think I incorrectly assumed DG settng is when the aircract compass matches the standy compass . Can you please enlighten me? What is the DG setting? When it comes to the standby compass, it seems to never be affected by the magnetic field of the CV but it also never shows the same heading at the BDHI. Is there a reason for all these discrepancies?

Hi, I did not try much to reach the mach 2.34 top speed we most often find in books about the F-14. But the few times I tried, I could only reach mach 2.1. Under what kind of circumstances can one reach mach 2.34 in level flight assuming the aircraft configuration is clean? Thanks

Thanks Rust for the informative reply. How can I revert the compass to the DG setting?

In the pilot cockpit, on the right console, there's a knob next to the ILS, with the label: Compass HDG slave knob? Do you know what is its use?

Thanks for the info. You made me want an F-111, after we get a Tornado :)

I am a sceptic as to the fix Ragnar says he found. There are still issues on the HUD symbology that haven't been adressed. Chiefly, the manual is of little help to understand how to interpret the HUD symbols are they do not always match with the description. I prepared this document to document what I found out (you can comment on the doc): https://docs.google.com/document/d/1w4F1qyClzRZgyJ26-l--6xnNt9Mlj6_L7ku2G1KPwyc/edit?usp=sharing It relies on the following track file: bombs_short1_DotOnTargetOn1st&2ndTriggerWAutopilot.trk

Just did a few trials and the results are inconsistent. I can put the bombs on target about 35% percent of the time. I tried at different altitudes from 200m, 250m to 400m at the moment of release. It's not a matter of altitude. Following the yellow needles on the ADI does not influence the results so far obtained. The only way to almost consistently put the bombs on the target is to raise the nose of the plane while dropping them. Posted one of the trks of a successful run at the target. bombs_short1_SafeAltLowSuccess.trk

Hi Rifle, I did exactly as you do and the bombs did indeed fall short. Now I am puzzled as I don't know anymore how I put them on target like just a few days before! I think one of the issues is the safety altitude because on the last video I dropped the bombs from 400+m and this time from an altitude of 200m. I'm not sure how or if it is related to the air density bug Ragnar is talking about?

Got this to share: System 37 VIGGEN

I did try the toss bombing method. 4 out 4 times, I got the target in the middle of the bomb run. 3 out of 4 times, the bombs did land before and after the target and only damaged it (the target was in the interval between the bombs). 1 time, one of the bombs directly hit the target. See video here: The issue with what I see on track 7 is that you are not following the procedure for toss bombing. Please check the manual on page 313. Also note, toss bombing is heavily dependent on the accuracy of your INS. You have to make sure TERNAV has compensated for the INS drift before release the bombs. If you're on flat terrain, you'll have to do an INS fix using some terrain feature.

I watched your first track. I noticed you pulled the trigger to the first detent while having the dot right on the target. But, you released it. And then pulled it again, a few dozen meters before the target. That's when you went from first detent to weapon release. The computer calculated the impact point where you designator dot was when you pulled the trigger to the first detent the second time. What you should do is : aim at the target, pull trigger to first detent. Hold it there until you get the fire cue on the HUD. Afterwards, you will see the ring go up, it means you have to pull the stick for a 4G climb. This is how the computer spreads the bombs at the interval you selected on the weapon interval selector. Not convinced. I did a video to show it: Note I did not even bother configuring the QFE on the altimeter. Edit: I also disabled target motion measurement (TAKT IN 221)

QFE should be carefully set because it may influence the impact point calculation. If the computer thinks ground level is higher than it actually is, you might overshoot your target (see image). Else, you might hit right before the target (as if, in the image, the target and dark line were above the red line while the orange line stays in the same position. The impact point would then be to the right of the target). I found out this happens more often with rockets.

Thanks for the quick reply. Let me sum up your reply as I understand it: HUD fin = time-error computation relative to the next waypoint TID output = time-error computation relative to the waypoint for which a ToT has been set. Is that what you meant? My finding is that: HUD fin = time-error computation relative to the ToT for Bx8), using the speed of the missile as a reference (as if the missile were to be released immediately, with no consideration for the missile's limited range) TID output = time-error computation relative to the target waypoint (e.g. M3), i.e. when the aircraft should be at M3 for the missile to be released and reach Bx8 at the defined ToT. I just flew WoT mission 8 again. In the mission planner, I adjusted the aircraft speed to mach 0.55 for all waypoints, including M3. I noticed the same behaviour where the HUD fin would not agree with the TID output (HUD fin shows I'm too early as compared to the TID output). But, in following closely the cues on the TID output, i.e. keeping it at 0, I could make the HUD fin cue to eventually agree with it at M3, when it was time to release the missiles. Following this method, the missiles did reach the russian ships at 0713. What do you think? Is this interpretation right? This is how I modified the mission cartridge in the mission planner: LS at 0640 WP1 at mach 0.55, no ToT set in the cartridge but in the mission order, have to hold there until 0701 (I did not follow this procedure and only focused on the output TID screen). WP2 at mach 0.55, no ToT WP3 at mach 0.55 no ToT Release of RB-15F Bx8 at 0713 ToT L1 at mach 0.55, no ToT Also, I noticed after release of the missiles and on my way to L1, the HUD fin continues to behave as if I was still going back to M3 to release the missiles again, Even after I switched to LAND NAV. Actually, even after lowering the undercarriage, no landing cues did appear. They were superseded by the ToT on Bx8 cues. Not sure it is a bug or if I should cancel the TID input (but if so, how?). Thanks

Did any of you try to complete the Viggen campaigns as if they were flying an AJ 37? I did with the Wrath of Thunder (WOT) and Mjolnir response (save, so far, for the mission where you need to use RB 15F in WOT #8) while only using the following loadouts: AJ 37 Loadouts IMO, when it comes to rockets, guns and bombs, the AJ is about as good as an AJS. HE Bk-90s can be substituted by SB71s in long and wide area mode using toss bomb mode and varying the angle at which the aircraft arrives on the target. But I cannot think of anything to replace the effect of that weapon in compact mode? AP Bk-90 does not seem to have a substitute? RB-15Fs cannot be easily replaced with RB-04Es since modern ships have long range SAMs. I don't know if it is possible to coordinate the launch of many RB-04Es from several planes) to hit an enemy task force at the same time (like input TID Bx8 for the RB-15)? The absence of TERNAV can be compensated for using terrain features to regulary do INS fixes. The closest to the target one can update the INS, the better, especially when tossing bombs. Do you know of any workaround besides those?

In Wrath of Thunder, mission 8, we are supposed to make the RB-15s reach the russian ships at 0713. For the Ck37 to compute the ETA, I did the following Select Input TID (Datapanel) Press 071300 (Datapanel) Press Bx (Navigation panel) Press 8 (Datapanel) While in flight, the HUD cues do not agree with the Output TID on the datapanel screen. See screenshots. The HUD shows I am ahead or right on time. TID shows I am very late for the RB-15 to reach the russian ships at 0713. Is this a bug or is it I who have missed something?

There's another one. In Wrath of Thunder, mission 7, F-5Es drop illumination bombs over the target for you. But it all seems like a UFO is hovering above your head. See img.