Need for Speed 2016 - 3D Vision
  4 / 5    
Sorry SnickerSnack, but I'm out of ideas, because I did the same steps :(
Sorry SnickerSnack, but I'm out of ideas, because I did the same steps :(

CPU: Intel Core i7 7700K
Motherboard: ASUS ROG Maximus IX Hero
RAM: G.Skill Trident Z 16GB 3866MHz
GPU: ASUS GTX 980 Ti STRIX
Monitor: ASUS VG248QE
Headset: G930 7.1 Wireless

#46
Posted 12/08/2016 07:06 AM   
@SnickerSnack. You need to follow the instructions exactly. Why did you use NVInspector to export/import your profile? :) The custom profile has to be created by using the app "Geforce 3D settings profile manager".
@SnickerSnack. You need to follow the instructions exactly. Why did you use NVInspector to export/import your profile? :) The custom profile has to be created by using the app "Geforce 3D settings profile manager".

#47
Posted 12/10/2016 06:30 PM   
No WarLordY, you misunderstood. The only thing I did in NV Inspector was redirect the .exe to use the Batllefront profile, which was modified using the Geforce 3D settings profile manager per your instructions. I copied and pasted your instructions below from a previous post: 1. Install Need for Speed. 2. Extract the Star Wars Battlefront 3D Vision fix into your NFS folder. 3. Swap the "Star Wars: Battlefront (2015)" profile with the profile created by Helifax (app: GeForce 3D settings profile manager) 4. [i][b][u]Add NFS16.exe to the "Stars: Wars Battlefront (2015)" profile (app: NV Inspector).[/u][/b][/i] 5. Start Need for Speed, start a race, adjust the 3D convergence and you will love the game ;-)
No WarLordY, you misunderstood.

The only thing I did in NV Inspector was redirect the .exe to use the Batllefront profile, which was modified using the Geforce 3D settings profile manager per your instructions. I copied and pasted your instructions below from a previous post:

1. Install Need for Speed.
2. Extract the Star Wars Battlefront 3D Vision fix into your NFS folder.
3. Swap the "Star Wars: Battlefront (2015)" profile with the profile created by Helifax (app: GeForce 3D settings profile manager)
4. Add NFS16.exe to the "Stars: Wars Battlefront (2015)" profile (app: NV Inspector).
5. Start Need for Speed, start a race, adjust the 3D convergence and you will love the game ;-)

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#48
Posted 12/12/2016 03:43 PM   
There was probably a problem during your import using GeForce profile Manager. If a import completely fails, it will say import unsuccessful. But often times it will seem successful, but it's not. If the altered/reconfigured profile that you are trying to import contains an exe that is associated somewhere differently in the profile list that you are trying to over write, it will not be imported. Or if it's located in another portion of the list that you are trying to import. So prior to importing, make sure that you disable the profile associated with the exe, if you are putting the exe in a different profile. Also make sure that the exe that you are trying to reassign "by doing an import", isn't showing up elsewhere in the list that you are importing. If a game does not have a profile, a default profile is generated as soon as you hit "ctrl+alt+ins" to hide the overlay. This would need to be unassigned prior to an import as well. If you are simply importing new settings to an existing profile, it will over write them and is pretty straight forward. It's only problematic when moving the exe around. At least that has been my observations when messing with profile imports awhile back. Keep in mind that each time that you import a new list, Nvidia Inspector will need to be closed and re-opened to see the changes. If you are having too much trouble, just import the single profile. Then use Nvidia Inspector to confirm that you now only have one profile showing in the list and that it's correctly assigned to the exe. Importing the full profile list back at anytime for other games is simple. So try this if, my wall of text is too confusing :)
There was probably a problem during your import using GeForce profile Manager. If a import completely fails, it will say import unsuccessful. But often times it will seem successful, but it's not.

If the altered/reconfigured profile that you are trying to import contains an exe that is associated somewhere differently in the profile list that you are trying to over write, it will not be imported. Or if it's located in another portion of the list that you are trying to import.

So prior to importing, make sure that you disable the profile associated with the exe, if you are putting the exe in a different profile.

Also make sure that the exe that you are trying to reassign "by doing an import", isn't showing up elsewhere in the list that you are importing.

If a game does not have a profile, a default profile is generated as soon as you hit "ctrl+alt+ins" to hide the overlay. This would need to be unassigned prior to an import as well.

If you are simply importing new settings to an existing profile, it will over write them and is pretty straight forward.

It's only problematic when moving the exe around. At least that has been my observations when messing with profile imports awhile back.

