Jump to content

erjdriver

Members
  • Posts

    269
  • Joined

  • Last visited

Everything posted by erjdriver

  1. I run by clicking on DCS icon - everything's ok. No target running here right? I'm running the TARGET script editor w/ my script (with the above definition for the axis) and that causes the problems. I think if I leave the 2 commented lines in - it's a little bit better but not normal. i.e. as running DCS by itself. That code is straight from the script editor pdf file. I guess I could try the graphical TARGET editor and see what it does.
  2. But if I don't use my script - i.e. run TARGET - then when I run raw DCS - my setup runs fine. Doesn't that mean that DCS itself and the controls are set up correctly. I get this behavior only when I run via TARGET script editor.
  3. I should clarify that i'm getting the above behavior if I comment out MapAxis(&Throttle, SCX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); But with those active also - there's something wrong.
  4. Using the script editor to set up some definitions I have the following in the code at the bottom of this post in my file - straight copy of the document I can set up the plane and trim for level straight flight, but as soon as i make a big throttle adjustment - plane yaws and goes into a dive. Not good. What am I doing wrong. Thanks. MapAxis(&Joystick, JOYX, DX_X_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Joystick, JOYY, DX_Y_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, SCX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, THR_FC, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
  5. I noticed that for keys that i do not define in TARGET - the pass thru works fine. For example - not re-defining VIEW LEFT/RIGHT - works fine. It just seems to be a software design issue. If the key combination - even if part of a layer - is not defined - then it should just act as a pass thru. Thanks for the answers and I will look into the script editor. If I did that - is there a way to start the config file + DCS w/o starting up the TARGET program and the pressing the FLY-NOW button. Or at least - can I just make it one key press.
  6. I'm using the TARGET GUI to program some keys using layers and sub-layer (i/o). I defined an action for H1 Up when the sub-layer button is pressed. It works fine. H1 is part of the main directional button on the joystick. But now the normal H1 Up function (w/o the sub-layer button pressed) - i.e. view down - doesn't work. Does use of layers of sub-layers require I have to re-define every combination even though I'm not redefining the key. i.e. isn't there a way of saying - if not defined in TARGET use the default key action.
  7. I'm just starting with A10 and would like to set the default main view to be closer to the hud + angled up a little bit - none of the main gauges visible (they're on 2nd monitor). I understand I can have to set FOV etc. I googled but can't seem to find the right files. Also my folder structure seems to be different - have c:\dcs\Config\View\View.lua All the threads seem to mention a file within the A10 folder. Any help appreciated by this newbie.
  8. thank you - i will definitely give it a try. It seems like this application demands a touch screen 20-24". The only problem is that my computer is too slow with fps when running this game at 1920x1200. that's my normal windows rez. is there any way to force a lower rez just when running the game.
  9. can i get the CDU on this second display also???
  10. thanks - that worked like a charm! small detail i've got main 1920x1200 and the MFD monitor at 1920x1080 (different heights) i can't seem to vertically center the MFDs. for left MFD, i have y = 140; height = 800; since the height is 1080 - setting y and height to 140 and 800 should do the job...right? it's almost as if the height is 1200.
  11. I'm just starting with warthog - but an experienced developer. i've got a 2 monitor setup. i'd like display both the MFDs on the second monitor - control the position size etc. Can it be done and if so any help appreciated.
  12. I'm just starting with warthog - but an experienced developer. i've got a 2 monitor setup. i'd like display both the MFDs on the second monitor - control the position size etc. Can it be done and if so any help appreciated.
×
×
  • Create New...