1. OSBot Version (do NOT put "current version", be specific)

OSBot 2.4.105

 

2. A description of the issue. Include relevant logs.

https://gyazo.com/e11940a6258e1efd534fcf050dc49f25

 

3. Are you receiving any errors in the client canvas or the logger? 

None.

 

4. How can you replicate the issue?

It happens when I start the Logger or Options. Like this: https://gyazo.com/4ab14b59cd63fedd4b07f4064bbd67fe

 

5. Has this issue persisted through multiple versions? If so, how far back?

Yes 2.4.101 did it aswell.

 

 

 

This is caused by G-Sync monitors apparently. 

This is caused by G-Sync monitors apparently. 

Will test disabling G-Sync I'll let you know the results

@Alek so it seems that my Monitor has no G-Sync 

https://gyazo.com/b21a3b0ffcb65d240640ef42f0a3c18d

This is caused by G-Sync monitors apparently. 

 

Got the same problem, not notice'd if before the update to .105

 

got it now on 2 proxy's

Edited December 19, 20169 yr by jappa

It's really hit and miss for some people, did you try starting OSBot in Low Resource Mode through CLI?

 

@jappa - It's not specific to the .105 release, even if you just started getting this issue after .105. 

It's really hit and miss for some people, did you try starting OSBot in Low Resource Mode through CLI?

 

@jappa - It's not specific to the .105 release, even if you just started getting this issue after .105. 

 

tried litterly everything, proxy seller also checked the proxy's and confirms that its a problem with osbot, and that there is nothing with the proxy's

 

 

 

edit: swapped the 2 not working proxy's for other, so cant test anything anymore

Edited December 19, 20169 yr by jappa

It's really hit and miss for some people, did you try starting OSBot in Low Resource Mode through CLI?

 

@jappa - It's not specific to the .105 release, even if you just started getting this issue after .105. 

Will try with CLI I'll report back

@Alek Yep Low Resource mode works. There is no debugger in LR mode, to check positions etc (never used this before).

Will try with CLI I'll report back

@Alek Yep Low Resource mode works. There is no debugger in LR mode, to check positions etc (never used this before).

 

Thanks for letting me know, everyone is the past who has reported this issue was never able to figure out how to use low resource.

Thanks for letting me know, everyone is the past who has reported this issue was never able to figure out how to use low resource.

It's not hard after you provided such a good explanation with the CLI picture and post. I hope to one day become as good as you to be honest hehe

 

EDIT: This can be closed aswell I think?

Edited December 20, 20169 yr by Xerifos

actually iv'e been getting this error with my proxies too. only after 105 although it only seems to happen every now and then.