Aquamark wrapper won't run on old GPUs

[Antinomy 208]

Don't see a thread on this case but current Aquamark wrapper doesn't work on old GPUs. Tested on Prosavage DDR, SiS 315 integrated and Mirage.

The benchmark itself works as usual. The wrapper shows a black screen for a second after you hit the run button and immediately pops back to main screen. Systeminfo, priority and the rest don't help with this one.
315.zip is SiS 651 chipset. Aquamark.zip is SiS 661 chipset.

Aquamark3.zip 315.zip

Edited June 12, 2020 by Antinomy

[ludek 10]

I also have a problem with Aquamark. First, It doesn't start on my i845 integrated GPU.

But, after playing around with priority, aquamarka does start. Then I have to start aquamark and my result is shown, but after this, the hwbot aquamark "launcher" app is closing... and it's frustrating, because I wait 30 minutes (lol old gear) and there are no results! Is there any solution?

[Leeghoofd 3206]

Nope only solution is not to bench aquamark, there's no more support for the wrapper.... yet we need it for security reasons to validate the benchmarks output

[ludek 10]

So to meet HWBot rules I can't simply do a score "as in the old days" without "wrapper" app? Is there any clue what happens to the wrapper? Is this to do with low memory count? Or some software timmings?

[Antinomy 208]

17 minutes ago, ludek said:

Is there any clue what happens to the wrapper? Is this to do with low memory count? Or some software timmings?

I believe that at some point (after another update) the wrapper enforced using Aquamark's default settings which are AF at least and maybe some more. But when a hardware can't support these, Aqua would run with downgraded (automatically) settings. And the wrapper detects this downgrade and just throws it out.
So I can run Aqua without wrapper but it'll exit immediately using it.

[klopcha 2]

Then you need to remove all the accrual of points for Aquamark.

[GENiEBEN 20]

Let's see if the project is still compilable, especially since Qt support for XP has dropped a long time ago.

What is the Crew's take on this, should I add a 'legacy' option for such hardware, clearly marked in UI?

[Leeghoofd 3206]

That would be a good option.

If possible able to fix the datafile size too, users either had to run with systeminfo off and/or reduce the screen resolution before saving. Otherwise the API would reject the file

[Antinomy 208]

1 hour ago, GENiEBEN said:

should I add a 'legacy' option for such hardware, clearly marked in UI?

IMHO it would be best to behave like original Aquamark - set default settings on auto but when hardware can't make it, lower down to it's capabilities. So you can't lower settings below default for capable hardware (like things are now) but so you can run it on older hardware with lowered settings by Aqua itself.

I'll provide any help I can to fix this, just PM me.

[ludek 10]

I have never played with 3d benchmarks, (but now I am). I remember old aquamark benchmark. It is one of good old one, that run on GeForce 2 or pentium 3 integratedGpu.

I didn't know about any work-arounds like resolution changing before save the result. It would be great if the Aqua wrapper project was resurrected.

Edited April 9 by ludek

[GENiEBEN 20]

9 hours ago, Antinomy said:

IMHO it would be best to behave like original Aquamark - set default settings on auto but when hardware can't make it, lower down to it's capabilities. So you can't lower settings below default for capable hardware (like things are now) but so you can run it on older hardware with lowered settings by Aqua itself.

I'll provide any help I can to fix this, just PM me.

I see, this does remove a layer of security, will see what compromise I can make. Also, do you happen to have a list of common issue reports? I can remember the issue with cyrillics in paths and the file size (can default to lower quality and also check result file if it goes over a threshold), anything else that comes to mind?

[Antinomy 208]

26 minutes ago, GENiEBEN said:

anything else that comes to mind?

No, not to me.

 

26 minutes ago, GENiEBEN said:

this does remove a layer of security

Well, the point is to make it's behaviour like the original Aquamark. So settings don't get downscaled on modern hardware, only on old ones. Like the original Aquamark was.