Make sure you have the latest version of RM, the latest "Recommended" build of Forge and no other mods installed before proceeding. All of those issues (except the same name thing) sound like things I've previously fixed. Though I guess shaders could have broken it again, wouldn't be the first time that happened.
Please post the contents of the fml-client-latest.log
file inside the logs
folder inside your .minecraft
folder to some pastebin site and link to the post here.
Note that this log will only contain information on the last time you started Minecraft, not any previous runs.
Please also upload the replay (either to the Replay Center or some other file hosting site) and link to it so we can try ourselves. It'd also be handy if you can provide concrete steps using which you're able to reliably reproduce the bug (e.g. open replay, pause, jump to time X, jump to player Y, play for 30 secs, player Y disappears).
Thanks for the quick response!
After updating to the latest (recommended) forge version and removing all other mods from the folder (including optifine which didn't allow me to try this out with shaders) the issue with the disappearing player seems to have been solved in the replay viewer. And I say only in the replay viewer because every time I tried to render out a camera path the game crashed at the exact moment I clicked on the render path selection button. I thought this was a problem with shaders before but this time I didn't have any. And it didn't happen every now and then, it happened every time I tried to render something. So I can't tell if the player shows up in the render yet but here is the stuff u asked me to share:
Link to the text from latest.log as fml-client-latest.log didn't seem to work with the latest version of forge.
Also, I uploaded it to the replay center where you can find it under the name of "Closing Ceremony" it's by TotiGonzales.
Here is the crash report too.
Thanks for the help!
Toti