flyco

I have finally upgraded to Win 10. Almost there, but lots of niggles. Main problem with Helios is that when using the soft controls on the touch screen monitor to call up the subsidiary panels (Radio, UFC etc), a single tap will call up the panel but only briefly. It then disappears immediately and seems to require a double tap or sustained press to keep it in place - it also doesn't seem consistent. Has anyone come across this or anything similar, and any suggestions to cure it?

But how do you set those frequencies. The NTTR defaults bear no relation to frequencies used in the scenario.

I am a newcomer to Mission Building. I notice that in DCS 2.0 MB, there appears to be an option to set Radio Presets for aircraft. This is shown as the last tab in the airplane group window. However, when I tried this for the L-39C, it seemed to have no effect. Furthermore the default frequencies are all UHF - does the L-39C have UHF? Can anyone help?

I set both pedals on my rudder as brake axes, with a dead-space initially. Then to steer, apply full rudder, followed by a touch of brake (either pedal, but it is more natural to use the side you're turning towards). The other trick is to 'think nose wheel direction'. That is always be aware that the nosewheel will castor freely, all you can do is 'nudge it' in the direction you want to go, with a dab of brake, and then monitor it from the results, re-nudging as necessary. It will gradually ease itself back to the centre (depending on any crosswind). For take off just use full rudder and, only if you're clearly going to leave the runway, a very small dab of brake.

I seem to have lost the aircraft symbol from the TAD, in DCS 2.0 Open Alpha. Anyone else found the same and any suggestions as to how I might get it back?

A Rate 1 turn takes 2 minutes for a full 360 degree turn. So far as I am aware all the turn indications on a turn meter relate to this, so that the first graduation is Rate 1, the second Rate 2 etc. I cannot speak for helicopters but all the aircraft I have flown, from Chipmunks to C130s and Hunters, have the same calibration That said the standard turn indicator will over-read under g, and is calibrated for level balanced turns, albeit only approximately.

I am running an A-10C Helios profile very satisfactorily. However, I am unable to get either the P-51 or the F-15C running (both published by Capt Zeen). All I get is a bright red screen with a large black cross on it together with some captions. In addition the red area is only 95% of the full screen size. Can anyone throw any light on this problem.

I tried updating AMD catalyst, but it removed my Eyefinity set-up, and duplicated 2 of my monitors. I tried to reinstall my latest preset with no effect. Anyone any suggestions?

Looks like you were right Timber Sour. I just ran a leisurely start with a CBU103, a CBU105, a GBU 31 and a GBU-38, requested as load. I waited for Align to show 4.0 0.8 and initially they were all showing UNS. After a few seconds the GBUs both went to RDY, while the CBUs went to DEG ( presumably degraded). After a further short wait they all went to RDY. as I taxied the CBUs went back to DEG. My conclusion is that I need to wait for the full align before moving, and that as I move they may switch back and forth. I'm just not sure that when I first encountered this in the air they all stayed solidly at UNS throughout the flight. Presumably because I had taxied before full alignment. More haste less speed, as my old granny used to say. Thanks again. The problem with Forums (or Fora if you're a purist) is to separate the chaff from the grain - your input was genuine grain.

In this case the caption ANS UNS came up while on the ground immediately,after a re-arming, on both CBU-103's. I have subsequently tried it several times with both 103 and 105, both before starting engines and after full INS alignment, with the same result. This was in multiplayer. When I tried in single player it was OK. Strange!

Thanks for the input. I was above 15,000ft and spent some time manoeuvring quite moderately, so I can rule out some of the suggestions. This leaves the suggestion that they did not ground align properly. I was very quick starting and taxiing to get into the fray so that suggestion is feasible. The annoying thing is that the code UNS is not one described in the manual. It is a widespread problem in computing circles that strange errors are indicated that no-one seems to know the meaning of. Someone coded 'UNS' and presumably they knew why. It may be that the meaning is classified, but if anyone does know it would greatly ease my frustration. I can only think of 'unsafe', but why

