Relevant log: http://dpaste.com/10018GN (The traceback does not appear in the crash report which just reports a generic NPE)

As you can see the server is trying to call several render methods which fails of course.

I can't see from the log if it's actually Funky Locomotion causing the crash or if it is triggering a block on the frame machine to do weird things.

Parts on the frame machine:

• RFTools: Builder, redstone transmitter/receiver, Timer, Matter Receiver
• Thermal Dynamics: Fluxducts
• Thermal Expansion: Tesseract
• Dimensional Anchors: Dimensional Anchor
• Railcraft: Void Chest
• Immersive Engineering/FMP: Sheet Metal Block strips
• ProjectRed: Red Alloy Wires, Toggle Latch

It doesn't seem to happen when I am near the frame machine. - If anyone can point me to a specific block among those that's known to cause errors I'd be happy to replace those with some alternative.

Version of FL is Beta 7, Forge 1558.

Edit: Replaced a few blocks with alternatives to see if I can narrow it down and crossed them out above.

OK, now I have ruled out everything except Tesseracts, which people have certainly used before with frames. Something must be seriously wrong with at least my install of FL, judging by the other reports here it's probably not just me...

Further notes: The frame machine is in a RFtools dimension, no idea if that matters.

i have exactly the same error, when i stay close of the frame machine dont crash the server but if i dont be 50 blocks nearby it crashes my server.

Actually, my analysis of the log was completely wrong.

What I assumed to be the culprit is actually properly caught by the reflection code.
The real bug seems to be in MoveManager.java:239 which has changed quite a bit since the last release half a year ago.

I changed the title accordingly.