Keep in mind that each time that you import a new list, Nvidia Inspector will need to be closed and re-opened to see the changes.

If you are having too much trouble, just import the single profile. Then use Nvidia Inspector to confirm that you now only have one profile showing in the list and that it's correctly assigned to the exe.

Importing the full profile list back at anytime for other games is simple. So try this if, my wall of text is too confusing :)

#49
Posted 12/12/2016 05:21 PM   
Thanks for the suggestions D-Man11. I'll try soon as I have the time and report back.
Thanks for the suggestions D-Man11. I'll try soon as I have the time and report back.

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#50
Posted 12/13/2016 01:25 PM   
Another thing that you can do to confirm that the profile is importing properly, is to change the name of the profile completely or just add a letter or two. Neeed for Speeed
Another thing that you can do to confirm that the profile is importing properly, is to change the name of the profile completely or just add a letter or two.

Neeed for Speeed

#51
Posted 12/13/2016 01:47 PM   
Well, I just don't get it. I've spent another hour on this and it's not working. I have gone back through all of the steps and added in the words of caution from D-Man11, but my main problem at this point is I can't get the stupid profile manager to import the .txt file back in once I edit it. I get an error every time. I only managed to get it to work one time, and the 3D was still buggered in NFS, so.... I'm giving up for now. But for kicks and giggles, does anyone know why I can't get the profile manager to import the text file?
Well, I just don't get it. I've spent another hour on this and it's not working. I have gone back through all of the steps and added in the words of caution from D-Man11, but my main problem at this point is I can't get the stupid profile manager to import the .txt file back in once I edit it. I get an error every time. I only managed to get it to work one time, and the 3D was still buggered in NFS, so.... I'm giving up for now.

But for kicks and giggles, does anyone know why I can't get the profile manager to import the text file?

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#52
Posted 12/15/2016 04:24 AM   
A profile import can also fail and will state that it's unsuccessful if the export was corrupted due to nvdrssel.bin not being deleted first prior to exporting. Refer to the compatibility mode sticky by helifax for details.
A profile import can also fail and will state that it's unsuccessful if the export was corrupted due to nvdrssel.bin not being deleted first prior to exporting. Refer to the compatibility mode sticky by helifax for details.

#53
Posted 12/15/2016 04:42 AM   
Thanks D-Man11, I did that though. The sticky says to delete it before you export and also before you import. Interestingly, I noticed that if I run the Profile Manager as administrator (Windows 10) the nvdrssel.bin file is created even when I open the profile manager... like, I don't even have to do anything in it, it just creates it when the program is opened. I have also tried opening the program normally, but it hasn't been working either way. I know very little about this sort of thing, but here's a question I'm trying to wrap my head around: Why are all of the steps above necessary? The whole 'switcheroo with Star Wars Battlefront, changing the .exe, etc..? Because the whole premise of this 'fix' is that the games use the same engine, right? So why is it I need to fool my driver into thinking that NFS is actually Battlefront? Why is it not possible to replace the Need for Speed profile with the fixed Star Wars Battlefront profile without changing anything with the .exe? (This is provided I can actually get the profile manager to work, which right now seems like a tall proposition).
Thanks D-Man11, I did that though. The sticky says to delete it before you export and also before you import. Interestingly, I noticed that if I run the Profile Manager as administrator (Windows 10) the nvdrssel.bin file is created even when I open the profile manager... like, I don't even have to do anything in it, it just creates it when the program is opened.

I have also tried opening the program normally, but it hasn't been working either way.

I know very little about this sort of thing, but here's a question I'm trying to wrap my head around: Why are all of the steps above necessary? The whole 'switcheroo with Star Wars Battlefront, changing the .exe, etc..?

Because the whole premise of this 'fix' is that the games use the same engine, right? So why is it I need to fool my driver into thinking that NFS is actually Battlefront?
Why is it not possible to replace the Need for Speed profile with the fixed Star Wars Battlefront profile without changing anything with the .exe? (This is provided I can actually get the profile manager to work, which right now seems like a tall proposition).

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#54
Posted 12/15/2016 01:28 PM   
As soon as you export a profile, import it. If it imports successfully prior to being manipulated, the export was a success. If you can not import your fresh export, it's getting corrupted. Are you messing up like others have and deleting a similar named file in Program Files vs the appropriate file Program Data? Do you have GeForce Experience installed? I do not have this game and can not comment on the fix being used.
As soon as you export a profile, import it. If it imports successfully prior to being manipulated, the export was a success. If you can not import your fresh export, it's getting corrupted.

