Announcement

Collapse
No announcement yet.

can someone explain this to me?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • can someone explain this to me?

    In Windows 2000 you cannot use more than 15.8MB of AGP texture memory for DiME cards like all the Matrox cards since the G200, and not more than 31.6 on all DMA cards like all nVidia cards.

    However, in an attempt to test the difference between 1x and 2x AGP texturing speed on my pc, I found something very weird:

    I tried changing the settings in the 3DMark2000 benchmark in such a way, so that the framebuffer would take up slightly less than 15MB on the G400, forcing it to use as close to the maximum of 15.8MB of AGP textures as possible for the 32MB AGP texture rendering benchmark in 3DMark2000.

    When I tested at 1152x864x32 with triple buffering, I got satisfying results, but I wanted to see 3DMark report 'could not perform test' with 32MB textures, just to make sure I pushed the amount of non-local AGP textures to the limit. So I increased the resolution one more notch, and to my surprise, 3DMark just ran the 32MB texture test! I was really surprised, because I thought there wasn't enough texture memory to perform this at that res.

    The next step was that I increased the resulution to 1600x1200x32 bit with triple buffer, and guess what? 3DMark ran the 32MB test without the slightest complain! WTF? It also reported that 30MB of the G400 was in use for framebuffer, so that leaves exactly 17MB of RAM including AGP for textures? How can it perform the 32MB test at this res.???

    And why can't I run the 64MB test, even at the smallest framebuffer settings?

  • #2
    I can confirm that. 1280x1024x32 32 bits-Z triple buffering can run the 32 Mb AGP texturing test and reports 63 fps.

    This is with 5.20 drivers, as 5.3x completly disable AGP (rumors, eh? )

    Comment


    • #3
      rumors, eh?

      as long as I don't know the exact cause I have to put it somewhere

      did you try upgrading to DirectX 8.0a or downgrading to DirectX 7.0 yet? I am interested in what the results will be!

      [This message has been edited by dZeus (edited 31 January 2001).]

      Comment


      • #4


        Ok, here the latest: DX8a fixes nothing (tried it now), and DX7 (Default win2k install) has the same problem. Matrox must have introduced something new in 5.3x that screws AGP in (most)VIA systems...

        Here http://forums.murc.ws/ubb/Forum5/HTML/010154.html other guy, bradwark, reporting that he´s got the same problem either with DX7 or DX8.

        Comment

        Working...
        X