Holton181

Hi Trying to make a vanilla copy of my Mi-8 in the Saved Games folder. I have successfully managed to get it to show in the Module manager as installed, its own controller profiles, own Special tab entry and logbook entry. But I can't select it in ME, only one instance of the Mi-8 is selectable. I have looked at the Bell47_2 entry.lua based on the Huey and edited the copy entry.lua accordingly, I attach it here if anyone can see what I have missed, maybe I need to do some corrections elsewhere. I just simply added '_2' behind every original entry of Mi-8. Thanks! entry.lua

In the name.lua located in DCS World 2 OpenBeta\Mods\aircraft\Uh-1H\Input\UH-1H_TrackIR_Gunnerthe info is wrong. It says return _('Mi-8MTV2 TrackIR Gunner')when it should say return _('UH-1H TrackIR Gunner')Making it impossible to configure the UH-1H TrackIR Gunner /H Edit: Sorry, forgot to mention DCS version, it's on 2.5.1.16543 OB Edit 2: Turned out the name.lua in UH-1H_TrackIR_Gunner and in Mi-8MTV2_TrackIR_Gunner has been mixed up.

Just a thought, how good is your hardware controls, especially the one you use as collective? If it's low resolution, noisy or worn-out potentiometers you can get this behavior I believe on a sensitive helicopter. But if these issues are small enough they can be masked by the FM of less sensitive ones like the Huey. I don't own the Gazelle yet but have noticed issues with my controller resolution on the Viggen while flying Huey, Mi-8 and the Shark without issues. Need to use another controller for the Viggen.

So, unsurprisingly the Bell 47 stopped working in 2.5.1. Don't despair though! /H

So, unsurprisingly the Bell 47 stopped working in 2.5.1. Don't despair though! I got it working with some additional files copied from UH-1H and a small edit of one of them. I put them in a zip an share them here. Original files included (obvious naming) for easy comparison. I also included "devices.lua" since the 2.2->2.5 transition even if it hasn't changed in 2.5.1, due to the collective issue. Good Luck! /H EDIT: Forgot to mention I sometimes get game crash when crashing this helicopter in 2.5.1. Not always and I haven't seen any pattern of it yet. Bell47_2_2.5.1_changes.zip

Known issue in DCS 2.x

Don't bother about this. It's more about feeling than looking at the instruments. Looking at the instruments is more for when you gained some experience, the angle on the HSI is different for different speeds and loads. With empty helicopter you have one angle, with full combat load another for the same speed. As I said earlier, do small corrections and let the helicopter settle at a new speed, then and only then you make further corrections and settle. Eventually you successfully stabilize at the speed you want. Dont stress it now in the beginning, further on you will manage to make the corrections more direct and quicker.

Do you mean you push the stick forward a bit? Don't do that. Don't do this either.

To add to my post above: Keep your fingers, hands, arms, feets, neck...ah what the heck, your entire body relaxed! Otherwise it will be very hard to do those tiny controller corrections in a smooth and non-erratic way.

When you say this, do you mean you first move the cyclic back slightly to slow down then move it forward to straight and level? If so, that's not how to do it. You move it slightly (itsy bitsy tiny bit) backwards and lower the collective in the same manner. Let the helicopter slow down and settle at a new speed with this configuration while maintaining altitude with small, small, small, small movements with the collective. When it has settled at a speed, is it still to fast? to slow? Spot on? Correct with yet smaller movement of the cyclic and collective. Settle the speed. Correct. Repeat until you're settled at the speed you want. Now keep this configuration, don't try to "level" the helicopter by pushing the stick forward. A helicopter get the speed that correspond to its attitude, not like fixed wings that basically point their nose straight forward whatever speed they have. A helicopter has a nose low attitude when going fast, nose high at slow speeds and hover (relatively speaking, depends on model). Do things slow and carefully with small movements, especially in the beginning. Eventually you start doing it without thinking as if the helicopter was a part of you. Mind you, these stuff is actually much easier IRL thanks to wider field of view and physical feedback from the aircraft.

Not a good thing to do! Flying helicopters necessitates almost constant coordinated input on all three controls. Only at well trimmed straight and level flights and slow and calm turns you can relax a bit with collective and pedals. The power you apply at liftoff is in general higher than at cruise, and even if the collective doesn't directly adjust what engine power you apply it does control rotor blade pitch and hence drag that has to be overcome with engine power, automatically adjusted by under-the-hood systems. You need to lower collective and move the cyclic backwards to slow down without gaining height, and to this adjust the pedals for reduset torque on the main rotor mast. All these adjustments should be TINY! Use only your fingers, not arms! Something highly recommend for everyone flying helicopter sims is to remove any centering springs and detents from their joysticks, and if possible extend it a couple of dm.

Yet another "display bug"... The Gazelle TV and Huey cargo cam also broken. Hopefully we get another update rather quickly.

Can't verify this potential bug myself yet, will update to 2.5.1 next week.

And "Datalink Data Mode" is set to "Commander"?

@BBQ I have discovered a bug in mission #13. Have played it several times but only reached 99 in success rate. So I examined it in ME and believe I found what's causing it. I'll send you a PM not to ruin the fun for others.

Why use this when it's avaliable in the settings? I have everything including ABRIS in English without any mods.

I just remember, the folder to look in can be metafx AND/OR metashaders folder. metafx is a subfolder to metashaders. Delete metashaders (including metafx) after each DCS update (this has actually nothing to do with UltraMFCD, god thing to do for everyone).

ME stand for Mission Editor. Open it and repeat the procedure for all maps you have. About the metafx folder, that bullet isn't all that necessary but can give a hint on when you're done with the zooming stuff. The folder is located in your [Windows user name]\Saved Games\DCS.... folder. Open it and you can see how the files are created while doing the zooming. You should have a file counter in the bottom left of the Explorer. When the counter does not increase anymore when you move around the map zooming up and down, you are probably done with that map and can move on to the next, or start flying. It's a good idea to simply delete the metafx folder after every DCS update, and of course redo this procedure to recreate the files again. It's when DCS wants to create one of these files in the metafx folder the game crash if UltraMFCD is running.

Thanks! Looking forward to it [emoji106]

So, the obvious question regarding today's DCS changelog in which the Viggen ones again isn't mentioned: Will any of the already announced Viggen updates be present?

"Compass ° degree" might, perfectly logicaly, be used in real world. But in these specific mission briefings the "ME ° degree" is given (i.e. relative grid north). Unfortunately there is quite much confusion regarding DCS and different headings: https://forums.eagle.ru/showpost.php?p=2117082&postcount=10

I've checked, and the reason for the disparity in leg lengths between ME and the briefing pictures are because WP1 and WP2 is located slightly different. [ATTACH]183139[/ATTACH] As you can see in the picture WP2 are supposed to be located above a bridge, specifically stated to be so, while in ME its located 3km to the east on a small hill. WP1 (FARP) should be located north of Tskhinvali, but are located abour 2.5km south on the west side of the town. If measured from the mentioned positions the distances are correct. In that respect you are right, something is wrong. But the interpretation of the numbers are still "DISTANCE[km]"/"TIME[min]" "HEADING[true/ME]"

Why on earth would the Russians use miles?? If my memory serves me right from when I investigated this myself, it's definitely in km. But I'll have a look tomorrow.

The first leg, did you measure from the FARP or the SP/DP? The numbers given are from SP/DP. For the second one it do sound strange. Might have a look tomorrow.

Actually, HB have mentioned this problem is due to how they implemented random numbers not using EDs standard way. It will be changed to EDs in the next update, hopefully solving this problem for the Viggen.