lxsapper

Rgr hadn't seen this before.

Yes Sokol, asside from the fact that the warthog and the cougar use newer smaller versions of the chip, they are logical chips have the same reference number and work the same way. The FLCS had however a few connections inside wired diferently so I had to swap some wires around to get all the HATS and buttons reporting correctly.

I confirm.

I'm not sure if this is a bug introduced by the new patch or if something got corrupted in my instalation. I did not install any mods recently and the only mod I have installed is the AI Bf-109. This is what my UFC is looking like: Uploaded with ImageShack.com

I confirm the issue. It's hapenning on several frequêncies. 150.00 and 152.00 I remember, but I fount at least one other. Another topic repoting the same problem: http://forums.eagle.ru/showthread.php?t=112786

That's a really cool scheme to have in hand sokol. For my purposes I prefer the Warthog interface. I don't have to buy an extra controler board, I keep my warthog programing and only 5 wires go to the stick grip (wich is handy because it's a tight fit inside the grip pole). But if one wants a completly independent controler, the BU0836 or equivalent is the way to go.

Posted this is another tread and over at SimHQ but seems relevant to put it here again. This is what I'm working on: It will work with eighter a Warthog or a Cougar for interfacing. Some wiring has to be switched inside the handle to make it work properly but it's not too complicaded.

Sorry I didn't see this thread before I reported much the same problem on the "Problmems with A-10A" thread.

CBU's 97 CCIP delivery is (and I belive CCRP) highly inacurate. The A-10C places you in a much stepper diver when delivering the 97's in pure CCIP. This resultes that when employing them with the A-10A the balistics are off, the CBU cassings do indeed arround the target but the BLUs on parachute fall very short from the Target. I started to compensate by aiming forward of the Target and can now get them to fall right over the target area to great effect. But unless the A-10A didn't compute CBUs 97 trajectory properly like it is in the Sim right now. Then it's a bug.

Ok found the solution, setting the TV to "Just Scan" and not "16:9" or "Original" (what I had) solved the Issue.

Ok I partially solved the problem, but now I have another issue. Aparently my Graphic card cannot display a DVI and a HDMI output at the same time. At least I solved it by connecting the TV with a DVI to HDMI cable using both DVI outputs on my graphics card. The problem now is that I now have some horizontal jagginess on the TV, it's not terrible but it's not good eighter, and I don't have this issue using the HDMI cable. I don't know if this is a problem because I'm using the DVI to HDMI cable, or it's a problem with the cable it self since it's a cheap one. Anyone have experience using such a cable with a FullHD display?

I bought a used LG LED 32" FULLHD TV today to use as my main PC (Flight sims!!!!!) display. I also have a 21" 1600x900 touchscreen wich I used to have with my now to retire 19" 1280x1024. I used to run both windows desktop and flight sims such as DCS without any issues with each screen using it's native resolution. But now I can't use the TV and the touchscreen toguether. They both connect just fine buth I can only have the Desktop in one or the other I can't expand the desktop or duplicate it. My GPU is a Saphire HD6870 with 1gb graphic memory. The card has 2 DVI connections 1 HDMI and a couple of dysplay ports. It used to ge connected to 1280x1024 with a standart VGA cable using the DVI adapter provided. The 1600x900 touchscreen was and is connecter with a DVI cable. The FullHD TV in now connected with a HDMI cable. Anyone has some idea on how to fix this?

Quite honestly forget about game mode. If that's what you are after games like H.A.W.X. 2 and Combat Ace (now for PC) will give you a much better experience. DCS A-10C was designed as a high fedility simulation game like mechanics were added in my opinion to boost sale. Sure you can shoot some things in that mode but it's all preaty dull. Simuliation is what it was designed for and that's where it shines. Also if you are looking for multiplayer game mode will be a no go. Start wtih the ingame tutorials they are a good start in my humble opinion.

I just wanted to add my 2 cents here, because I'm alergic to stupidity. So to all you good people, including a valuable ED tester, telling the man (By the way I only bought the full version BS2, so I never had this problem) he should just buy the full version BS2, or shut up. I say: WHAT? Are you MAD? The man's point is perfectly valid, sure ED never got around to it and probably never will, but he's is rightfull complaint don't try to take that from him and dissmiss him as he was talking nonsence. As far as I'm concerned you are the ones who had brain diarrea there. Sorry for beeing frank, but like I said supidity makes me like that.

Actually the diference between High and mediums settings (as per the DCS world manual) is that in medium you only have trees arround urban areas. So what you want to do seems a bit redundant.

There are some photoframes that can be used as USB monitors, look for Samsung they have a few. I think you can only use one though. Obsiously not as cheap as other photoframes, if that was your idea. But I think your idea is not really doable. Belive me I've had some wishfull thinking too....

The electronics part should be fairly straight forward it's the mecanical instalation that may present the chalenge, in anycase it probably won't be hard to do with a little "smart" thinking.

It looks awesome! You won't regreat going force trim.

Thank you for the tip, it's worth checking out. But I think I will be keeping it this way at least for now. It's really meant to be a stop gap solution, at least while I check if I can boost the output on my other MSFF2 to drive 2 or stronger motors. My electronics are limited and my coding nearly non-existant. I will be getting help however. The arengement isn't impratical for me because the WH base will sit on a sidestick configuration (it could be put inside the stand I'm going to build but I intend to use it for flying as well), whenever I want to fly my FF stick I will just put it in place and connect through the Hog maintaining all the programing. Idealy I will end with my WH grip replacing the FLCS (wich is butt ugly and has crap buttons) much like PeterP's cougar grip.

