cheat console

[marneusCalgar]

i am unable to open my cheat console once i am running the game.

any ideas as to how to fix that???

[Gishank]

Are you sure you're pressing the correct key? (it's the one with ¬ & ' & | on) Does it give an error?

[marneusCalgar]

it's supposed to be the tilde (~ &`) right??

if not that then what key is it and where is it on the keyboard??

[JimboUK]

I found this....

 

 

http://fallout.wikia.com/wiki/Fallout_3_console_commands

 

The key is the top left key under escape, on non-US keyboards. (Example: § or ½ on Scandinavian (Swedish, Danish, Norwegian etc), circumflex (^) on German keyboards, ² on French ones.)

 

It's common for Vista users and some XP users to be unable to access the Console. Following are some possible causes & solutions:

 

 

"Infrared Device" drivers interfere with the "Tilde" (~) key being able to access the Console, so must be disable/uninstalled.

 

Here's a direct quote from Bethesda Softworks Technical Support: "If you have a new system with the Microsoft eHome devices, these will conflict with the program being able to read the scan code for the tilde key from the keyboard. Those Microsoft eHome devices or drivers need to be disabled in order to allow the game to "see" the tilde key being pressed. The MIRC (Microsoft Infrared Remote Control) seems to disable the tilde (~) key in both Oblivion and Morrowind. Simply disconnecting the MIRC from the USB port will fix this issue."

 

To Unistall/ Disable the conflicting device(s), try the following steps:

 

Open up the "Start" menu, go into "Control Panel" > "System and Maintenance" > "Device Manager". Click "Human Interface Devices". If you see "Microsoft eHome Infrared Transceiver", right-click and uninstall it. If not, then locate the driver with the word "Infrared" in it's name elsewhere in the Device Manager and uninstall. Unfortunately, when you turn-off and then restart your pc, it will automatically reinstall the driver. As a result, you'll have to repeat the uninstall procedure whenever you go to play and wish to have access to the Console.

 

-or-

 

[Temp Fix] Control Panel > System > Hardware > Device Manager > Human Interface Devices > uninstall Infrared driver (don't ask me why but this driver interferes).

 

If using a controller, you have to switch back to mouse/keyboard control to get the console, switching to mouse/keyboard control will occasionally crash the game to desktop, so save before you try, just in case. (Tested with 360 controller on Vista 32)[Works also on Vista x64 with xbox 360 controler]

 

It has been reported that the console will not work with some Vista 32 and 64 bit systems with NO fix. Those people can only hope for a mod that solves this (example - the ring of console in Oblivion).

 

For Vista 32 and 64 bit http://www.fallout3nexus.com/downloads/file.php?id=1711 its a mod for the Console and works

 

HOWEVER, try this, before giving up and using the ring of console.

 

This editor has no infrared device drivers, and tried this. It worked.

 

Open regedit (Go into Command Prompt and type in regedit... this will open a new window.)

 

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

 

There should be an entry named OverrideKeyboardSubtype with a type of REG_DWORD and a value of 2. Set the value to 0 and reboot.

 

now, uninstalling the IR drivers in the device manager (if you have them) will work to enable the console to come up.

 

if you don't have any IR drivers, then just doing the reg change should fix it for you.

[edit] Ring of Console fix

 

Follow the steps on the page to help activate the console. The page can be found at here.

 

You must have the original ring of console as well.

 

NOTE: This is only for users who CAN NOT under any circumstance open the console. Please try other solutions before resorting to this option, you might save yourself some time. This mod is in a beta, so use at your own risk.

 

This mod works in the same way as the Ring of Console, and the item is gained after you escape from the vault.

[edit] Console Key Binder fix

 

An easier alternative to the Ring of Console fix would be the Console Key Binder mod, removing the hassle of equipping/unequipping an item. The file can be found here.

 

This mod allows you to bind another key to open the console (default is F4) which is very useful if your tilde key does not work. Take note, however, that this mod requires Fallout Script Extender (FOSE). FOSE can be found here.

[edit] Microsoft eHome remote/receiver

 

If you use the Microsoft eHome remote/receiver (official media centre remote and USB receiver) you'll notice under your device manager you have a new device named Microsoft eHome MCIR 109 Keyboard; this is the cause of the tilde key not working. It also affects your plus, minus, parenthesis, hash, @, and slash keys remapping them to different functions. (some are even Kanji characters)

 

NOTE: Many "ITECIR" (infrared) drivers under the device manager also cause the same issue.

 

Solution is as follows and will not affect the functionality of your Media Centre remote:

 

1. Go into Device Manager -> Keyboards.

 

2. Right-click "Microsoft eHome MCIR 109 Keyboard", choose "Update Driver" ("Update Driver Software" on Vista).

 

3. Choose "Browse my computer for software" (XP users tell it not to install automatically and say you'll specify the location, then when it asks you where you would like it to search for drivers choose the option to choose from a list) then "Let me pick from a list of device drivers on my computer".

 

4. Make sure "show compatible hardware" is checked, then select "HID-compliant device" and click next. Click any remaining "OK" or "Finish" buttons after Windows has installed the driver.

[edit] AutoHotKey Fix

 

AutoHotkey is a free, open-source utility for Windows, used to remap keyboard or mouse buttons. If your "Tilde" (~) key isn't recognized in Fallout 3, one fix is to install AutoHotKey, and in the script used by the program, assign the "~" to another key. For example, to turn "F12" into a "~", use the line:

 

F12::~

 

Now "F12" will be recognized as the command line button.

[marneusCalgar]

thanks for the advice it worked!