EA 117 Gaming Community

For some reason I am not able to move anymore. Aside from the mouse look I have no forward/reverse or left/right movement. My "F" keys work and I can hit the K and/or L buttons to bring up the in game chat which the game does recognize all buttons including WASD when used for posting in chat but not for movement. My mouse buttons do not work either. Any ideas?

Played last night with no issues .. today a no go.

Try using a Brass hammer...I hear they don't leave marks.

No statement of "and I can see these are still the assigned keys in my 'Infantry' controls section." If the keys work in chat, but don't move you, the first thing to rule out is that for whatever reason they're not set as the movement control keys any more.

-Trench

Sry Trench... yes they are. That was my fault for assuming that was a given. But given my job and seeing how many times the obvious are looked over by the end user I completely understand. All of my movement keys except for crouch and prone are still default.

Not sure why this would change anything but I logged on directly from BF1942 instead of my link on the desktop I have the target saved to go directly to the server and looked at the settings in there. Well low and behold ... all the of setting were blank in there???? That makes no sense though as my desktop link is just a shortcut tooo ... the DC folder. But the main .exe for DC is run through the BF1942.. .correct??? Oh well. Its better off I just gonna consider it fixed and move on because if I keep trying to figure this out I will just become more confused than I am now LOLOL.

Anyways thanks for your help on that one Trench. And I guess Sarge too ...........

That probably has a BF1942-specific cause, e.g. some way in which the command line is causing a different BF1942 player profile to be defaulted or loaded as opposed to the fully interactive launching of BF1942 where you select the profile manually. I've never played much with the BF1942 player profiles, so I don't know what the issues or "gotchas" there might be launching directly into the game from the command line / shortcut.

The other Windows 6.x-specific reason that comes to mind is the Windows User Account Control (UAC) and the file redirection that will occur when an application wants to write to a protected area, but because the program is not run using "Run as Administrator", it cannot actually write to that area. Check whether you're getting BF1942 configuration files created under "C:\Users\<username>\AppData\Local\VirtualStore". This could make it so that BF1942 launched with "Run as Administrator" sees one set of files, but launched as non-Administrator would see a different set of files, even though both instances otherwise thought they were doing the same thing.

-Trench

I believe "Run As Administrator" sets the option on the executable, so it should include any shortcut that points at it. Doesn't 1942 still write to program files and not the user profile? If so, nothing ever gets saved unless UAC is off or you run it as admin.

Swanny-CG wrote:I believe "Run As Administrator" sets the option on the executable, so it should include any shortcut that points at it. Doesn't 1942 still write to program files and not the user profile? If so, nothing ever gets saved unless UAC is off or you run it as admin.

Agreed, but an option named "Run as Administrator" is available as a per-invocation option, in addition to being a "Compatibility" tab setting. (Choosing to invoke or not invoke using "Run as Administrator" is the scenario in which you could be running the same application but getting two different results, depending on whether you used "Run as Administrator".)

Yes, I agree that setting "Run as Administrator" (or even "Windows XP") in the "Compatibility" tab is setting the Application Compatibility shim settings for the .EXE itself for the specific path the .EXE exists on. Launching that same .EXE at the same path by some other method such as a shortcut should honor whatever "Compatibility" tab settings were made.

32-bit applications not designed for Windows 6.x that try to write to specific secured that normal Users group members cannot write to get redirected to a "sandbox" such that they're not actually writing to the "real" secured directory and therefore cannot actually compromise system integrity. But their attempts to write do get saved; just into the "sandbox" area that only other low-permissioned applications will ever see.

That "sandbox" is what the "C:\Users\<username>\AppData\Local\VirtualStore" area is. Same applies to attempting to write to specific secured registry areas too; instead of just failing and returning ACCESS_DENIED, Windows will redirect attempted writes to specific areas into a [HKEY_CURRENT_USER\Software\Classes\VirtualStore] area instead.

The point of both approaches being that an application not designed for Windows 6.x and which requires write access to protected system areas will "think it's actually succeeding", and for most intents and purposes will operate successfully. But in reality it's not being allowed to compromise system integrity, and it's writes have been redirected to an area only it (and other applications being subjected to the same redirection) will ever see.

-Trench

I know what you're saying, they're like system shortcuts, like the "local settings" folder in the user profile.

The thing is, all my BF controls are saved in the program files (x86) folder where BF is installed. just like they were on XP. I think until I ran as admin my settings never stuck, but maybe that's my faulty memory, as I KNOW PB services didn't work until I ran as admin, which didn't let me play (for long) anyway. Maybe I just didn't notice, and running as admin lets me write wherever I want.

As far as run as admin goes, my experience is this - when you set it on a shortcut, it sets it on the exe. thereafter, no matter how you shortcut to it, the exe runs as admin. Now I have certainly NOT seen everything, and there is definitely a use case possible where that isn't true, I just have never seen it.

Is calling it Windows 6.x some hipster way of saying Windows 7?

Swanny-CG wrote:Is calling it Windows 6.x some hipster way of saying Windows 7?

"Windows 6.x" is just a way of saying "Windows Vista, Server 2008, Windows 7, Server 2008 R2, Windows 8 or Server 2012" all in one breath. The marketing names "Windows Vista" and "Server 2008" are Windows 6.0 to Microsoft, "Windows 7" and "Server 2008 R2" are Windows 6.1, and "Windows 8" and "Server 2012" are Windows 6.2. (http://msdn.microsoft.com/en-us/library ... s.85).aspx)

-Trench

That reminds me. I did get an alert message that said something about a Windows 8 update or something along those lines. To be honest it was one of those bubbles that pop up on the bottom right that I generally ignore so I could not give you the exact message. Anyways why would I get anything about Win 8 when I am running Win 7 and would that have anything to do with my game configuration issue? ... No this PC has not surfed for porn before I get that question/comment.

There aren't any updates from Microsoft's Windows Update on Windows 7 that would have proported to be a "Windows 8" update or offer, so I would just assume whatever was seen was from one of the myriad of other applications installed which might have had a Windows 8-compatible update to their application. Possibly a Windows 8 upgrade offer from your computer vendor (Dell, HP, etc.) if their bloatware is still installed. I'd suspect its unlikely to be related to the BF1942 launch issue.

Just throwing ideas out there: Any chance playing around with Origin's version of Battlefield 1942 1.62 caused a change here?

-Trench

No and the only reason I say that is I do not have the Origin version of 1942 loaded. I do have Origin loaded from when I tried to get BF3 to run on my PC. So unless having Origin itself loaded would allow it to see my disc version of BF1942, I do not think that would be the culprit.