xray20

I'm using a Thrustmaster warthog. I'll try Hans's modified LUA and let youk now how I get on

I'd like to assign the F1 key to my HOTAS joystick paddle switch (BTN#4) so I can use it for the majority of communications. This seems to be set as a keyboard only command. I can't see a comms F1 setting in the control options menu and therefore cant map it to the joystick. Can this be done? Thanks

I found this official document PILOT OPERATIONAL PROCEDURES--A/OA-10(PACAF) on http://fas.org/man/dod-101/sys/ac/docs/11oa10v3.pdf I'm not sure if its in the DCS A-10C documents collection as most of the links for these documents are currently broken, but its very interesting and I recommend you download it while you can. It has this to say about lighting: *3.19.2. Night Takeoff. For formation takeoffs, flight/element leaders will turn the anti-collision strobes OFF and position lights BRIGHT (DIM as desired) STEADY when reaching the run-up position on the runway. At the flight leader's direction wingmen may leave anti-collision strobes OFF until brakes release subsequently turning the anti-collision strobes ON and position lights BRIGHT—STEADY for takeoff. The flight/element lead may direct wingmen to turn or leave the strobes OFF anytime the lights cause distraction. All aircraft will turn formation lights ON. During a night formation takeoff, call brake release and configuration changes over the radio. Following takeoff, each aircraft/element will climb on runway heading to 1,000 feet AGL and accelerate to 200 KIAS before initiating turns, except where departure instructions/local procedures/obstructions specifically preclude compliance.

I have built a big complex scenario that I use as a basis for my mission files. It's taken months to develop. I turned on random failures in mission options, just to see what it would do. Decided i didn't like it as, a) it wasn't random enough and b) failures were far too frequent. Trouble is, now it won't turn off. I have unchecked the box but the failures persist. Unfortunately I made about four hours of other modifications so its going to be a pain reverting to a previous working version. Has anyone had this experience? Is there anyway to get into the .miz file to edit out the error? In terms of the random errors, It would be fine to have an engine fire once every 100 hours and single system failure every other flight. Three electronics failures and a serious engine malfunction every hour is just ridiculous. Is there a way to tune the failures outside the complexity of a LUA script? Thanks Matt

OK just as I thought. Is there any way to limit their ability? Maybe set their proficiency to low?

I have set up a mission with a large number of ground targets over a very wide area. If I tell my AI flight to engage targets, they quickly find units that I would never be able to find by scanning the ground with my targeting pod. My question is, are they impossibly good or am I missing something in the way I find and engage targets?

@Nevo The screens are 55" NECs that came out of a refit job I was doing. The backlights are a bit tired (hence they are no good for professional work) but they are fine once they warm up. I built low level stands with castors so they are at the right height and easier to move around. Matt

@Ian Brilliant! That works perfectly. Thanks very much for your help. The facilities of my workshop are at your disposal if I can repay in any way. Matt:thumbup:

@Ian Further to my last: I have just followed your instructions for the RWR and they work exactly as advertised. I suspect something is wrong in my CMSP_init.lua file

@Ian Thanks for your prompt reply. Unfortunately I still get the default, big CMSP display as shown in the original image. Would you have a look at my .lua files (attached) please and see if I've got it right? They are from: CMSP_init.lua C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\CMSP\indicator both aircraft and aircrafts folders exist. I've modified both. and thtg5760x1080 - standard.lua from C:\Program Files\Eagle Dynamics\DCS World\Config\MonitorSetup Thanks Matt thtg5760x1080 - standard.lua CMSP_init.lua

Hi, I want to export my CMSP info onto my main screen. As you can see from the attached image, I've nearly got it. (sorry its upside down, but you get the idea :)) I want to make it smaller and re-position it. I have modified the CMSP_init.lua and ViewportHandling.lua but only as far as copy/paste existing files created for Helios export (I'm not much good at coding...) I have tried the following test entry in monitors.lua ED_A10C_CMSP = { x = 0; y = 900; width = 270; height = 70; } but its clearly not being read. Following Peter P's instructions, I have tried adding: --------------------- Eagle Dynamics A-10C = ---------------------- (CMSP_init.lua) ED_A10C_CMSP To my monitors.lua, but it seems to corrupt the file to the extent that I cant read it in the screen setup options list. It's obviously important as it references ED_A10C_CMSP What am I doing wrong? Thanks Matt

@Hans The HUD is on the main screen. It took a lot of adjustment to get the HUD image in the right place and the right size (from the seat position). It works really well. I was going to put a HUD screen underneath the mirror, but there's no need (other than the challenge of making an LCD display in reverse).

