Quote:
Originally Posted by GooDobby
And i dont have DriveHud or Table Tamer only the converter
Yes, I'm aware. I'm just stating that we sell a lot more drivehud, and if there's was a specific issue w/ the catcher, we'd hear about it on 2+2, in our forums, etc.. and anything crash related is black and white and we hear about it in floods right away. Just look at the last time the client updated and there was a problem.
Any ways, like I said, I'm more than happy to help. I'm guessing it's something w/ their replayer then, which makes sense. BOL is already pretty resource intensive as is. I'll have to ask the developers when they are back in where the BOL log is and we can take a look at that to narrow it down.
For now, I wouldn't open their re-player obviously. And if you get any crash not related to it, then please send us another log. All logs are helpful in narrowing down a problem.
Like I said, there was no crash related to BOL CC commands in your logs. It captures and process all exceptions. It's happening somewhere else, outside of the card catcher.