Blooze

I fly MP missions every day and have no issues with the accuracy of SPIs. You hook the SPI first in the TAD then slave your TGP to it.

If you wear your gear while doing your manly duties she will get used to seeing you that way. (illustration included)

Great idea. I just added a lounge to my TS server.

Here's a new Avatar if you like.

I usually log on to my TS server at 8PM CST as well to see if anyone else is there so just do the same if you like.

Ogreman, your commentary truly sums up every aspect of this subject in a way that should leave no remaining questions concerning the benefits of Teamspeak or other alternative voice programs used within a multiplayer environment. IMO this would benefit the multiplayer community by becoming a sticky thread in the multiplayer category. Thanks for taking the time to offer this valuable post. :notworthy:

Do a google search using this phrase "Windows cannot load the drivers required for this device. (Code 31)" and you will see some options that may be helpful.

When I looked at Saitek's drivers downloads I don't even see the X52 (non pro) listed any more. I wonder if they no longer support that stick with updated drivers for Windows 8. Wish I could be of more help.

I host MP missions every day so click my sig and try it out sometime.

Well this is a sad state of affairs indeed. About a year ago I was a struggling noob looking for some friendly folks to fly MP missions with and show me the ropes. I will always be grateful to the Firehouse crew for providing just that and will always have fond memories from those early days. The MP community owes a debt to Eno for carrying the torch of enthusiasm throughout some very trying times brought about by the consequences of an evolving platform and I am hoping that this move is just a hiatus.:bye_3:

Go into your DCS audio options and turn down the WORLD slider. That should help.

:unsure:

Way too much information.:puke:

Who knows what danger may already be lurking somewhere in the remote terrain of the Nevada deserts?:unsure:

I'm glad you could join us and feel free to jump in any time.

Click HERE for something that may be of help.

try deleting the keyboard folder in the saved games config folder and let it build a new one.

If it were me I would start over by deleting everything Saitek that you can find including the joystick folder in the saved games folder. Download the latest drivers being careful to select the right ones for your system. Plug in the stick to a usb2 connection only when prompted and see what happens. Then download and install the SST software.

Thanks again sir!:notworthy:

Do you plan on offering an updated version of WTS A-10 only soon?

Not sure what modules you fly but click my sig for something that may be of interest. I am retired and do this every day.

:music_whistling:

I will be curious to know if this is indeed a bug that came with 1.2.7 that may have had an impact on other missions or just an issue with this mission. Hopefully an answer to this question can be found in the final analysis. So often I have asked myself the question, did I fail a mission because the mission is broke or because I lacked the skills to be successful? I wonder if ED realizes that the number of faithful DCS enthusiasts is dwindling and that many like myself are hanging on by a thread only due to their enjoyment of the MP aspect alone. This kind of issue may be trivial to many that dabble in SP only, but HUGE to folks like me.

I have had success coming in low with a 65D and hitting the radar unit first. That disables the launchers. It's a truly engaging and challenging mission without all the fancy stuff that so many are trying to incorporate in their missions and IMO should be used as a guide for mission designers. I added a couple KA-50 slots for the chopper freaks and a good time was had by all.

I think that what some of you fail to realize is that by getting involved you will be enhancing the experience of others. I always feel privileged to have the opportunity to speak to someone from another country.