Sven2157

Did you save the file after you opened it in the editor? Try That, if not....

Yeah, whatever is on the site. If you open the Profile Editor, it will tell you what Software version and what driver version for the Stick you have. Mine is SST v7.0.2.7, Stick v6.0.4.1. Remember I have a x52, not a Pro. The only difference is the MFD, and material used for the actual stick. Do you have the pedals too? If so, you need to right click the Stick Icon for the Stick, and the Pedal Icon for the Pedals.

No worries! ;) Here is what it looks like with the Profiler Software running, but no profile loaded: And then when the profile is loaded:

Roger... In the editor, can you see the assignments? If so, click save, then try the "test". You may have to load the profile first, then open the editor and test.

Hey Maachine, The "A-10C Warthog.pr0" file goes into the following directory( this is the default ): "C:\Users\Public\Documents\Saitek SD6 Profiles\" folder. Once the file is there, start the Profiler( "Click Start>>All Programs>>Smart Technology>>Profiler" ). You will see a little joystick icon in the tray, by the clock. Make sure that your slider on the throttle is set to 1/2 way( 50% ) and then right click the icon and select the "A-10C Warthog" profile from the top of the right click menu. Now the Profiler icon will turn green. Move the "=170= A-10C.lua" file to: "C:\Users\<YOUR_NAME_HERE>\Saved Games\DCS\Config\" folder. Start DCS and go to "Options", then the "Controls Tab". Click anywhere in the column for the "Saitek x52 Pro", and then click the "Load Profile". Select the "=170= A-10C.lua" That should be it. If you have the Pro Flight Rudder Pedals, or the Pro Flight Combat Pedals, you will need to right click that icon separately, and choose the "A-10C Warthog.pr0" for it too. When you are finished - and this is important - you will need to right click the icons again and choose "Clear Profile". Then you can close the Profiler. When you want to play again later, all you need to do is start the Profiler and activate the A-10C Warthog profile again. Now, the way that the SST Software works, is that it simulates button presses while the game is going. That is why it is important to set your slider; otherwise the key command combination will "act" like it is being held down. For instance: To preform Coolie Hat Up, you press 'U' on your keyboard. With the profile, if you hold the Pinky Switch and press POV 1 Hat up, it sends the key command( 'U' ) to the game. Hope that helps! Let me know if you need anything else! ;) *** EDIT *** What I should have said here, is that it simulates Keyboard Button presses, either Single or Combinations, period. Whether or not the game is going, is irrelevant. You could program your x52 Pro for Microsoft Word short cuts. When you assign a Key press, or combination to a button on the x52, it is the same as pressing it yourself. Sorry Had to clarify...

You most likely didn't find anything because new pilots usually don't say "threat", they say "bad guys" or "enemy": dcs a-10 find enemy :D In that post, if you go to Crescendo's post( #6 ), he provides a link to a very well written psuedo-guide. Hope that helps! ;)

