JNelson

Hi, sorry Farlander and myself were busy for a few months up to Christmas. Hence the lack of updates. Just last weekend however we did another test event for the A-4 EFM. If you want to keep better up to date you should join our discord. The EFM is nearing release, we are just polishing and fixing bugs at the moment. There is no firm release date yet however.

We released a small update a couple of days ago. It's been in the oven for a while now we are making good progress we just want to be conservative about the timeframes hence the several months estimate. Here is a little clip of it stalling with some slat action :joystick: Thanks, JNelson

Description: Crash to desktop caused by skidding or the sparks from broken tire. Steps to reproduce: 1. Spawn in ready on ramp instant action. 2. Taxi to runway. 3. Taxi down the run way at speed using NWS HI to put the nosewheel all the way to one side so that it skids. 4. Continue to cause the nosewheel to skid until it crashes. 5. This takes about 1-2 minutes. Alternative steps to reproduce: 1. Spawn in ready on ramp instant action. 2. Taxi to runway. 3. Pop one of your tires. 4. Taxi along with a popped tire. 5. This will crash much more quickly. The crash is happening due to a mem copy in the genInt function which I assume is why it takes some time to set up the stale pointer/bad reference and then use it causing the crash. Attached is the DCS log with the callstack. Thanks. JNelson dcs.txt

Hi. When you TWS (PID) lock a contact often other contacts will disappear. Whether the contacts other than the locked contact reappear or not depends on the pitch of the aircraft which seems incorrect. Furthermore a contact locked next to another contact which is the same altitude will disappear even when the radar is still locking TWS (PID) locking the original contact. Steps to reproduce: 1. Create Mission with two aircraft out in front of the mirage that are at the same altitude as each other. 2. TWS (PID) lock one of the contacts. 3. If the other contact disappears then pitch up and down until it can be seen again. If it doesn't disappear then pitch up and down until it disappears to demonstrate the bug. Workaround: Fly your plane like a dolphin and bounce up and down to detect contacts other than the one you have TWS (PID) locked. Please see the attached video for a clearer view on what is happening. Also attached is the track of the same recording. Thank you. JNelson

Any news on the PID bug it makes the radar really annoying to use in a target rich environment?

You can use the dcs view key rctrl rshift * and / on the numpad to move forward backwards amd then there is a bind called save cockpit angles

Looks like you can mod the old centreline tank model.

Looks like you can mod the older F-16 Centre tank model in and it works.

Are we getting a centre tank for our viper? I see it is mentioned a few times in the manual but never directly stated that we have one? There doesn't seem to be one in the game. Is this a limitation of the block 50?

There must be a difference between ours and their build then because the trim tabs going end to end make no noticeable difference. Furthermore every aircraft I've flown has been trimmed for the cruise speed. Neutral rudder required at cruise. In the yak a lot of right rudder must be applied which is not consistent with this. As you can imagine holding a lot of right rudder in is not particularly fun in the cruise, especially when going far. The numbers I edit in the lua file make the trim correct with a trimmed aircraft around the cruise speed.

I did it at 120 and 110 mph in this video which are kinda close to stall be the effect can still be seen. Furthermore I rolled slightly extra just to be sure. The fact of the matter is that the ball is displaced to the right meaning that if you are wings level you will turn left no matter what because there is no force to balance the force of the tail and propeller.

This is very little response from the aircraft then? This was also without WEP. So that would make it worse if you really went full stop to stop.

Chaps, I found the problem. ED has set the trim tab way too far to the left. See this post for more details on how to fix it for yourself https://forums.eagle.ru/showthread.php?p=4028810#post4028810

I do have to put in left rudder with the correct trim settings however it was much less than at launch this may have been due to the fact the aircraft was not trimmed at launch. Eg if you set the trim of the rudder to zero it will take a fair amount to compensate for the moment. So I'm not really sure what is accurate.

