Red Earth

Thanks for confirming this. It is weird you're right, though I didn't know that it wasn't SOP with military - I am positive it's standard with commercial aircraft. So how that works when military aircraft depart from civic/commercial airports begs a question.

With regard to radio use in the F18/A, is it necessary to spool the engine before using the radio? If so then you cannot actually call for start up before you've started up? You just jump through that menu after start up and go for the taxi to runway? So the tower give you clearance to start up even though you've already done so? Can someone clarify please? If this is the case, apart from being unrealistic modelling of ATC, it's really disappointing given all the updates for the f18/A and the DCS environment that aims at producing a simulation? And yet most other aircraft radio work for start up as you'd expect? Perplexed

My folder placement was correct anyhow, but def worth checking to eliminate all possibilities. But yes we have success, it now works..phew! Odd thing is that I see there are two new commands created in controls in-game which I bind my flaps to. I didn't have these new commands in my own attempts to get it working, so it's still not clear to me what the explanation is for the appearance of these commands. Still, all is good, immense thanks to both of you for your help! I'm going to set up some other buttons for MiG 21 now such as L Gear as a single button (up/down) as is possible as standard with most other modules. I'll let you know how I get on with that. Also have the MiG 19 flaps and L Gear to do, so will let you know how it goes. :thumbup:

No file attached. What is the full correct folder address for the default.lua? I could have it in the wrong folder. Thanks

Thanks really appreciated, this answers the preliminary issue. Now I can just set up the commands from fresh.

attached new mig21 default.lua I've tried starting again with fresh button set up but the created ARU commands still exist in control/commands (in-game). It seems I cannot even get a fresh blank start by deleting my input files. There must be another input file I need to refresh to absolutely start from fresh. default.lua

No tested again - no work. I actually started again with a virgin copy of the default.lua from the main DCS folder, so there's something else going on. In my control commands in game, there are two new entries: ARU Manual/Auto - on. ARU Manual/Auto - off. These must have been created by my error in the prior default.lua file. I suspect these could be causing the error. Which file do I need to scratch and replace with a virgin file from main DCS folder - name.lua perhaps? Secondly, which are the commands in control commands in-game that need to be bound: a. flaps 0 - button xx b. flaps 25 - button xx c. flaps 45 - button xx d. flaps on - button xx e. flaps off - button xx Currently I have my two flap commands on the T warthog throttle bound to a. and c. Is that correct? Or should there be some new commands created like ARU auto/manual to bind to? Thanks

Thanks I tried your suggestion but with no success.

I tried setting up a 3 position switch for the MiG21 and Mig19 flaps as per instructions given in the "how to Edit controls...".pdf. More specifically within this guide, the section with MiG21 as an example: 5.6 Creating a 3-Position Flaps control (Mig-21bis) Didn't work for me! When I go onto controls changes (in-game), two entries have been created but they are unrelated to flaps. Here is my MiG 21 entry in default.lua in joystick folder: --FLAPS Modified {down=device_commands.Flaps0,cockpit_device_id=devices.FLAPS,up=device_commands.Flaps25,cockpit_device_id=devices.FLAPS,value_down=1.0,value_up=1.0,name=_('Flaps_3_Pos_Up'),category=_('Flight Controls')}, {down=device_commands.Flaps45,cockpit_device_id=devices.FLAPS,,up=device_commands.Flaps25,cockpit_device_id=devices.FLAPS,value_down=1.0,value_up=1.0,name=_('Flaps_3_Pos_Down'),category=_('Flight Controls')}, Any guidance on this please? Thanks

Thank you for assessment of my log file and your guidance based on this. I've followed your advice and it has helped me to understand the problems as I deal with each item of user content. I thought I might highlight one observation that has become apparent to me during this process for benefit of anyone else experiencing similar issues: The .cmp file is the information used to sequence all individual component files used for a campaign. If that .cmp file is corrupted or not scripted correctly (which can be the case with user made content), then the whole of that aircraft's campaigns (including purchased campaigns) will not show in the campaign menu folder. This was an issue for me and resolved by deleting that campaign once testing demonstrated that there was a fault. Thanks again Eduardo! :thumbup:

Since come to my attention that my purchased campaigns are not showing in the campaigns menu either. Definitely downloaded them sometime ago after purchasing and they show as active modules in the modules info in-game but not appearing in correct menu. Can anyone help advise please?

attached and thanks! dcs.rar

I'm running stable and these files, whilst in the 'correct' folder, do not show up in the in-game Training menu. For that matter I don't have any training missions for any aircraft in said Training menu. It's literally empty! I only realised this cause I thought I'd try out the Farmer on demo today and whilst there are training missions downloaded with the module, they don't show in game. But I have no aircraft training sessions showing in game, even my purchased modules. What is going on? Can anyone advise? Revised folder structure, or is there currently no folder structure working for training missions? :mad:

Okay I've discovered the answer to this issue. Pre-start-up procedure includes left and right fire test. Both tests shut off their respective bleed air valves. Once the engines have started this will prevent any transfer of fuel from external fuel tanks. This is actually indicated in the fuel display of the DDI - "LFT BLD" /"RHT BLD". Naturally this can be cleared but only if this is undertaken after both engines have started. I believe ED's tutorial carries out this process after only the right engine has been cranked. It means that the left will remain shut off and no transfer will occur. Of course you wouldn't know this unless you are carrying ext fuel because it has no impact otherwise. Because I wrote out my own F18 checklist based on the ED tutorial, this is essentially the problem - it's out of sequence and my own checklist needs adjusting to accommodate for this! Thanks for everyone's responses, with these at least I could eliminate the possibility of a bug and ultimately has led me to a better understanding about the fuel functions.