LeCuvier

Just updated to 2.7.11.21408 and the reflections are gone. Thanks ED!

I fly the Spit rarely and I like a challenge... First time I tried it was almost dark and I could hardly find the runway. Fortunately there was some parked aircraft or vehicle and I had labels on so I could locate the runway. I managed to land, but ended up on the grass. In the following runs there was reasonable daylight and that helped. I crashed more often than was good for my ego. I lack practice with the brake steering of course and that doesn't help. The advice from @flyco is nice, but I could not find anything like clouds that would serve as reference. I generally land taildraggers with a relatively steep descent at 10m/ (2000FPM) vertical speed and pull up to 5 m/s (1000 FPM) when I'm rather close to the threshold, so I lose visibility of the runway rather late in the game. But this runway is so narrow that it doesn't help. I have to agree with @Hamilton: this mission is very challenging and the runway is very narrow. In fact, a lot of the Instant Action missions are very challenging and could be discouraging for newbies. The other finding for me is the changes of daylight conditions. My first run was at dawn with little visibiliy, and then there was more and more daylight. That means mission start time changes. What causes this variation? I looked at the mission's "Time and Weather" tab, and I found a slider with -1 and +1 at the endpoints I haven't noticed before. The User Guide does not not show it, so it's apparently something new. I wonder if that's what controls the start time variation? PS: I created copies of this mission replacing the Spit with FW-190A and Bf-109K4. Both were easier to land because I have visibility of the runwayright and left of the aircrafft before and after touchdown.

In the F-16C you should bind the command Throttle OFF/IDLE to JOY_BTN29. That's the switch built into the right throttle lever. It activates when you move the lever all the way back to OFF, and de-activates when you move from OFF to IDLE. The de-activate moves the simulated throttle to IDLE (sounds like reverse logic but that's the way it is). To add to the "strangeness": The mission needs to see you moving the lever back to OFF before it recognizes the move forward over the "hump". For the A-10C (both versions) it's the same except there are two lever switches (JOY_BTN29 and JOY_BTN30) and they are bound by default to the commands "Right Engine throttle set OFF" and "Left Engine Throttle set OFF". The naming is counterintuitive, but that's what is is.

The subject mission starts with the helicopter cold and dark. When I run the auto-start everything seems fine except the EKRAB indicates "RIGHT TRANSM OIL PRESS" and there is not enough engine power to get airborne. It's not a problem of the auto-start macro because that works fine in other missions or Instant Action. I have been trying to find something in the mission that would cause it but with no success. Right now my work-around was to change the mission to a hot start, and the engines work fine. Can somebody tell me what causes the problem? PS: I did check the "Failures" tab in ME. Nothing ticked there.

You can kill almost everything in SP if you attack head-on. See attached track. If you didn't damage him badly enough the first time continue straight at full power to get some distance, then turn around without losing too much energy and go for a new head-on attack. Works most of the time for me. Fire with all guns! Probably not realistic, but neither is the stellar performance of the AI. FW-190A Head-On kill Spit Veteran.trk PS: I need to use labels due to my poor eye sight and the poor presentation of small targets on my screen.

I see this frequently with Spitfires. I can make the crash if I do a good job, but it's difficult because they are so slow in this mode. Very little time for getting a good aim.

This instant action mission is challenging for me too although I have lots of hours with the FW-190D, because it starts just seconds before the merge, your speed is low, your aircraft needs nose-up trim, your gunsight is not set for the Mustang wing span and the gunsight brightness is too high. And your AI wing man needs to be told to engage. So a lot of things need to get right quickly, power-up and trim first priority for me. However, with enough practice the mission is quite winnable. I tend to get behind one of the bandits rather quickly, but the bastard then starts maneuvering wildly which makes it hard to hit him. Deflection shooting with very short bursts works best for me in this phase. Once he runs out of tricks and tries to climb away, a solid well-aimed burst will work. Also need to make sure I'm not chasing the same bandit as my wing man. Talking to the wing man via F keys would force me to look at the keyboard which is dangerous. I'm using Voice Attack so I can talk to my wing man without losing sight of my target. AI wing men tend to be passive. You may have have to repeat the "engage bandit!" to keep him at work. For a rookie pilot I would recommend to modify the mission (increase the distance) to give you more time to set everything up. Just copy the mission to your "Saved Games" folder so you don't lose your changes during updates.

Interesting statement! I will look for that going forward. Anyway, this is a tricky subject and even with considerable practice I sometimes find myself struggling to get back into control, with the AP lights flashing. It takes a lot of practice to avoid this situation.

It's pointless for someone to say that he has no spotting issues, this does not help. I'm one of those who do have spotting issues, and part of that is due to my age. My work-around: I have changed the dot symbol from a "." to an asterix ("*"). That's easy to do via a little edit of the file "labels.lua" under "C:\Users\YOURNAME\Saved Games\DCS.openbeta\Config\View". Open the file with Notepad++ and go to line 63. It should show this: return {"˙","CenterBottom", blending or 1.0 , opacity or 0.1} Change it to return {"*","CenterBottom", blending or 1.0 , opacity or 0.1} and save the file. You need to start DCS World after making the change.

