Windows .exe Unable to connect to server - tile.null error

[Merelia]

Operating System, bit type: Windows 8.1 - 64 Bit
Java version/update, bit type: Version 7 Update 51 - 64 Bit
Launcher version: v1.3.4
Completed the troubleshooting guide (y/n): Y
Console log, pastebin.com link: http://pastebin.com/XVHDUEb0
Description of the problem: Can not connect to server. When attempting to do so I get disconnected by the server with the error message: "The following microblocks are not installed on this client: tile.null"
Server is the same version and no one else playing on that server has this problem.

 

[Tristam Izumi]

Unrelated to your server login problem,

[14:45:42] [INFO] MinecraftLauncherNew.setMemory:151: Setting MaxMemory to 1024

THIS will cause you headaches if you're using any of the 1.6.4 packs other than FTB Lite 2. You're using 64-bit Java, so you should be able to allocate more RAM than 1 GB.

That said, have you tried to force an update to redownload the pack? Just click the "Force update?" button under options then load the pack the way you normally do.

 

[Merelia]

Unrelated to your server login problem,

THIS will cause you headaches if you're using any of the 1.6.4 packs other than FTB Lite 2. You're using 64-bit Java, so you should be able to allocate more RAM than 1 GB.

It was still at 1gb since I had re installed everything. I usually run it at 6.

That said, have you tried to force an update to redownload the pack? Just click the "Force update?" button under options then load the pack the way you normally do.

And yes, I have done a Force update but the problem persists.

 

[Gabriel Theodoulos]

Several of our members are getting this error too.

Any thoughts on what needs to be tweaked?

 

[Tristam Izumi]

There might be some small config difference between what's on the server and client. As a temporary fix, can you try copying the config folder (or at least the microblock config file) from the server to your instance?

Be sure to back up your config folder first, just in case.

 

[Merelia]

There might be some small config difference between what's on the server and client. As a temporary fix, can you try copying the config folder (or at least the microblock config file) from the server to your instance?

Be sure to back up your config folder first, just in case.

We tried this, among some other things, but still no luck. The problem persists. =(