Announcement

Collapse
No announcement yet.

Problems with the new ICD

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

  • Problems with the new ICD




    The picture above was borrowed from one of Sharky's reviews, as I don't have a webpage to show you one taken with my vanilla running the new ICD in Quake 3. But the problem is the same as they are speaking of there.


  • #2
    Got any idea what might cause that ? except for the ICD OpenGL itself.

    Comment


    • #3
      I am talking about the ICD in the Official 5.52.015 PowerDesk here.

      Comment


      • #4
        I have the exact same problem. But it doesn't really matter, 'cause there's no reason for using the 5.52 ICD since the TurboGL is still way faster.

        Torben R.
        G400 news, info, downloads and mailinglist : http://TRsDomain.homepage.dk

        Comment


        • #5
          This also happens in the ICD coming with the new final drivers for Win2k, didn't happen with the beta drivers...
          mostly shadows acting like that...
          <font size=1>Primary System: ASUS P4B533-E, Intel Pentium4 1.6A GHz, 512MB Samsung PC2700, Leadtek GF4 Ti4200 64MB, SB Audigy, 2xSeagate Barracuda IV 80GB, Pioneer DVD 106S, NEC CD-R 40/10/40, InWin Q500 Case w/ Enermax 353W PSU, Windows XP Pro, Samsung SyncMaster 753DFX.

          Secondary System: ECS K7S5A, Athlon XP 1600+, 256MB PC133, Asus GF2 GTS 32MB, Seagate Barracuda IV 20GB, Aopen HQ08 Case, Windows XP Pro.</font>

          Comment


          • #6
            I too have noticed this visual anomaly.
            The only work-around is to 'transplant' the 5.50.010 ICD from the previous release into \windows\system\ (or even the Q3A folder) as this seems about the best ICD version so far.

            Comment


            • #7
              exact same problem here. OPengl ICD from the new WIN98 drivers 5.52.012.

              Comment


              • #8
                Glad to hear I'm not the only one who gets them.
                What bothered me was that the betas worked fine, slower but no visual problems... and now as they decided to release an official pack, something like this shows up.

                Been using TurboGL since it came out and seems I'll keep on using it

                Comment


                • #9

                  I have noticed this bug(probably z-buffer bug) in the last betas OPengl ICD and in TurboGl driver for Pentium II, but it`s very hard to identify. However it`s visible from big distance and mainly when you look at jump pads. In the new OPENGL ICD from the latest drivers PD 5.52.015 this bug is intolereable.

                  MATROX please repair this bug ASAP.

                  Comment


                  • #10
                    John, I think you mean something else, I'm only refering to the way the stairs or the walls or anything I shoot at looks like.

                    The bug you are speaking of shows in UT and some Quake 3 maps, it is a different bug, but still a bug.
                    It's like cuting a piece of the envirenment and trying to fit it back in. In Quake 3 it started to show with the betas and seems to be gone in this release. Can't say the same thing about UT, it still shows and has showed since PD 5.41, although they have tryed to fix it and each release after that was an improvement

                    Or, you might just be refering to the effects of edge aliasing if you're running Quake 3 in 800x600.



                    [This message has been edited by andrei (edited 26 February 2000).]

                    Comment


                    • #11
                      This happens in the win2k 5.03 PD too.

                      Comment


                      • #12
                        Hi Andrei

                        I`m not speaking about the very known UT image clipping, it`s maybe a different problem or maybe the same but STILL UNSOLVED, WHY MATROX?
                        With the new OPENGL ICD 5.52.015 in Q3arena I have flickering shadows under players and flickering explosions mark on the floor, like striped, maybe some kind of texture problem. Old betas ICD a TurboGL are not affected by this problem.
                        **********************
                        But I`m sure, that the MATROX OPENGL ICD and TURBO GL(Pentium 2) driver also has the known UT image clipping problem.

                        Simply demonstration of image clipping in Q3arena. Now I`m using TurboGL for PentiumII and I loaded Q3DM17 map, the known map from Q3test series. Please jump to the highest deck(QUAD DAMAGE is here) and take a look with ZOOM enabled at the far field region(deck where is railgun). NOW YOU MUST SEE THE SAME PROBLEM AS IN UT- Image clipping on the railgun deck. All maps in Q3 are affected by this effect, but it`s only visible from big distance, heh, and in Q3Arena are mostly small maps.


                        Sorry my english stuff

                        best regards
                        Rambo

                        P2 450Mhz, AbitBh6,128MB SdRAm, G400DH 32MB,Sblive,.....

                        Q3 test settings: 1024x768x32 bit x 32 bit textures, full texture slider, bilinear, game options default, TurboGl for P2, driver info shows 32bit depth,16bit Z-buffer,0 bit stencil buffer.

                        Comment


                        • #13
                          Hi,

                          The real question should be, why the new bug ? new drivers are supposed to fix old bugs, not create new ones

                          About UT, I run it in D3D not OGL, sorry for the confusion. But the bug in UT D3D is simmilar to the one in Quake 3 (ICD or TGL), though as I said in Quake 3 it doesn't show that much.

                          I'm just courious of how much fps you get with those settings in Quake 3 timedemo 1 ?
                          I get 32 with my vanilla overclocked to Max values and 28 with it at its default clock.

                          The frames tend to drop with A3D enabled.
                          ----------------
                          p3 450, Intel SE440BX-2, 128 PC100 SDRAM, G400 DH 32 SGRAM, Vortex 2



                          [This message has been edited by andrei (edited 27 February 2000).]

                          Comment


                          • #14
                            "new drivers are supposed to fix old bugs, not create new ones",I agree with you Andrei. I`m talking about the new bug in ICD 5.52.015, weird (like striped) shadows and explosion marks on the floor.
                            *******

                            But the same image clipping problem is there in UT(D3D) as well in Q3(OGL,TGL), it`s fact. Yes, it occurs less than in UT. I hope that you check out my simply demostration.


                            regards
                            Rambo

                            P.S. I got exact the same fps number, but now is fps for me irelevant. not o/c 28fps, o/c 32-33fps

                            Comment


                            • #15
                              Hi all

                              Im getting the same f**ked up shadows and explosion marks on floor and walls since i installed the latest "FINAL" driver from matrox,So what can I do about it????.

                              I have been looking forward to the final driver for some time now and to have this sort of serious problems is not appreciated at all

                              Is this problem due to the fact that I didn,t totally uninstall the previous beta driver or not.Also is it essential to completely remove all exsisting matrox drivers before installing a newer version??.

                              I have resorted to the previous BETA driver as at the moment I have no other solution to this problem Laterz AkA Max-Payne

                              Comment

                              Working...
                              X