The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    163.16 Application-specific 3D controls fail

    Discussion in 'Gaming (Software and Graphics Cards)' started by ShadowoftheSun, Aug 23, 2007.

  1. ShadowoftheSun

    ShadowoftheSun Notebook Consultant

    Reputations:
    27
    Messages:
    181
    Likes Received:
    0
    Trophy Points:
    30
    Hi all, I was just wondering if any of the other 163.16 users are experiencing this problem. I have my drivers to force certain settings in certain games- for example, I force 4x AF and 2x AA in Guild Wars because the GW control panel only allows for basic AA. However, it seems every time I change settings, the application will whipe if I restart. I was just wondering if this has been happening to anyone else.

    On a side note, are the 163.44's only good for Bioshock, or do they present other performance benefits? Since it's unlikely I'll play Bioshock soon (if I do I'll install drivers then) I'll probably avoid these drivers unless there are improvements in other areas as well.

    EDIT: Just noticed the settings will whipe if I choose another setting. For example, setting AF to 4x will return my AA settings to application-controlled from 2x. Looks like I'll be trying out the 163.44's after all.
     
    ShadowoftheSun, Aug 23, 2007
    #1
  2. ShadowoftheSun

    ShadowoftheSun Notebook Consultant

    Reputations:
    27
    Messages:
    181
    Likes Received:
    0
    Trophy Points:
    30
    Sorry for the double post, but I wanted to make sure this gets bumped if anyone wants the solution.

    From the 163.44 release notes:

    So, apparently 163.44's fixed the issue.
     
    ShadowoftheSun, Aug 23, 2007
    #2