Steam Community :: Guide :: Fixing weapon FOV

Store Page

STAR WARS™ Jedi Knight II: Jedi Outcast™

All Discussions Screenshots Broadcasts Videos News Guides Reviews

STAR WARS™ Jedi Knight II: Jedi Outcast™ > Guides > Bluebeak's Guides

81 ratings

Fixing weapon FOV

By Bluebeak

In Jedi Outcast if you run the game in widescreen the player's gun appears closer to the screen. Here's a way to fix it

Award

Created by

Bluebeak
In-Game
DARK SOULS™ II

Category: Modding or Configuration

Languages: English

Posted

Updated

3 Jan, 2017 @ 1:04pm

3 Jan, 2017 @ 1:12pm

6,032	Unique Visitors
92	Current Favorites

Guide Index

Overview

Introduction

Temporary method

Permanent method

Comments

Introduction

In Jedi Outcast and most Quake engine games. If you run the game in a widescreen resolution the player's weapon appears closer to the screen and certain details are cut off. This is especially noticeable with the E11 Blaster Rifle. Here are two comparison screenshots as a reference.

4:3

16:9

Thankfully this is fixable with a console command

Temporary method

The fastest method to doing this fix is to open the console with the ~ key

Then input these commands

helpusobi 1
cg_gunx 3
cg_guny -1

then the game will look something like this

This method is less than ideal because you would need to do this every time you start the game. But it's the fastest way to get it to work.

You can also play around with the offset commands in your spare time. Here are all of them

cg_gunx
cg_guny
cg_gunz

gunx will move the gun model across the X axis which is left/right

guny will move the gun model across the Y axis up and down

gunz will move the gun model towards or away from the player's camera

the default for each is 0. So to restore all of them back to the original position input

cg_gunx 0
cg_guny 0
cg_gunz 0

Permanent method

This is a slightly slower method but you should be familiar with it if you've already modded the widescreen resolution. There are 2 downsides to doing this method.

This command is cheat protected which means you will start the game with cheats on at all times. This isn't necessarily a bad thing but some players will refuse to play the game with cheats enabled.

This does not work in multiplayer because this command is for some reason cheat protected. You will need to start a multiplayer server with cheats enabled to get this to work.

Go to your jk2config.cfg in your base folder. This is commonly located

c:\program files (x86)\steam\steamapps\common\Jedi Outcast\GameData\Base

Now find your jk2config.cfg file. If it's not there, run singleplayer once and change some of the graphical settings and then close the game to generate it.

Open jk2config.cfg in wordpad (or notpad or some other text editing program) and scroll to the bottom. Now input these commands

helpusobi "1"
seta cg_gunx "3"
seta cg_guny "-1"

Save the file. Now the game will always run with these commands and look like this

You can alternatively input cg_gun commands based on your preference by playing around with it in the console. These are just my preferred view commands.

18 Comments

< >

Norman 15 Mar @ 9:29pm

This is honestly the most useful and essential way to make the game look better in 16:9, thanks so much

Kweeb 21 Dec, 2024 @ 5:44pm

https://steamproxy-script.pipiskins.com/sharedfiles/filedetails/?id=3389052298
see

Kweeb 21 Dec, 2024 @ 5:24pm

in 4:3 aspect ratios is
seta cg_gunx "3.00" --backward / forward
seta cg_guny "-2.50" --right / left
seta cg_gunz "0.00" --down / up

mihdolgov 10 Dec, 2024 @ 10:55am

Thanks, worked

Xaviruso 16 Aug, 2024 @ 10:30pm

@Bluebeak they are cheat restricted because they are a cheat.The gun model's location is used to determine where the bullet spawns. You can do absurd stuff like setting gunx 100 and instantly hit targets that are 100 meters away, or change guny and gunz to 4 or 5 to center them and get increased accuracy, or you can even make your weapons be located to the sides with guny -100 or guny 100 allowing you to shoot around corners without peeking. This would be an insane cheat in MP tbh.

For some reason, they tied the spawn point of the bullets to the gun model in FP, rather than having some static point to spawn bullets and allow the gun model to be completely independent.

What makes it clear that this was an oversight that was quickly patched by making the commands cheat restricted is the fact that they are cg_ commands.

Xero399 7 Feb, 2024 @ 9:56am

It's not working for me. After launching the game it modifies the values. I tried to set the file to only read permisions and it don't change the values but doesn't fix the problem. I have to fix it by the console every time I want to play

HYPELORD 1 Dec, 2020 @ 4:48am

Damn I wish this worked for Quake 3 too. I love the gun models in that game as much as this one. Although obviously JK2 is an actual single player masterpiece and I use Q3 single player to just let some steam off on my own against bots.

O'bannon 14 Apr, 2019 @ 5:15am

Great guide, thanks. I had to make my config file read only so the settings wouldn't revert, however.

Nilex 5 Jun, 2018 @ 6:35pm

You mentioned it works for Jedi Academy but not for me. Tried both in-game console and .cfg methods. Outcast: no problem. Are the commands different in JK?
Anyway thank you for the guide, helped with immersion in Outcast.

UPDATE: Nevermind, I literally found a solution after 10 mins in form of a hacked .dll on WSGF [www.wsgf.org]. Only 2 bytes differ from the existing original file in \GameData. Noice!

IanTheStanMan 30 Dec, 2017 @ 5:22pm

Another alternative is to type the command "cg_fov (insert number)". To permanently set it, you would have to type, "seta cg_fov (number here)" without the quotation marks. Personally I got used to 110 and have stayed since. Be cautious about the number however. Too high and it could distort the skybox. I tried that in JK3 multiplayer and that happened...I don't know about JK2 SP. Still, going too high regardless will distort things.

"Pretty trippy..." - Kyle Katarn (my customized quote jokingly..)

< >