GLHypertorus is not working for me.

But all the other runs fine.

RWO

@RWO

Crash? Freeze? or simply no rendering? (You'r a developer yourself, you know better than to just say "it does not work" )

ya you got me... it must be a library problem for its not loading at all. No preview and not possible change setting as its not loaded.

RWO

Here it doesn't work the GLHypertorius and the GLMatrix.. a simply black screen..

Thanks for this nice Screen blanker.
GLHypertorus doesn't work here too.

With some help from RWO I have found the very very silly error I made.

To fix GLHyperTorus simply rename the file from sys:Utilities/Blankers/GLHypertorus.blanker to sys:Utilities/Blankers/GLHyperTorus.blanker. (note the case of "Torus")

A new archive has been uploaded to os4depot which fixes this stupid spelling error, nothing else has been changed.

@nubechecorre

The only reason I can think of why GLMatrix would not work is because you are low on gfx mem.

In that case the blankers will just silently fail.

How much memory does it need ?

Hi Shadow,

The GLBankers as an idea are very cool.

I have a general question about the speed
of the blankers.

I've got a micro-A1c (256MB RAM) running OS4.1 and what puzzles me are how slow the
blankers run. I would estimate a fps of
maybe 5 fps (could be less, could be more).

I would have thought it was possible to
have fluid movement with these, rather
simple objects? Or is it just not possible
with hardware such as this?

Thanks,

@nubechecorre

The memory required depends on the screen resolution and depth you have chosen. If you are using 4.1 please try to disable compositing or try to lower the resolution the blanker use.

@Kotler

Are you thinking of a specific blanker or just in general?

They should be able ro run faster, but the current implemtation of MiniGL and Warp3D does not support transformation and lighting(T&L) in hardware, so MiniGL has to do all the transformations of vertices on the CPU, depending on which blanker you wish to use that is a heavy task.

Also some of the blankers are implemented rather na?ve and could run fast if optimized, but I have no intension to do so, I just port them

Some of the blankers just use a lot of CPU time. Try Cubenetic and try to adjust the texture size, you will discover it will slow down significantly, in this case the 3D object being rendered is very simple, but generating the texture is a lot of work.

Personally I prefer Flurry of the publically available blankers ;). It is both fast and look good.