Using the shader workaround mentioned in "Game fails to pass Title Screen", I am able to begin playing the game. Unfortunately the game runs poorly, but it does not appear to be a normal performance issue. The intro text crawls onto my screen one character at a time, as I would expect (since I played the Windows version) but the time between the characters appearing is about a second per character. Could be strange performance issue, but maybe you used a platform-specific timing or sleep function somewhere? Anything I can do to help provide more info for you? It seems to use 100% of one of my cores but doesn't do much with it.

You need to profile the game with a profiler and take a snapshot to see what's taking up the most CPU.

I use Visual VM. Here's a long-winded tutorial I made about it a while back: https://www.youtube.com/watch?v=UFRTSeG2e5c

The game did not behave well (profiler never ran, or game crashed) with the Apple Profilers. I can try VisualVM but I'm not holding my breath.

As expected, it doesn't behave terribly well, but I can see that 92.7% of the cpu time is eaten by org.lwjgl.opengl.GL11.nglDrawElementsBO. It doesn't give me a call trace. The actual profiler never is able to attach to the game.

Oh, it was in a different thread. I should have read more carefully. :)

Intriguingly enough: after editing some of the shaders to allow me to load in, I'm able to get the game to run with improved performance as long as I stick to the integrated graphics, whereas the dedicated GPU appears to still show the same performance issues. SolarLune, I am going to try to profile this a little bit more later. Is there a hidden profiler I can show in your game?

There is one in BDX, but I can't enable it during gameplay (it's either on or off at launch). I could just have it on by default, but i think the better approach is to add the ability to turn it on or off during gameplay so I can collect some more precise information from you both. Thank you for your patience!

https://drive.google.com/open?id=0BzWL7E-FTHJhUkZIcDRKbHVWU1E

https://drive.google.com/open?id=0BzWL7E-FTHJhbGtmWDYtczlodEE

https://drive.google.com/open?id=0BzWL7E-FTHJhZUZrTTNVNFpLeUk

https://drive.google.com/open?id=0BzWL7E-FTHJhenVGdWVrN2xaTEk

Here are four screenshots. In order they should be:

In game - Dedicated

In game - Integrated

Title - Dedicated

Title - Integrated

I have some better calltraces, including OpenGL calls. Sorry I couldn't hunt this down earlier. The end of the semester got kinda rough. The calltraces are currently locked inside an Apple ".trace" file. I need to analyze them a bit more.

Huh, none of those screenshots lead to anything for me - are the links correct?

Anyway, I fixed up the profiler a bit and changed some things around that hopefully can resolve some things (or at least push in the right direction). I'll see about updating the demo tomorrow.

Hey, I updated the builds again - if someone who uses OSX could try this one, that'd be helpful.

If you press the 1 key, you can see the profiler and see the GPU wait time (if it's greater than 0, then that means that the rendering process is slowing the game down, which is in line with what you mentioned, rainybyte). Also, I adjusted the lighting a bit - try turning off advanced lighting to improve the framerate, if the game runs slowly.