F.E.A.R. 1 in 3D Vision
  4 / 4    
Well, it seems the game now works nicely enough. My only real problem left is the in game crosshair which is off center the more I raise the separation level. In another game I had solved this by changing the convergence but it does not seem that F.E.A.R. allows for tweaking it.
Well, it seems the game now works nicely enough. My only real problem left is the in game crosshair which is off center the more I raise the separation level. In another game I had solved this by changing the convergence but it does not seem that F.E.A.R. allows for tweaking it.

#46
Posted 04/30/2017 05:06 AM   
What did you use for a Profile? Or what did you use to edit/create it(NI/nPI/G3DPM), because the in-game Crosshair isn't off-center... You can tweak Convergence in F.E.A.R., it just doesn't/shouldn't affect the in-game Crosshair... the default Profile has the LaserSight enabled, then you just set the in-game Crosshair' Alpha to 0. ...but the more you increase Convergence the less range the LaserSight has, close(er) range becomes 2D.
What did you use for a Profile? Or what did you use to edit/create it(NI/nPI/G3DPM), because the in-game Crosshair isn't off-center...

You can tweak Convergence in F.E.A.R., it just doesn't/shouldn't affect the in-game Crosshair... the default Profile has the LaserSight enabled, then you just set the in-game Crosshair' Alpha to 0.

...but the more you increase Convergence the less range the LaserSight has, close(er) range becomes 2D.
#47
Posted 04/30/2017 12:29 PM   
Hello TsaebetH. Sorry for ny delayed reply but I am away from home. I used nPI to create a profile that is practically a duplicate of the original Nvidia profile. Then when i enabled both the in-game and the 3d vision crosshair at the same time I noticed they do not overlap. Increasing the depth makes it worse. I played with 3D Vision an old game called Deus Ex using a D3d 9 renderer and there I could fix the issue by changing the convergence. I was hoping to do the same but it didn't work for F.E.A.R.
Hello TsaebetH.

Sorry for ny delayed reply but I am away from home.

I used nPI to create a profile that is practically a duplicate of the original Nvidia profile. Then when i enabled both the in-game and the 3d vision crosshair at the same time I noticed they do not overlap. Increasing the depth makes it worse.

I played with 3D Vision an old game called Deus Ex using a D3d 9 renderer and there I could fix the issue by changing the convergence. I was hoping to do the same but it didn't work for F.E.A.R.

#48
Posted 05/02/2017 11:00 AM   
I was able to get InGameLaserSight to work with this unfortunately it's not defined in nPI(unless you're using a custom xml) so you can't just add it to a Profile... you can export the Profile as nip and add the following lines to it and reimport it... [code]<ProfileSetting> <SettingNameInfo /> <SettingID>1885663426</SettingID> <SettingValue>9</SettingValue> </ProfileSetting>[/code] Or just download[s], rename(remove .png)[/s] and import the [s]attached[/s] nip... [url]https://www.dropbox.com/s/wm65tjrp603t2dk/NOFEAR.nip?dl=0[/url] edit:or not... Lol, friggin forum crap... [quote][INFECTED! FILE REMOVED] NOFEAR.nip.png [INFECTED! FILE REMOVED] NOFEAR.nip.jps [INFECTED! FILE REMOVED] NOFEAR.zip.gif[/quote]
I was able to get InGameLaserSight to work with this unfortunately it's not defined in nPI(unless you're using a custom xml) so you can't just add it to a Profile... you can export the Profile as nip and add the following lines to it and reimport it...

<ProfileSetting>
<SettingNameInfo />
<SettingID>1885663426</SettingID>
<SettingValue>9</SettingValue>
</ProfileSetting>

Or just download, rename(remove .png) and import the attached nip...

https://www.dropbox.com/s/wm65tjrp603t2dk/NOFEAR.nip?dl=0

edit:or not... Lol, friggin forum crap...
[INFECTED! FILE REMOVED] NOFEAR.nip.png
[INFECTED! FILE REMOVED] NOFEAR.nip.jps
[INFECTED! FILE REMOVED] NOFEAR.zip.gif
#49
Posted 05/09/2017 04:11 PM   
Wow... It did work. I noticed I can no longer enable the 3D vision crosshair but the ingame crosshair's aim is now fixed. How did you do it? What does that parameter you changed to 9 do? Rather than import your .nip profile, I exported my own and added those five lines up there and then reimported it, like you suggested to do. The Profile Inspector shows (I think) your change at 0x7064F0C2. I think you should submit your fix to Helix so that it can be part of the 3D Fix Manager. I know you do not use it personally but it would be a great contribution. Please let me thank you again for your support! Cheers!
Wow... It did work.

I noticed I can no longer enable the 3D vision crosshair but the ingame crosshair's aim is now fixed.

How did you do it? What does that parameter you changed to 9 do?

Rather than import your .nip profile, I exported my own and added those five lines up there and then reimported it, like you suggested to do. The Profile Inspector shows (I think) your change at 0x7064F0C2.

I think you should submit your fix to Helix so that it can be part of the 3D Fix Manager.

I know you do not use it personally but it would be a great contribution.

Please let me thank you again for your support!

Cheers!

