Nereid

Yes, the path is for A10, but BS2 is similar. If you don't change the aspect ratio you will have to experiment with coords, because the view wont appear as you might expect them. My first solution was to adjust the x/y coords of the MFCDs but then I got the aspect valua right an voila all views show up as expected. Maybe my finding is not the whole truth or perhaps wrong, but it worked for me. PS: its in the "saved games" folder of the OS user; most often C:\Users\username\Saved Games, if "username" is your login name.

Well... its not that hard. It had cost me one evening for the basics and another for bugfixing the script. But ok, I'M working as a software developer in real life, so I have a bit experience in learning new languages. ;) But really: Its not that hard. I had ignored the script language of the CH manager so far. But A10 asks for a lot of keys and new solutions. Used up all 50 keys on the MFD for BS2 and nearly all in A10, but still not fully configured. So scripting was the last solution because another MFD would be to expensive and not practical, because it would use to much space on my desk. ;)

No, it relies on CH Control Manager programming. So its only useful for the CH HOTAS. I use it mainly on my MFD and I use it a lot at the moment. But it works well when a audible feedback from the game is given. A primitive example of the script: ---------------------------------------- // Master Arm Switch %DEFINE MasterArmSwitchArm CMS.B5 %DEFINE MasterArmSwitchSafe CMS.B6 %DEFINE MasterArmSwitchTrain CMS.B7 [...] // Master Arm button observer sequence wait( JS4.B31 ); MasterArmSwitchArm = JS4.B31; delay(1); MasterArmSwitchArm = false; delay(10); MasterArmSwitchSafe = JS4.B31; delay(1); MasterArmSwitchSafe = false; delay(10); MasterArmSwitchTrain = JS4.B31; delay(1); MasterArmSwitchTrain = false; endsequence Buts thats the easy part. Rotation knobs are a bit complicated: // Formation Lights Knob %define FormationLightsButton (JS4.B44 OR JS4.B94) %DEFINE FormationLightsTimer CMS.B19 %DEFINE FormationLightsFlag CMS.B20 %DEFINE FormationLightsInc CMS.B37 %DEFINE FormationLightsDec CMS.B38 // formation lighs knob observer sequence wait( FormationLightsButton ); FormationLightsTimer = false; delay(10); FormationLightsTimer = FormationLightsButton; // was button release in first 0.5 seconds? if( FormationLightsFlag ) then FormationLightsDec=FormationLightsButton; else FormationLightsInc=FormationLightsButton; endif endsequence // formation lighs knob increase, if button was not releasedin first 0.5 seconds // formation lighs knob increase, if button was released in first 0.5 seconds sequence wait( not FormationLightsButton ); if( not FormationLightsTimer ) then FormationLightsFlag = true; else FormationLightsFlag = false; endif delay(20); FormationLightsFlag = false; endsequence ---- PS: indent is not shown and its an incomplete part of my script. But if anyone has a question, just ask. And: the CMS-buttons had to be assigned with the correct keys of cause...

Is there a way to get the ingame map (F10) only on one monitor in a multimonitor setup? Is there a way to limit the size for the ingame map? I have configured A10 and Bs2 with a multimonitor setup an currently 3 monitors (soon 4 monitors). Unfortunately all with a different resolution. Well in flight it works great with one exception: the ingame map. I use it mainly for testing and training but because of the different monitor resolutions a part of the map is hidden. I'm still looking in the luas but didnt found anything so far...

Did you adjust the aspect value in the ...\Saved Games\DCS Warthog\Config\options.lua? If not, try ["aspect"] = 3674/1440, I had similar problems before I have done this. André

Well, in A10 its nearly useless. Agreed so far. In BS2 I trim the pedals often back to middle and so I cant live without Ctrl-Enter. Agreed also. But a trim reset can implemented in a way that do not lead to the are-you-still-there-question. Of cause the reset has to be done in a smooth way and at the moment the reset key is released the trim reset stops (even its not in neutral position). No rocket science. AFAIR the trim-reset in BS2 is not done in a smooth way, so for me it was useless. BTW: Is there any known way to get the Ctrl-Enter-Display on another screen position/monitor? PS: Ah! now I understand! You have an axis for trimming on the HOTAS. So yes, thats an interesting question how to utilizise this with a trim reset. :)

No. They say their Control Manager works with CH Stuff only - which is obvious of course. Logitech for example also states on their website that their driver and programs are compatible with logitech products only. But other mices dont stop functioning only because you have a logitech mouse plugged in... Trust me, I'm using the MFP myself and the Cougar MFD also. They both work. Its quite nice to have the CH MFP but of course its only a compromise. Still 50 keys are not enough but thats the max number you can order in groups and remember on such a small area. And flexibility comes with a compromise - thats nearly unavoidable.

