Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Graphic issue on Slackware -current
#1
Hi,
After updating mesa 8.0.4 to 9.0.3 on Slackware -current I have a strange graphic issue.

   
   

I'm using Gallium 0.4 on AMD RS780 and here console output:
Code:
PCSX2 1.1.0.r5566  - compiled on Feb 21 2013
Savestate version: 0x9a0a0000

Host Machine Init:
        Operating System =  Linux 3.7.1-smp i686
        Physical RAM     =  1739 MB
        CPU name         =  AMD Athlon(tm) II X2 260 Processor
        Vendor/Model     =  AuthenticAMD (stepping 03)
        CPU speed        =  3.211 ghz (2 logical threads)
        x86PType         =  Standard OEM
        x86Flags         =  178bfbff 00802009
        x86EFlags        =  efd3fbff

x86 Features Detected:
        MMX.. SSE.. SSE2.. SSE3
        MMX2  .. 3DNOW .. 3DNOW2.. SSE4a

Installing POSIX SIGSEGV handler...
Reserving memory for recompilers...

Loading plugins...
        Binding   GS: /home/lukk/PCSX2-svn/plugins/libzzogl-0.4.0.so
        Binding  PAD: /home/lukk/PCSX2-svn/plugins/libonepad-1.1.0.so
        Binding SPU2: /home/lukk/PCSX2-svn/plugins/libspu2x-2.0.0.so
        Binding CDVD: /home/lukk/PCSX2-svn/plugins/libCDVDnull.so
        Binding  USB: /home/lukk/PCSX2-svn/plugins/libUSBnull-0.7.0.so
        Binding   FW: /home/lukk/PCSX2-svn/plugins/libFWnull-0.7.0.so
        Binding DEV9: /home/lukk/PCSX2-svn/plugins/libdev9null-0.5.0.so
Plugins loaded successfully.

(GameDB) 9643 games on record (loaded in 260ms)
HLE Notice: ELF does not have a path.


Initializing plugins...
        Init GS                                                                                                              
ZZOgl-PG:  Calling GSinit.                                                                                                  
ZZOgl-PG:  GSinit finished.                                                                                                  
        Init PAD                                                                                                            
        Init SPU2                                                                                                            
        Init CDVD                                                                                                            
        Init USB                                                                                                            
        Init FW                                                                                                              
        Init DEV9
Plugins initialized successfully.

Opening plugins...
        Opening GS
ZZOgl-PG:  Calling GSopen2.
ZZOgl-PG:  Capturing ZZOgl window.
ZZOgl-PG:  glX-Version 1.4 with Direct Rendering
ZZOgl-PG:  Supported Opengl version : 2.1 Mesa 9.0.3

ZZOgl-PG:  Using multitexturing.
ZZOgl-PG:  Maximum texture size is 8192 for Tex_2d and 8192 for Tex_NV.
change vsync 0
ZZOgl-PG:  Disabling MRT depth writing.
ZZOgl-PG:  Using non-bilinear fill, quallity is outdated!
ZZOgl-PG:  Initialization successful.
change vsync 0
ZZOgl-PG:  Disabling MRT depth writing.
        Opening PAD
        Opening SPU2

Also I tried mesa 9.1 and official pcsx2 builds but I got the same result but If I revert back to mesa 8.0.4 everything is ok.
Does anyone know what could it be? Thank you in advance.
Reply

Sponsored links

#2
Quote:ZZOgl-PG: Using non-bilinear fill, quallity is outdated!
If this message doesn't appears on 8.0.4, it means that mesa wasn't compiled with texture float extension.
Reply
#3
Thank you for your reply.
Mesa 9.0.3 is compiled without texture float feature just like mesa 8.
I compared the two outputs, mesa 9 give me a "Disabling MRT depth writing." more before "Opening PAD" line.
Next days I'll build mesa 9 adding "--enable-texture-float" in mesa.Slackbuild and I'll post results
Reply
#4
Could be related :
http://www.phoronix.com/scan.php?page=ne...px=MTMxMjI
Reply
#5
No luck with texture float option, I think I'll stick with mesa 8 for now.
Maybe you are right its hd3000 with opensource driver that cause the issue however kde desktop effects and other GL stuff are working good (out of curiosity i tried unreal and quake) so could be a pcsx2 related problem too. Really I don't know.
Thanks for your time.
Reply
#6
If the application doesn't use the same code path, it doesn't mean anythings.

PCSX2 work with proprietary driver. It used to work with radeon driver too. So either radeon support new GL extensions that change zzogl code path, either driver got a regression.

If you've got some free time, we can validate that the driver is buggy (or not) with the tool apitrace. You can generate a trace with apitrace on mesa 8. Replay the trace and validate that the trace is working nicely, be sure there isn't any GL error (otherwise report them to me). Then replay the trace with mesa 9. If the trace doesn't work (and there isn't any GL error), open a driver bug on mesa and attach the trace (and don't forget to said it is good with mesa 8).
Reply
#7
OK,I built apitrace from git and generated a trace in mesa 8 with "$apitrace trace pcsx2" and booting bios. after I replayed the trace in mesa 8 for validation and I got some warning
Quote:0 1980 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_RGBA32F, width = 128, height = 512, border = 0, format = GL_ALPHA, type = GL_FLOAT, pixels = blob(262144))
1980: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE
0 1982 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_ALPHA32F_ARB, width = 128, height = 512, border = 0, format = GL_ALPHA, type = GL_FLOAT, pixels = blob(262144))
1982: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE
0 1984 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_ALPHA32F_ARB, width = 128, height = 512, border = 0, format = GL_ALPHA, type = GL_FLOAT, pixels = blob(262144))
1984: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE


replaying trace in mesa 9 i got same graphics problems with a similar output:
Quote: 1980: glDebugOutputCallback: High severity API error 0, GL_INVALID_VALUE in glTexImage2D(internalFormat=GL_RGBA32F)
0 1980 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_RGBA32F, width = 128, height = 512, border = 0, format = GL_ALPHA, type = GL_FLOAT, pixels = blob(262144))
1980: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE
1982: glDebugOutputCallback: High severity API error 0, GL_INVALID_VALUE in glTexImage2D(internalFormat=GL_ALPHA32F_ARB)
0 1982 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_ALPHA32F_ARB, width = 128, height = 512, border = 0, format = GL_ALPHA, type = GL_FLOAT, pixels = blob(262144))
1982: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE
1984: glDebugOutputCallback: High severity API error 0, GL_INVALID_VALUE in glTexImage2D(internalFormat=GL_ALPHA32F_ARB)
0 1984 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_ALPHA32F_ARB, width = 128, height = 512, border = 0, format = GL_ALPHA, type = GL_FLOAT, pixels = blob(262144))
1984: warning: glGetError(glTexImage2D) = GL_INVALID_VALUE
Rendered 1638 frames in 33.2881 secs, average of 49.2068 fps
Reply
#8
Is the trace working (render correctly) on mesa 8.0 ?

Edit: I don't think those errors are important. I think I've found the root cause. I will see if I can correct them.
Don't need the trace anymore.
Reply
#9
Hum, I think I need to fix those errors. We store data in the alpha channel (opengl 2.0) but opengl 3 only support the red channel... Behavior is probably undefined here.

Edit: Hoppefully there are fixed on latest trunk. Could you test it.
Reply
#10
It's no working neither with mesa 8 nor with mesa 9.
I got this:
[Image: wrong7.jpg]

and no this:
[Image: wrong8.jpg]

Apitrace give me same errors like before.
Let me know if you need other infos or I'm making some mistake.
Reply




Users browsing this thread: 1 Guest(s)