Bline
New Member
- Joined
- Sep 30, 2011
- Messages
- 32
- Reaction score
- 0
FIXED: Extreme logs and malfunctions
THIS HAS BEEN FIXED BY REINSTALLING .NET FRAMEWORK!! YAY
USING THIS:
THIS HAS BEEN FIXED BY REINSTALLING .NET FRAMEWORK!! YAY
USING THIS:
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.
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
Attachments
Last edited:






