What type of controller will you be using for Elite Dangerous

I finally found a shop that had the X-55 on stock in NL.
Call me crazy for spending €190 on a joystick ... I probably am ...
I suppose it should arrive next Tuesday. And if it does I'll join premium beta.
Until then I'll be playing Star Control II.

So did you hear the joke about the store that had a Saitek X-55 Hotas on stock?
... they didn't actually have it in stock.

And the joke is on me, again. This is the 2nd time I've ordered and paid for a Saitek Hotas. I cancelled the previous order because I didn't want to wait for 6+ weeks. But now I'm pretty sure, where ever I'd order it, I'll just have to wait. So I'm not going to cancel my order again.

In the meanwhile, I've gotten my hands on a wireless gaming receiver so I can use my Xbox 360 controller on the PC.
Blasphemy! I know, but that's just going to have to do for now.
 
BTW Xbox game pad, can I ask you to explain step by step how to connect this pad to the game ?
I got reciver, driver is instaled, but... game can't see anything, should I setting up this controler somewhere ?

S.O.S !!!
 
Last edited:
I have a Cyborg Evo Force right now, it works fine with Elite since I 'modded' the spring but I wonder if a true HOTAS system might not be worth an upgrade, unfortunately those things are so quite expensive.

So I am wondering if upgrading just for Elite (well and maybe I'll unearth FS X at some point from my games pile) is worth it, my Evo is quite old and I can't use the throttle since it won't stay in any position but full or none without keeping a hold of it...

What do you guys think?
 
BTW Xbox game pad, can I ask you to explain step by step how to connect this pad to the game ?
I got reciver, driver is instaled, but... game can't see anything, should I setting up this controler somewhere ?

SOS !!!

It took me a few tries to get the receiver to work. The supplied drivers on disk were for XP, and WIN7 refused to run the setup.exe due to a version conflict.
In addition, WIN7 was unable to identify the receiver or find drivers for it.

To check if Windows can see your XBOX controller:
Hit start, type: JOY.CPL and hit enter. A little windows should open, listing all of your connected (and switched on) game controllers. If your XBOX controller is not in this list, you're probably having driver problems like I did.
If your controller IS in this list, your problem is not windows driver related.

How to manually install the driver for the receiver:
Plug the receiver into a USB port.
Hit start, go to the control panel.
Go to the Device Manager.
Under "Microsoft Common Controller For Windows Class" there should be your "XBOX 360 Wireless Receiver for Windows" IF the driver is installed and working correctly.
But I had an unknown device with an alert-icon, of which no driver was installed.
Hit it with the right mouse button, choose "properties".
Click "Update driver..."
Choose to manually search and install a driver.
In the next screen, choose to select a device driver from a list.
Now you should get a shortlist for 4 possible devices. (I did)
Choose the "XBOX 360 Wireless Receiver for Windows".
Ignore the xenophobic warnings windows gives you.
This driver works (for me), even for my non-genuine after market replica wireless receiver.
Now you should be able to connect the controller. Press both the button on the receiver, and the little button on the back of the controller for them to connect to each other.
Hit start again. Type in JOY.CPL again. And now the controller should appear in the list of game controllers.

Hope this helps.
 
It took me a few tries to get the receiver to work. The supplied drivers on disk were for XP, and WIN7 refused to run the setup.exe due to a version conflict.
In addition, WIN7 was unable to identify the receiver or find drivers for it.

To check if Windows can see your XBOX controller:
Hit start, type: JOY.CPL and hit enter. A little windows should open, listing all of your connected (and switched on) game controllers. If your XBOX controller is not in this list, you're probably having driver problems like I did.
If your controller IS in this list, your problem is not windows driver related.

How to manually install the driver for the receiver:
Plug the receiver into a USB port.
Hit start, go to the control panel.
Go to the Device Manager.
Under "Microsoft Common Controller For Windows Class" there should be your "XBOX 360 Wireless Receiver for Windows" IF the driver is installed and working correctly.
But I had an unknown device with an alert-icon, of which no driver was installed.
Hit it with the right mouse button, choose "properties".
Click "Update driver..."
Choose to manually search and install a driver.
In the next screen, choose to select a device driver from a list.
Now you should get a shortlist for 4 possible devices. (I did)
Choose the "XBOX 360 Wireless Receiver for Windows".
Ignore the xenophobic warnings windows gives you.
This driver works (for me), even for my non-genuine after market replica wireless receiver.
Now you should be able to connect the controller. Press both the button on the receiver, and the little button on the back of the controller for them to connect to each other.
Hit start again. Type in JOY.CPL again. And now the controller should appear in the list of game controllers.

Hope this helps.

Thank You Ivo, your help is priceless... :)
 
Thank You Ivo, your help is priceless... :)

I'm happy I was able to help! :smilie:

(I'm still baffled at how difficult MS makes it to use MS hardware on MS windows. It's almost as if they didn't want you to use your xbox controller on another platform. As if they want you to go and buy a whole other controller especially for windows. Oh ... well would you look at that: http://www.microsoft.com/hardware/en-us/p/xbox-360-controller-for-windows
Well ... not today MS!)
 
