Gadroc

It's not power necessarily. If I remember right the display link drivers are kind of a hack which taps into an existing driver instead of supplying it's own full blown display driver. It wouldn't surprise me if that has issues with advanced things like eyefinity.

USB monitors will probably not work for performance reasons on this kind of data display. You have really three options. 1) Get a TrippleHead2Go to run main three screens and connect the two MFD displays directly to your card. 2) Disable crossfire and use secondary video card to drive two MFD dipslays 3) Add a third video card. Performance will be an issue if you don't have another suitable PCI-E slot.

I asked this of Wags at the HOTAS Warthog event. The MFD displays will be able to be placed on secondary monitors just like the ABRIS and SHKVAL in Black Shark. He did indicate it was process for doing so was streamlined, but no further specifics. Note that saying second monitor is not the same thing as via lan connection. The way Black Shark works today it has to be a monitor connected to the same computer, I would guess that the same limitation will apply. Leavu takes export data and generates new screens, this is easy to do across a lan connection. Exporting full graphics like the TVM display would require a different scenario of encoding the frames in real time to a network friendly protocol and displaying them on a secondary computer (aka treat them as real time streaming video), or it would require a MS Flight Sim like capability of running the same simulation on multiple computers. It would be very cool, but I'd imagine low on the priority list as those are niche of a niche market type capabilities.

They are working on new software to program the stick with, but it was not finished as of the launch event. It was still in testing. The stick and throttle on the warthog are completely separate physically. They each have their own USB cable and plug directly into the computer so you can use your existing Cougar stick and the new throttle. They did not have any indication of selling them separately and I would highly doubt they will. In any case you will want the new stick even if it is just to put the new grip on your existing cougar base as the new stick grip has MUCH higher quality buttons and feel to the existing cougar grip.

This is a known issue. There is no way to extract any of the seven segment displays (PVI800 or UV26) from the simulation. The UV26 display in TouchPal is a hack which assumes you control the counter measures through TouchPal only.

1024x768 is just what the profile was designed for. You can modify or create your own profile. It can be done and "easy" is in the eyes of the one doing it. If you have a good grasp of XML you should be able to modify as you see fit. You may also have to redo some of the graphics. Not hard if you have a good grasp on XML and have some graphics skill to make the images. Also look earlier in the thread as someone has already created an editor based on open office. LUA is not required (unless you want to interface to a new simulations like FC2) TouchPal supports two-way communication with the sim. It reads the state of the sim to display switch positions and indicators. TouchPal sends absolute switch positions to the simulations. This all means TouchPal is never out of sync with the simulation. Varies greatly. I've gotten one as low as $50 US from e-bay, but they often go for $200+ on ebay as well. You can get new 21-23" touch screen new from HP and Acer for $300-$500 so check before you plunk down the higher end for a used 15". You can also get kits to add touch screen to an existing monitor for $80+. Just that you'll have to setup your own profile. There is not enough screen real estate to do ABRIS or Shkval on them either, but that may not be important to you.

There is a slight bug in my releases of TouchPal which prevent this from working. Try the version by ddahlstrom earlier in this thread. I've been to lazy to merge his changes into the official source tree and re-release.

That will work fine Manne. Keep in mind Touchpal does not display the shkval and ABRIS you have to configure Black Shark to put them on the right place on the screen... Touchpal just draws around them. The Black Shark profile that I've posted is designed for 1024x768, but you can with a little effort modify the xml file to display it any way you want. I have not tried trujillostm's editor yet but that may be an option to modify it to your resolution as well.

I've done the same. If you don't have a lot of background things messing with the trackir camera the hatclip seems to work just fine.

Glad you enjoy! Unfortunately there is no know way at this time to extract that information from BlackShark, so it will remain blank until someone hacks a way or the PCIP is released. From recent forum posts it may be a while.

How is the performance of running the ABRIS on the USB display? I ran into performance problems running the ABRIS on a secondary PCI video card.

Welcome back!! You're work was an inspiration to start some of mine. I'm very interested in the cyclic as well. I've also though about a mechanical trimmer.

The only way to get rid of the that is to setup so your secondary monitor is virtually below your primary monitor.

PVI will always be blank as that information is not available from the simulation. Do EKRAN messages show up? If so the Export.lua is working correctly. To get the ABRIS and Shkval at the correct locations make sure to follow DickDastardly's posts on how to setup black shark correctly.

1) The biggest hit is just using a windowed multi-monitor config in Black Shark. You will take this hit no matter what you do beyond a single monitor. 2) I would expect you would at least be able to run at least 20-30 fps probably more after tweaking. 3) Up to you on if the additional input method is worth the price. I'd have a hard time going back. 4) Touch screen overlays on ebay go from 80-150 depending on the size and aspect ratio. Always pay attention to the shipping cost before bidding as most of them have $30+ in shipping, as these panels are primarily shipped out of Asia and are delicate. I ended up getting a couple good deals so I have not used one of these.

On to step 3. The view buttons are use keyboard emulation so they work no matter what. The ABRIS is blanked out until it is turned on as BlackShark has funky graphics glitches. In order for TouchPal to know the ABRIS is turned on and for the other buttons to work the Export.lua file needs to be installed an executing correctly.

Reread / do step 2 of the instructions in the first post of this thread. Touchpal is not finding the touchpal.xml file, which is usually caused by expanding the blackshark profile into the wrong directory.

Yes, the changes are part of the 1.0.1 patch. That wiki page is unfortunately the entirety of the official information on this topic. I have posted several times in various threads on how to get the information you need from the lua files included with the game. Search through my old posts to find them. I know several where in Oakes build thread, but some where scattered as answers to other questions.

That depends on the touch screen drivers, so the answer may be different depending on the manufacturer. I have three touch screens hooked up on mine. The dell's I have run 3m controllers and screens. Their latest driver supports multi-screen configurations. I've even got it to run properly with two of the touch screens running as one display using a matrox dual head 2 go.

There are examples of doing what Oakes said in both his SIOC scripts and the Touchpal scripts. One thing to note is that not all commands can be executed like this. Only clickable items in the cockpit can be triggered through lua. For other things (like controls on the collective, view controls, etc) must be done either through mapping direct x buttons in game or keyboard emulation.

Flim as a HP L2105tm which he said works well. I do not know if he's hooked it up yet in a multi-monitor configuration.

The E153FPTc are touch screens to begin with. I did not have to buy an overlay.

I realize that. My comments where to Unicorn0578 about the string of adapters. He won't see anything in a control panel until he wires the pedals to some electronics which show up as a Direct X controller in windows. The string of plug adapters will not do that.

Hence the step 2 in the Touchapl thread which tell you to do exactly that with the second zip file. :doh: This is one of the most common "issues" I've seen written up and the error message is not very friendly. You can place the touchpal window anywhere you want. Just edit the touchpal.xml file and modify the X and Y values under the Layout section of the file.

Once properly connected yes they could be used in the game. I would highly recommend not trying to connect those pedals as you've described. You will likely burn out your USB port if you try. The difference between those connector's is MUCH more than just the physical contacts which you are adapting. There are ways which you could connect those pedals via USB, but probably not worth it. It would cost about half of what a real rudder pedal setup would cost, while still not physically functioning correctly as Prophet4no1 states. In addition given your original plan I'm going to assume that exercise of figuring out the real pin-outs for the connection would be a stretch.