Fallout 4 Console Command Warning

A tweet from late last week from Bethesda's Pete Hines says that Bethesda does not recommend the use of console commands to alter your game state in Fallout 4. He was responding to a question about why console commands (ironically) don't work on consoles, when he warned: "@fortech_mike nope. use of the console is not supported or recommended on PC. that kind of thing isn't permitted on consoles anyway." He later clarified that the warning is because console commands "can very easily mess up save games" in the post-apocalyptic RPG sequel. Thanks HARDOCP.
View : : :
25 Replies. 2 pages. Viewing page 1.
Newer [  1  2  ] Older
25.
 
Re: Fallout 4 Console Command Warning
Nov 25, 2015, 09:37
25.
Re: Fallout 4 Console Command Warning Nov 25, 2015, 09:37
Nov 25, 2015, 09:37
 
Running on a 660Ti 4GB OC'd, a 3-4 year old card. Have had zero issues and runs under full screen no border. When I first started playing, it would sometimes fire up under windowed, but I just went in and changed it.

Have you tried that 3rd party program to change settings before starting the game? Don't have link in front of me - might be in the forum I created.
24.
 
Re: Fallout 4 Console Command Warning
Nov 25, 2015, 02:20
24.
Re: Fallout 4 Console Command Warning Nov 25, 2015, 02:20
Nov 25, 2015, 02:20
 
OpticNerve wrote on Nov 24, 2015, 22:03:
InBlack wrote on Nov 24, 2015, 09:46:
Has anyone figured out how to get the game to work in Fullscreen mode and not Borderless window yet? I can run the game fine in bordeless window, but I feel that (Nvidia GTX970 user here) the game doesn't do Vsync correctly, and I noticed some weird graphical anomalies and some performance issues too.

Dunno if this'll fix things, but if you edit your Fallout4Prefs.ini (with a text editor) in C:\Users\%YourProfileName\Documents\My Games\Fallout4 there are two entries:

bBorderless=1
bFull Screen=1

Both were set to "1" by default for me and setting bBorderless=0 didn't mess up anything in-game so far.


Tried that. And a whole lot of other combinations. Nothing worked other than bFull Screen=0, and BBorderless=1.

This comment was edited on Nov 25, 2015, 02:40.
I have a nifty blue line!
Avatar 46994
23.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 22:03
23.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 22:03
Nov 24, 2015, 22:03
 
InBlack wrote on Nov 24, 2015, 09:46:
Has anyone figured out how to get the game to work in Fullscreen mode and not Borderless window yet? I can run the game fine in bordeless window, but I feel that (Nvidia GTX970 user here) the game doesn't do Vsync correctly, and I noticed some weird graphical anomalies and some performance issues too.

Dunno if this'll fix things, but if you edit your Fallout4Prefs.ini (with a text editor) in C:\Users\%YourProfileName\Documents\My Games\Fallout4 there are two entries:

bBorderless=1
bFull Screen=1

Both were set to "1" by default for me and setting bBorderless=0 didn't mess up anything in-game so far.

Avatar 23638
22.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 16:42
22.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 16:42
Nov 24, 2015, 16:42
 
Dev wrote on Nov 24, 2015, 15:56:
Creston wrote on Nov 24, 2015, 12:57:
You can do hilariously bad things with the console. I tried to 'setscale' an irritating bush, that was messing up an awesome house I was trying to build, to 0 , and instead I apparently clicked, like, "THE WORLD", and setscaled that to 0, and oops.
LOL, what happened?

A fairly large chunk of stuff just went away, leaving me with a funny hole in the world through which I could see... I dunno, more world? It was weird. Then I tried to walk into it, and fell. And fell. And fell. I think my character is still falling.
Avatar 15604
21.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 16:41
21.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 16:41
Nov 24, 2015, 16:41
 
Raven wrote on Nov 24, 2015, 13:26:
I wonder what would happen if you tried 'disble' instead on the bush and hit the world instead. Well, I guess that would easily mess up your save game, if you saved afterwards.

I don't think a bush or the world are "disable" items. You can "markfordelete" them. So yeah, doing that to the world, or the ocean, would be fun the next time you load that zone.
Avatar 15604
20.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 16:30
20.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 16:30
Nov 24, 2015, 16:30
 
Blackhawk wrote on Nov 24, 2015, 12:45:
That's just the usual disclaimer. If you open the case, you void the warranty. If you fiddle with console commands and break a quest or corrupt your save, it isn't ours to fix.

So if I get a corrupted save and don't use command lines, they'll fix it? Their support is that good? I've only known very small developers with small user bases ever really offer anything like that.
Avatar 17232
19.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 16:29
19.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 16:29
Nov 24, 2015, 16:29
 
descender wrote on Nov 24, 2015, 10:49:
use of console is not supported, but we leave it there so you can actually complete our games.

It is silly, they make the stuff, allow modding and then will say don't do it for some reason or another. Everyone loves to sell them the fear.
Avatar 17232
18.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 16:04
Verno
 
18.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 16:04
Nov 24, 2015, 16:04
 Verno
 
