blaster454

It's working for me with Loz's profile (main monitor and 23-inch touchscreen position below the main). Only thing not working right now is the radio control interface and I believe Gadroc said that could be worked around by mapping keys (although that might be a nit painful). I'll wait to see what happens. I can say that once having used Helios it's become like TrackIR and a good HOTAS ... indispensable! :)

Jeff, I have not tried to export the CDU display since it can be sent to the MFCD. Maybe someone else here can help. I now have Loz profile running with the RWR, the 3 UHF frequency/preset fields, the digi clock, the CMSC and CMSP displays, plus the 2 MFCD's. In the air in the instant action mission, I get ~60 FPS with the profile running on the same computer as DCS.

Thanks guys! :thumbup: I prefer to keep the virtual windows monitor setting the same as the physical position (top-bottom). For me it makes it easier in other non-gaming programs when the mouse cursor moves from monitor to monitor "the way I think it should" ;) I fiddled with your settings Loz and have everything displaying although some things seem a little big so maybe have to adjust my scaling (UHF repeater readings. Some of your x-y coordinates were off for me and some were spot on -- perhaps it has to do with monitor differences. But, I've got everything "in the window" and readable so that is super. Now just waiting for the radio interface issues to be worked through. Really appreciate the help and also the work people put into making profiles and mods. So far, I don't see any FPS hit at all with Helios running although I've not tried it yet on a busy field or over a large city. Loz, are you working on your v2.0? If you need any help, just give a shout.

Following with great enthusiasm and much applause! Can anyone post the x-y coordinates for each of the exported displays for Loz's 1920 x 1080 profile with the touch screen below the main screen? My monitor config is a 28-inch 1920 x 1200 with a 23-inch touch screen at 1920 x 1080 directly centered under the main display (physically and in Win7), so I know my dimensions are x=0...1920 and y=0...2280. I've been tweaking -- painfully :cry: -- but it is taking a really long time. If anyone cares to share their results, I'll gladly buy the virtual beer! I do have all the init files fixed for 1.0.9 but the coordinates are a tad hard coming to these old eyes. Appreciate any assistance. The only thing after that is the radios.

Could someone with 1.1.0.9 tell me if the commands spreadsheet is the same one I posted? If so, I will commit to updating it to 1.1.0.9 and posting it here. I am also working on a radio commands listing that includes ATC, AWACS, and FAC as well as the flight and wing man commands -- useful for VAC users who want to set up a comm profile.

FWIW, the 30-Jun-2011 document file has a version 0.9 entered in the Subject box.

Are not the number in that trigger to test if the unit ("Player") is within the specified heading (001 through 049)? If so, then the message is sent telling Player to turn to a heading of 300 degrees.

Might be some ambiguity at play here. Spudman, you said "SPI/waypoint" and it's not clear (to me) if you meant one or the other or if you considered them to be the same (and they are not necessarily so). CCRP requires there to be an SPI (sensor point of interest) defined as a point in space where one of your sensors is looking. That could be designated by slewing any of your sensors (TGP, HUD, MAV, and TAD--if there is a mark or way point on the target) over a desired target and using the HOTAS to designate that point as SPI. So, you can just pick a "random" target somewhere and drop an LGB on it. That target just has to be an SPI. It does not necessarily have to be over a way point, steer point, or mark point unless the TAD is your SOI. Hopefully that made some sense :)

OK. The errors you are getting sound like something is not executing properly. I am not Vista-familiar ... does Vista have the same protection scheme as Win7 (UAC)? If so, it could well be that you have a folder permissions problem. Did you install under C:/Programs(x86)? You might check to see if you have read/write access to all of VAC's install folders (might not be finding a dll or read/write error on another file). Sorry, I know it's not much help. Shift_E will get back to you with an answer as soon as he can. He can probably point you in the right direction. Or perhaps there is someone else here that has had this problem and knows the solution.

My tests so far with VAC (v2.60) and DCSW have been OK. I am running Win7 64-bit. Are you running the latest VAC build?

Intriguing quote from Wags: "We envision DCS as an open-ended simulation environment. While we are currently focused on high-fidelity simulation of modern aircraft, we also intend to later broaden it to other types of vehicles, at different levels of fidelity and at various historic eras" This should bring on a lot of speculation in these forums. :)

+1 ... would make it much easier to get info

That IS good news

Take a look below the sticky posts on this page. I posted the RC keyboard list with a few other files.

We don't have a mission building folder (yet) so I'll put this here. Attached is a file with the cockpit device ID's that can be used with trigger actions. I am working on extracting a human-readable list of action ID's and arguments. This only works in SP for now but can be useful for building training missions. In general, the perform cockpit Clickable Event action takes three arguments: the device ID as a numeric 1-255 (e.g., LMFCD, CMSP, etc.), the action event ID as a numeric 3001 to 3999 (but only about 70 defined now), and an argument for the event (like 0, 1 for off and on). A-10C Device Enumerations.pdf

Thanks, StrongHarm! I tried to do it in one page but the typeface was hard to read at any distance (old eyes here :)). I also have it in Excel (one of my favorite apps!) but will look at yours and see what I can do. BTW, I am anxiously awaiting your VAC profile for the RC .. I shamefully am holding off because yours was such an excellent piece of work!

Thank you! I found this easier as a desk side reference than the chart in the manual. There are lots of ways to represent this data and maybe yours is better ... why not post it anyway?

Thank you! Corrections made and a new file posted above. Also added a matrix to allow easier key assignment choices.

I had posted this buried in another thread and thought they might be more visible in a separate thread. Hope they are of some use. EDITED 4 MAR 2011 1. Updated the default key assignments list to correct two errors and to show it is for a US keyboard. 2. Added a matrix of US keyboard keys and modifiers to allow easier choice of key assignments. A-10C HOTAS CHART.zip AVAILABLE KEYS MATRIX (US).zip A10C RC DEF KEY ASSGNMENT (US).zip

Here is the Excel file zipped. This is a work in process so not all the sheets are finished but the first one has the event assignments. I'll be updating this with event assignments against all available keyboard commands to aid in setting up auxiliary controllers for some of the commands. Enjoy! :thumbup: Keyboard Key Matrix (WIP Rev 0.1).zip

Actually, I have the list in Excel but put it into PDF format to make it more usable. Send me a PM to let me know how you want it sorted and I'll be happy to comply. Or, I can attach the Excel spreadsheet if you can use that.

Here is an updated set of what I think are all the available commands (events) plus those assigned to keystrokes in the default keyboard file for the Release Candidate. No guarantee of accuracy since there is a lot of data to pull out of the files and it's easy to make a mistake. :smilewink: Hope this is useful. A-10C Keyboard Key Matrix.pdf

Sorry, I should have explained a bit. There are a set of .lua files which allow you to compile to text all of the control settings you have programmed in the simulator. There are two batch files (*.bat) which drive these .lua files. In effect they go through the input files for each controller and select out the assignments and format them into more human-readable content as text files. One of the definitions of "parse" is to analyze the syntax (structure) of a file to enable pulling out desired detail.

Thank you, Rik.

No one has the parser batch files? Were they included in the release candidate?