Seems odd that my ~ doesn't work for console commands.

[smikaj]

I decided to play the game again after a few years of not playing, Have Windows 7 Ult., I7 3770k CPU, 3.50ghz, 64 bit, 16mg ram, Geforce GTX 750. Installed a few mods, FOMM. Game plays fine just seems odd that ~ doesn't work to be able to put in any console commands. Any tips be appreciated, don't need it just like to have the option.

[Nextasa]

I have a similar problem however mine is on Windows 8.1

[M48A5]

I decided to play the game again after a few years of not playing, Have Windows 7 Ult., I7 3770k CPU, 3.50ghz, 64 bit, 16mg ram, Geforce GTX 750. Installed a few mods, FOMM. Game plays fine just seems odd that ~ doesn't work to be able to put in any console commands. Any tips be appreciated, don't need it just like to have the option.

Go to your Fallout3.ini located in the Documents/Games folder (the one where your saves are located) and open it. Scroll down to the [interface] section. Locate "bAllowConsole". Make sure it says "bAllowConsole=1". If it says "bAllowConsole=0", change it and save the change. This should allow the use of the console.

Edited January 2, 2015 by M48A5

[smikaj]

Thx for the response Resident poster, but I checked bAllowConsole=1 is there not sure if should try making it =0 then reset to 1 again ?

[Purr4me]

Thx for the response Resident poster, but I checked bAllowConsole=1 is there not sure if should try making it =0 then reset to 1 again ?

 

I decided to play the game again after a few years of not playing, Have Windows 7 Ult., I7 3770k CPU, 3.50ghz, 64 bit, 16mg ram, Geforce GTX 750. Installed a few mods, FOMM. Game plays fine just seems odd that ~ doesn't work to be able to put in any console commands. Any tips be appreciated, don't need it just like to have the option.

To clarify ,what commands and how are they typed out in console mode, give an example of what your doing, seems unlikely there would be a problem if the game runs.

in the init, before game run time =0 means dead stop, do not run, =1 means to run or allow it to run, but...in game, scripting instructing differ on this matter, =1 is full stop and =0 is full go, these are reversed...where init in game is = = 1 while can be thought of as =0, this depends on the instruction. Or run...

 

so not to confuse you too much, there has to be a difference between external commands verses internal commands ...or there would be drastic memory leaks created from the game and the system. it is a software firewall, a game of (0's) and (1's)

 

ini files (=1) Enables functions in game (=0) is disabling functions in game before game starts.

 

While IN Game. (=0) is run / Go and (=1) is full stop, and do not run

(After game starts)

 

xml files are the bridges and can override this, so xml files are volatile, need to be carefully constructed in order to function correctly.

 

this is where most loose it. The grey area.

 

The game works in a paused condition using console commands, this means the menu items are available to you, the inter phase between the two

worlds. UI mods use the commands to override the default codes, instructions between these worlds, ini files do the same but are positive, are concrete, and are not configurable while running. they are static...so once it loads, what ever is set, stay's set.

 

ENB's are static sets, because how it works, these can interfere with internal codes that override external sets. your console commands are internal commands using running code from the game from inside the engine, not from the system.

 

this is a dumb ed down version / explanation of how it all works. networking is another animal that uses these too. But ,the commands you type need to be typed out that fit the engine and not the system. AKA example, Map markers. The command to Enable them in console mode is (~ then you type out [ tmm 1 } and hit enter. exiting the terminal and opening up the pip boy shows all map markers slated for use as found.)

 

To undue it ,the command would be ( Tmm 0) Notice the zero here? it's not -1 but both would work.... one removes all , one responds to code in game. there is so much wiggle room to make mistakes it's laughably ridiculous.

 

=1 is correct, so what are you typing out in console? OR do you have access to console ?

 

just seems odd that ~ doesn't work to be able to put in any console commands

T idle is not working ?

Edited January 5, 2015 by Purr4me

[smikaj]

The ....bAllowConsole=1 is there, I get nothing at all when I hit ( ~ ) I should see a little header on screen where I put in a command as I recall.

[Purr4me]

The more I look at this, the more I am thinking the language thing is at play, the systems kb.sys file that controls the keyboard is incorrect...possible damaged or the software installed is from a CD for a gaming keyboard for a language package not that of English?

 

what language is the game and the hardware?

[Purr4me]

http://s26.postimg.org/4wup7it55/kbsytem.jpg

or:

http://s26.postimg.org/n0xps5qtl/kb_sys.jpg

Edited January 5, 2015 by Purr4me

[M48A5]

The ....bAllowConsole=1 is there, I get nothing at all when I hit ( ~ ) I should see a little header on screen where I put in a command as I recall.

 

If by a header you mean something across the top of the screen, you are looking in the wrong place.

 

When you press the tilde (~) key, your HUD will disappear and an insertion point ( | ) will appear in the lower left corner of your screen. This is where you enter the console commands.

Edited January 5, 2015 by M48A5

[smikaj]

Thanks again, but checked keyboard is set English USA, same with FO3, I never get to type a command tho as the ~ key doesn't do anything. Oh well maybe keyboard is quircked ? Iskind of old but still functions fine as far as I can see.