nHancer feedback thread

[nekrosoft13]

Grestorn

New driver 169.01, they changed something again in NVAPPS.xml

<PROFILE Label="Medal of Honor: Airborne">
<APPLICATION Label="moha.exe"/>
<APPLICATION Label="mohademo.exe"/>
<PROPERTY Label="multichip_rendering_mode" Value="0x02402001" Default="0x02402001" Itemtype="predefined"/>
<PROPERTY Label="aa_feature_bits" Value="0x00000045" Default="0x00000045" Itemtype="predefined"/>
</PROFILE>

those Default values where not there before.

Do you know if nHancer will still work? I will try it out once i get home.

[bagman]

Originally Posted by nekrosoft13

Grestorn

New driver 169.01, they changed something again in NVAPPS.xml



those Default values where not there before.

Do you know if nHancer will still work? I will try it out once i get home.

Agreed.
Even deleting OS_TYPE="Vista" in nvapps.xml still does not make nHancer work.

cheers

update: ignore the above. I re-did the deleting OS_TYPE="Vista" and nHancer now works.
I must have deleted one line too many.

[nekrosoft13]

only ones that are causing the issue are under "multichip_rendering_mode"

[mikeyakame]

Let me add, make sure you change the nvapps.xml in both c:\windows\system32 & c:\programdata\nvidia, whichever changes u make to one make to the other. These are both offending xml files that nHancer reads. You can change back the nvapps.xml (create backup of file and copy back over) in system32 after you import the profiles in nHancer if you like, its only required for this purpose.

[K007]

So the problem with the 169 is only effecting Vista users?

[bagman]

Originally Posted by K007

So the problem with the 169 is only effecting Vista users?

I'm running these with a 7950GX2 and XP Pro (SP2) without major issue, after deleting OS_TYPE="Vista" in nvapps.xml.

MOH Allied Assault had some graphics issues ( the landing craft on Omaha Beach was balc and white stripes ). Other than that no problems.

cheers

[K007]

Originally Posted by bagman

I'm running these with a 7950GX2 and XP Pro (SP2) without major issue, after deleting OS_TYPE="Vista" in nvapps.xml.

MOH Allied Assault had some graphics issues ( the landing craft on Omaha Beach was balc and white stripes ). Other than that no problems.

cheers

I still get a error saying that...everytime i change a setting.

I searched the .xml file and removed OS_TYPE="Vista"

[Grestorn]

A new version that'll work with 169.x and that supports G92 is on the way.

Anybody interested in testing that version right now, can write to grestorn at gmx dot net.

[bagman]

Originally Posted by Grestorn

A new version that'll work with 169.x and that supports G92 is on the way.

Anybody interested in testing that version right now, can write to grestorn at gmx dot net.

Using the latest version of nHancer with the 169.01's I'm getting black and white zebra stripes on certain surfaces in Medal Of Honor Allied Assault.

I'm wondering if it has anything to do with the changed values that nekrosoft13 mentions. I do notice that even with MOHAA they have changed them in these drivers compared to previous versions.



Cheers

[Grestorn]

Version 2.3.2 is available, with support for G92 and Forceware 169.x.

Get it from www.nhancer.com

[Grestorn]

Originally Posted by bagman

Using the latest version of nHancer with the 169.01's I'm getting black and white zebra stripes on certain surfaces in Medal Of Honor Allied Assault.

I'm wondering if it has anything to do with the changed values that nekrosoft13 mentions. I do notice that even with MOHAA they have changed them in these drivers compared to previous versions.

Hm, unless you actually change the profile using nHancer, there's no way nHancer could interfere with the game.

In the past there were some strange effects with .NET and OpenGL, but even if such a thing would come up again, it should suffice to shut down nHancer while playing the affected game.

[bagman]

Originally Posted by Grestorn

Hm, unless you actually change the profile using nHancer, there's no way nHancer could interfere with the game.

In the past there were some strange effects with .NET and OpenGL, but even if such a thing would come up again, it should suffice to shut down nHancer while playing the affected game.

Hi Grestorn
Thank you for replying.
When you say "shut down nHancer", do you mean go into services.msc and disable nHancer to see if that make any difference ?
I do not have nHancer start when I boot into Windows nor is it sitting in my system tray

cheers