Renguard client 1.0323 does has serious problems [message #262824] |
Sun, 03 June 2007 11:51 ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
tonyrolm
Messages: 132 Registered: July 2006
Karma: 0
|
Recruit |
|
|
I have used renguard since it's inception and never had the problems I am encoutering today with this version. The 1.032 Beta ran better than this release.
If you guys think it's an isolated issue with a few operating systems or computers I think your mistaken.
I don't know if you are all consumed with trying to stop the RG bypass issue but it has adversely effected it's basic function all together.
Something needs to be done to revert it back to performing the basic function before it's perception is ruined once again.
(I think it's too late for that)
I for one believe in Renguard but cannot handle the crash to desktop starting it, running it, connection lost issues, and constant frustration with it just staying online.
I even went as far as reverting back to the Beta 1.032 only to have the crashing update shoved at me.
PLEASE RESTORE THIS BACK TO PERFORMING THE BASIC FUNCTIONS !!!!!!!!!!
Thank You
Tony
http://www.BadDog-Server.com
|
|
|
|
Re: Renguard client 1.0323 does has serious problems [message #262828 is a reply to message #262824] |
Sun, 03 June 2007 12:34 ![Go to previous message Go to previous message](/theme/Renegade_Forums/images/up.png) ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
![](http://renegadeforums.com/images/custom_avatars/21090.gif) |
JohnDoe
Messages: 1416 Registered: May 2006
Karma: 0
|
General (1 Star) |
|
|
Yeah, we probably had 10 disconnects total in a 8 game clanwar series...we lost 2 games solely because Renguard kicked us at crucial times. It's really sad that you have to choose between Renguard screwing up your games or giving people the chance to cheat against you...
lol
|
|
|
|
|
|
|
|
Re: Renguard client 1.0323 does has serious problems [message #262835 is a reply to message #262827] |
Sun, 03 June 2007 12:53 ![Go to previous message Go to previous message](/theme/Renegade_Forums/images/up.png) ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
![](http://renegadeforums.com/images/custom_avatars/21327.jpg) |
futura83
Messages: 1285 Registered: July 2006 Location: England
Karma: 0
|
General (1 Star) Viva la Resistance! |
|
|
gamemodding wrote on Sun, 03 June 2007 20:28 | I was forced to run this "program" when I was forceRGed on my favorite server, but, I couldn't run it for more than half an hour before it disconnected and I got kicked. Problem caused by me? I think not. Renegade would be more alive if this "program" never existed.
|
What server is that?
And which n00b forceRGed you?
Cos if you start owning and one person does it, then pretty soon some other n00bs will see the oppertunity...
This is a signature. Reading this is wasting your time.
|
|
|
|
|
|
|
|
|
Re: Renguard client 1.0323 does has serious problems [message #262972 is a reply to message #262824] |
Mon, 04 June 2007 00:00 ![Go to previous message Go to previous message](/theme/Renegade_Forums/images/up.png) ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
![](http://renegadeforums.com/images/custom_avatars/4882.jpg) |
Goztow
Messages: 9734 Registered: March 2005 Location: Belgium
Karma: 13
|
General (5 Stars) Goztoe |
|
|
The current Renguard version does not have a publically availlable bypass.
Renguard now automatically reconnects when it dc's. However, brenbot didn't recognise this until yesterday when the newest 1.51 beta got released. It now doesn't kick you for a disconnect anymore but checks if you reconnect within x seconds.
I hope there will be a 1.50 update coming out with this modification. This should solve the DC-problem.
The "unauthorised renegade instance" can usually be solved by waiting 20-30 seconds before clicking 'renegade'. The LAN-exploit message showing up more often now: don't know.
You can find me in The KOSs2 (TK2) discord while I'm playing. Feel free to come and say hi! TK2 discord
|
|
|
|
Re: Renguard client 1.0323 does has serious problems [message #263087 is a reply to message #262972] |
Mon, 04 June 2007 11:47 ![Go to previous message Go to previous message](/theme/Renegade_Forums/images/up.png) ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
![](http://renegadeforums.com/images/custom_avatars/21090.gif) |
JohnDoe
Messages: 1416 Registered: May 2006
Karma: 0
|
General (1 Star) |
|
|
Goztow wrote on Mon, 04 June 2007 02:00 | The current Renguard version does not have a publically availlable bypass.
Renguard now automatically reconnects when it dc's. However, brenbot didn't recognise this until yesterday when the newest 1.51 beta got released. It now doesn't kick you for a disconnect anymore but checks if you reconnect within x seconds.
I hope there will be a 1.50 update coming out with this modification. This should solve the DC-problem.
The "unauthorised renegade instance" can usually be solved by waiting 20-30 seconds before clicking 'renegade'. The LAN-exploit message showing up more often now: don't know.
|
Thanks for the info...guess the clanwar server owners will need to wait for a new Brenbot.
lol
|
|
|
|
Re: Renguard client 1.0323 does has serious problems [message #263139 is a reply to message #262824] |
Mon, 04 June 2007 16:06 ![Go to previous message Go to previous message](/theme/Renegade_Forums/images/up.png) ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
icedog90
Messages: 3483 Registered: April 2003
Karma: 0
|
General (3 Stars) |
|
|
I am having the same exact issue that all of these guys are having. It is definitely NOT a problem that sits between the keyboard and the chair. Good to hear about the Brenbot update though. Let's hope it fixes the issue, because I seriously cannot stay in a server for more than 5 minutes without RenGuard disconnecting/crashing and being kicked by the server.
|
|
|
Re: Renguard client 1.0323 does has serious problems [message #263170 is a reply to message #262972] |
Mon, 04 June 2007 20:53 ![Go to previous message Go to previous message](/theme/Renegade_Forums/images/up.png) ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
tonyrolm
Messages: 132 Registered: July 2006
Karma: 0
|
Recruit |
|
|
Goztow wrote on Mon, 04 June 2007 00:00 | The current Renguard version does not have a publically availlable bypass.
Renguard now automatically reconnects when it dc's. However, brenbot didn't recognise this until yesterday when the newest 1.51 beta got released. It now doesn't kick you for a disconnect anymore but checks if you reconnect within x seconds.
I hope there will be a 1.50 update coming out with this modification. This should solve the DC-problem.
The "unauthorised renegade instance" can usually be solved by waiting 20-30 seconds before clicking 'renegade'. The LAN-exploit message showing up more often now: don't know.
|
Gozy:
All you are saying is that this is the fix for the clients exiting the game from Brenbot related servers.
I can see where this would correct an issue with Brenbot ejecting the player but I can't see how a Brenbot fix will correct the other problems 'clients' are having exiting to their desktop.
This post was to point out that the BASIC function of Renguard is no longer reliable and BHS needs to get the CLIENT side back to performing reliably.
So to indicate that Brenbot premature ejections issue will fix this CLIENT side is mis-leading.
You state that the "unauthorised renegade instance" can be solved by having a little patience and waiting 20 to 30 seconds.
Did you read that back to yourself?
This is a software application that requires the CLIENT to wait 20 to 30 seconds before executing it again.. Come on.
BASIC function as it relates to NOT crashing to the desktop, NOT losing connection to Non-Reguard and Renguard related servers. Not to mention whatever server bot maybe running should not even be a factor in the client side of this application.
I give all respect to BHS for trying to improve Renguard but at what point do you take notice of your latest efforts and realize that something is just not right with this version and fall back to a more stable release until those errors can be corrected.
I appears you just keep letting the broken version continue to frustrate people until they just had enough.
Once again I plead with you guy's/gal's at BHS to restore the BASIC function back into this program.
Tony
http://www.BadDog-Server.com
[Updated on: Mon, 04 June 2007 20:59] Report message to a moderator
|
|
|
|
Re: Renguard client 1.0323 does has serious problems [message #263191 is a reply to message #262824] |
Mon, 04 June 2007 23:28 ![Go to previous message Go to previous message](/theme/Renegade_Forums/images/up.png) ![Go to next message Go to next message](/theme/Renegade_Forums/images/down.png) |
![](http://renegadeforums.com/images/custom_avatars/4882.jpg) |
Goztow
Messages: 9734 Registered: March 2005 Location: Belgium
Karma: 13
|
General (5 Stars) Goztoe |
|
|
I don't disagree and want to specify that I'm not a member of BHS. I just try to help people with their problems.
You are right principally speaking but practically speaking the player doesn't care if it's brenbot or the renguard client solving the problem.
I don't say wait 20-30 seconds before you relaunch renguard btw, I say launch it and wait a bit before clicking 'renegade' (do NOT use the automatically loadup renegade - function). This will allow Renguard to scan all your files before running. No, it's not elegant but it does the trick for now.
You can find me in The KOSs2 (TK2) discord while I'm playing. Feel free to come and say hi! TK2 discord
|
|
|
|
|