I recommend using notepad++. It's free makes things like this easier. Turns out my original post my joystick was uncalibrated so the aileron trim should be zero. Attached the lua with zero aileron trim and the correct rudder trim. FMOptions.lua

For those of you who have a problem with the rudder in the yak being far too much to the left and having no need for left rudder on takeoff. This is due to the trim tabs that ED has implemented. They are not editable from the menu however you can edit them in your game files. You need to navigate inside your game install DCS World/Mods/aircraft/Yak-51/FM/FMOptions.lua Inside this file you will find several lines. aileronTrimTab = 0.0 elevatorTrimTab = 0.0 rudderTrimTab = -0.666 This -0.666 is the root of your problems. For a perfectly trimmed aircraft in the roll and yaw at 250 kmph (80% RPM and 600mm) I have found these settings for aileron and rudder. Edit: Turns out my joystick was uncalibrated so aileronTrimTab should equal 0.0, not -0.13. aileronTrimTab = 0.0 rudderTrimTab = -0.25 (for some reason the aileron trim tab is inverted negative value means right whereas positive means left) This file appears to be loaded between flying sessions so you can use the instant action mission freeflight to tune your aircraft to your desired trim. Lastly this file will be overwritten each update so it's best to use something like JSGME to make it a mod. Hope this helps.

Any updates on this? Makes the Yak a bit of a pain to fly. Especially since we can't fix it with the adjustable trim tabs.

Take the last 3 digits and multiply by 0.06. For example N 4434067 E 3949600 would be 067 * 0.06 = 04.02 600 * 0.06 = 36.00 so the coordinates would be N 44 34 04.02 E 39 49 36.00

You are talking about a moment. Work is strictly the energy require to to apply a given force across a given distance. Although the formulas are similar and have the same units moment is similar to torque not energy.

This the correct answer. The reason a gyroscope can detect the rotation of the earth is due to conservation of angular momentum meanining the gyroscope will appear to rotate in your reference frame. The centripetal acceleration and gravitational acceleration cannot be distinguished from each other locallly.

Possible IFF Bug on today's update. So Wags said this about the IFF for today's update. I may be incorrect with this so someone correct me if I'm wrong. I would assume that to interrogate a contact as enemy you would need an NCTR confirmation of what the target is as apposed to an unknown. Currently as implemented: Mode 4 enemy -> stays as unknown. (Correct behaviour I believe) STT Lock Enemy -> stays as unknown Turn on NCTR -> goes from unknown to enemy despite the NCTR type saying UKN. Turn off NCTR -> goes from enemy to unknown. I believe the bug is in step 3. The contact in the attached track is beaming and as such should have no confirmed NCTR return correct? The second thing is that the friendly in the mission below is that the friendly was IFF'd as a friendly despite not mode 4'ing the friendly. PossibleIFFBug.trk

Have you done the RIO position yourself? If they are in your TID screen but have a cross through them it means they have been dropped, also you might be looking at data-link contacts. Him locking the wrong target could be due to STT picking up the wrong target. As a human RIO I have had this happen before you try to grab a closer target and it locks the one behind, you should just fire in TWS.

Change the AWG-9 from standby to XMT.

When in tws it will label the firing priority on he right of the contact. If you fire the firing priority will change to time to impact and the priority on the remaining contacts will decrease by 1. It is possible to change the priority but the rio must do it.

Don't fight the mig with guns unless you are basically clean. With the loadout you start with it's completely pointless to guns fight the mig. Your most precious resource is fuel. I finished the mission with like 3000 lbs of fuel flying very conservatively. So you should hit the mig15 with an aim9x. The tactic for this mission I found best. Was to use aim-9x on the mig-15, 19, 21 since these guys will waste your fuel (for various reasons) trying to gun them, then guns the guys poor in a dogfight and that should save you enough long range sticks for the big bois. Attached is a tacview of my attempt at the mission. Also don't fire Aim-120's outside of ten miles. DACT.zip