Quote:
Originally Posted by serinity
Ok well i figured out the problem. ~.noclip was turned off for somereason. I enabled the console, and d.noclip=0 ; i then fell to the floor and all is good.
If anybody encounters this issue in the future try this to fix it. It worked for me. I dont know why or how d.noclip could have been changed from =0 to =1 because i never messed with the console or any of the "cheats" until this happened. Weird.. but its fixed now  I have to now keep the console enabled, because everytime i load the game i have to retype ~d.noclip=0 and then ~d.fly=0 in that order.
Why are these two important settings permenantly on =1 or set to true by default? How can i change it so i dont have to open the console everytime and type it in?
****Sidenote: Also a few things i noticed when i pressed ~ after enabling the console.
1) It said something about not being able to find script r.anisotropic in init.cfg Does this mean that it actually doesnt work when applied turned on from the graphics settings? |
Same thing happened to me when I enabled the console, can't find script r.anisotropic. Strange ?
But about this init.ini file would it be possible to enter your console settings in it and save the file or would it be best to enter them into the autoexec.cfg file in the main folder. It seems as tho the autoexec.cfg file will load and execute commands appon loading of the game.
Just a thought mind you.