NKD wrote on Nov 24, 2015, 15:17:
Console commands are pretty much a requirement to make a decent looking settlement. Gotta tinker with collision and use precision positioning commands etc.

Also pretty essential for advancing quests that have become broken as is usual for Bethesda.

I don't know, I've made some pretty spiffy settlements with the base game and my imagination. The clipping stuff gets annoying but I can usually workaround it. It is weird how much they limited the item pool though. In terms of broken stuff I think this is my first Bethesda game where everything just works. Maybe I've been lucky so far but no crashes, no script trigger problems or etc. It's just been smooth sailing.
Playing: FF7R
Watching: The Last Dance
Avatar 51617
17.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 15:56
Dev
 
17.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 15:56
Nov 24, 2015, 15:56
 Dev
 
Creston wrote on Nov 24, 2015, 12:57:
You can do hilariously bad things with the console. I tried to 'setscale' an irritating bush, that was messing up an awesome house I was trying to build, to 0 , and instead I apparently clicked, like, "THE WORLD", and setscaled that to 0, and oops.
LOL, what happened?
16.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 15:28
16.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 15:28
Nov 24, 2015, 15:28
 
Lost companion, was my only use of a console command so far. This needs a mod, a device to summon unlocked companions or at least send them to settlements to be found.

I like how he says "can easy mess up saved games" Have you even played this game yet dude? Just saving your game as it is can mess up your game.
Avatar 58207
15.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 15:17
NKD
15.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 15:17
Nov 24, 2015, 15:17
NKD
 
Console commands are pretty much a requirement to make a decent looking settlement. Gotta tinker with collision and use precision positioning commands etc.

Also pretty essential for advancing quests that have become broken as is usual for Bethesda.
"Fuck off, bard." -Geralt of Rivia
Avatar 43041
14.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 14:19
14.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 14:19
Nov 24, 2015, 14:19
 
Console commands saved me about.... well, probably about evened me out in the end, ha. Hit the game-breaking bug with the "Confidence Man" quest, and my last safe save was at least an hour behind due to a lot of building and distributing weapons/equipment at several settlements in between. Then it took me about an hour to look up the bug and the possible fixes and try several before getting to one that worked well enough...
13.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 14:02
Kxmode
 
13.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 14:02
Nov 24, 2015, 14:02
 Kxmode
 

To be honest console commands actually make the game MORE fun.
"Hard times create strong men. Strong men create good times. Good times create weak men. And, weak men create hard times." - Those Who Remain by G. Michael Hopf
Avatar 18786
12.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 13:47
12.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 13:47
Nov 24, 2015, 13:47
 
btw, use of the Terminal in OSX is also not supported by Apple
11.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 13:32
11.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 13:32
Nov 24, 2015, 13:32
 
So, we REALLY need a company to tell people this? Did people just start playing PC games yesterday?

And why is this such an issue? People have been using console commands since PC games came out!
10.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 13:27
10.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 13:27
Nov 24, 2015, 13:27
 
It amuses me that so many sites are passing this around as if it's a big shocker... I think the real news here is the implication that some people expected the head of Bethesda PR to say anything different. "Yeah, sure, guys, go ahead and dick around with our dev commands as much as you want, we'd LOVE to help you fix your games that were broken through no fault of our own. That is the most effective way for our support staff to spend their time, after all!"
9.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 13:26
9.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 13:26
Nov 24, 2015, 13:26
 
I wonder what would happen if you tried 'disble' instead on the bush and hit the world instead. Well, I guess that would easily mess up your save game, if you saved afterwards.
8.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 12:57
8.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 12:57
Nov 24, 2015, 12:57
 
You can do hilariously bad things with the console. I tried to 'setscale' an irritating bush, that was messing up an awesome house I was trying to build, to 0 , and instead I apparently clicked, like, "THE WORLD", and setscaled that to 0, and oops.
Avatar 15604
7.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 12:45
JTW
7.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 12:45
Nov 24, 2015, 12:45
JTW
 
That's just the usual disclaimer. If you open the case, you void the warranty. If you fiddle with console commands and break a quest or corrupt your save, it isn't ours to fix.

A more accurate statement would be, "Don't use console commands unless you know what they do and what effect they can have."

Also, make a hard save (and back it up) before altering your character with them.
6.
 
Re: Fallout 4 Console Command Warning
Nov 24, 2015, 11:19
6.
Re: Fallout 4 Console Command Warning Nov 24, 2015, 11:19
Nov 24, 2015, 11:19
 
InBlack wrote on Nov 24, 2015, 09:46:
Has anyone figured out how to get the game to work in Fullscreen mode and not Borderless window yet? I can run the game fine in bordeless window, but I feel that (Nvidia GTX970 user here) the game doesn't do Vsync correctly, and I noticed some weird graphical anomalies and some performance issues too.

I have a GTX970 as well, tied to an Asus G-Sync monitor. I let the GeForce Experience set the settings, everything has been fine on the display front for me.
25 Replies. 2 pages. Viewing page 1.
Newer [  1  2  ] Older