RPCS3 Forums
Intel HD 4400 - Driver Issues - Printable Version

+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: Support & Issues (https://forums.rpcs3.net/forumdisplay.php?fid=17)
+--- Forum: Support (https://forums.rpcs3.net/forumdisplay.php?fid=18)
+--- Thread: Intel HD 4400 - Driver Issues (/showthread.php?tid=199946)

Pages: 1 2


Intel HD 4400 - Driver Issues - Ahlclark07 - 01-06-2019


.rar   RPCS3 log.rar (Size: 33.54 KB / Downloads: 1)

Hello everyone, I'm new to this forum and I use a translation tool, so escuse me a lot if I made a mistake part. Since 3 days I try to start emulator, initially I had only 2 options in "renderrer", i had "null" and "openGL" but the openGL did not work and an error message appeared saying that my gpu was incompatible, I managed to solve problem by updating all my graphics drivers. Then now with the option "null" the game works but obviously there is no picture but the sound is there and the game responds. Parcontre with openGl, which should work, for the game I have a black screen that appears with an error code in the table below I admit that I do not know much about it.

here is my configuration:
Processor : Intel® Core™ i3-4005U Processor (3M Cache, 1.70 GHz) 
Graphics cards : intel hd 4400
Ram : 4gb
OS : windows 8.1 professional 64bits

And the game :
Name : Dragon ball raging blast 2
Type : Disc


RE: thread compiler error - Ani - 01-06-2019

Your GPU is likely not compatible, Intel drivers are not supported too because they're too bad

·E 0:00:19.054321 {RSX [0x0000000]} RSX: OpenGL: initialization of glDepthBoundsEXT failed.
·E 0:00:19.054448 {RSX [0x0000000]} RSX: OpenGL: initialization of glGetTextureImage failed.
·E 0:00:19.054462 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureSubImage1D failed.
·E 0:00:19.054474 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureSubImage2D failed.
·E 0:00:19.054483 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureSubImage3D failed.
·E 0:00:19.054514 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureBufferRange failed.
·E 0:00:19.054542 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureBarrier failed.
·E 0:00:19.054549 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureBarrierNV failed.
·! 0:00:19.054581 {RSX [0x0000000]} RSX: GL RENDERER: Intel® HD Graphics 4400 (Intel)
·! 0:00:19.054592 {RSX [0x0000000]} RSX: GL VERSION: 4.3.0 - Build 10.18.14.5057
·! 0:00:19.054596 {RSX [0x0000000]} RSX: GLSL VERSION: 4.30 - Build 10.18.14.5057
·W 0:00:19.054925 {RSX [0x0000000]} RSX: Texture barriers are not supported by your GPU. Feedback loops will have undefined results.
·! 0:00:19.054983 {RSX [0x0000000]} RSX: Supported texel buffer size reported: 134217728 bytes


RE: thread compiler error - Ahlclark07 - 01-06-2019

(01-06-2019, 05:04 PM)Ani Wrote: Your GPU is likely not compatible, Intel drivers are not supported too because they're too bad

·E 0:00:19.054321 {RSX [0x0000000]} RSX: OpenGL: initialization of glDepthBoundsEXT failed.
·E 0:00:19.054448 {RSX [0x0000000]} RSX: OpenGL: initialization of glGetTextureImage failed.
·E 0:00:19.054462 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureSubImage1D failed.
·E 0:00:19.054474 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureSubImage2D failed.
·E 0:00:19.054483 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureSubImage3D failed.
·E 0:00:19.054514 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureBufferRange failed.
·E 0:00:19.054542 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureBarrier failed.
·E 0:00:19.054549 {RSX [0x0000000]} RSX: OpenGL: initialization of glTextureBarrierNV failed.
·! 0:00:19.054581 {RSX [0x0000000]} RSX: GL RENDERER: Intel® HD Graphics 4400 (Intel)
·! 0:00:19.054592 {RSX [0x0000000]} RSX: GL VERSION: 4.3.0 - Build 10.18.14.5057
·! 0:00:19.054596 {RSX [0x0000000]} RSX: GLSL VERSION: 4.30 - Build 10.18.14.5057
·W 0:00:19.054925 {RSX [0x0000000]} RSX: Texture barriers are not supported by your GPU. Feedback loops will have undefined results.
·! 0:00:19.054983 {RSX [0x0000000]} RSX: Supported texel buffer size reported: 134217728 bytes
[quote pid='302855' dateline='1546794285']
Thank you for the answer, ok I see but we can not do anything to fix it? Or find another option for "renderrer" ? 
[/quote]


RE: thread compiler error - Ani - 01-07-2019

You can try using a Linux distribution with up-to-date mesa drivers


RE: thread compiler error - Ahlclark07 - 01-07-2019

I admit I did not understand ... buy another computer running on Linux?


RE: thread compiler error - Ani - 01-07-2019

No. If you're going to buy another computer then get one with a dedicated card that supports Vulkan.
Using Linux with up-to-date mesa drivers is a suggestion for your current computer.


RE: thread compiler error - Ahlclark07 - 01-07-2019

ok I see but how do I use linux, I admit that I do not know anything, would it be an OS like windows? or an Emulator? how do I proceed? without much trouble

I will do some research I will warn you in case of problems

if i chose the option to install linux as an application on windows, will it be able to fix my current problem?


RE: thread compiler error - Ani - 01-07-2019

Don't know, you'd have to try.
If you don't know what you're doing, don't do it. You need a new computer with a dedicated GPU in order to use RPCS3 properly.


RE: thread compiler error - Ahlclark07 - 01-07-2019

Okay, I will keep you informed

I think I made my case worse, I installed ubuntu 11.04 on a disk partition, but now the bootloader does not show me more Windows 8.1 and the worst thing is that the wifi does not work on ubuntu, I'm completely fucking

I download the boot repair disk 64bit.iso hoping that it could help me


RE: thread compiler error - Ani - 01-08-2019

Why are you trying to install a beta version of ubuntu from 7 years ago? It's obviously not going to work even if you managed to install it, RPCS3 is only supposed to support 14.04 and up and I'm not even sure if it works on 14.04, everyone uses 16 or 18.

I said before, if you don't know what you're doing, don't do it. You're going to end up killing both your partitions and render both OSes unusable.