flanker0ne

As the title says, the 4 signal flares are shooted toward the front of the helicopter. Not toward the left side where the rack is facing. Inviato dal mio SM-G930F utilizzando Tapatalk

ATM, in the new cockpit the pilot body is not present.

Up

UP

Click at the base of the stick to show/hide the cyclic

Looks like 2.5.6.49314 solve this bug. Thanks ED and BIGNEWY for their work

Yes, opening the 3D model of the weapon in the ModelViewer2, and with the texture tool/list, read the texture name

If you are at the beginning with the Ka-50, my advice is to fly with Flight Director ON. That setting exclude all the Autopilot concern, keeping the stability augmentation functions

Hope this is the sign that also the Ka-50 is also evolving, taking advantage of all the new stuffs, ED is making

Thank you buddy :thumbup:

My Ego really need to show to all my friends how I'm good at piloting the Huey!!!

I play in 4K and are almost invisible So ED "Make Frame Rate Counter Great Again"

What really annoying me about the PVI-800 is the lack of elevation datas on creating a Target Point. You can't targeting in a 3D world, thats is a bummer!!!

It can be done, maybe you miss something

Of course is a real PVI-800 limitation simulated by ED, but your question led me to this feature request. Maybe it can be a realism setting, handled in the Special menù

Maybe you have to create a transparency with alpha channel on the Shkval monitor location.

No (Saddly), and I think it's a huge void in the tactical employment of the asset. Any time I move from a shore zone to a more hilly or mountaineous zone, the lack of altitude input, need particular skills.

It depend on the hitbox, not on the visible 3D model

Because that night itsn't very night

I can confirm. The Ka-50 NVG is like this You have to become very proficient with those 3 tumbwheels and all the other cockpit light's dimmers

The switches on both collectives are reproduced as a ON-OFF-ON instead of a momentary (ON)-OFF-(ON), to direct the landing light beam vertically. File : Mods\aircraft\Uh-1H\Cockpit\Scripts\clickabledata.lua Line number: 635 (for pilot) and 639 (for copilot) Old line only for pilot (actually I rebuilt taking the copilot line as example, so it may differ): elements["LDG-LT-2-1-PTR"] = default_3_position_tumb(_("Landing Light Control Switch , EXT/OFF/RETR"), devices.NAVLIGHT_SYSTEM, device_commands.Button_7, 205, true, true) Corrected lines: PILOT line 635 elements["LDG-LT-2-1-PTR"] = default_springloaded_3pos_switch(_("Landing Light Control Switch, EXT/OFF/RETR"), devices.NAVLIGHT_SYSTEM, device_commands.Button_7, device_commands.Button_7, -1, 0, 1, 205) COPILOT line 639 elements["LDG-LT-2-2-PTR"] = default_springloaded_3pos_switch(_("Landing Light Control Switch Copilot, EXT/OFF/RETR"), devices.NAVLIGHT_SYSTEM, device_commands.Button_36, device_commands.Button_36, -1, 0, 1, 212)

Divide by 3,14 ;)

From my attempts, I realize that the pre-settings (filter) for axis work only if you pre-assign a joystick axis. If the line start with {action = ... and not with {combos = ... DCS ignore any pre-setting (filter)

Actually this happen in other user created missions, showing a a major bug not only a particular misson problem. Many missions I used recently, have this problem. I must say, they are not created from scratch. This bug came out on the Tarawa also.

You set the wrong keybinding. Cockpit Gauges Illumination (stick)