Quip

I have modded the script, allowing the CAPs to start from the runway. The reason is that quite often teh AI screws up while taxying, so this prevents that, at least on takeoff (they return home far from more seldom :P) I don't know if this is interesting, but here's the run-down. I added this early in the script: Then I modified the lines adding the aircraft (twice) in the script:

How can you have more than 32 buttons per DirectX controller??

SnapViews and its associated files control all the views in DCS, both interior, axternal as well as nsap views and non-snap view. Besides, isn't it up to every player to decide if he/she wants to have snap views or not? But that's besides the point. The point is that the update has broken the game for all players using more than one screen, and that this change is undocumented. The irony is that the remarks in the new files states: "reformatted per-unit data to be mod system friendly" But this reformatting to make the game more mod friendly, isn't documented. And it's a major change. Huge PS: This is in the files, and I suspect it changes the default camera position for external views.

So. 1.2.4 was released, "yey". I read on the official Release Notes and thought "fine". Wrong. Nothing in the Release Notes say anything about the structure of the .lua-files for snap views being redone entirely. Would that have been so hard to add? Isn't that important, in view of the fact that so many threads on this forum historically concern editing of SnapViews(default) and multi-monitor setup? This is really quite bad. /Quip

The game needs a "mods" folder. All files are read from there first, and if a file exists, the game reads that file instead of the default file. Super- simple to implement and makes modding so much simpler.

PeterP, question: Why do you need these settings if you create a new viewport as you describe in your post here? Once I had a new viewport created (with some modifications, see below) I - in fact - had to undo the changes to the two files above. What we need is a simple tool in which you can enter your 3 screens' resolution, and your bevel compensation, and which creates a file for us to put into the folder MonitorSetup. Or am I missing something? Changes in bold

OK, here's v2. Note several about this version that moves it away from SFJack's Coolie moved to Throttle Hat and CMS moved to Switched throttle hat Joystick base buttons no longer control Engines, but controls lights and MOST IMPORTANT, the profile is meant to be used with my own Snap views for better acces to the side consoles and a Zoomed-in MFD view! :-D Read the readme! Quip-on-SFJack v2.zip

if you're doing it for a Mod I suggest you the following: local screenW1 = [x of screen 1] local screenW2 = [x of screen 2] local screenH2 = [y of screen 2] local bezel = [bezel value] And then in the functions: for Status bar: window:setBounds(screenW1 + bezel, screenH2 - h, screenW2, h) for Dialogue box: window:setBounds(screenW1 + bezel, 0, screenW2, height)

Here's what I suggest for the function "updateBounds" in StatusBarDialogue.lua. It allows you to set your exact setting with regards to screen resolution, bezel adjustment and all. Edited parts in bold O.O.T, but this works equally well for the function "initialize" in CommandDialogsPanel.lua. It's the function that draws the comms on the top of the screen: (the function goes on, but there are no changes there)

@Friedric: the lua for controls don't need to be "placed somewhere". You need to load them from within the game. Do remember that DCS titles uses 4 controller setups per aircraft; one each for Keyboard, joystick, mouse and TrackIR. So make sure you have clicked in the joystick column before you load the lua. @Hunter: Yes. This is something you have to fix in your keyboard controllers. Any function that you need to be able to use both unshifted and shifted (pinky), you must add both states to in the controller setup. For example, I have had to add [N] aswell as [JOY BTN 6 + N] for the airbrakes. This mainly applies to the controls you mentioned: airbrakes and ministick slew controls. For that same reason, in my latest private version, I have removed engine ON/OFF from the stick. The reason is that holding pinky and manipulating the flaps would potentially kill the engine. I have also moved the Coolie to the throttle and placed the CMS as shifted throttle hat. To me, this makes much more sence. If you're interested, I can upload this latest version too. But it's becomming less an SFJack profile.

SFJackBauer's profile converted for Saitek X-52 Pro Yes, I have done the job of converting SFJackBauer's profile for the X-52 Pro. It is fully functional, and anything and everything SFJack's said also applies to my profile. There are 2 major changes, which are also in the readme: 1. T3, T4, T5 and T6 switches. These have been remapped so the the left switch manages the left engine, and the right accordingly. I think this is more logical. 2. MFD buttons on Throttle. These are entirely different on the X-52 Pro compared to the non-pro. Also, the START/STOP button sits above the "RESET" button, which makes it more natural to have the START/STOP go to VHF1. DO READ the Readme. There's some important information on importing the .lua to A-10C in there. Please feel free to use the attached files. Instructions as per SFJack's, and the readme. Also please let me know of any bugs as you find them. This is version 1.1 The zip containing the files can be found here! /Quip

Sounds like a problem with the Saitek Magic Bus (don't blame me, it's what it's called). Reinstall the Saitek Drivers, and then, and this is important, the Saitek SST editor. Reboot when/if told. /Quip

SFJackBauer' Profile converted for X-52 Pro Yes, I have done the job of converting SFJackBauer's profile for the X-52 Pro. It is fully functional, and anything and everything SFJack's said also applies to my profile. There are 2 major changes, which are also in the readme: 1. T3, T4, T5 and T6 switches. These have been remapped so the the left switch manages the left engine, and the right accordingly. I think this is more logical. 2. MFD buttons on Throttle. These are entirely different on the X-52 Pro compared to the non-pro. Also, the START/STOP button sits above the "RESET" button, which makes it more natural to have the START/STOP go to VHF1. DO READ the Readme. There's some important information on importing the .lua to A-10C in there. Please feel free to use the attached files. Instructions as per SFJack's, and the readme. Also please let me know of any bugs as you find them. This is version 1.1 /Quip Quip-on-SFJack 1.1.zip