tsa add "Also it doesn't seem to remember positions/sizes of windows. For example on v5 I always have my Graal maximized (but not fullscreen). v6 doesn't remember this and starts not maximized. The playerlist and PM windows still open in weird positions (pm windows opening where your mouse x and y is) and it doesn't remember any resizes. " to your list :}

Added, though slightly altered the part about starting maximised/restored as this can be achieved through shortcut "Run Maximized" setting (On Windows) anyway.

Does V6 have a scheduled release date?

Nope.

Ok the F2 problem was more a problem of the script now reflow()ing the text, it should be fine now. Please check if the log window is also not slowing down things too much now.

A new version (5.261) has been packaged and will be released soon. Following modifications have been done:
- fixed mouse wheel scrolling
- fixed keys getting stuck when pressing the Alt key
- improved switch from fullscreen to window mode
- the setup is working, if possible test this by renaming Graal.exe to GraalSetup.exe (it has now a scripted folder selection for better compatibility or later use on other platforms)

Still wanting to check out how this beta performs... :D

I'm intrigued too, and I wonder how soon.

These all seem to be functioning correctly. There is another bug I have found which I thought had already been reported but going through all the pages I couldn't find it. Tile related.

V5: http://i36.tinypic.com/10yo2og_th.png v6: http://i34.tinypic.com/2s5y2rb_th.png

Notice in the V6 one, where there were pure black tiles suddenly became "Motion blurred". The post I thought had already pointed this out was relating to the Laser Tag lobby (Also on Era).

v5: http://i35.tinypic.com/dfr79_th.png v6: http://i37.tinypic.com/sdmz4o_th.png

• Also, if the client (v5.261) has been running for an extended period of time and you try to close it, the client stops responding. I'm not entirely sure exactly how long "extended period of time" is, but long enough to have a decent game play session and ready to close it.

Sidenote: I'm not entirely sure if this counts towards the "Slowdowns" you mentioned before when altering the Log Window, but it appears the memory leak is back in this version. After an hour of gameplay, the Graal.exe process got upwards of 250,000K - 350,000 K Memory (Private Working Set). This has only happened to me once as I haven't spent longer than an hour on it today, but it had at least stopped going anywhere near that high (Most ever was 100,000K) in previous betas.

Also, there are still a few things on the first page by Tig's first post that aren't fixed. Things like canresize, canclose, etc on external windows.

Have you checked if there was a lot of stuff in the log window?

What?

It's been happening for like a year, ever since external windows came out (at least on Mac, not sure if it's new on Windows).

I haven't checked, but after an hour of gameplay it would be easy to assume the log window gets pretty large during a single session, yeah.

Seems to be a problem of the script, like using fixed font size for calculation of the text.

The problem might be that some tilesets are containing transparent pixels, someone should fix the tileset if that is not intended.

Happens on pics1 lol.

It ain't Stefan's fault... he tried so hard but he's still a victim of these streets...

I was reading this in some update file:
but this is not working for me. If I hold the Windows key and press L to switch users, then I log back into my username, Graal will be frozen and I have to restart it. This is quite annoying because it's automatically doing this every time I go AFK and screensaver pops up. Also in Windows 7/Vista, if a window pops up asking for permission to use administrator privileges it will freeze Graal permanently until I restart it.

What?!?!? Public Beta?!?!? :)

Resize the window and it will work again :D

what???? where's the beta download link????????????


EDIT:

Stefan please make v6 not lag on windows 7 thanks :D

I always figured that was UN giving external windows a go without actually doing it properly then being lazy and not fixing it or at least making it internal again. Bad on UN that they didn't test it in a separate weapon.

That said, I know coordinates differ internally that externally as I always had to do a a (isexternal ? x : x) for positions

For a problem that has nothing to do with external windows, you sure mention external windows a lot.

Yes, bad on UN (The entire server and its staff, players, and affiliates) and not the one guy who has anything to do with the forums, who barely has enough time to log on to Graal in the first place let alone troubleshoot problems on a half-baked nothing-freaking-works-yet client. That's me. After all -- "fixing" a problem that only exists on a grossly unfinished client in closed beta is a great investment in time because it'll be 100% the same when it's public, right?

Obviously, portions of the script (Particularly the ones that deal with GUI controls) were done incorrectly because they, despite having worked for several years, do not exhibit identical behavior on a client with more bugs than the rich soil horizons of the Amazon.

