Jump to content


  • Posts

  • Joined

  • Last visited

Personal Information

  • Location
  1. Please forgive me if this topic has already been covered. Also, please direct me to any threads covering this inquiry. While I love the ease in which Capt Zeens profile for the A10C II allows you to setup the viewports, what I am struggling with is the ability to modify his profile. What I'm wanting to accomplish is to have a profile more in line with Capt LozSM v2.1 profile where each panel(AHCP, Fuel, Landing Gear panel...) are all individual panels with their corresponding buttons/switches that I can move around and resize as needed. I have the Thrustmaster Cougar pack which I have mounted to the upper left and right corners of my 1920x1080 touchscreen that I would like to use. The issue with Capt Zeen's profile is that everything on the front dash is all on one layer and I can't move/resize each panel individually and get rid of the left and right MFCD frames/bezels. I've tried to use Capt Loz's SM v2.1 profile in the new version of Helios(1.6.3605.0) but I can't seem to get it to work properly. I'd also would like to make the panels look nice and new like in the game(non worn look) and have two Helios profiles, one that looks like the cockpit during the day and one that looks like the cockpit at night for night ops. I have attached some nice clean day and night panels so you can se what I'm talking about. I downloaded those images from the internet but I would like to know if anyone has extracted the new non worn panel images from the actual game. Here is a pic of my issue(A10 Setups) and an old photo(433) of my older setup using a non-touchscreen using Capt Loz profile that I modified slightly to fit my requirements.
  2. A-10C II TAD and TGP issue Is anybody else having this problem? On my TAD page I see a camo print over top of my map. On the TGP page the symbology shows around the border and the crosshairs but just no image from the camera. And it's only with the A-10C II. When I switch to the regular A-10C they show up fine.
  3. So here I go once again replying to my own threads. (I think I'm going crazy. Who knows?? I do!!) So it seems like there was an update( and it looks like the MFCD_init.lua got updated) JUST NOW for the OpenBeta version. So I ran the update, copied over the export .luas to the Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Cockpit\Scripts\AN_ALR69V...\indicator directories, relaunch the OpenBeta, ran one of the training missions, and POOF! everything is showing up on my 2nd monitor nice and purdy, ready for a Helios overlay.
  4. Hey guys, I hope everyone is doing well and staying safe. With the new release of the A-10C 2 DLC I'm getting back into DCS after a long hiatus. This is the first time I'm dealing with the OpenBeta version of DCS and I'm just looking for some guidance regarding exporting my viewports such as the Digital Clock, RWR, UHF... to my second monitor when using the Open Beta version of DCS. I have them all setup and working in the standard version(\Eagle Dynamics\DCS World) but it looks like the file structure is a little different in the Open Beta version. I followed the instructions in the second post from here(https://forums.eagle.ru/showthread.php?t=70716) but I'm not sure If I put the files into the correct locations in the Open Beta version and if I need to reference the name of my monitor.cfg file(A10C Touch.cfg) in one of the other files such as the "ViewportHandling.lua". I might be wrong on that. It's been a while since I set these up and I can't really remember. The issue is that I'm not able to see the viewports for the A-10C 2 in the Open Beta. I can see the MFCDs on my secondary monitor so I know part of it is working but I'm looking for some help making sure I've got the other .lua's(Digital Clock, RWR, UHF...) in the right directories and where, and if, I need to reference my monitor.cfg file name in any other files. Or, maybe there is just another setting or edit I missing somewhere. Hopefully that made sense. Please let me know what information you may need and I will gladly provide. Below are the instructions I followed and the directories I used for both DCS World and DSC World Open Beta. (NOTE: I slightly edited the instructions to make more sense to me and these were for version of DCS so I know the file structure has changed since then.) 1. Copy the "Aircrafts" folder from either preset 1. MFCD in cockpit ON or 2. MFCD in cockpit OFF into Eagle Dynamics\DCS A-10C\Scripts\ and allow to overwrite. I went into the Aircrafts\A-10C\Cockpit\AN_ALR69V folder from the provided .zip file and placed the .lua file in the following directory; Eagle Dynamics\DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALR69V\indicator folder. (I made a backup copy of the original AN_ALR69V.lua in the same directory) I repeated this for the CDU, CMSC, CMSP, DigitalClock, MFCD, and UHF_Radio I also placed the ViewportHandling.lua file from the Aircrafts\_Common\Cockpit into the following directory; Eagle Dynamics\DCS World\Scripts\Aircrafts\_Common\Cockpit directory. For the DCS World OpenBeta directories; Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Cockpit\Scripts\AN_ALR59V\indicator folder. (I did make a backup copy of the original AN_ALR69V.lua in the same directory) I repeated this for the CDU, CMSC, CMSP, DigitalClock, MFCD, and UHF_Radio I also placed the ViewportHandling.lua file in the following directory; Eagle Dynamics\DCS World OpenBeta\Scripts\Aircrafts\_Common\Cockpit directory. 2. Copy "Export example.lua"(monitor.cfg file which mine is named A10C Touch.cfg) to "\Eagle Dynamics\DCS A-10C\Config\MonitorSetup" DCS World directory; Eagle Dynamics\DCS World\Config\MonitorSetup DCS World OpenBeta directory; Eagle Dynamics\DCS World OpenBeta\Config\MonitorSetup 3. Select "Export example"(in my case A10C Touch) in the Options screen from the "Monitors" drop-down tab in the game menu. And like I said the left and right MFCD's show up on my second monitor but nothing else. My In-game setup is the following; Main Monitor is 2560x1440 and my secondary monitor is 1920x1080(where I want the exports to be) Resolution=4480x1440 Aspect Ratio=1.7777777777779 Monitors=A10C Touch I just copied the A10C Touch,cfg file that is working in the standard version to the open Beta version and I only see the MFCDs so I'm missing something. Please help. I know it's probably something simple I overlooked and any help is greatly appreciated. Thanks for reading my nonsense.
  5. Does anyone have a copy of one of the older versions of the driver for the X-52 Pro that when you look in the properties of the device it gives you the option for the the POV2 LED adjustment? I've noticed that the newer drivers seem to be for the standard X-52 stick where the POV hat on the stick does not have an LED.
  6. I found the directory where the inti.lua files go and setup all my viewports last night. Special thanks to my own brain. :)
  7. Hi everyone! I'm back in the game after a long hiatus. Since the upgrade to 2.5 I have noticed some of the file structure has changed in the ED directory on my PC. I'm looking for a little assistance with getting the other viewports to show up on my secondary touchscreen monitor. I briefly glanced over some other threads and seeing some other users with the same issues such as being able to see the RWR, CMCS... viewports. I have a copy of Loz SM 2.1 which contain the the individual inti.lua files but I'm not sure if they are still applicable and/or where they go. Any assistance would be greatly appreciated or at least point me to a helpful thread. If I find something that works I wouldn't mind putting together a document and video showing how to set all this up from scratch. Thanks again, 0utLAW
  8. Lars would you happen to have just an outline layout of your files? I'm looking for templates for the layout and hole sizes for plate that the switches would screw into and the same for the face plates.
  9. Also, I know I'll want to add rotaries and digital displays for for the counter measures and radio type panels. I have a very basic under standing of electronics and 0 programming skills(I'm not a fan of looking at lines of code). I'm interested to see what easy-to-use low-cost options are available. I have been interested in working with arduino's but again, code. I know being able to control the displays will require some level of coding and I'd like to ask for help with that when I get to that point. I think I have all of my toggle switchs covered with the 3 GrooveyGameGaear boards and now all that is left are the rotaries and the displays.
  10. I have files that look like this but I just want an outline of where the hole placements are and the panel shape.
  11. Looking to redo/upgrade my consoles since I now have the Thrustmaster Warthog. I'm looking for just some basic outlines of the base plate(what the toggle switches screw on to) and the hole sizes and location for the faceplates(the top most plate you see). I'm just looking for outlines of the hole locations. I plan on printing them on clear stick paper to place on acrylic to use as a template. I have some files but the entire area is filled in in black. I'd like to conserve a little ink.
  12. So I just got the Warthog and I'm still at work. I opened the box and man, I'm inpressed so far. Just the handgrip alone must weigh like 2lbs. Can't wait to get it setup!!!!
  13. Yeah, I'm looking at making a custom desk with pull out left and right consoles. I also want to mount the stick on to my chair with a buttkicker attached to both the chair and the stick for feed back when I hit the GAU-8!!! Also, what kind of grease are you guys using for the stick? Can you get from Pepeboy's or some other automotive shop?
  14. I finally bit the bullet and ordered the Warthog HOTAS and Saitek Pro pedals! Now I can take my madness to the next level. Now that I have these items I'm going to be building a custom desk pit with pullout side consoles and and a recess for the front dash/touch screen. Wish me luck!!!!:pilotfly:
  • Create New...