No GPU driver available

[DamD]

H.642 인코딩을 원하지만,

스트리밍을 시작하지 못했습니다.
출력 시작에 실패했습니다. 자세한 내용은 로그를 확인하십시오.
참고: NVENC 또는 AMD 인코더를 사용하는 경우 비디오 드라이버가 최신인지 확인하십시오.

PC
CPU: amd 라이젠7 3700x
GPU: 엔비디아 지포스 RTX 2070 슈퍼

GPU가 있지만 obs 비디오 인코더가 GPU를 인식하지 못합니다.
그래서 드라이버와 obs를 다시 설치했지만 여전히 문제가 지속됩니다.

로그를 분석한 결과 Microsoft Basic Render Driver만 인식됨을 확인했습니다.

전에는 이런 문제가 없었는데 갑자기 발생하네요
내가 그것을 고치는 방법

 

[DamD]

H.642 encoding is desired,

Failed to start streaming.
Failed to start output. Check the logs for more information.
Note: If you are using NVENC or AMD encoders, make sure your video driver is up to date.

PC
CPU: amd Ryzen7 3700x
GPU: Nvidia GeForce RTX 2070 Super

I have a GPU, but the obs video encoder does not recognize the GPU.
So I reinstalled the driver and obs, but the problem still persists.

An analysis of the logs confirmed that only the Microsoft Basic Render Driver was recognized.

I didn't have this problem before, but it just happened
How I fix it

 

[R1CH]

Make sure your monitors are connected to the GPU, not the motherboard. Then do a clean driver install.

Performing a clean GPU driver installation

If you're experiencing strange issues or errors that might be related to your GPU drivers, one of the easiest potential fixes is a clean driver installation. Follow the instructions below. 1. Download the latest version of Display Driver...

obsproject.com

 

[DamD]

Make sure your monitors are connected to the GPU, not the motherboard. Then do a clean driver install.

Performing a clean GPU driver installation

If you're experiencing strange issues or errors that might be related to your GPU drivers, one of the easiest potential fixes is a clean driver installation. Follow the instructions below. 1. Download the latest version of Display Driver...

obsproject.com

Thank you for your reply
But the monitor is connected to the GPU + clean driver

The connection with other apps is working fine.

Problem only occurs on OBS

 

[Suslik V]

...
03:50:05.898: QuickWriteFile: Failed to open file 'C:\Users\담\AppData\Roaming\obs-studio\updates\branches.json': Illegal byte sequence
03:50:05.898: AutoUpdateThread::run: Could not write file 'C:\Users\담\AppData\Roaming\obs-studio\updates\branches.json'
...

Is way more interesting here.

What last version of OBS you had before you updated to v29.1.3?

Edit:
It seems that this part of the issue now has a fix: https://github.com/obsproject/obs-studio/pull/9183

 

[DamD]

Is way more interesting here.

What last version of OBS you had before you updated to v29.1.3?

I remember it as the 28.1.1 version
But it's interesting because it's the first time I've seen it

 

[Suslik V]

To workaround this last issue (Unicode symbols in the path) you can try OBS portable mode.
For portable mode make folder "C:\obs" and unpack OBS files into it like it was mentioned here (read only after the "If it was not clear"): https://obsproject.com/forum/thread...»-when-opening-app-settings.82157/post-346499

 

[DamD]

To workaround this last issue (Unicode symbols in the path) you can try OBS portable mode.
For portable mode make folder "C:\obs" and unpack OBS files into it like it was mentioned here (read only after the "If it was not clear"): https://obsproject.com/forum/threads/crash-with-«could-not-find-locale-ini-path»-when-opening-app-settings.82157/post-346499

what?! how do that??!
Thank you for save my life
know i can see h.264 yeah!!