Graal v4 Bugs - For Stefan/testers

[xAndrewx]

And cause more clientside lagg? I can't wait

[Ajira]

Originally Posted by xAndrewx

And cause more clientside lagg? I can't wait

Either your computer sucks, or your computer sucks.

[Admins]

- Using WinXP, if you lock the computer while the playerlist is opened (windows key + L), an errors occurs: "A Win32 API function failed"

I have no idea how to test that, on Windows 2000 that key shortcut doesn't exist. It would be good to make a screenshot of that.

Hmmm found some hints:

Error: "EOutOfResources," "Win32 Error," "A Win32 API function failed" or "The parameter is incorrect"
These errors are usually caused by a lack of system resources under Windows 98/Me.

Eventually it would be good to check if there is some strange resource problem when running Graal PMs. Zwr had problems with too many sound handles. You can use the task manager to check that.

[Ibonic]

How 'backwards compatible' is Graal v4 supposed to be with Graal v2? Because there are a bunch of things on the little bit of Classic that exists which don't work right in v3/4, and I don't know if I should report them as bugs or update the scripts.

About the 'locking' bug: maybe someone else can provide a screenshot, with the newest build the error message stopped showing up for me. But I still have the problem of the directx surface being black and the game freezing; Something similar happens when I use a screensaver, except the surface is left as the window color (default is grayish) instead of black.

And there's still a sound problem with my Audigy 2 ZS card as I described already. I can't hear any, other than what Graal v4 plays, regardless of volume or what other program I use to test it with. To add onto that: If I kill the graal4.exe process, I lose all sound period until Windows is rebooted. I haven't had this problem with any other game yet, including WoW which you said uses the same library etc.