Windows v6 beta test

[Admins]

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)

[TSAdmin]

Originally Posted by Stefan

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)

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: v6:

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: v6:

• 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.

[Admins]

Originally Posted by TSAdmin

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.

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

[DustyPorViva]

What?

[cbk1994]

Originally Posted by DustyPorViva

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).

[Twinny]

Originally Posted by DustyPorViva

What?

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

[_Zelph]

Originally Posted by Twinny

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?

Originally Posted by Stefan

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

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

[Twinny]

Originally Posted by _Zelph

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?

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.

Originally Posted by _Zelph

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

Why have you never mentioned this until now?

[TSAdmin]

Originally Posted by Stefan

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

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.

[Admins]

Originally Posted by DustyPorViva

What?

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

Originally Posted by TSAdmin

V5: v6:

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

[Rufus]

Originally Posted by Stefan

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.