Alright folks, following up on this issue. Short Answer: Saitek packaged the wrong drivers in the installers. Created my own installer package and they seem to work fine now. Long, Detailed Answer: We literally spent the last couple of days trying to get this thing to work, and I have some good news! I think I have done it! Here is the how: NOTE: Please forgive me, I was not logging any of this, as I didn't think it was going to go this far. Version numbers may be off a bit. Please also note, that this was all done by me over TeamViewer. There are a lot of threads stating that the Saitek Smart Technology Software( for ease of this post, SST ), for the X65F, was functioning undesirably and crashing; this was especially made true if you have the Pro Flight Combat Pedals. If you visit the Saitek Support Downloads site, you can download the X65F Driver v6.8.0.49 and SST SD6 v6.8.0.52. Now my friend also has the Pro Flight Combat Pedals. These have available, Driver v7.0.3.7 and SST SD7 v7.0.10.6. I also, never mentioned( forgot really :music_whistling: ), the fact the the SST was causing BSODs referencing SAIC0B6A.SYS, as the culprit. Now here is where it starts to get really complicated, so bear with me here.... :huh: If you just install the Drivers and SST for either controller, all seems to be well; though I cannot really confirm that completely. However, if you want to use both of them, it really takes a turn for the worst. When you install the drivers for the X65F it installs driver information for the following with it, but provides no functionality: Saitek Magic Keyboard Saitek Magic Hotkey Device Saitek Magic Mouse Since there is no Human Interface Device( HID ) driver installed, it renders the use of the Ministick, to operate as a fully functional, secondary mouse, useless. That is where the SST comes into play. Now, when installing the SST, the software also installs the HID drivers for the X65F, making the Mini-stick on the throttle function as a mouse properly. Next, we installed the Drivers for the Combat Pedals. Immediately upon doing so, the SST SD6 software will not start properly. When viewing the Task Manager Processes, you can see the ProfilerU.exe running, but have no interface to load or create profiles. There is also a second processes that is installed and constantly running: SaiMFD.exe. The functionality of this second process is not quite clear. When you end the ProfilerU.exe process, it seems to have no effect on the SaiMFD.exe. The SaiMFD.exe process also seems to have no bearing on the X65 anyway, as I suspect that it's function is for a MFD - Like the x52/x52 Pro. So we uninstalled everything, again. :cry: :drink: Next we tried installing in reverse order; installing the Pedal Drivers( v7 ) first, and then the Flight Stick( v6 ). No Joy! :unsure: After getting no change, we tried installing just the Drivers for the Stick( v6 ), and the Drivers( v7 ) and Software( SD7 ) for the Pedals. This was better, as the Profiler software started, but would not recognize the Flight Stick. :chair: UGHH! What a :pain:! Which then leads to more :drink: ! Then I had a flash of the install in my mind: "What if those drivers for the Flight Stick were bad?" :detective: So we uninstalled the X65F Drivers( v6 ), but this time we let Windows Update install drivers. :shocking: Now we were on to something, because Windows Update has drivers, from Saitek, version 7.0.0.0! Who would have thunk it!?!? Building off this, we reinstalled the drivers for the Pedals( v7 ). Next we decided to leave the SST SD6 out of the equation. So we installed the SST SD7 from the Combat Pedals download page. However, when installing the SD7, I noticed that the drivers for the... Saitek Magic Keyboard Saitek Magic Hotkey Device Saitek Magic Mouse ...no longer said that. Instead it said, sorry this is not exact, something like: Human Interface Device for Magic Keyboard Human Interface Device for Magic Mouse Human Interface Device for Magic Hotkey Device This still did not work, as the BSODs were still occurring! Which then leads to more :drink: ! After another flash in my mind, I said, "We can't use the SD6 - which provides the correct Magic Drivers, and we can't use the SD7 - which provides the correct software for both devices. :detective: We need the Magic drivers from SD6 and the software from SD7!" :shifty: So I started another install of the SD6. This time just to see where it was unpacking the files( "C:\Windows\Temp\" ), and then stopped the install. I then did the same with the SD7; same place. SD6 folder name: Saitek_X65F_Flight_Controller_SD6_64_Software SD7 folder name: Cyborg_RAT_7_Gaming_Mouse_SD7_64_Software Now, this is where I told my friend, "Hey check this out, I saw it in a cartoon once...", and pulled a typical redneck, "Hold my beer..." - How can you tell when a redneck is about to do something stupid? He says, "Hold my beer..."... You get it... Anyway, back on track. I found inside both of these folders, the following 4 files: saibus.cat saibus.inf saibus.sys saimini.sys Final Push: So, we uninstalled everything again. Leading to MORE :drink:! Then we installed the Windows Drivers by Saitek( from Windows Update ) for the X65( v7.0.0.0 ) , and the Drivers from Saitek for the Combat Rudder Pedals( v7.0.3.7 ). I then copied the 4 SD6 files to the SD7 folder; overwriting the files in the SD7 folder, and ran the installer( setup.exe in the same folder, by Right clicking and choosing "Run as administrator" ). While installing, the SST SD7 this time, it installed the drivers for the Saitek Magic Devices. Further confirmation came, in Windows Device Manager. The Flight Stick and Pedals are all correctly listed in the Devices List: Human Interface Devices HID-compliant consumer control device: Under Properties, General Tab, Location: on Saitek Magic Hotkey Device Saitek Pro Flight Combat Rudder Pedals( HID ) Saitek Pro Flight Combat Rudder Pedals( USB ) Saitek X65F Flight Controller( HID ) Saitek X65F Flight Controller( USB ) [*]Keyboards HID Keyboard Device: Under Properties, General Tab, Location: on Saitek Magic Keyboard [*]Mice and other pointing devices HID-compliant mouse: Under Properties, General Tab, Location: on Saitek Magic Mouse [*]Saitek Magic Bus Root Enumerator Saitek Magic Hotkey Device Saitek Magic Keyboard Saitek Magic Mouse :drink: Last night we were able to fly last night for 3-5 hours without 1 incident! Well... After much :drink: we were a bit :drunk: and our ability to operate an Attack Jet was severely hindered! But the Saitek X65 and Combat Pedals worked like a charm. Over then next couple of days, we will monitor them, and I will report back either way - on the success or failure of my efforts! I have also created a ZIP file of the installer for the SST SD7 Software package for use with the X65F and Pro Flight Combat Pedals x64 ONLY. I have uploaded it to one of my websites( http://170thclan.com ). To install: Ensure that Windows has installed the driver for the X65( v7.0.0.0 ) - if not remove the drivers via the Device Manager, and run Windows Update. Download the Pro Flight Combat Rudder Pedals Drivers from Saitek Install the Drivers for the Combat Pedals Download an unzip the package: Saitek_SST_SD7_X65F_COMBAT_PEDALS_x64.zip( 59.1MB ) Right click the setup.exe and choose "Run as administrator". While the Drivers for the Saitek Magic Bus are being installed, make sure that they say Saitek! Confirm in the Device Manager, that you have the same as posted above. You may have more, LEAVE those, as they are for other peripherals on your computer! Kill things! Hope this helps the would be Google'er or Fellow Pilots who spent A LOT of hard earned money on such poor product support!

Cool... We''ll wait and see how it goes. Another issue that was causing crashing( again on my friend's computer with the x65 ), was that he had downloaded my "training" mission and stored it in his DCS Saved Games folder. When he would try to join the MP session, he would get in for roughly 1-4 minutes, and it would CTD him. One thing that I think helped, that we did, was to create a fresh DCS Folder and .LUA file for Keyboard/Joystick. He had bought the Steam version and was was using his DCS Folder from that install. I believe that the config files in this folder were not playing nice with the new ones. Ultimately we figured out that it was were he was storing that training mission; we moved it and his MP CTD stopped. His x65 is another story though, that I believe we may have fixed; globally even, as there are many threads about the same issues. I have a thread called Saitek X65F/SST Software Issues for that though. Keep us posted...

You are right! Just nothing... So that is what will be given... Good Luck gents, figure it out yourself! Guys like Lange_666 can help you - though he hasn't posted any helpful suggestion.... I all I wanted to know was what system hardware you have, OS you are using, what you tried already, etc, etc... I guess that is too much to ask... We, the people, trying to help, are just too conceited and should pry out the needed information. I am out.

Well Turtle, I thought I would share my 25+ years in experience with computer software and hardware. So I guess that means that I have to beg for the information that I would need to determine a possible cause or solution? I love wasting my time with people that are too lazy to include relevant information and then be met by the attitudes that I should be privileged to have met said attitude. Would love to help you, but you said that already.... :disgust: How about something I could use? Who the F%^k knows? You haven't given us ANY useful information( ppssstt!! Look at my signature for starters... )! :doh: Sorry, I hate to sound like a dick. :noexpression:

Hey guys, thanks for the replies! I was really hoping that this wasn't THIS isolated, and that there were others. Found this thread - Saitek SST Problem on Win 7 64 bit - and have completely removed Saitek anything from his computer. Unfortunately, he had to work tonight( Restaurant Server ), so we agreed to resume tomorrow morning. I will post back in the morning/afternoon if we have any luck.

I have a friend having the same issue. This is BSOD, right, not CTD? We have narrowed it down to his Saitek x65F; either drivers or actual hardware. I have seen the x52 Pro reported to function this way as well.

So my friend spent $300+ on this stupid thing; I hate it! Works great in FSX, as no drivers or software is needed from Saitek. However, when he tries to fly in DCS World with A-10 Module, random buttons on both the stick and throttle, will just stop working. If he clears the profile, it as though the buttons are still being pressed. If he closes the Saitek Profiler, same thing: like the buttons are stuck on. I have never seen this behavior before, and have been scouring the internet for days now looking for either the answer, or someone else that has this issue. When I tried to search for the Saitek Forums( using keyword FORUMS ), via the Saitek website I get :huh: : This looks promising! :doh: The other issue I have, is that the Driver for the x65 is a 6 series. The software is a 6 series version as well. If we install the SST Software SD6, it will not work on his computer( installs fine, but won't run ). BUT, the SD7 SST Software works. I guees what I am getting at here is: Has ANYONE even heard of this before? Know where we can get working drivers and software? We have tried all the BETA drivers and software from New X65F Beta drivers; no joy. Any input would be greatly appreciated.

Subi, In addition to what SkateZilla and Wolf Rider have said, did you install DCS with full Administrator privileges? Could be caused by a bad sector of the hard disk - as stated, but also because the file doesn't have permission to operate from its installed directory. In this case, a System Folder: Program Files. When you try to start the game, try right clicking it and choosing "Run as administrator" Just as a side note. Whenever you install something that is going into the System Directories on Windows Vista/7/8, you should always right click the installer and choose "Run as administrator" - ONLY if you trust the installer! You should also run the program this way as well. You can automatically set the program's icon to do this for you, but right clicking the icon. Choose Properties, and then on the Shortcut tab, select the Advanced button. In the new window put a tick in the "Run as administrator" box, apply and close.

As far as I understand it. No. DCS World IS the program, and the DCS Combined Arms Module "unlocks" the ability to enter certain vehicles as a simulated "driver". Just install DCS World( be sure to right click and choose "Run as administrator" on Windows Vista/7/8 ), when the Microsoft Visual C++ 2010 thing pops up, ignore it with the cancel button, OR, just un-tick the box at the beginning of the install, for install additional: "Microsoft Visual C++ 2010". You already have it installed! No need to worry about it, or uninstall, reinstall, etc, etc...

So.. no link to support your claim? :huh: See, I see it as the installer is preventing the user from shooting themselves in the foot; by installing an older version, when they have a newer, better version already installed. Thus working as expected. How long have you been programming computer software? I started in the 5th grade back in 1985, with a PC World magazine and good ole DOS! Anyway, let's not further take away from the OP's issue, while we obviously can't agree that this one way or the other. I accept that you will reply to this, but I am going to stick to the topic from here on out.

First of all, I wasn't trying to upset you; which I believe I have. Bugs - The installer is performing as expected. It sees the newer version and halts the setup; as it should. It then informs the user that if they want to install the version they are trying to install, they need to uninstall the newer version first. This, again, is not a bug - mis-worded perhaps. It would be a bug if the versions were the same, or there was an older version already installed, and the installer still prompt the user. The only results I find searching with Google, are that from the MSDN Social Forums; public forums just like these. There is no "Official" word from Microsoft about this( that I have found ). Do you have the link for the confirmation from Microsoft? This MS VC Installer is also NOT blocking programs from being installed; this is a separate and completely isolated batch of runtime libraries for Visual C++.

Just click cancel. DO NOT UNINSTALL IT! The MS VC Installer is detecting a newer version than the one you are trying to install. Just click cancel, and move on. Most likely, you installed it some time ago, and already have MS VC 2010 SP1. There is no bug! It checks versions, and saw the newer one already on the machine. It is saying, if you want to install the older version( the one currently trying to install ), you must first uninstall the one that is already installed( the newer version ). *** EDIT *** Try this suggestion: MS VC Install. BE SURE TO FOLLOW AS DESCRIBED!

A great simulator will cause schizophrenia! "( 25:25 )...Who wrote this!? - Me - Shut up!..." :megalol:

What version of DCS A-10? Steam's v1.1.1.1? If so, see this thread: Steam/DCS World Or is this a DCS World Module? When you say you un/re-installed C++, did you install just the 64 bit version( x64 - NOT IA64! ), and which VC++ version? 2005? 2008? All 2005 - 2010? Did you get the Service Packs as well? When is crashes is this in Single Player( SP )? Or Multiplayer( MP )? Or Both? Try the following: Download the following files, and install/repair them in this order!( it takes longer to type this post, then to download and install/repair all of these! ): ***NOTE: If the installer gives you the option, to ONLY Repair or Remove - choose REPAIR. When installing/repairing 2010, you may receive a message about versions, and to uninstall the newer version, just click cancel and move on to the next installer in the list. Microsoft Visual C++ 2005 Redistributable Package (x86) Microsoft Visual C++ 2005 Redistributable Package (x64) Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) Microsoft Visual C++ 2008 Redistributable Package (x86) Microsoft Visual C++ 2008 Redistributable Package (x64) Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) Microsoft Visual C++ 2010 Redistributable Package (x86) Microsoft Visual C++ 2010 Redistributable Package (x64) Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) DirectX End-User Runtime Web Installer [*]Reboot/Restart your PC [*]Update your Video Card Drivers( check either nVidia or ATI/AMD [*]Reboot/Restart your PC [*]Report Back on progress. Good Luck, and the whole C++ thing is very quick, just make sure you do them in order! ;)

Are you asking for help? I ask because you have provided no useful information, and just a brief on what you are experiencing; makes any help near impossible. :music_whistling:

Well I believe that I found the answer... Cinch those seat straps down tight, because you are not going to believe me... ..So I found proof. I looked on the net, and found an actual A-10 Flight Manual. On page 380, it shows the left console of the aircraft, sections them out, and gives explanations for each section. As far as I can tell... That is a Poop-Chute Handle! :lol: No Joke! It is for the Piddle Pak Storage. If someone else could review the manual and see if they could find different, that would be great! :megalol:

Congrats! :beer: Glad you got it figured out...

Hey Maachine, if you set your "Page" rotary on the AAP( Avionics Auxiliary Panel ) to "Steer". This will display bearing, distance, wind, IAS WP information, and a slew of others, on the MFD( Multi-Function Display ) that has CDU selected as the active page: default is the Right MFcD. Is that what you are talking about? Or are you asking about the true runway heading in the CDU? If that is the case, then you have to use, as Rongor has pointed out, the charts located in your DCS folder( "C:\Program Files\Eagle Dynamics\DCS World\Doc\Charts" ), or the ME to see the ILS Fan Tails; at the end you will see the true runway heading.

Isn't it a manual Canopy release?