jwputnam

Thank you. Figured it out.

I am new to this screen exporting in DCS A-10C. I purchased the Cougar MFD set and two Lilliput 80 (non-touch). I am experimenting with the various programs for exporting, such as Ultra MFCD, Virtual Cockpit, etc. I have yet to be entirely successful with integrating any of them with the running simulator, but I am getting close. Along the way, I stumbled onto the A-10c server app for iPad and it intrigued me. Is it possible to send the MFDs to the two Lilliput monitors and separately utilize the iPad app for the engine, radio, etc. controls? That would be really nice, but I can't find an answer to this anywhere on the net. I kind of assume that it is NOT possible, since the monitor selection in the game seemingly cannot recognize multiple applications (*.lua), but maybe one of you geniuses have already addressed this and solved it. I have managed to crash DCS World twice in attempting to research this possibility. Crap it takes a long time to download!!!!!! Thnx!

I went back to the docs and re-read and I found the explanation in the "Campaigns" area. I do not play multi-player and I have never attempted a multi-aircraft mission, so I did not read that section carefully enough. I get it now. Thanks again!

Oh for crying out loud! I see it now. I need to set the skill level to "player". I had forgotten about this. Frankly, I never understood what these selections actually did and why they are there. I have never read anything in the documents about them. Thanks so much. Now I can get back to flying!

I have to be doing something terribly wrong. The simple missions that I create will not let me take control. They fly all by themselves and do not allow me to get in the cockpit (F1). I am a spectator only in the F2 mode. I have toyed around with FC2 for awhile and I am pretty familiar. I am running Windows 7 64 bit on a Intel i7 with 9 gigs of ram. I use TrackIR 5 and an X-52 hotas. I have even tried reloading the program to no avail, so I am thinking that I am the problem. Pre-installed missions run just fine. My creations do not...and they are truly simple ILS practise missions. Any help is much appreciated. This thing is driving me NUTS! PS I never had any problems with the mission editor in Lockon 1.12 and I used it a lot.

Thanks! The attached urls did the trick. Can't believe that I didn't find them in my relentless searching of the forums.

I have read the manual in it's entirety and I have watched all of the training videos (I am anal as hell). I am also an instrument rated pilot with lots and lots of hours, but I am having a hell of a time with navigating the A-10. Three stupid questions: 1. Why the hell is the HUD display not centered sometimes? I can correct it with rudder trim, but I am sure that is not correct. Drives me nuts! I gotta being doing something wrong. 2. I have read and researched lots, but I still do not get how and when to switch to ILS mode. This is just not intuitive to me. I realize that my final waypoint in the training exercise takes me to the IAF. When I get very near it, I switch to ILS and it shows me a #2 (for what reason I have no idea) and gives me a distance to the field, but if I cycle it again, I still get a #2 with a new distance....which I am assuming is the next nearest airfield. What is the significance of the #2? 3. Why are the ILS needles sometimes bright yellow and sometimes a dull greenish yellow. (I know....this is REALLY the most stupid question!) I have a feeling it is because I have selected a too distant field in my experimenting or when have intentionally shot the back course for giggles. At any rate, I truly appreciate your help.

mig29movt I have also spent a few hours developing a very logical (in my opinion) profile for the A-10. It is WAY best to make your own so that you understand WHY it works, but if you want it, I can post it.

Thank you so very much! Finally, I can play the damn game after two days of frustration!

Problem is resolved. How do we let others know?

Log is attached Very kind of you to offer so much help! DxDiag.txt

I'll give this a try and let you know in an hour or so. OH MY GOD!!!! OH MY GOD!!!! You are a f^%*&g GENIUS!!!!!!! It works! It works!!!!!! THANK YOU THANK YOU THANK YOU

