- #Epsxe chrono cross pete 2.9 incompatible driver#
- #Epsxe chrono cross pete 2.9 incompatible software#
I know my limits (though they're not without their bizarre problems like this), I know Twitch's limits, and after much testing and some researching, I've come to a set of encoding parameters I'm comfortable with. It's not that important for 2D or games that have a lot of static scenes, which is why I'm using quality 10 high amount of static scenes. I'm also streaming at 60FPS, resulting in the need for more bitrate and a high buffer the latter of which is really required to avoid compression artifacts on motion, especially sudden motion. There's a chance that it's the specific game I'm running at the time or another issue with the configuration of my plugin(s), but I've yet to go that in-depth with the testing.Ĭould you send me your GPU plugin settings?Īs for my encoding settings: Quality freak. You mean OpenGL2, as the original OpenGL version is 1.77. So, go with a lower max bitrate (Twitch advices never going over 3.5Mbps anyhow), not going with a custom buffer size and reducing the quality to Q-7 at the most and see if the problem persists. Looks fine, right? No sluggishness, quality pretty damned solid. Personally, I stream PSX titles in Q-7 at 3000 - 3500 Kbps and they look more than fine. Never forget - there is a certain degree of quality loss taking place on Twitch's end as well. Also, Q-10 is really unnecessary and will only serve to fill that buffer. I would like to note one thing though, regarding the log file - it is safest to NOT specify a custom buffer size and just leave it the same as the max bitrate. Your hardware is far superior to mine so that can't be the issue either. It will do it with Window Capture though. Regarding getting a black screen with a DX7 plugin - OBS does not capture DX7 in Game Capture. Given the recent improvements to the OpenGL capture of OBS, it is in fact preferable to go with an OpenGL plugin, for best performance. There is nothing wrong with going OpenGL actually.
#Epsxe chrono cross pete 2.9 incompatible driver#
I am using ePSXe 1.8.0 as well, running Pete's OpenGL Driver 2.9 and I have yet to see this particular issue you mention. Any other alternative is very old DirectX which is lacking in features and accuracy and generally never used unless one's using a very old system and/or has issues with OpenGL.
This is a real big issue for people running PSX emulators, as the only good GPU plugins for PSX emulators are OpenGL based. This is what boggles my mind why does Dxtory not cause any issues yet if either OBS or XSplit (maybe even FFsplit and FMLE) take Dxtory's output the issue appears? The broadcast program shouldn't even be affecting the source only Dxtory should.
Dxtory by itself exhibits no issues in my testing. It also happens when taking Dxtory's output. When using a DirectX plugin (DX7 I think) OBS only produces a black screen.
#Epsxe chrono cross pete 2.9 incompatible software#
Originally I thought it was due to the software nature of the plugin, but upon testing I found it still happens with a hardware based OpenGL plugin. XSplit has this issue as well, but not as bad (random as opposed to constantly).
I'm running a PSX emulator ( ePSXe 1.8.0) and using a software based GPU plugin ( BladeSoft) and when I attach Game Capture to it I suffer from random sluggishness, as if I'm dropping frames in my own video feed. I'm having issues with Game Capture injected into an OpenGL rendering pipeline (or so it says). Mentioned it in the test build thread, but it wasn't resolved by the time the stable release came out, so I'm creating a dedicated thread about it.
0 kommentar(er)
