Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
GSDX OpenGL related issue.
#1
Hi, i have questions related opengl renderer in gsdx. Correct me if i am wrong, i believe that the dev is focusing on opengl 4.5
I think my GPU does not support for OGL 4.5, when i start game in hardware mode after choosing opengl in gsdx setting, the screen becomes all white.
But when i switch to software mode (by pressing F9), the game are rendered properly.

I have my curiosity regarding that. It is hardware limitation or there are some setting that i need to do?

My PC Spec:
Intel Core i5-3470
Ati Radeon HD 5570 1GB
4gb DDR3 RAM


I apologize if the same question already asked before. I did try to search for related issue but results shows from many years ago. I think it would not be relevant due to the dev constantly improving the plugin.
Reply

Sponsored links

#2
(10-22-2016, 03:40 AM)rosli_2252 Wrote: Hi, i have questions related opengl renderer in gsdx. Correct me if i am wrong, i believe that the dev is focusing on opengl 4.5
I think my GPU does not support for OGL 4.5, when i start game in hardware mode after choosing opengl in gsdx setting, the screen becomes all white.
But when i switch to software mode (by pressing F9), the game are rendered properly.

I have my curiosity regarding that. It is hardware limitation or there are some setting that i need to do?

My PC Spec:
Intel Core i5-3470
Ati Radeon HD 5570 1GB
4gb DDR3 RAM


I apologize if the same question already asked before. I did try to search for related issue but results shows from many years ago. I think it would not be relevant due to the dev constantly improving the plugin.

same problem with me, when using OpenGL hardware : the screen all white

but when use the software : work properly

even using the latest pcsx2
Reply
#3
You're wrong. I'm only using 3.3 HW features (except for a rare case).

Try latest 1.5 version and post me this part of the log
Quote:OpenGL information. GPU: GeForce GTX 760/PCIe/SSE2. Vendor: NVIDIA Corporation. Driver: NVIDIA 352.79
INFO: GL_EXT_texture_filter_anisotropic is available
INFO: GL_ARB_gpu_shader5 is available
INFO: GL_ARB_draw_buffers_blend is available
INFO: GL_ARB_viewport_array is available
INFO: GL_ARB_shader_image_load_store is available
INFO: GL_ARB_clear_texture is available
INFO: GL_ARB_get_texture_sub_image is available

Available VRAM/RAM:3840MB for textures
Reply
#4
OpenGL information. GPU: AMD Radeon HD 6670. Vendor: ATI Technologies Inc.. Driver: Core Profile Forward-Compatible Context 15.200.1062.0
INFO: GL_EXT_texture_filter_anisotropic is available
INFO: GL_ARB_gpu_shader5 is available
INFO: GL_ARB_draw_buffers_blend is available
INFO: GL_ARB_viewport_array is available
INFO: GL_ARB_shader_image_load_store is available
INFO: GL_ARB_clear_texture is available
INFO: GL_ARB_get_texture_sub_image is available

Available VRAM/RAM:2026MB for textures
Reply
#5
Could you edit the gsdx.ini file and add this option
Code:
debug_glsl_shader = 1
Tell me if you see error message on shader compilation. Otherwise I will suggest to upgrade to the beta crimson (the one that is still working with older GPU). There is likely a driver bug but I don't get which one? Could you also try to set accurate blending to the max to test if it is a blending issue or another one?
Reply
#6
(10-22-2016, 12:51 PM)gregory Wrote: Could you edit the gsdx.ini file and add this option
Code:
debug_glsl_shader = 1
Tell me if you see error message on shader compilation. Otherwise I will suggest to upgrade to the beta crimson (the one that is still working with older GPU). There is likely a driver bug but I don't get which one? Could you also try to set accurate blending to the max to test if it is a blending issue or another one?

Code:
Current Renderer: OpenGL (Hardware mode)
    Opening CDVD
    Opening USB
    Opening FW
    Opening DEV9
OpenGL information. GPU: AMD Radeon HD 6670. Vendor: ATI Technologies Inc.. Driver: Core Profile Forward-Compatible Context 15.200.1062.0
INFO: GL_EXT_texture_filter_anisotropic is available
INFO: GL_ARB_gpu_shader5 is available
INFO: GL_ARB_draw_buffers_blend is available
INFO: GL_ARB_viewport_array is available
INFO: GL_ARB_shader_image_load_store is available
INFO: GL_ARB_clear_texture is available
INFO: GL_ARB_get_texture_sub_image is available

