Stonedog

Hey, so if I use WASD then my keyboard is way over to the right? Not sure it's the most ergonomic of solutions

Swap your mouse to your other hand and play a game.

The issue is that it hasn't been fixed. 1. It was a careless oversight. 2. *months* later, with full understanding of the impact it has on a group of players, EA have not fixed it.

This is one of the possible workarounds. But as soon as the game files need verified, my fix gets deleted. And why should I have to edit game files or download 3rd party software to access this game? I'm left handed. 10-15% of people are in the same boat.

I mean, not sure what a lefty keyboard would look like. The issue is more that somebody didn't imagine a situation where somebody wouldn't be able to use WASD.... yet when it was brought to their attention, they did nothing about it.

It is *absolutely* discrimination if, after learning about the issue, which has a fundamental impact on the ability of some players to interact with the game, they do nothing about it. Assuming you are right handed here, have you tried playing a game as a lefty? I don't think you get to say what is and isn't discrimination based on your perception of its severity. Why should I have to edit game files or download 3rd party software to access a game?

I held off installing Jedi Survivor until now because of the abysmal state of the game at launch. However I gave it a go last night, and crashed face first into an issue that makes the game *unplayable*. I am left handed. I've had to rebind the keys on every 1st and 3rd person game I've played in the last 25 years. I use the mouse with my left hand, and the cursor keys to control movement. In Jedi Survivor these keys are locked for use by the UI. I rage Googled, and discovered dozens of comments on the Steam and EA forums from left handers, people with disabilities, and even right handers who just don't want to use WASD. Solutions included editing game files, downloading autohotkey etc. But the core issue is that this has been ongoing since April. And it's not fixed.

Thanks for the reply. I tried reseating the gpu and memory. I tried the gpu in another similar machine (no luck) then tried a different gpu (no luck) and both gpus in an older version of the same machine. Both worked.

Hi, yeah the card is powered through the slot. The Firepro v3900 takes 50watts. The PSU has (relative to this) plenty of headroom.

Hi all, I have an HP Elitedesk 800 G5 SFF (9th gen Intel) at work. I have three monitors, two on DP and one on VGA. I want to add a 4th monitor, but I've run out of ports, so I figured I would add this old AMD Firepro v3900 GPU I have to give me an extra display port. The GPU works just fine on our older HP desktops, but the second I plug it into the new machine, I get three long beeps and three short when I hit the power button. I tried both PCIe slots, no joy. All I want is an extra display port... help?

Hi there. I have literally no idea why this might be, but I cannot get the microphone output in this headset above 4 or 5% when I am speaking at a volume that can be clearly heard across the room. For comparison, I got a hold of my wife's work from home Plantronics headset, and it's mic output is a comfortable 60-70% at the same distance and speaking volume. I am trying to use the headset for voice attack, and I have to shout for it to pick anything up. I have been into the volume mixer and made sure the microphone was at 100%, I downloaded iCUE (Corsair's software) and made sure the volume was at 100% in that too.

So I have a 'vintage' Thinkpad that I got through my university. It came preloaded with Vista, and has been running 7 for years. I just cloned the HDD onto an SSD and updated it to Windows 10. But now I can see a partition on my SSD which is labelled the E: drive. Most of the stuff on it hasn't been modified since 2006 or 7... however, in spite of Windows being on C : ... the boot folder is on E: along with the BCD file, which was modified today. I would really like to delete this partition, but I don't want to break Windows. Help?

Ok. Update. The SSD wasn't it. I reinstalled windows on a completely virgin SSD straight out of the box with nothing else plugged in and it still gave me the error. So I pulled the GTX 760 and stuck the old 400 series back in annnnmdddd... Windows works.

Well... here goes!