Yes, it is too old.
Question / Help OBS 7.2: Failed to initialize video: unspecified error
- Thread starter Darragh Cattigan
- Start date
Yes, it is too old.
Dragonis0819
New Member
Failed to recreate D3D11: Failed to create resource view (80070057)
this is the crash report im getting. anyone know how to fix it?
this is the crash report im getting. anyone know how to fix it?
Harold
Active Member
@Jason2578 you're not having the same error as the thread is dealing with.
gregfrankenstein
New Member
Frankly, that's ridiculous. There's no reason OBS couldn't work on older graphics cards if it was configured to do so. Under the hood, it's just streaming with ffmpeg, and you can live stream with ffmpeg on ANY hardware, even an old 2008 ThinkPad, with little to no performance issues. The devs have just arbitrarily decided to refuse support for lower OpenGL versions because their primary demographic is gamers with multi-thousand dollar hardware.
There's always the workaround of launching with "LIBGL_ALWAYS_SOFTWARE=1 obs", but that bypasses the graphics chip entirely and your CPU will shoot up to 100% and overheat, even if OBS is just sitting idle without streaming. What's up with this, by the way? I mean I know I'm bypassing the GPU when I do that, but no other application does this when I add that flag. I can launch a web browser with LIBGL_ALWAYS_SOFTWARE enabled and stream multiple videos in 4K without a flinch, but OBS ravages the processor just to load its basic GUI. You know what, I answered my own question. I see why OBS refuses to launch without OpenGL 3.2 now.
Unfortunately, the FTL streaming on Mixer, as well as StreamJar overlays are both next to impossible without OBS, otherwise I wouldn't bother. I've tried using the ftl_sdk and CEF browser as standalone tools but they seem to be very specfically intended for OBS and won't work by themselves. In short, I'm annoyed by all of this, and I probably would have let it go if I hadn't come across a thread with glib snark like "Your computer is too old and bad to run OBS".
There's always the workaround of launching with "LIBGL_ALWAYS_SOFTWARE=1 obs", but that bypasses the graphics chip entirely and your CPU will shoot up to 100% and overheat, even if OBS is just sitting idle without streaming. What's up with this, by the way? I mean I know I'm bypassing the GPU when I do that, but no other application does this when I add that flag. I can launch a web browser with LIBGL_ALWAYS_SOFTWARE enabled and stream multiple videos in 4K without a flinch, but OBS ravages the processor just to load its basic GUI. You know what, I answered my own question. I see why OBS refuses to launch without OpenGL 3.2 now.
Unfortunately, the FTL streaming on Mixer, as well as StreamJar overlays are both next to impossible without OBS, otherwise I wouldn't bother. I've tried using the ftl_sdk and CEF browser as standalone tools but they seem to be very specfically intended for OBS and won't work by themselves. In short, I'm annoyed by all of this, and I probably would have let it go if I hadn't come across a thread with glib snark like "Your computer is too old and bad to run OBS".
Needing OpenGL 3.2 or higher is not arbitrary, OBS needs certain functions to be able to render (not encode) the output efficiently. This is the same as on Windows where it needs DirectX 10 or higher, which is of similar age.
And under the hood OBS isn't just doing "streaming with ffmpeg", it needs to do scene compositing, scaling, running shaders etc.
Also the ftl-sdk is not specifically intended for OBS, other streaming applications capable of streaming FTL also use it. CEF also isn't specifically intended for OBS, the browser plugin for OBS is not intended to be run standalone but as a source in OBS, not sure why you would want to use that standalone, just use a regular browser?
And under the hood OBS isn't just doing "streaming with ffmpeg", it needs to do scene compositing, scaling, running shaders etc.
Also the ftl-sdk is not specifically intended for OBS, other streaming applications capable of streaming FTL also use it. CEF also isn't specifically intended for OBS, the browser plugin for OBS is not intended to be run standalone but as a source in OBS, not sure why you would want to use that standalone, just use a regular browser?
Faiz uddin
New Member
I have the same problem