As soon as you try to analyse something, but works fine in 6235, don't know about the intermediate versions... Probably a similar problem with prime reporting content not playable in SF "browser" in 6238 when amazon tries to queue up the "play" button in the browser (although the prime downloader's working as that's extracting links in a different way)...
Announcement
Collapse
No announcement yet.
[6238] Peacock is doing the Puss-in-Boots error again...
Collapse
This topic is closed.
X
X
-
Can anyone confirm this? Peacock is basically the only module I use at this moment, and I'd hate to go through the bother of an update if I'm only going to be pussied out.
0xFeedBeef, are you located in the US and not using a VPN? Please attach your StreamFab.log of a 6238 Peacock session. Thank you.
-
Originally posted by Cats4U View PostCan anyone confirm this? Peacock is basically the only module I use at this moment, and I'd hate to go through the bother of an update if I'm only going to be pussied out.
0xFeedBeef, are you located in the US and not using a VPN? Please attach your StreamFab.log of a 6238 Peacock session. Thank you.
I don't see what the fuss about "upgrading" is- just install each new version in a separate folder, and you can flip between versions any time you like...
Comment
-
Originally posted by 0xFeedBeef View Post
Did you miss the part that it was working fine with 6235 despite the Puss-in-Boots with 6238? Sure, when I eventually have a reason to try 6238 again, or more likely 6239 when that gets released and I have a reason to try it. Maybe when you install 6238 over 6235 some component gets kept back that is missing in a fresh 6238?
I don't see what the fuss about "upgrading" is- just install each new version in a separate folder, and you can flip between versions any time you like...) the latest release.
As far as your comment -Maybe when you install 6238 over 6235 some component gets kept back that is missing in a fresh 6238?
Comment
Comment