I recently had both CBU103s refuse to drop, with an indication on the DSMS of UNS, and the selections a solid white. Anybody know what I was doing wrong?

Sorry if this is an inappropriate thread, but can anyone tell me what Raptr is. It has suddenly appeared on my system, and I don't like software that does that! I don't think I want it or need it. Can anyone tell me whether it eats up CPU time etc, or whether I am going to regret removing it. Thanks Flyco

The Wiki description is just about perfect, except for the insistence on using a 45 degree angle-off to define the central axis. In fact you can choose any angle you like - if you use an angle of 90 degrees it's a loop, if you choose 0 degrees (i.e. Straight ahead it's a slow roll (in theory). It is called a barrel roll because the aircraft follows a path around the surface of a large barrel (or more accurately an oil drum, or tube), with the cockpit pointing toward the central axis of the barrel. With a lower powered aircraft it helps to chose a point a little above the horizon to roll around, and always ensure that you have passed the wings level inverted position before the nose drops below the horizon. Many pilots have died trying to continue with a descending barel roll instead of relaxing the pull, accepting defeat and rolling out as soon as it looks nasty. I found that the barrel roll was the most poorly flown manoeuvre by student pilots, until you explained that they were just driving the nose around a big circle centred on the horizon. The aircraft should always have positive(but varying) 'g' and the ball should always be in the middle. It requires good coordination because in most aircraft the speed varies throughout the manoeuvre, requiring you to adjust both back pull and aileron deflection all the way round. Practice by flying level, or a slight climb, choose a clearly defined spot on the horizon (about 20 to 45 degrees off the nose) and fly the nose in perfect circle around it. Check that you are at 90 degrees angle of bank above the spot, inverted before you let the nose go below the horizon, at 90 degrees aob directly below the spot, and end up wings level flying in the direction you started. Throughout try and keep the roll rate constant. By choosing different angles off the centre axis for different rolls, you will quickly get a feel for what you are trying to do. Good luck, and 'Many Happy Rolls of the Day' Flyco (Once a know-it-all QFI, always a kitQFI)

I've knocked a few P-51 ailerons off on landing. I've also shot off a Fw 190 aileron, and it never seemed to affect his roll rate!

Unless my eyes deceive me, the rudder balance tab on the P51 works the wrong way round. All the other balance & trim tabs seem to be OK. Very strange. Yes, I know I'm sad case. Flyco