The log is too big to post here at 40,000 characters. How about this: ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Saitek Magic Hotkey Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06A3, 0x5081 FF Driver: n/a Device Name: Microsoft Wireless Optical Desktop® 2.10 Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x009D FF Driver: n/a Device Name: Microsoft Wireless Optical Desktop® 2.10 Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x009D FF Driver: n/a Device Name: Microsoft Wireless Optical Desktop® 2.10 Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x009D FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC518 FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC518 FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC518 FF Driver: n/a Device Name: Saitek X52 Flight Controller Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06A3, 0x0255 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub | Vendor/Product ID: 0x10DE, 0x026D | Matching Device ID: usb\root_hub | Service: usbhub | Driver: usbhub.sys, 10/23/2009 23:28:24, 343040 bytes | Driver: usbd.sys, 7/13/2009 19:06:23, 7936 bytes | +-+ Saitek X52 Flight Controller (USB) | | Vendor/Product ID: 0x06A3, 0x0255 | | Location: Port_#0006.Hub_#0001 | | Matching Device ID: usb\vid_06a3&pid_0255 | | Service: HidUsb | | OEMData: 03 00 88 11 22 00 00 00 | | Driver: hidusb.sys, 7/13/2009 19:06:22, 30208 bytes | | Driver: hidclass.sys, 7/13/2009 19:06:21, 76288 bytes | | Driver: hidparse.sys, 7/13/2009 19:06:17, 32896 bytes | | | +-+ Saitek X52 Flight Controller (HID) | | | Vendor/Product ID: 0x06A3, 0x0255 | | | Matching Device ID: hid\vid_06a3&pid_0255 | | | Service: SaiH0255 | | | OEMData: 03 00 88 11 22 00 00 00 | | | Driver: SaiH0255.sys, 2/15/2008 18:24:18, 178304 bytes | | | Driver: SaiD0255.pr0, 2/15/2008 18:24:18, 8252 bytes | | | Driver: SaiC0255.Dll, 2/15/2008 18:24:18, 1052160 bytes | | | Driver: SaiC0255_07.dll, 2/15/2008 18:24:18, 8192 bytes | | | Driver: SaiC0255_09.dll, 2/15/2008 18:24:18, 7680 bytes | | | Driver: SaiC0255_0A.dll, 2/15/2008 18:24:18, 8192 bytes | | | Driver: SaiC0255_0C.dll, 2/15/2008 18:24:18, 8704 bytes | | | Driver: SaiC0255_10.dll, 2/15/2008 18:24:18, 8192 bytes | | | Driver: SaiC0255_11.dll, 2/15/2008 18:24:18, 5632 bytes | | | Driver: SaiC0255_0402.dll, 2/15/2008 18:24:18, 7168 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + HID Keyboard Device | Matching Device ID: hid_device_system_keyboard | Service: kbdhid | Driver: kbdhid.sys, 7/13/2009 19:00:20, 33280 bytes | Driver: kbdclass.sys, 7/13/2009 20:48:04, 50768 bytes | + Microsoft USB Dual Receiver Wireless Keyboard (IntelliType Pro) | Vendor/Product ID: 0x045E, 0x009D | Matching Device ID: hid\vid_045e&pid_009d&mi_00 | Service: kbdhid | Driver: kbdhid.sys, 7/13/2009 19:00:20, 33280 bytes | Driver: kbdclass.sys, 7/13/2009 20:48:04, 50768 bytes | + Terminal Server Keyboard Driver | Matching Device ID: root\rdp_kbd | Upper Filters: kbdclass | Service: TermDD | Driver: i8042prt.sys, 7/13/2009 18:19:57, 105472 bytes | Driver: kbdclass.sys, 7/13/2009 20:48:04, 50768 bytes | + HID-compliant mouse | Matching Device ID: hid_device_system_mouse | Service: mouhid | Driver: mouhid.sys, 7/13/2009 19:00:20, 31232 bytes | Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes | + HID-compliant mouse | Vendor/Product ID: 0x045E, 0x009D | Matching Device ID: hid_device_system_mouse | Service: mouhid | Driver: mouhid.sys, 7/13/2009 19:00:20, 31232 bytes | Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes | + Logitech HID-compliant Cordless Mouse | Vendor/Product ID: 0x046D, 0xC518 | Matching Device ID: hid\vid_046d&pid_c518&mi_00 | Upper Filters: LMouFilt | Lower Filters: LHidFilt | Service: mouhid | Driver: LHidFilt.Sys, 6/17/2009 11:54:22, 55312 bytes | Driver: LMouFilt.Sys, 6/17/2009 11:54:30, 57872 bytes | Driver: KHALMNPR.Exe, 6/17/2009 11:53:26, 130576 bytes | Driver: mouhid.sys, 7/13/2009 19:00:20, 31232 bytes | Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes | Driver: WdfCoInstaller01005.dll, 6/1/2009 13:49:56, 1918856 bytes | + Terminal Server Mouse Driver | Matching Device ID: root\rdp_mou | Upper Filters: mouclass | Service: TermDD | Driver: termdd.sys, 7/13/2009 20:45:55, 62544 bytes | Driver: sermouse.sys, 7/13/2009 19:00:20, 26624 bytes | Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes

The mouse and keyboard drivers are showing as working properly and drivers are 6.6.6.9. I looked at DXDIAG and noticed that I have DX 11 loaded and the game requires DX 9, but I wouldn't think that to be a problem.

I am using 6.6.6.9 as well and I have reloaded it as well as the 6.2.2.0 drivers several times now. I prefer using SST as I like it a lot. I have cleared the X52 "category" inside the game, but I leave the keyboard commands (obviously) so that I can use the keyboard. I complete my profile and load it. When I start the game, once again I press on the "fire" button in mode 1 (navigation...for me) and I get altitude hold ("h" versus "Rcntrl h")...and my flaps toggle instead on just go down because the modifier is not recognized it seems. This is true of ALL those commands that need a modifier. I have reloaded the game and update twice now with no success. I run the game in "administrator", but I did not install it as "administrator". I am going to try that, but I don't expect much success. I would suspect a software glitch in FC 2, but no one else seems to be reporting this problem. Incidentally, I am running Windows 7, 64 bit on an AMD Dual Core with 4 gigs of ram. Almost forgot....I note that I can get the "fire button" to work (changing the HUD color) IF I manually press the Rcntrl key on the keyboard, so it really makes me think that the problem is in the SST program not sending the instructions completely, but when I check the instruction using the test profile, it shows it as "HControlKey" (with blue repeaters after the H and ControlKey).