Lixma 06

In the Mi-8 when you're going through the 50kph transition the air frame shakes and rattles - we are all familiar with that. But these days it's accompanied by a low frequency whup....whup....whup sound effect. (at 8 secs and at especially at 24 secs - sorry about the potato quality) It never used to do this - here's a couple of takes from a video of mine from February of me transitioning through 50 kph.... Lots of shaking but no grinding whup....whup...whup... sound. The reason I think it's a bug is that it seems to be exactly the same sound effect you hear when your rotor RPM drops dangerously low in a vortex ring, but as you can see in the first video RPM is fine. Maybe it's being triggered by accident?

The Server.lua has an entry for the 51 which might be what you're looking for.... C:\Users\Nealius\Saved Games\DCS\Config\View ViewSettings["P-51D"] = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {-1.500000,0.618000,0.000000}, CameraViewAngleLimits = {20.000000,120.000000}, CameraAngleRestriction = {false,90.000000,0.500000}, CameraAngleLimits = {200,-80.000000,90.000000}, EyePoint = {0.025000,0.100000,0.000000}, ShoulderSize = 0.15, Allow360rotation = false, limits_6DOF = {x = {-0.050000,0.450000},y ={-0.200000,0.200000},z = {-0.220000,0.220000},roll = 90.000000}, }, }, -- Cockpit Chase = { LocalPoint = {0.200000,-0.652000,-0.650000}, AnglesDefault = {0.000000,0.000000}, }, -- Chase Arcade = { LocalPoint = {-21.500000,5.618000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } It might not pass the integrity check, though. This thread re: Mi-8 cockpit limits might be of use.... https://forums.eagle.ru/showthread.php?t=202645

The problem with the current Mig-15 reflections isn't that they're a bit blocky - it's because they look exactly like textures painted on the canopy. I'm sure Nick Grey is right about how intrusive reflections can be - but until we can model reflections properly in 3D with parallax and all that good stuff we're stuck with textures painted to the canopy. And the more intrusive you make them the more terribly obvious it becomes that you're looking at a texture stuck to the canopy. So you have to dial them back a bit. In terms of intrusiveness the reflections in 1.5.x might have been underdone but at least they didn't scream 'TEXTURE' at you.

If only they stayed that subtle.... They were OK in 1.5.x days, i.e. before the new renderer, but now they're really ugly. Maybe they will be reworked for the LO4 release?

When you turn it on the 21 becomes very floppy and when you turn it off it flies like it's on rails. Shouldn't it be the other way round?

This was the rationale for the zoom at the time.... https://forums.eagle.ru/showpost.php?p=1033206&postcount=8 I don't know if this feature is still useful (or used) but they never got around to the 'optional' part.

To make aiming a bit easier enable 'Salvo Mode'. Ostensibly this allows you to fire two missiles in one go but it also centres the big HUD circle which would otherwise be offset to the left or right.

Flashing LA is not enough, you need steady LA by ensuring that the small target circle is within the larger Vikhr circle on your HUD. eta: also, with Vikhrs you don't need to worry about turning the laser on, it activates automatically when you launch the missile.

Only just saw your post, fantastic - thanks again, NOALB.

Take a peek at these two pictures. The first one shows what's needed to have the mini-stick generate a key press when pushed left. The second pic is to the right. The UP/DOWN is exactly the same principle. This is the basic setup for a radar cursor slew - please note I'm using the arrow keys for this but DCS default are , . ; / so bear that in mind If starting from scratch make sure you're in TARGET's Advanced Mode and you've created an event by double clicking on the desired axis on the throttle's 3D model. Make sure too that you've selected Axmap2 Event name is up to you. Key Command is the key you want the mini-stick to activate. Type is what kind of key press. There are four available but we want Hold because we want our radar cursor to slew for as long as we hold the stick. Delay is default - no reason to mess with this. Now the sexy part - the big arrow represents the axis' range of movement. The orange region is where the axis will generate a key press - in this case if the axis is found to be within that orange 0%-40% zone then it will hold down LARROW which will slew my cursor left. The red bar is simply showing us there's another key press programmed (slew right RARROW) on the same axis. So we have <0----LEFT----40> <--20% deadzone--> <60----RIGHT---100> I'll attach the TARGET profile if you just want to import the relevant bits. TEST.rar

Are you using TARGET? If you are you can program the axes to send key presses. That's how I do it & it works fine.

Great post, NOALB. Yep - some modules use them, some don't. Wish it was standard, they are really useful.

Is it just an artefact of a digital camera (like with propeller blades) or is the spinning really that obvious from the pilot's seat?

Preload radius (I think).

It is a bit much.

I've noticed the same thing - I see it most by focusing on the vertical HUD supports as they (or rather our virtual head) move laterally while maneouvring. It feels like the numbers being crunched to achieve the affect (which I love) are a bit coarse grained resulting in 'steppy' motion.

It's the 'Server.lua' that MP has an over-ride on (which includes min/max FOV and min/max head rotation). Your 'Snapviews.lua' should be OK.

I've been having similar trouble but I can't 100% replicate it. I would save my preferred cockpit view with ALT-KP0 and it would be fine. But I would then load a different mission and have the cockpit view revert to a previously saved position - and not the default either. Got me thinking whether view settings are being included in mission files now?

Flight Director mode is awesome - it's like 'sports mode' on your car.

Don't worry, it's being fixed....

Why did you buy the Su-27 when you already had FC3?

I just tried the 25T Kh-29T/KAB-500Kr training mission and couldn't get a proper lock. The mission is set in very murky conditions (low light & overcast) so I wonder if this is the cause?

It's the street lights. Try a Las Vegas flight at 6am - runs great. Now try a flight at 4am - fps tanks like a lead balloon. 2.2 wasn't like this.

Sorry to pimp my own thread in yours but if you get a chance could you ask him about the rudder? https://forums.eagle.ru/showpost.php?p=3339781&postcount=1

Don't know your RBK-250-275 AO-1SCh from your B-8V20A S-8TsM? Me neither.