Bonus: I couldn't even troubleshoot it if I wanted to. The PCID system is so broken that I wouldn't be able to log on to the beta client if I were so audacious as to restart my system.

Why yes, I'm bitter about the whole Graal thing at the moment. How could you tell? :D

It's because GuiMLTextCtrl.height is returning 0, which works fine on v5

Are you really this stupid? I have no idea about the staff structure of UN. I have no idea how many NATs work there. I have no idea how many are involved in any script. I have no idea who you are. Given this, I can only make the only generalization I know: the SCRIPT IS ON UN. This might sound crazy but what is publically shown on UN is a representation of the entity which is UN. I don't think about individualism when it comes to servers. Don't ***** to me, thinking I know the state of every staff member and their relevant project on UN. Also, if you really thought I was blaming the players of UN for this then you have some extreme bitterness which is blinding you something fierce. More likely you were just being a self-righteous ****.

My thoughts are simple: if trying out external windows, perhaps create a separate testing script so can leave the original intact. It seems somewhat logical to me that you don't add scripts you are testing/developing to every single player. The beta is closed for now, yes, but if the beta goes public with the same apparent issue?

I haven't had issues with GUIs moving from v5 to v6 except when external windows were involved. The forums are being drawn externally and have been for a long time. An assumption was made. Your sarcasm does you no favors here.

Why have you never mentioned this until now?

Look. I was being facetious there. That's my fault, although I tried to be over the top.

I was just playing on the fact that you, while making it clear that you didn't have a clue regarding the circumstances of the bug or who was involved with it, still had no problem in not only diagnosing it but calling people lazy too. This hapless finger-pointing irks me to no end and has gotten me screwed over more than once in "real life". You could have just said "I think it's a problem with external windows" instead of making a black sheep.

My thoughts are also simple. The v6 beta is the "separate testing script" and v5 is the "intact original". A 30+ page thread full of bug reports, half of which seem GUI-related, are why I won't have any qualms about the forums looking bad in a situation where people expect things not to work right in the first place. The forum script is not in testing and whether it's "under development" or not is subject to interpretation. The fact is that if v6 were functioning properly (defined by the behavior of GUI controls for the past numerous years), then the forums would look fine. The placement of all GUIs is external-agnostic in the sense that they all use client-relative placement.

If v6 is about to be rolled out and a tweak has to be made for them to look good, then fine. However, it'll be the developers who lose in that situation because they now have to retrofit their scripts to accommodate a bug in the new client that didn't exist before.

Did I miss a deadline or something? I think I'm less active here than you think.

The font size has always been like that on Linux, Mac and Windows OpenGL mode...

i would like to ask about any planned changes to v6's playerlist...because most people use the old external one and not the internal which we will all be forced to use on v6. reason i ask is because the majority of the actual playbase will feel alienated by this new forced playerlist that they didnt want to use before.

eh, which makes up for a vast minority of overall users.

OpenGL mode isn't even playable for me, I can't even test it.

What does that have to do with GuiMLTextCtrl.height returning 0 when it's not supposed to be? (Serious question)

Player profiles MLText (well pretty much all of them) controls like to mess up when the quotes are too long. The text should automatically reflow (or whatever resizing does that fixes it) when it's changed anyway.

Well, considering you have access to the v6 beta you know how it is currently working. Right now (aside from windows opening at bad x/y) it's working basically how the regular playerlist is working. I don't see the problems?

Double-clicking the tabs on the playerlist seems to open PMs, kind of annoying imo.

I'm asking if there are any changes planned to the playerlist that's on the v6 client.

Bug: You can't receive tile data from any layers above 0, see here for example:

http://forums.graalonline.com/forums...hp?t=134260466

Who all is in the private beta for V6?

We're pretty limited with what we can do to the playerlist since PM windows, for the most part, are not really editable. So there isn't really much else we can do to make it much better.

Option to let users use the old external one?

What's so majorly wrong with V6 that's preventing it from going to public beta?

Nothing is majorly wrong with V6 from what I've read... unless the "shaky player movement" bug still exists, I'd say it's ready for public use.

A new version will soon be released:
- fixed the title bar icon
- works better as plugin inside browser (internet explorer) again
- rotatable body sprites
- speed improvements with in-game text rendering
- particles support text and ganis again
- the showimg shadow color is now multiplied with the alpha value
- extended screenshot functions (makescreenshot2, makescreenshotgame, makescreenshotfull)

:o?