Are you messing up like others have and deleting a similar named file in Program Files vs the appropriate file Program Data?

Do you have GeForce Experience installed? I do not have this game and can not comment on the fix being used.

#55
Posted 12/15/2016 02:50 PM   
SnickerSnack@ Do you have NVidia Inspector running at the same time ?? I have experienced an import error a couple of times, when NVI was running in the background !
SnickerSnack@ Do you have NVidia Inspector running at the same time ??

I have experienced an import error a couple of times, when NVI was running in the background !

Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Aurus 1080 TI 2.08 GHZ - 100% Watercooled !
Monitor: Asus PG278QR
And lots of ram and HD's ;)

#56
Posted 12/15/2016 03:58 PM   
To the above questions: No, I'm not making a mistake by deleting the wrong nvdrssel.bin file. In fact, there is no other one that I have found. I'm in the Program Data folder which is hidden by default. I HAVE had NV Inspector running simultaneously, but not every time that it has failed. In fact, most of the time I have NOT had it running, but here's a thought.... Is there something regarding NV Inspector still running in the background that I would need to eliminate via Task Manager? I can try some more troubleshooting this evening. Thanks for the suggestions guys. I really appreciate your trying to come up with solutions for me.. I realize you don't have to do that and I appreciate it.
To the above questions: No, I'm not making a mistake by deleting the wrong nvdrssel.bin file. In fact, there is no other one that I have found. I'm in the Program Data folder which is hidden by default.

I HAVE had NV Inspector running simultaneously, but not every time that it has failed. In fact, most of the time I have NOT had it running, but here's a thought.... Is there something regarding NV Inspector still running in the background that I would need to eliminate via Task Manager? I can try some more troubleshooting this evening.

Thanks for the suggestions guys. I really appreciate your trying to come up with solutions for me.. I realize you don't have to do that and I appreciate it.

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#57
Posted 12/15/2016 09:53 PM   
Okay, so I've tried again... This is so weird... The fix seems to be working when the game is first started up. When I reach the main menu (the one with all of the live tiles where you can choose "Play," "Settings" etc.) everything looks great - UNTIL - I move to select one of the options. If I move the selection to "settings" or anything else, the fix suddenly appears to be broken and the tiles and text are suddenly distorted. What in the world?
Okay, so I've tried again... This is so weird... The fix seems to be working when the game is first started up. When I reach the main menu (the one with all of the live tiles where you can choose "Play," "Settings" etc.) everything looks great - UNTIL - I move to select one of the options. If I move the selection to "settings" or anything else, the fix suddenly appears to be broken and the tiles and text are suddenly distorted.

What in the world?

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#58
Posted 12/17/2016 05:47 PM   
There are two patches for Battlefront, the v1.2 is not great for fake 3D (extended letters like SnickerSnack pictures), the other one is good though. Real 3D is bugged, wrong light and wheels 3D position are messed up like SnickerSnack picture (Very annoying in the garage), not playable for me. I've swapped BattleFront 2015 profil, adress the NFS16.exe and NFS16_trial.exe to the BF2015 profil, patch with the BF2015 Fix. (I've try both of them). Also disable Origin In Game, disable the SLI, match desktop resolution and game, disable AA and Vsync in Nvidia control panel, same problems. I use the 10H Trial version. W7 64 / 375.70 .
There are two patches for Battlefront, the v1.2 is not great for fake 3D (extended letters like SnickerSnack pictures), the other one is good though.

Real 3D is bugged, wrong light and wheels 3D position are messed up like SnickerSnack picture (Very annoying in the garage), not playable for me.

I've swapped BattleFront 2015 profil, adress the NFS16.exe and NFS16_trial.exe to the BF2015 profil, patch with the BF2015 Fix. (I've try both of them). Also disable Origin In Game, disable the SLI, match desktop resolution and game, disable AA and Vsync in Nvidia control panel, same problems.

I use the 10H Trial version.

W7 64 / 375.70



.
3D video in game: (set for 24") At 1:16 it's Compatibility Mode. [u][url=https://s3.amazonaws.com/dhr/STAR.WARS.Battlefront.3Dfix.zip]Works great with alternative Fix from DHR[/url][/u] https://www.youtube.com/watch?v=dExlKleFXX0&feature=youtu.be Have we missed something ? .
3D video in game: (set for 24")

At 1:16 it's Compatibility Mode. Works great with alternative Fix from DHR

;feature=youtu.be

Have we missed something ?


.
  4 / 5    
Scroll To Top