Tell me about it!, I've been sending emails and letters to Microsoft and Bill gates for the last year now trying, no begging them to pick up support once again for the MS sidewinder force feedback 2. And create new better drivers (win7,8,9>) with a new control panel with all the force feedback test and set up, and button programming back. Instead of the basic pot luck driver you get now with windows 7, with no set up and control. Trying to make them aware of just how many people still have and love the MS sidewinder FFB2.

They listen politely, and then commit my correspondence to the loony bin.
 
Last edited:
I never had any trouble to get x360 wireless controller working under win7. Quick system question for driver and getting it from windows update. Worked like miracle, max two minutes.

And after few tries to go with mouse+keybord I have searched my old Cyborg X (I think it should be identical to Cyborg Fly 5, just it has it's years) and I hope I will be able to configure it comfortably.
 
Since I was not happy with the feel of the X-52 I tried a lot and I use now
a custom setup of old Thrustmaster Hardware modified by myself.

It's based on a F-16 FLCS Stick with F-16 TQS and RCS Rudders.
Since they had all gameport I had to put them apart an rewired them with a Bodnar BU0836A 12-Bit Joystick Controller.
This joystick controller has build in 12-bit (4096 steps) resolution each channel and analog input filtering the FCLS and TQS setup went very smooth. For more stability I put wights into the base.
I replaced the mini stick of the TQS with a anlog stick from an old Thrustmaster gamepad and use this now for the horizontal and lateral thursters.
I'm very happy with that setup now, also I don't want to miss the pedals for yaw control.

But, next I want to try out my Microsoft Forcefeedback 2 with Elite, but I think there ist no force feedback build in right now. If forcefeedback should work in Elite than I have the idea to replace the Microsoft Grip with my F-4 Grip from my old Thrustmaster X-Fighter and use it with a CH-Pro Throttle.

I think until the release I will then have found my setup :)
 
an ancient Nyko airflow, Track IR5, Power grid on I've not decided yet, and and old dell keyboard.

nykoairfloex1.jpg

I have been using the XBox 360 controller, tbh it's been doing the job fine, may be its a bit over responsive when trying to centre the cross hair on the targets. The only thing that I'm missing is having a few buttons that I can program, like launching missiles, 2 buttons for the head look, silent running etc. I was thinking the X52 Pro type stick will put all these switches within easy reach, as I've not had a opportunity to try these out, I'm thinking In practice holding the stick in one hand and the throttle in the other will not be as comfortable as a control pad, which fits naturally in two hands with all buttons easily available.

So I like the idea of a more configurable control pad, may be like the one quoted or the Razor Sabertooth (£69) which has I think 6 more buttons that you can program yourself.

http://gamepad-review.toptenreviews.com/razer-sabertooth-review.html

It does seem expensive for a controller, especially being wired (the only thing that's putting me off) but Razor is highly ranked in gaming.
 
Last edited:
Is that pad useful when you've got a million switches on the hotas and only 2 hands?

Yes, I use it because I just need to move my hand very little to access it. Moreover the Joy-stick on the side is very good to control YAW and UP/DOWN

The zillion buttons on the throttle I haven't mapped yet, still working on the lay out :D rul of cool, never run out of switches/buttons :cool:

1269526549164_hz_myalibaba_web9_289.jpg
 
I have a Logitech G940, which is great (except for the quality control issue with one too short wire in the throttle, that causes it to jitter after a few months - had mine replaced once already), and TrackIR. I'll be using those if I can be *****, but I have to admit that I generally just break out the 360 controller for daily play - it's sooooo much more convenient :).
 
It took me a few tries to get the receiver to work. The supplied drivers on disk were for XP, and WIN7 refused to run the setup.exe due to a version conflict.
In addition, WIN7 was unable to identify the receiver or find drivers for it.

To check if Windows can see your XBOX controller:
Hit start, type: JOY.CPL and hit enter. A little windows should open, listing all of your connected (and switched on) game controllers. If your XBOX controller is not in this list, you're probably having driver problems like I did.
If your controller IS in this list, your problem is not windows driver related.

How to manually install the driver for the receiver:
Plug the receiver into a USB port.
Hit start, go to the control panel.
Go to the Device Manager.
Under "Microsoft Common Controller For Windows Class" there should be your "XBOX 360 Wireless Receiver for Windows" IF the driver is installed and working correctly.
But I had an unknown device with an alert-icon, of which no driver was installed.
Hit it with the right mouse button, choose "properties".
Click "Update driver..."
Choose to manually search and install a driver.
In the next screen, choose to select a device driver from a list.
Now you should get a shortlist for 4 possible devices. (I did)
Choose the "XBOX 360 Wireless Receiver for Windows".
Ignore the xenophobic warnings windows gives you.
This driver works (for me), even for my non-genuine after market replica wireless receiver.
Now you should be able to connect the controller. Press both the button on the receiver, and the little button on the back of the controller for them to connect to each other.
Hit start again. Type in JOY.CPL again. And now the controller should appear in the list of game controllers.

Hope this helps.

Microsoft are, unfortunately, famous for not supporting their own damn hardware. Which is a shame, because I think the Xbox 360 controller is the best game controller ever designed.
 
Back
Top Bottom