erjdriver

Yes - what be the trick?

Is DCS World (A10) compatible with Windows 8/10

Found it C:\Users\<my-profile>\Saved Games\DCS\Config\View\SnapViews.lua Thanks again.

Blooze - you're a genius! Any chance you know where this key definition is stored.

How do I contact him? Thanks blooze - think your method will assign a zoom view to a snapview button - i.e. i have to press a button to get that view. I would prefer it to be default on startup. Thanks.

I'm trying to config my A10C setup to set a certain zoom level on start up. Zoom in a little bit closer to the hud. Thanks.

I'm trying to get the default view for my A10 to be closer to the hud with the main panel not showing (on 2nd monitor). I was playing with /config/view/snapviewdefaults.lua file and modified the default view for the A-10C. I can "move" the camera view forward - but the hud text seems to be the same old size. If I zoom in with the JS - then the hud text size changes - that's the view I would like. How can I mimick a zoomed in and slightly angled up view? Thanks.

Did you get the mods comm feature to work?

Am using the Cap Loz A10. Works. But cannot get the communication feature to work. the panel goes black..but no comm options or clickable. Any help appreciated.

bump! any help on this issue.

Where can I get it? Thanks.

bump. The documentation says ...have to change some of the /Eagle Dynamics/DCS A-10C/FUI/Resources/Radio .res files as per this guide. http://files.digitalcombatsimulator.com/en/84648/ That link is no longer active. Any help?

I'm trying to get LOZ/Helios touchscreen functionality working. This add-on allows you to display the COMM menu on the touchscreen. It's not working - i'm pretty sure it's because i've got a different monitor setup. I'm trying to understand the format of the menu.res file. What are the 3 different sections. Specifically explanation of the COORDINATES fields.

The left, right and the panel below the HUD - all of their labels are blurred. My main panel the labels look fine. For example, the CDU switches, buttons all blurry. What could the problem be?

So I have to disconnect the auto-pilot, turn and engae AP again.

Apologies for newbie questions. * can the auto-pilot on the A10 follow the heading bug on the HSI? * if there's a flight plan in there - will the A10 auto sequence to the next waypoint.

Ok I gave up on TARGET - the amount of work necessary is ridiculous and also lack of documentation. I used the in-DCS modifier and it's not too bad. One of the features I liked in TARGET was able to assign an action to a button press and another on release. For example I would like to assign RIGHT-VIEW (w/ S4 mod) TO map-view and on release back to cockpit view.

I've actually done what I need - that is program the layers. But now it looks like I have to re-define every button on the HOTAS. Whee I'm stuck at is can I write via TARGET that this button was pressed (e.g. COOLIE forward) and then DCS assign the correct action based on context. Right now it seems like I have to use map-key to a DCS action. But then I get confused how to figure out the different contexts (e.g. SOI) WHen I use MapKey( &Throttle, CHF, ??? ); for ??? can i use DX? whatever as opposed to a keyboard assigned action.

One of the great benefits of a combined device (throttle+joystick) is you can define commands w/o the requirement to touch the keyboard. For example, The main trim button is VIEW around in default mode. if you want to press a button in the cockpit, you have to switch by pressing alt-c. zoom another key or mouse. You're taking away from the simulation by touching the keyboard and mouse. With TARGET - you define the same VIEW button to do different things in different modes. For example, if you have the boat-switch forward - you can set it up to trim the airplane. if you have it backwards, you can make up/down VIEW buttons zoom and the LEFT/RIGHT do other things - (e.g. view the theater map) etc. But alas it seems like it's going to be a lot of work and am giving up.

Yes

This TARGET setup is amazing and also a huge pain! I'm just trying to add some additional functionality - but looks like I have to redefine every button. Has someone already done this that can be downloaded? I'm trying to wrap my head around this thing and am confused by something. When I define a button, do I define it as a key or a DCS action. And if the latter sometimes there are no keys for some actions. For example, trying to define china-hat forward. Doc tells me what the action should be under different SOI scenarios - so what do I define. For example when HUD is SOI, the short is Set Mav as SOI and long is Slave all to spi. Now I can't find the definitions for these. Since there are different SOI contexts - i would imagine DCS just needs to know the button was pressed (long/short) as opposed to the exact action (that would depend on the context). Right? Any help appreciated? Actually a full TARGET tmc would be great. p.s. the slew button on the controls wasn't working. Had to go into DCS options to map them. They're a little bit too fast - any way to slow them down.

Thanks for the help - I cleared the rudder settings and now works like a charm. Also FYI, seems like DCS saves the setting on subsequent restarts - so no need to do it manually every time. Why one would set the throttle to the rudder beyond me. Now a way to automate startup. Right now I start up TARGET script editor and then select my file, run it and then run DCS. Any way to automate that? Can I select my script also from the TARGET GUI editor.

So in DCS I should go and clear the definition for RUDDER - right? It'll be "saved" for all subsequent sessions?

Ok I went to the DCS in-game options and looked at the axis definitions for the combined virtual device. The problem seems to be that for RUDDER I have RZ defined. When I run DCS by itself - there's nothing for RUDDER - which makes sense. How did that definition for RUDDER get in there (from my file?)

Thanks for the responses. I understand that TARGET creates 1 virtual device. My axis definition for this virtual device is in the original post - copied straight from the documentation. Not right? If I define them as I have, I would think that overrides the in-game settings in DCS. I haven't done anything there. Should I go into DCS options and clear out the RUDDER definition.