Ragtop

This is actually very useful for those that don't know - This allows more accurate marking of a target when being acquired (Mainly from shallower angles). This is because when the laser is not being employed, the actual point being marked is where the line of sight hits the ground behind the target. (New users often find this phenomenon to cause bombs to fall long on targets.) If you use the laser the point will be on the actual target itself.

There's two possible answers here. A) It's on the newer suite jets and therefore not modelled in the DCS module. B) It was not approved by the government/Fairchild/various legal bodies for simulation. Some elements are not in the sim due to legal limitations.

Personally I wouldn't say it'd cause problems. Flight sims aren't exactly the most snappy things in the world. Try starting and stopping a stopwatch reliably in 60ms. I think you'll find it's a pretty insignificant number!

Is there a solution for other profiles? I have a custom profile for my pit but it is derived from Loz'. Is there a way that I can edit my own profile to fix the radios without having to totally rebuild?

Game install directory>Config>MonitorSetup then choose whichever file is currently selected in your preferences. You need to alter the X and Y coords for the MFD's.

It's approximately the same height as my 27" 16:9. Edit: Put 24", meant 27"

It will ding your framerate a bit but it's totally worth the upgrade. No distortion, that's the purpose of the curve!

It's called "Parking Hot". That will drop the jet in a ramp or bay in a green status.

Thanks for what you do for the community Capt Zeen - It's sincerely appreciated.

I'd like to see your take on the A-10C. Loz profile is excellent but your texturing skills seem extremely good!

Agreed. The CMSP is powerful enough that you can do this with a custom profile.

Ah, that's a very sensible way to do it! Of course it would be easy to wire up larger connectors for panels needing more inputs - This is a great solution.

Does that mean there is no need to send a ground to the switch itself? That'd make wiring the switches MUCH simpler! At the moment I run a common ground across all the switches. Do the Arduinos require a diode on each input to prevent them from crossing?

http://www.gadrocsworkshop.com/node/185 Here's a link to the panel counts for the A-10C. Obviously you'll need to add one or more ground lines for some panels, so factor that in to your counts, but 15 pin dsubs should suit most panels, with some larger ones for others. Don't forget it's also possible to connect numerous DSubs to one panel (CDU/UFC) will need this for sure.

Amazing! Definitely want this as an upgrade to my Hog pit! 40pin ribbon cables - DSub conversion would be my challenge!

Is it possible that the profile for your X-52 has changed? If the buttons were bound to keypresses, perhaps the keypresses have changed. That'd result in DCS seeing them as different buttons. If you don't use a profile and it's simply mapped directly to DCS, then it's possible Windows is seeing the device with a new USB ID and has not associated it with the old bindings. Not sure how to solve that one. Probably altering the ID in the input lua file. If you can find the ID that is.

Yeah just grab the User/Saved Games/DCS/ folder, that will contain the required settings etc. Things like monitor configuration (If you use a custom multi monitor setup) are located in the Program Files install directory. (DCS: World/Config/MonitorSetup/)

Thanks. I'll check the lua files to see if theres simply a null value in there preventing me from adjusting them before deleting. Otherwise that should do it! M

HOTAS Warthog. I have the pinky paddle set up as a modifier already, however when I hover over the particular command I want to set for the MFD (Set Left/Right MFCD Day/Night/Off) The relevant button on the binding page is not clickable. (No box appears over the button on rollover, like it's greyed out) It's like DCS is telling me that it's not a valid button.

This issue is now resolved. Both the overlaying and repeating displays and the stuck terrain view. Thanks ED for getting this fix out the door!

Indeed, they are fixed for me! Thanks ED.

When you get a good view position set, use RAlt-Num 0 to set it as the default view. Ensure that saving user snap views is enabled in the preferences.

I want to use my Cougar MFD's to input some other controls in the A-10. Specifically I want to use a modifier plus the brightness rocker to turn on the displays. However the control inputs for DCS will not allow me to bind these controls using the MFD's. I really don't want to have to use TARGET as it's a very heavy application for something so simple. Is there a way around this?

I don't think anyone has achieved the black background on exports. A few have managed to get them to appear, but none have made them appear correctly. MFCD's appear to be somewhat reliable but nothing else. Not heard from Developers on this topic, is it being addressed?

Have you checked the mapping in Options>Controls? Ensure it is mapped correctly by clearing the input and reconfiguring those buttons. Also check that the Coolie hat isn't mapped to another controller that could be clashing.