What's the difference when I use OpenGL? I don't see any noticeable changes or any performance improvements.

The difference is, simply put, that everything is rendered using OpenGL instead of DirectX. There are no visible performance impacts on most computers, but it does use more processing time, and things like taking screenshots takes longer, which delays certain effects one could code (like the one Dusty made :3).

Also some GPUs support DirectX or OpenGL better than one or the other. On my current PC I can't really tell a difference, but on my older PC's openGL was unplayable, not only because of speed, but also because it had a ton of graphical glitchesl; especially relating to rendering text.

I blame that on Graal's implementation of OpenGL. It actually made games like Quake run a lot better than they'd have with DirectX.

Hmm, this only solves the display issue of it though. If I make the 4095 tile transparent, the cached tiles in surrounding levels are still blocking. :(

Yeah I do have a single core processor. Planning on getting an upgrade soon, hopefully. My laptop has a dual core, but the LCD light blew out or something, I need to replace the screen.

Going by task manager CPU percentage, V6 is performing significantly better for me with both OpenGL and DirectX now I've put back in a different graphics card. OpenGL has gone from 7 - 10% idling in an empty level on Classic (scripted systems considered) to .5 - 2%.

I have a GeForce 6100 nForce 405 video card. It's integrated, though. But it has run countless games without problems before. I think it may very well be my single core processor. Idk, I'm going to tweak some settings in the NVIDIA control panel. See if I can make it perform a little better with OpenGL.

One thing I found annoying was when you're in the middle of a PM or you have several PMs open, if the client gets disconnected all PMs will close.

No matter what server I logon, GraalControl seems to not have focus so I can't do anything until I click somewhere on the screen to give it focus.

Really frustrating and it only happens in v6. Worked around it on Maloria by running GraalControl.makefirstresponder(true); when the player logs in, but it's still an inconvenience with the client.

EDIT: Likely related to playerlist.

Similar issue when opening/closing the playerlist. It can easily be fixed through script but it's annoying if you're on a server that hasn't added a fix. When you close the in-game playerlist, GraalControl no longer has focus, and you have to click to give it focus.

I've been having some problems with a certain account name (presumably because it begins with a number) breaking attr[] values.
For instance, lets say I do this serverside:

When attempting to read this.attr[3] clientside, it would always be read as "1". Only by doing temp.s = @this.attr[3]; could I access the value.

At one point I also attempted to store a list of player IDs rather than accounts, this caused the problem of the attr[] somehow not synchronising to clients while working normally serverside.

Stefan must be a very busy man. V6 still isn't released and he makes such subtle changes/updates every 6 months...

Stefan, I have found another problem regarding layers. Logon Maloria, and warp to forest.nw. There's nothing wrong with the level itself, but the client seems to have some rendering problems with it and skipping tiles in the top layer randomly. If you resize the window a few times, it eventually renders the level correctly.

If you need to see how the level itself is designed: http://forums.graalonline.com/forums...hp?t=134266558