Gimbal, Sorry if I was not clear. If your system now works then that is fine. However, if you do leave the modifed "default.lua" file in the main game folder then, just as cichlidfan said, when you apply the next DCS update, it will over-write your replacement "default.lua" file that you have put in the folder "DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick" (Obviously the section A-10C will be different for different aircraft) You will then lose all the changes that you have made to your "default.lua". At the very least you need to save a back-up copy of your modified '"default.lua". You can then simply re-replace the default.lua file afetr each DCS update. Alternatively you can put a copy of your own customised default file in the above folder, under another name, which DCS will ignore on updating. The name you should give to this is the name which DCS assigns to your own specififc joystick (or buuton box, or rudder edals etc). This is the same name that you found in your 'Saved Games\...\joystick folder (without the {ad56b410....} serial number. The actions that DCS assigns to button inputs is automatically worked out at DCS start up, by the program combining the 'default.lua' file in the folder "DCS World\Modes\aircaft\...joystick" and the specific joystck file stored in 'Saved Games\...\joystick". The result of this combination is what you see when you open the page "Options\Controls" from the DCS game opening page. Any changes you make on that page are made automatically by the DCS program to the Saved Game ...diff.lua file. I hope that helps a little. Flyco

Gimbal, If I understand you correctly, the default.lua will revert to the true default at the next update. In addition, if you add a second button device it is also going to use the same default. Instead you can save it as a customised joystick lua, by renaming it. I have done this for several additional button boxes etc as well as a set of rudder pedals. Look in DCS at your Options|Controls page and note what DCS calls your joystick. It will be something like SuperJoystick{3d4...........etc.} (the 3d4.....etc. will be different in your case, unless I have guessed correctly, in which case let me know and I'll buy a lotery ticket!). Now close DCS and go back into 'DCS World\Mods\aircraft\.....\joystick' and rename your lua as 'SuperJoystick.lua'. The long sequence in the curly braces is simply a DCS-assigned serial number. Also, if you have a copy of the original default.lua it mght be as well to replace it in the same directory. If not it will be replaced at the next update. Now run your DCS and the new settings should appear. in 'Options|Controls' If you need to modify them subsequently then a new SuperJoystick{3d4....}.diif.lua will be saved in Saved Games. Hope this helps Flyco

If in doubt, substitute one possible cause at a time. If your stick works OK try assigning one of those axes to your rudder input in Option>Controls -remembering to delete the true rudder input. If rudders work then the fault is most probably a physical one in the rudder controller itself. However, like most have said, it is probably another control input to the rudder; it could be a button or key input. For example, if opening the throttle gives you a pitch change then it's a rogue input. I suggest you go to Controls and check that there is no input from any source to your rudder, other than the one you want Good luck Flyco

G00dnight, I have found the same problem on about 20% of case. I don't understand why, but you can solve it as follows. First, go back to the 'Mods\aircrafts\A-10C\input\A-10C\joysticks\default.lua' and remove the additional 'up = section ...'. Then go to the relevant 'Saved Games' lua and in the line you are trying to change replace any command number after the 'u' with 'nil' (In practice you may find that DCS has already deleted this line because it couldn't understand it - that's OK). Then go into DCS Options>Controls and set the control as normal. The second line should have disappeared and the key should be stored OK. Then go back to the defaullt.lua and re-insert the 'up = ...' section. Go back to the relevant Saved Games lua, find the relevant key entry and replace the 'unil' with 'uxxxx', where xxxx is the same 3 or 4 figure code that is shown after the 'd' earlier in the same line. Sve everything and t ry again. You should find that in DCS Options>Controls the double line is back, but one of them will have the button number inserted. A bit messy, I know, but so far it's worked every time for me, and I have 7 Button Boxes and BU0836x, with about half populated with buttons and the other half with rotary encoder inputs. On reflection, it would have been easier in the first place to copy each of the lines that I wanted to amend in the default file and comment out one of them. Then by amending the un-commented version, I could have switched easily between the 2 by deleting and un-deleting the comment (--) at the start of each line. That would have saved me a lot of time going back to correct faults I had made (usually, doubler or missing commas!) Let me know how you get on. Flyco

Demon, can't help with that one - not explored far enough. However, aFter your post, I did change the Value Up from -1 to 1 in the A-10C Seat Down command without any apparent effect. It still works exactly the same.

Thanks, DeJohn. Now I've trIed it via the mouse in the cockpit, I can see it's spring loaded.

I believe that I have found a way of making 3 and 2 position toggle switches operate in a more useful way within DCS World 1.2.8.I do not claim to understand fully how it works, but it does (so far!).Please forgive me if I am a little long-winded in this post, but I do think it's worth explaining my method and suggested changes in some detail - both to get improvements or suggestions from more knowledgeable readers, and to encourage others to experiment. I will just deal with the A-10C, but the same principle should apply to all other aircraft. Before continuing I will put in a plug for a very useful, free lua editor - ScITE.Not only does this allow editing but it also automatically displays different elements (keywords, variables, comment etc) in different colours, indents the text to make understanding easier, and applies an element of syntax checking before allowing you to save an amended lua file.This makes it safer than notebook etc.You can download it from http://www.scintilla.org or http://www.lua.org and it can also be used with other scripting languages. My DCS cockpit is enhanced by 5 Leo Bodnar Buttonboxes and 2 BU0863X boards, which drive a wide variety of additional panels (Electrics, AHCP, Fuel, TACAN, ILS, Radios, Landing Gear Etc).I had spent some hours modding my Saved Games joystick .lua files to make them work - including various 3 position switches (e.g. Inverter Test/Off/Stby), and making 2 position switches operate both on and off.Consequently I was very frustrated, like many others, when the new 'diff.lua' system trashed much of my set-up. I began by exploring the structure of the DCS World folders and files, reading this forum, and trying various changes to see what effect they had.As a result, I have concluded that the 'diff.lua' files (in '...Saved Games\DCS\Config\A-10C\joystick\') represent changes solely to the default file, and that these changes are made and amended within Options>Controls within the game.The default file to which these changes are applied appears to be 'DCS World\Mods\aircrafts\A-10C\Input\A-10C\joystick\default.lua'.This is the file used for all generic or non-recognised joysticks; the recognised joysticks (Joystick - HOTAS Warthog , F16 MFD 1, etc) all have their own lua files to use as the default.I have been unable to identify the purpose of the several other default.lua files sprinkled throughout the DCS directory or of the base_keyboard_binding.lua and base_joystick_binding.lua. I experimented initially by copying the DCS provided 'CH PRO PEDALS USB.lua' and renaming it 'Saitek Pro Flight Rudder Pedals.lua'.I got that name by looking at what DCS had called my pedals in the Options>Controls, and deleting the serial number which followed it i.e. {56AB.....D34}.A quick look at the file showed that no further changes were required within this file. By now a little bolder, I made 2 copies of the 'DCS World\Mods\aircrafts\A-10C\Input\A-10C\joystick\default.lua' file, and renamed them as 'Button Box Interface.lua' and 'BU0836X Interface.lua'; again I got these two names from looking at what they were called in 'Options>Controls' with the serial numbers deleted.I strongly recommend that you check what DCS calls your own interface devices and rename copies of default.lua accordingly, putting them in the joystick directory with the original default.lua.Even if you do decide not to rename your amended file I strongly urge you to save a backup of the original default.lua before you start amending it.DCS does not seem to worry about various additional files in this directory (for example I have a spare named 'blank.lua' as an additional backup. Having created 2 new 'default' files (Button Box Interface.lua and BU0836X Interface.lua) in DCS World\Mods\aircrafts\A-10C\Input\A-10C\joystick\, the next thing I did was to amend these by deleting all the assignments they contained (carried over from the original default.lua).Just go through each line and amend any that start with {combos = .........} by deleting everything up to the word 'pressed' or 'up'.In my version they are lines 15-23, 204, 205, 266, 1013-1016.This will stop the system trying to assign the POV, Btn1 - Btn5, and Axes X, Y, Z and JOY_SLIDER1 to every joystick on your system. (This is where the SciTE, with its colour coding and search facility is very useful - just search for 'combos'). The first new facility is to make a 3-position toggle switch activate 3 inputs.I will use as an example the Electrical Panel Inverter Switch, which I have wired up with the central contact to ground and the two ON contacts to 2 input on your joystick interface (in my Case a Button Box or BU0836X).In your newly created file (which I will call MyDeviceDefault.lua) you need to find the 2 lines that operate the Inverter to TEST and STBY.In my case these are lines 433 and 435.If you look at these lines it may become clear why I have chosen these as my example - half the job is already done!These lines are: 433{down = iCommandElectricalPowerInverterSTBY,name = 'Inverter STBY', cate...etc} 434{down = iCommandElectricalPowerInverterOFF, name = 'Inv....etc}} 435{down = iCommandElectricalPowerInverterTEST,up = iCommandElectricalPowerInverterOff, name = 'Invert........} For some reason the TEST line (Line 435) does not need amending since it already has a section assigning an action to up/OFF, whereas the STBY line (433) does not.To remedy this simply copy from Line 435 the section ' ,up = CommandElectricalPowerInverterOff' and paste it in line 433 immediately after the section 'down = iCommandElectricalPowerInverterSTBY'. Take care to get it exactly correct, spaces don't seem to matter in most cases but commas certainly do. Because it is so easy to make small syntax errors, I test the amended file (MyDeviceDefault.lua) after every 2 or 3 changes, rather than get to the end of 30 or so and find that it doesn't work.In the latter case I would have to go through every change to try and find my error. To test it, save 'MyDeviceDefault.lua.' and then start DCS.Go to Options>Controls and in the column for the interface you are programming assign the Up selection of your toggle switch to 'Inverter STBY', and the Down position to 'Inverter TEST'.You will notice that there are 2 lines labelled 'Inverter STBY', but you can only add an assignment to one of them.This is a result of your modifying the default file.Strangely the 'Inverter TEST' line (the one which already had an up option) is not duplicated.I confess to not understanding why this is so. If you do not get these results it suggests that you have probably made an error in modifying 'MyDevicedefault.lua'.However, if you are successful, exit Controls, fly the aircraft, and confirm that the switch now works as required.Once you have done that save a backup copy of your new .diff.lua so that you do not lose all your successful work to date if you mess it up with a later amendment.The new diff.lua should look something like this: local diff = { ["keyDiffs"] = { ["d1074pnilu1075cdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key" = "JOY_BTN11"], }, }, ["name"] = "Inverter STBY", }, }, } return diff That's it.Now assign all the rest of your 3 position switches, checking that they work at regular intervals. The final mod is to configure on/off switches, where DCS has not provided a separate input method for each. I will use the APU Gen Power switch, which on my set-up is a wired as a simple on/off switch. Of course it will work without any modification, but will require you to move the switch to On and then back to Off in order to either switch on or switch off the aircraft device.Following this mod the aircraft switch will toggle back and forth every time the physical switch is moved.The only problem arises when the two are out of sequence..This can be quickly remedied by selecting Pause, operating the physical switch once (while the aircraft is not looking!), and then un-pausing.The switches should now be synchronised. As before, we modify our new 'MyDeviceDefault.lua', remembering to save any changes at regular intervals for safety.Go to the line below: 432{down = iCommandAPUGeneratorPower, name = 'APU generator power', .... etc and modify it to read 432{down = iCommandAPUGeneratorPower,up = iCommandAPUGeneratorPower, name = 'APU generator power', .... etc That's it.Save it, start DCS, go to Options>Control, assign a switch input to the APU Generator Power line, check that it works in flight, and exit.The 'MyDeviceDefault.diff.lua' will have been modified. Finally, one extra advantage in making new MyDeviceDefault.lua files, is that future updates will not over-write them as they might for the default.lua.Thus any changes made should survive updates - until DCS change the whole system again!

I also have 3 monitors in an eyefinity set-up with a touch screen, running helios, below it. It runs well but I have found adding a monitor to a working eyefinity display is a hassle. I lost the combined display and the three original monitors all showed identical main screens. The eyefinity set-up is still there but you have to go and look for it. It is not helped by the Catalyst Control Centre which I find counter-intuitive - I usually have to use a combination of the CCC and the Windows screen resolution set-up. Then of course, when I added a fifth display, a Lilliput to display the CDU, I had to go through the whole rigmarole again! It took me a little less time on this occasion - practice makes perfect. I just wish I could remember how I did it. Still it's worth it - luckily I find the setting up almost as engrossing as the flying. Perhaps that's why DCS like to reset all my mods when they issue an update - it's their way of keeping me busy now I'm retired.

Regarding use of 8" Lilliput with Win7 64 bit. I have two and they work fine. I I had some problems with the original drivers, but I suspect that was my incompetence. The latest 2 versions of the display link drivers work great, and it fits in with my 3 screen eye-finity, plus an additional 24" Flyco