In the attached track I tried to fight the Spit head-on, but he turned away. So I turn south towards the mountains and fly low. When I'm just past the first hill I turn west to disappear behind the hill, always very low. The Spit keeps flying towards where I am, although I'm now behind the hill, and crashes into the slope. I used this escape tactic a lot before I learned to fight the Spit, and it has always worked. Also when I was flying higher and hid behind a mountain. Spit hits Hill.trk

I'm surprised you say that. I think they always see me, even through thick clouds and mountains. Anyway, they start maneuvering wildly before I start shooting.

I'm more into WWII warbirds, and I find that the AI Spit, Mustang, Jug and Mossie now manoeuvre wildly when I'm getting onto their tail. They didn't do that a year ago.

Tutorial document: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu For the F-16 pitch auto-pilot add these 2 lines of code to "default.lua": {down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ALT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ATT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}},

It's certainly possible and I haven't waited for ED to do it. Just added 2 lines to "default.lua".

Correct. The default profiles for the original A-10C have always worked in the same way as the ones for the A-10C II now. I would just delete the stuff for the "old" A-10C under Saved Games.

I don't recall the earlier naming of these commands but they were always there for people who don't have the TM WH throttle. I'll try to put things i context. The file "Throttle - HOTAS Warthog.lua" defines these two commands for the TM WH throttle: {combos = {{key = 'JOY_BTN30'}} ,down = iCommandLeftEngineStop , up = iCommandLeftEngineStart, name = _('Left Engine Throttle Set OFF') , category = {_("Special For Joystick"), _('Systems')}}, {combos = {{key = 'JOY_BTN29'}} ,down = iCommandRightEngineStop, up = iCommandRightEngineStart, name = _('Right Engine Throttle Set OFF'), category = {_("Special For Joystick"), _('Systems')}}, and this part of the first line defines default bindings for the left throttle lever: "combos = {{key = 'JOY_BTN30'}". The file "default.lua" defines these 4 commands for use with 2 pairs of pushbuttons on any other type of game controller: {down = iCommandLeftEngineStart, name = _('Engine Start Left'), category = _('Systems')}, {down = iCommandRightEngineStart, name = _('Engine Start Right'), category = _('Systems')}, {down = iCommandLeftEngineStop, name = _('Engine Stop Left'), category = _('Systems')}, {down = iCommandRightEngineStop, name = _('Engine Stop Right'), category = _('Systems')}, A look at the detail shows that these 4 commands are made up of the same internal commands (e.g. iCommandLeftEngineStart) as the 2 commands for the TM WH throttle. Unforunately, ED does not use consistent naming so these commands have names like "Engine Start Left". PS: If you wanted to use a pair of maintained ON/OFF switches (instead of 4 pushbuttons) on a button box for this function, you could actually copy the two lines from "Throttle - HOTAS Warthog.lua" and paste them into "default.lua".

@jaylw314 Let's not confuse the facts! What @Yurgonstated is correct since @Wolf 37 uses a TM WH Throttle. The correct commands are "Left Engine Throttle Set OFF" and "Right Engine Throttle Set OFF". The names are a bit misleading I agree but these are the right commands, and by default these are bound to JOY_BTN30 and JOYBTN29 respectively. These physical switches in the throttle lever are ON in the "throttle OFF" position. And when you move the lever to IDLE then the physical switch goes OFF. This transition from physical switch ON to OFF is what triggers the transition from Throttle OFF to IDLE. It's reverse logic and it has always been that way.

I have the same TM WH throttle, and the cold start sequence still works here. But complaints from people seeing this kind of issue are all over the place and I feel that there is something in the design of the control bindings that causes these issues. Unfortunately I have no clue what the root cause of the issues is, and I might be next to suffer. I'm a bit paranoid about anything that could be the culprit. So after installing a new module I remove all the "combos..." statements from "default.lua" that cause the default bindings which are often duplicated. I'm suspicious about the "...diff.lua" files in the game folder. They are structurally like the profile files under "saved games" but don't have identical content. I have deleted them with no negative effect, but they come back with Repair or Update.

I copied everything under "Saved Games" from A-10C to A-10C II.

try this Ka-50_SHKVAL.zip

This works! I changed the colour of the bitmap file "SHKVAL_MSK.bmp to something yellowish, and changed the line in "SHKVA_init.lua" as indicated by @arthuro12. It's a very simple change. And now my Shkval screen has this changed colour which seems to improve visibility of targets considerably. I will keep that! However I will need to set it up with OvGME to protect it from being voided by the next update. And we know of course that any future update might just make it unusable.

If read this several times but it didn't help. Can you elaborate?

I have seen a lot of software developments during the 44 years of my career, and very rarely did they go live in the planned quarter or even month. And those were much less complex than flight simulators. I have seen some go live prematurely due to marketing pressure, and that was disastrous for productivity and image. I'm neither surprised nor disappointed. I would be very disappointed however if they released bad quality.

This is true for all aircraft modules I own, except A-10C and FC3 Should be reported under DCS World 2.7

I agree. This is a game. If I had to do a manual start-up for an A-10C or any other of these highly complex fighters or helicopters, I would never want to fly that mission. On the other hand, if a group of people decide they want to be dead-serious about it and not allow auto-start and ED would provide that option, I wouldn't protest. In reality, very few prople would want to fly there and those missions would join the large number of MP missions where you feel very lonely. ED has a huge backlog of issues to fix, and this one (which is not an issue but a wish) should have very low priority.