McdSlot 0 [File]: E:\pcsx2-v1.5.0-dev-1488-g1f44c4b-windows-x86\memcards\Mcd001.ps2
McdSlot 1 [File]: E:\pcsx2-v1.5.0-dev-1488-g1f44c4b-windows-x86\memcards\Mcd002.ps2
Plugins opened successfully.
EE/iR5900-32 Recompiler Reset
3.x GL context successfully created
OpenGL renderer is slow on AMD GPU due to inefficient driver. Sorry.
    Bios Found: USA     v02.30(20/02/2008)  Console
    BIOS rom2 module not found, skipping...
    BIOS erom module not found, skipping...
# Initialize memory (rev:4.00, ctm:196Mhz, cpuclk:147Mhz detected)

PlayStation 2 ======== Hard reset boot
ROMGEN=2008-0220, IOP info (CPUID=1f, CACH_CONFIG=14000200, 2MB, IOP mode)
<20080220-175343,ROMconf,PS20230WC20080220.bin:11824>
# Total accessable memory size: 32 MB (B:2:8:0) (400:2:7c30)
# TLB spad=0 kernel=1:12 default=13:30 extended=31:38
# Initialize Start.
# Initialize GS ...
# Initialize INTC ...
# Initialize TIMER ...
# Initialize DMAC ...
# Initialize VU1 ...
# Initialize VIF1 ...
# Initialize GIF ...
# Initialize VU0 ...
# Initialize VIF0 ...
# Initialize IPU ...
# Initialize FPU ...
# Initialize User Memory ...
Available VRAM/RAM:2026MB for textures
GSdx Lookup CRC:0
Frame buffer size set to  512x1280 (1024x2560)
# Initialize Scratch Pad ...
# Initialize Done.

EE DECI2 Manager version 0.06 Sep  5 2006 12:57:08
 CPUID=2e20, BoardID=0, ROMGEN=2008-0220, 32M

Patches: No CRC found, using 00000000 instead.
(IsoFS) Invalid partition descriptor encountered at block 0x10: ''
(IsoFS) Invalid partition descriptor encountered at block 0x10: ''


IOP Realtime Kernel Ver.0.9.1

   Copyright 1999 (C) Sony Computer Entertainment Inc.

Reboot service module.(99/11/10)
cdvd driver module version 0.1.1 (C)SCEI
Load File service.(99/11/05)
Multi Threaded Fileio module.(99/11/15)
iop heap service (99/11/03)
loadelf: fname rom0:OSDSYS secname all
loadelf version 3.30
Input ELF format filename = rom0:OSDSYS
0 00100000 00058530 ......
Loaded, rom0:OSDSYS
start address 0x100008
gp address 00000000
# Restart Without Memory Clear.
# Initialize GS ...
# Initialize INTC ...
# Initialize TIMER ...
# Initialize DMAC ...
# Initialize VU1 ...
# Initialize VIF1 ...
# Initialize GIF ...
# Initialize VU0 ...
# Initialize VIF0 ...
# Initialize IPU ...
# Initialize FPU ...
# Initialize Scratch Pad ...
# Restart Without Memory Clear Done.
# Restart Without Memory Clear.
# Initialize GS ...
# Initialize INTC ...
# Initialize TIMER ...
# Initialize DMAC ...
# Initialize VU1 ...
# Initialize VIF1 ...
# Initialize GIF ...
# Initialize VU0 ...
# Initialize VIF0 ...
# Initialize IPU ...
# Initialize FPU ...
# Initialize Scratch Pad ...
# Restart Without Memory Clear Done.
Get Reboot Request From EE

PlayStation 2 ======== Update rebooting..

PlayStation 2 ======== Update reboot complete
cdvdman Init
rmreset start
rmreset end
clearspu: completed
Pad Driver for OSD (2000/12/05 18:05) 392, 128


IOP Realtime Kernel Ver.0.9.1

   Copyright 1999 (C) Sony Computer Entertainment Inc.

