5punk

Check out the official forum for help, that's what I did and it really helps



Ah no, wait, actually it's just the usual load of internet wank

Well, I did some snooping and found something that helps (obviously not from the official forums)

(copied from somewhere else)

1) Go to the location where Origin installed battlefield. This folder is called: "Beta Battlefield 3" (grave accent on first e). Now this is the problem; the Windows registry system can't cope with the 'e' with the grave accent, so change it to a normal 'e': "Beta Battlefield 3".

2) Next press the Windows key + r on your keyboard and enter "regedit" (without the "), press enter. Now navigate to: HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> EA GAMES. Click on 'Bf3 Beta'. On your right you see a row of information where the 3rd and 4th row are filepaths, and there the annoying 'e' is back! Change the e's with the grave accent to normal 'e' in both filepaths and close the registry editor.

This might help other people that have trouble running it.

Mr. Johnson wrote:Windows key + r

That's my favourite keyboard shortcut!

/nerd

I had to do a restart before the game would work for me, strangely. I'd give that a try if you haven't

That was the first thing I tried. It should be the first thing everyone tries.

Dog Pants wrote:

Mr. Johnson wrote:Windows key + r

That's my favourite keyboard shortcut!

/nerd

You guys know that the Fista/7 Start menu search box works as the run dialog right? and that you can just start typing after hitting the Windows key? No need for the run dialog at all anymore.

Well bollocks. There goes one of life's few pleasures.

Dog Pants wrote:Well bollocks. There goes one of life's few pleasures.

Fill the extra time with a wank

I had a weird little bug earlier today which made the game unplayable for me, and it's a little hard to explain so I made a video of it:

[media]http://www.youtube.com/watch?v=DCHGvPr_w7o[/media]


While I was waiting for it to upload (which was very long) I went looking 'round the internet for a solution and most seemed to hint it had something to do with the 'raw mouse input' setting in the menu, so I played with that but without result; my character kept spacking out.
I was sure I had this bug before though, as I seemed to remember something similar happening in BACON, and my penny/eurocent/50p dropped.
The reason it happened in BACON was because I own one of these, and I have it setup so that there is the joystick to the right and the throttle to the left of my screen. I often had to lean close to my screen to see the distant enemies of THREEF, so I placed my monitor closer to my face whereby I accidentally tapped the throttle (which I always leave in neutral stand) and moved it a bit, causing my dude to flip out. BACON had the same thing because it didn't have proper joystick support. The raw mouse input thing is supposed to cancel it out, but apparently doesn't work.

So long story short, if you have similar problems try disconnecting your other controllers.

Have you updated your video with the explanation?

Dog Pants wrote:Well bollocks. There goes one of life's few pleasures.

Personally I still favour windows key + R.

However using the search thingy and holding down ctrl + shift when you press enter will make the selected program run as admin which is kinda handy

Dog Pants wrote:

Mr. Johnson wrote:Windows key + r

That's my favourite keyboard shortcut!

/nerd

*also fond of ctrl+shift+escape*

Seems a lot of people are getting driver ERRORZ with GTS-era cards.

Apparently the games makers and nVidia are recommending the latest beta drivers for not only Threef, but for Rage as well. Anyone tried them and had any issues?

I've stuck with the Win7 update ones since basically I had Win7 and never had any issues, so am a bit retiscent to go back to the "update drivers for every new game" faff of old.

Agreed. I've got the latest drivers and, whilst its better than with the latest drivers during the beta phase, it still crashes an awful lot. Hope they fix it for the final release...

The Nvidia drivers appear to be in beta too, so yeah.

I've been running the latest Nvidia beta drivers, but then I did just upgrade my card after installing the game so it made sense to grab them.

Performance wise I've had no problems.

FatherJack wrote:...but for Rage as well.

Bums, totally forgot that was out today! I shall download, play nd give initial impressessions asap.

HereComesPete wrote:

FatherJack wrote:...but for Rage as well.

Bums, totally forgot that was out today! I shall download, play nd give initial impressessions asap.

I'd wait Pete. RPS have done an article on it. Apparently it's a royal pita to get working properly (but is a good game).

I'm downloading RAGE now. I've heard some bad things about the bugs, but I can wait if it doesn't work right away. Plus I expect a new graphics card today, gotta test it with something.