@Richard: Warm. 7 screens and two PCs. You don't need a heater....

Hi All, I thought you'd like to see some pictures of version 2 of my cockpit. I built it mainly from secondhand, spare parts and scrap.(except the switches and the interfaces) There is no touchscreen. All of the switches and rotaries work With correct actions). I have built enough panels (and indicators) to do a full start up plus ILS and TACAN. The panels are built of alu-panel (aluminium composite) with printed vinyl skins. Where possible the panels are full size and exact. Thanks to Thierry, for the excellent panel PDFs, Gadroc for Helios and to everyone on this Home Cockpits Forum for ideas and inspiration. Cheers Matt

Thanks Overpro, I thought so. have you done this successfully? Wheres the ILS off assignment? I cant find it in the controls map. Matt

Further to my post above. I have just finished the cockpit build using a Bodnar board and cheap (50c/40pence) encoders and they work fine. Full 360 degree endless rotation and i have the heading/course bug, QNH, lighting, volume, etc working acceptably. The only problem is missing precise +/- 1 degree control every time on the HSI, but If I wind back I can usually get the numbers spot on. note, the bodnar board requires pulse width setting (8/16ms) to work correctly with DCS Matt

Thanks for your reply Mr Burns, I'm using a keyboard emulator (Hagstrom KE108USB), but that doesn't seem to matter. If I assign a keycode to ILS ON/OFF (say LCtrl+Rctrl+A) from within DCS A10, then using that code, whether from the Hagstrom or from the keyboard itself, I can turn ILS on and I would expect that a repeat of the keypresses would turn it off again; but it doesn't. Its the only one of 248 switches I have mapped which wont behave. I suspect a bug. Matt

Hi, My cockpit build is nearly complete (pictures soon). I can't find a keyboard/button function to turn the ILS off. The on/off command turns it on and the same command should toggle it off, but it doesn't. Anyone else seen this? Anyone have a solution? Thanks Matt

I'm try to do exactly the same as you at the same time (small world..) I'm using rotary incremental encoders (EC12E24204A9) on one of the the rotary inputs of a Hagstrom KE108-USB controller. It programs up OK and I get the letter codes for the clockwise and anti clockwise turns (I chose C and V) writing OK in notepad. But it doesn't work on the heading bug for the HSI. If I press C and V on the keyboard the heading bug moves as expected. I can only think that the 'keypress duration' coming out of the KE108 is too short to register in DCS. You may have more luck with your controller. I cant think of anything else to try to get the encoder to work. Im going to try a momentary switch and program C and V on each of the poles of the switch. Its clunky (and much more expensive - I need about 20). I dont get the nice rotary action I want, but it may work OK. Matt

Still cant make it work... Sorry to bang on about this but it just doesn't seem to work properly. Here's the simplified scenario. I have an aircraft on the ramp that I want to have take off and fly waypoints when I tell it to do so. So I set it up as follows: define the aircraft and its position (start from ramp) set waypoints set to uncontrolled create a trigger action - in this case I set a truck and a trigger zone so I can move the truck into the zone during the game (I cant make sense of the F10 comms trigger options) make a triggered action for the aircraft. And here's the problem - What command do I use to get the AI to control the aircraft? I have tried 'group AI on' (sorry if the syntax is not correct, I'm not in front of the sim) and the aircraft does not appear on the drop down list. I've tried start, resume and every combination of likely actions I can think of. BTW - I have set messages to come up with each of the trigger actions - so i know they are working OK. Thanks for your help Matt

Hi, Is it possible to restart and redeploy AI aircraft that have completed their tasking and are now parked? An alternative question, for the same result, is it possible to have AI aircraft sitting on the ramp, doing nothing, waiting for deployment by the game master? Thanks Matt

Duh.. That's got it. Thanks

Hi, Sorry this is a really dumb question. Mustang TF-51D I want to assign the Propeller RPM control to my throttle (HOTAS Warthog). I don't think I'll have a problem with the assignment (everything else is fine), but I cant find what the Propeller RPM is called in the 'adjust controls' settings. Its not listed as 'Propeller RPM' (as with the cockpit tooltip) and I have been going through the list for nearly two hours now trying to find what else they could have called it. I cant belive its not mapped. It must be one of the most important controls. Thanks Matt

Thanks All for your help. I was running from a user account which had insufficient permissions. Elevating to Administrator solved the problem. Matt

I had this earlier in the week. There appears to be an incompatibility between versions 1.2.8 and 1.2.9 in multiplayer mode. I know this does not address the issues of earlier posters but if you have had the problem since the release of 1.2.9 this may be the answer. Matt