lol :) Well of cause it will work. Its just another keyboard ADDITIONAL to a Cougar. You only will have to use an additional software (the control manager). Or do you really think, because the configuration software used for the cougar could not longer be used if you connect a logitech mouse for which the cougar software is of cause incompatible also? ;)

Something like this? http://www.chproducts.com/Multi-Function-Panel-v13-d-724.html ;)

I tried this but the sudden change in trimming caused me to many problems. So I prefer to retrim most of the time - and I will have to keep the pedals in mind. A "pedal reset" or a "stick only trim" would be a nice option. Often I retrim only the pedals back to center. With a little practise trimming works without an extra "pedal reset", but an extra key as an option would be a nice feature. especially if a keypress would not trim suddenly but trim smooth toward the center while the key was hold. Still dreaming... ;) BTW: The first days I have tried to fly in BS2 without trimming. A very hard experience. After reading the manual and some guides I got it. It works, but you have to get used to it. One of the first lessons flying the Ka-50 in BS2: You cant fly serious without trimming (and using/understanding the autopilot correctly). And someone mentioned allready: the RCTL-Enter key is very useful!!

Well, I have never owned the TM Warthog. Just got my hands on for a short time in store. Its a matter of taste I think. But if I had no HOTAS at the moment, the TM (TH was a typo) HOTAS would be my choice too. Regardless some users that have reported it gets a lose center after a few months of use and something like that. Price is nearly the same. On quality is a CH a bit on the plus side in my opinion, but it lacks the nice metal feeling and the second axis of the throttle. So... still hard to decide... for that price a HOTAS must last long. CH does, TM... well, a few strange reports are out there. For a first HOTAS I would take the risk. For an upgrade it has to be a better investment without such a risk. TrackIR is on my wish list way before the Warthog. And just before TrackIR my own selfmade panel with integrated MFCDs... so the Warthog has to wait. ;) In my oppinion the original poster should decide if he trusts in the long term quality of the Warthog. If he does, he should consider it over the CH HOTAS. If not, well, the CH is not a bad choice. BTW: In germany the 500$ are not enough. The Warthog alone costs over 300 Euro, plus TrackIR, plus pedals it goes over 700$ easy.

I know, but its a matter of priorities. At the moment I can live with some coolie hats and mini-sticks for viewing. ;) But Track-IR is on my wish list for the future. :) And because the original poster wants to buy Track-IR he probatly dont miss the mini-stick of the Pro Throttle to much.

Well, nice to hear. I had owned the first throttle from TM [incorrectly was TH before edit] about 15 years ago and at those days the options were quite limited. And the documentation from CH is also far away from ideal. At the moment its hard to decide between CH and TH I think. Two throttle axes are nice at the warthog but I would miss the mini-stick of the CH Throttle, because I still dont use Track-IR for viewing. André