#50
Posted 05/10/2017 06:09 AM   
InGameLaserSight(0x7064F0C2/1885663426) replaces the LaserSight with the in-game one, so when it's enabled toggling off the LaserSight just toggles the in-game one from Stereo to Mono. It's really great when it works but it doesn't really work with a lot of(newer?) games... there's info here: [url]http://wiki.bo3b.net/index.php?title=Driver_Profile_Settings#Laser_Sight_Settings[/url] :about most of the settings/values... as far as how they work in-game that usually takes a bit of trial and error. I wrote a vbs script that injects the missing Stereo SettingNameInfo(s) into the nips but it's more or less useless as far as using them in nPI, it doesn't import them when you import a nip/Profile. It's more for knowing what they are when viewing/editing in notepad++... To actually view them in nPI you want to save DarkStarSword's updated XML to your nPI root directory: [url]https://github.com/DarkStarSword/3d-fixes/blob/master/CustomSettingNames_en-EN.xml[/url] :and rename it to CustomSettingNames.xml, that's good for editing/creating Profiles.
InGameLaserSight(0x7064F0C2/1885663426) replaces the LaserSight with the in-game one, so when it's enabled toggling off the LaserSight just toggles the in-game one from Stereo to Mono.

It's really great when it works but it doesn't really work with a lot of(newer?) games... there's info here:
http://wiki.bo3b.net/index.php?title=Driver_Profile_Settings#Laser_Sight_Settings
:about most of the settings/values... as far as how they work in-game that usually takes a bit of trial and error.

I wrote a vbs script that injects the missing Stereo SettingNameInfo(s) into the nips but it's more or less useless as far as using them in nPI, it doesn't import them when you import a nip/Profile. It's more for knowing what they are when viewing/editing in notepad++...

To actually view them in nPI you want to save DarkStarSword's updated XML to your nPI root directory:
https://github.com/DarkStarSword/3d-fixes/blob/master/CustomSettingNames_en-EN.xml
:and rename it to CustomSettingNames.xml, that's good for editing/creating Profiles.
#51
Posted 05/11/2017 08:33 PM   
Excellent piece of information. I see that at that address the user can choose between different values. You set it to 9 even if 13 says F.E.A.R. Perseus Mandate. Very interesting... Thank you a lot again!
Excellent piece of information.

I see that at that address the user can choose between different values. You set it to 9 even if 13 says F.E.A.R. Perseus Mandate. Very interesting...

Thank you a lot again!

#52
Posted 05/14/2017 04:07 AM   
I have tried to make this work also on the first expansion but with no luck. The executable FEARXP.EXE needs the original file FEAR.EXE or it will complain that the game is not installed. Doing that will of course start the game but not the stereoscopic 3D, no matter whether or not I rename the FEARXP.EXE to something else. Have you by any chance tested the expansions as well, TsaebehT?
I have tried to make this work also on the first expansion but with no luck.

The executable FEARXP.EXE needs the original file FEAR.EXE or it will complain that the game is not installed. Doing that will of course start the game but not the stereoscopic 3D, no matter whether or not I rename the FEARXP.EXE to something else.

Have you by any chance tested the expansions as well, TsaebehT?

#53
Posted 05/23/2017 05:23 AM   
[quote="Salk"]Wow... It did work. I noticed I can no longer enable the 3D vision crosshair but the ingame crosshair's aim is now fixed. How did you do it? What does that parameter you changed to 9 do? Rather than import your .nip profile, I exported my own and added those five lines up there and then reimported it, like you suggested to do. The Profile Inspector shows (I think) your change at 0x7064F0C2. I think you should submit your fix to Helix so that it can be part of the 3D Fix Manager. I know you do not use it personally but it would be a great contribution. Please let me thank you again for your support! Cheers![/quote] Just found this topic here! Really nice find with the ingame Laser sight setting in driver profile. I didn't know about this. I'll add this to the F.E.A.R. profile in 3D Fix Manager. Currently the profile enables Nvidia Laser Sight and suggests that the user disables the ingame crosshair. This is not required any more then. Btw the profile also fixes fps drops with Logitech devices and 3D not activating. The only issues are still the broken sky / water. But this is minor as most of the time you are indoor.
Salk said:Wow... It did work.

I noticed I can no longer enable the 3D vision crosshair but the ingame crosshair's aim is now fixed.

How did you do it? What does that parameter you changed to 9 do?

Rather than import your .nip profile, I exported my own and added those five lines up there and then reimported it, like you suggested to do. The Profile Inspector shows (I think) your change at 0x7064F0C2.

I think you should submit your fix to Helix so that it can be part of the 3D Fix Manager.

I know you do not use it personally but it would be a great contribution.

Please let me thank you again for your support!

Cheers!


Just found this topic here! Really nice find with the ingame Laser sight setting in driver profile. I didn't know about this. I'll add this to the F.E.A.R. profile in 3D Fix Manager. Currently the profile enables Nvidia Laser Sight and suggests that the user disables the ingame crosshair. This is not required any more then. Btw the profile also fixes fps drops with Logitech devices and 3D not activating. The only issues are still the broken sky / water. But this is minor as most of the time you are indoor.

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

#54
Posted 10/15/2018 08:19 AM   
  4 / 4    
Scroll To Top