Thanks Swaty... also for removing my dumbness :)

Today I wanted to share a controller I'm costumizing a controller inspired by PererP's 2 MSFF2s merged with one cougar grip. I plan to try in the future to try something more like Peter's controller, but at this time I can't use his solution for using the 2 MSFF's. Basicaly because only works in DCS and I intend to use this with more sims than DCS. It's actually a defect in DCS that it works the way it does in wich any FF controller you hook up coopies the beavior of any controller. This was probably impremented to suport multi-crew cockpits I belive. But what it does in not to allow one to have for example FF rudders. I know there are no FF rudders on the market but one could make them and RoF (the only sim I know of) suports it. So in any case because implementing 2 motors per axis or stronger motors is going to be tricky, I came up with another solution as a backup. So instead of using a Cougar or Warthog's grip I got a really cheap old TM FLCS. Once I opened the grip I had the pleasent surprise to find out that the electronics inside the grip were very much like the cougar's. So instead of having to buy a USB board (like Leobodnar's) to drive the buttons and hats, I decided to try if I could interface it trough the cougar. Also I wanted to retain Cougar functionality (I was also planing a side project to make it a force sensing stick), but I've since switched the cougar for a warthog. Plan is the same here!!!! NOT TO ALTER the interns of the WH in anyway, shape or form! It was a real help that the cougar and WH grips can be interchanged, because I didn't have to change a thing. Originally I had to swap a few wires inside the FLCS grip because of swaped reports (similar to the cougar but not exactly wired the same) and the TG1 and TG2 not reporting anything at all. So I got it all working, it's still in the MSFF2 base waiting for me to build a central column box thing to house/suport it. But I made a video of it working. It's bad quality and my first video for youtube, my native language in not english, the video was shot in less than ideal conditions, at one point you can hear my daughter and my wife in the background.... basically it sucks!!! But I hope it can clear it all up, so that you can have an idea of how it's working.

Yes I was hopping for a .lua workaround. I've seen posts of people editing stuff like trackir default positions and other stuff, default fovs,etc. So I was hopping... I'm going to use a custom curve for now but I was realy hoping to make it temporary.

How can we get this to work on an Android app, but no one seems to find a way to do it on a second screen?

I know it's been a while since this subject has been discussed, but I'm having the same issue now, I can set the costum curve and I know I can do this very easily in TARGET. But I don't want to use TARGET and was hopping of a more perfect way of doing it than the custom curves. Is there a LUA edit one can do to set the Axis percentage when your AB kicks in?

There have been a few incorrect things posted here so here are the correct operation of TMS UP long and TMS down long: TMS UP Long - Make SPI (no matter what your SOI is the designator on your current SOI will be used to create a new SPI) TMS DOWN Long - Makes the steerpoint the SPI (again with any SOI), it does not make a steerpoint out of the SPI you would use MARKS to accomplish a similar funtion. When your steerpoint has been made the SPI changing your steerpoint will move the SPI. You can check this in page 88 of your flight manual.