Just my two cents: I own the CH HOTAS for several years now and I have seen a Warthog HOTAS in a store. First the Warthog is impressive and two axes for the throttle are nice (that the only thing I'm really missing at the CH Throttle). But: The Warthog is a little limited in use in my oppinion. Also some users reported its well build outside but the inner mechanic is plastic and dont last that long (but I do not have experience myself, so dont take this to serious). The CH HOTAS is - well plastic all over but none of my sticks broke so far or developed some kind of misfunction over years. A friend of mine had a CH Fighterstick and spring broke someday. He has written a letter to CH and they send him 5 (!) new springs (to germany!!) so he could repair his stick. Conclusion: sturdy and good support if needed. Also keep in mind the flexibility of the key assignment software. I don't know the if TH has a scripting language for his HOTAS but CH has. Take my other post (http://forums.eagle.ru/showthread.php?t=87629) as an example. But to honest: For the A10 I'm also thinking about the Warthog HOTAS. But some user reviews and the price are still keeping me away so far. And I still like my CH HOTAS, even it looks not as cool as the Warthog. André

Well, I dont know how many people are using the CH Products HOTAS here, but perhaps some are using it for A10 and have never used the scripting language and a CMS device so far. I'm using the Fighterstick, Pro Throttle, Pro Pedals and the MFP with a total sum of 90 keys (shift and layers not included), but even this amount of keys is not enough for A10 in my opinion. The main problem is building group of keys that can be remembered easy. Unfortunately there are some key combos in A10, that use up many keys on the HOTAS. Take enginge startup/shutdown as an example: LALT/LCTL-POS1 for left/right startup, LALT/LCTL-END for left/right shutdown. If you dont like shift layers (and I don't, because you have to press two buttons at the same time) this will use up 4 buttons an the HOTAS or MFP. Another example are three way switches as the Master Arm Switch or the Autopilot Select Switch, which have 3 keys to assign but assigning three buttons on the HOTAS is just a waste of keys and hard to remember in some cases. So I have played with the scripting language a bit (but I don't think I'm the first one ;), so you might find similiar ideas/solutions and perhaps better ones in other places) and configured my buttons on the MFD (but buttons on the HOTAS can configured in similar way) as follows: three-way switch: -------------------- - button pressed and released immediately selects first switch position (you can hear one "click") - button pressed and released after about 1/2 seconds selects second switch position (you can hear two "clicks") - button pressed and released after about 1 seconds or later selects third switch position (you can hear three "clicks") => one button: three keys! rotation knob: ---------------- - button pressed for longer than 1/2 second: knob is rotated clockwise - button pressed for less than 1/2 second and immediately pressed again: knob is rotated anti clockwise => one button: two keys, no shift key two buttons (to avoid a second layer or a shift key): ------------------------------------------------------------ - button pressed for less than 2 seconds, a release will give key x (e.g. right engine right) - button pressed for more than 2 seconds, a release will give key y (e.g. right engine stop) => one button: two keys, no shift key; => second key function is secured, because you have to press the button for a long time For BS2 other functions are possible: e.g. first short press opens close cover of a switch, second press toggles the switch. If somebody is interested I could give a description how to implement this. Its quite easy to do, but a bit complex to describe. So I will do that only if someone wants to try it out. André

Yes its just easier. But I would like that option too. Trimming even with a HOTAS ist still a pain in the ass in my oppinion. In BS2 I would like to get the option to reset the rudder only or to trim the stick only.

Easy (but naive) answer: You could use the fullscreen mode (FSM) with this feature (and use another application to draw the MFCDs on smaller displays). Fullscreen mode renders faster on most graphic cards so you will gain a few fps. But the problem (thats the reason why the answer is a bit naive) might be, that in FSM the graphics card could not render the images for the MFCDs, so it hat to be done by software. In one or two years all of us have better graphic cards, better cpus and even on my current machine (K2600, GTX 560 Ti) the fps impact for using two small USB TFTs and a second monitor (running A10/BS2 at 4000x1080 at the moment), is not that big. Even with mirros on its playable. Conclusion: Time will solve the issues with fps. I'm currently only testing not flying for real with 3 and in a few days 4 monitors. Its still playable in window mode at this resolution - and normaly I'm very picky with fps rates.

Nice idea. If there were some documented TCP/IP interface, I would allready written a program myself to export those displays on external monitors. There are 8'' USB TFTs out there which are great for displaying ABRISS, SHKVAL or MFCD displays. I'm currently planing to integrate two TM Cougar MFD with such TFTs (and lots of buttons and switches) in a case for that. But unfortunately I dont think it will be implemented soon (or ever?). So we will have to use the windowed mode. For myself the fps impact is not that great, but the configuration in the lua is a mess.

Well, it's not on top of my wish list, but easy to implement: A bit more flexible control options. The options in the configuration screens are quite good but key consuming on the HOTAS (and all other auxiliary input devices) have some disadvantages. At least every switch/button on the virtual cockpit should have a (optional) key command to toggle its state. In A10 this is not the case for all switches. The "Master Arm Switch" has three keyboard shortcuts for all its setting (which is great so far) but this means you have to configure three buttons on the HOTAS for that. I miss a control option that toggles the switch from ARM to SAFE to TRAIN. On the other hand it would be nice to have control input that set the switch to the state of the button. E.g. Button 25 on Device 3 pressed should set the switch into "on" setting until the button is released. This could be used by other input devices that have real swicthes (switch in up position hold the button, switch in down position releases the button). I'm currently building my own panel witch switches and two MFDs. But I'm limited to 128 switches at first and I have to keep other simulations in mind also. Three button or a three state switch for the "Master Arm Switch" is just to much. Regards, André

Ah! Thank you! Searched in the wrong forum! :doh: Nice to hear that it will be fixed. :)

Hi! Don't know if someone else has noticed this allready (searched the forum but found nothing): If an ai aircraft hits a ship with a guided missile (eg. a Sea Eagle) the sim crashed immediately. For me this is 100% reproducable. Has anybody else observed this? Is this a known bug? Sim: Black Shark 2 1.1.1.1 Regards, Andre