Reboot service module.(99/11/10)
cdvd driver module version 0.1.1 (C)SCEI
Load File service.(99/11/05)
Multi Threaded Fileio module.(99/11/15)
iop heap service (99/11/03)
read/write allocate memory 4000
open name rom0:OSDVER flag 1 data 4aa78
open fd = 2
open name rom0:ROMVER flag 1 data 4aa78
open fd = 2
open name rom0:XDEV9 flag 1 data 4aa78
open fd = 2
loadmodule: fname rom0:XDEV9 args 0 arg
dev9: unknown dev9 hardware.
loadmodule: id 32, ret 1
loadmodule: fname rom0:XDEV9SERV args 0 arg
loadmodule: id -200, ret 1
open name rom0:ROMVER flag 1 data 4aa78
open fd = 2
open name rom0:FONTM flag 1 data 4aa78
open fd = 2
open name rom0:FNTIMAGE flag 1 data 4aa78
open fd = 2
open name rom0:SNDIMAGE flag 1 data 4aa78
open fd = 2
open name rom0:TEXIMAGE flag 1 data 4aa78
open fd = 2
open name rom0:ICOIMAGE flag 1 data 4aa78
open fd = 2
open name rom0:TZLIST flag 1 data 4aa78
open fd = 2
_spu_rev_offsetaddr 1f9021
### addr = 1034255  size = 28640
_spu_rev_offsetaddr 1d9021
### addr = 968719  size = 28640
get val add 3c0 type 2 ret 1ff000
get val add 1ff000 type 2 ret 300
open name rom0:PS1ID flag 1 data 4aa78
open fd = 2
open name rom0:PS1VERA flag 1 data 4aa78
open fd = 2
open name rom1:DVDIDU flag 1 data 4aa78
open fd = 2
open name rom1:DVDVERU flag 1 data 4aa78
open fd = 2
(UpdateVSyncRate) Mode Changed to BIOS.
Frame buffer size set to  640x1280 (1280x2560)
BLENDING UNIT ULTRA
and i add the code u tell me to insert into ini
but still white screen Sad
Reply
#7
(10-22-2016, 10:44 AM)gregory Wrote: You're wrong. I'm only using 3.3 HW features (except for a rare case).

If you are using 3.3 only, why does my 9500gt fail to use Opengl altogether? I get this in the log:

3.x GL context successfully created
Failed to find glCreateQueries
Failed to find glBlendEquationSeparateiARB
Failed to find glBlendFuncSeparateiARB
Failed to find glBindImageTexture
Failed to find glMemoryBarrier
Failed to find glClearTexImage
Failed to find glClearTexSubImage
Failed to find glBufferStorage

Im using 314.22 Drivers.
Reply
#8
(10-22-2016, 03:54 PM)Paradise12314 Wrote: If you are using 3.3 only, why does my 9500gt fail to use Opengl altogether? I get this in the log:

3.x GL context successfully created
Failed to find glCreateQueries
Failed to find glBlendEquationSeparateiARB
Failed to find glBlendFuncSeparateiARB
Failed to find glBindImageTexture
Failed to find glMemoryBarrier
Failed to find glClearTexImage
Failed to find glClearTexSubImage
Failed to find glBufferStorage

Im using 314.22 Drivers.

Because those ones listed separately are the OGL 4.0+ extensions.
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#9
I said that I'm using 3.3 HW features. I used some GL4+ extensions to use feature available on Dx9 hardware (or older). It will work if you use the free Mesa driver. It even work on sandy bridge on linux which is far from a Dx11 GPU.

You're driver is limited on purpose (all vendors do the same) in order to sell new GPU.
Reply
#10
(10-22-2016, 05:34 PM)gregory Wrote: I said that I'm using 3.3 HW features. I used some GL4+ extensions to use feature available on Dx9 hardware (or older). It will work if you use the free Mesa driver. It even work on sandy bridge on linux which is far from a Dx11 GPU.

You're driver is limited on purpose (all vendors do the same) in order to sell new GPU.

Thanks for the explanation gregory. It's a rather trashy move by Nvidia. I was fine before with a 560ti, but that hit the dirt so im stuck with a 9500gt now Sad
Reply




Users browsing this thread: 1 Guest(s)