Extreme logs and malfunctions

FIXED: Extreme logs and malfunctions

THIS HAS BEEN FIXED BY REINSTALLING .NET FRAMEWORK!! YAY

USING THIS:

• 
  
  
  
  
  Both of the lastest HB's have been freezeing/crashing whenever i attempt to start. Whilst they are frozen/locked up the log file gets HUGE
  i have some log files that are too big to even upload (up to 50mb) i will upload as many logs as i can that are not of huge size and a code insert of the repeating log htat is too large to upload. i will also upload them on an uploading website
  I feel this is very important and i have not been able to find anyone else with the same issue. i am using the HB 256 i believe in order to have a working HB i would like to know if this is ok.
  
  EDIT: i have locally uploaded with a zip archive
  
  ALSO, would like a confirmation 2.5.6 is still safe because thats what im using ATM

 

Hi, Bline,

We do not look at logs from 3rd-party sites. Please upload the logs locally. Thanks.

cheers,
chinajade

 

I would love to and understand why you would not, but these logs well exceed the local allocated file size. the logs are in excess of 10mb each. Could i put them into a code excerpt? how do you recommend i do this?

 

.Zip works great. The forums can easily hold 30-50 MB logs when zipped.

cheers,
chinajade

 

wonderful i will get right on it, appreciate the help

DONE

 

Hi again, Bline, and thank you!

[06:36:41.318 N] Error - Endscene hook failed: The type initializer for 'MainDev.RemoteASM.RemoteAsm' threw an exception.​

The development team is aware of the issue. The problem doesn't happen for everyone, and the DevTeam has been unable to replicate the problem on *any* of the development machines.

Please try these possible fixes:

• Raphus indicates that removing and reinstalling the .NET4 framework will clear the problem.
  Be certain to 'uninstall' .NET4 before you try to 'reinstall' it.
  
  
• Natfoth & Clanstyles have something else for you to try, if needed.

cheers,
chinajade

 

That what i figured, I will be trying to all of these fixes and let you know how it goes. Either way is 256 still viable?
again, i appreciate the help and advice.

 

the current build is 566 and thats what you should be using. i was recommending the beta last night because our developers thought that would resolve the issue in some cases. but then they traced it back to a .net framework issue.

you can download the latest build from here.
http://updates.buddyauth.com/GetNewest?filter=Honorbuddy

 

this has been fixed by reinstalling .net!! Yay