80kb 1024x768 jpeg backdrop draws 2megs of RTG mem???

[Amigaz]

Have had some Warp3D problems recently but discovered that the cause has been that I'm using a wallpaper on my desktop, the size and complexety doesn't seem to matter..it eats 2 megs of my RTG memory which results in that no Warp3D stuff will run
Without a backdrup I have almost 5 megs free mem according to availp96 and with an active backdrop it drops to 2.5 megs

This is ridiculous  :crazy:

[Thomas]

1024 x 768 x 3 = 2,359,296 Bytes (2.25 MB)

JPEG file size does not matter. In memory the gfx data has to be uncompressed in order to be displayed.

Bye,
Thomas

[Amigaz]

Thomas wrote:

1024 x 768 x 3 = 2,359,296 Bytes (2.25 MB)

JPEG file size does not matter. In memory the gfx data has to be uncompressed in order to be displayed.

Bye,
Thomas

Thanks for the tech. info, Thomas  :-)

A1200+Mediator=8mb RTG memory = sucks!  :-(

[keropi]

mediator eh?  :-P  :-P  :-P

[Amigaz]

keropi wrote:
mediator eh?  :-P  :-P  :-P

arghhh...gimme a DCE BPPC  :pissed:

[adolescent]

AMIGAZ wrote:
A1200+Mediator=8mb RTG memory = sucks!  :-(

Why not turn on the MMU and use all the memory?

[Karlos]

AMIGAZ wrote:
This is ridiculous  :crazy:

No, it's perfectly normal. Of course, the alternative is that the image is stored in Fast RAM and freshly exposed bits of it copied to the workbench screen's framebuffer as you move windows etc around. Then you'd complain it was too slow at redrawing ;-)

[Amigaz]

adolescent wrote:

AMIGAZ wrote:
A1200+Mediator=8mb RTG memory = sucks!  :-(

Why not turn on the MMU and use all the memory?

Then Warp3D PPC stuff won't run..  :-(

[derringer3]

After boot my os3.9 up, the system eat 15MB. I use 1024*768@16bit,and some stuff (blitzkick) wich eat some too. But since I have 128MB fastram its siply don't care.

Anyway try  reinstall. I have the same problem, with different mediator drivers.

[itix]

No, it's perfectly normal. Of course, the alternative is that the image is stored in Fast RAM and freshly exposed bits of it copied to the workbench screen's framebuffer as you move windows etc around.

But is it good idea waste 1/4 of precious VRAM to the image?

[adolescent]

AMIGAZ wrote:

Then Warp3D PPC stuff won't run..  :-(

Bummer.  I guess no background for you.  :-D

[Amigaz]

adolescent wrote:

AMIGAZ wrote:

Then Warp3D PPC stuff won't run..  :-(

Bummer.  I guess no background for you.  :-D

 :boohoo:   :-D

Life can be a {bleep}  ;-)

[Amigaz]

itix wrote:

No, it's perfectly normal. Of course, the alternative is that the image is stored in Fast RAM and freshly exposed bits of it copied to the workbench screen's framebuffer as you move windows etc around.

But is it good idea waste 1/4 of precious VRAM to the image?

Yeah, glad I have an A4000 mediator system too which I have 16mb to play with instead of 8  ;-)

[keropi]

it is god's way to punish u Amigaz, for not being online to chat... LOL

[Karlos]

itix wrote:

No, it's perfectly normal. Of course, the alternative is that the image is stored in Fast RAM and freshly exposed bits of it copied to the workbench screen's framebuffer as you move windows etc around.

But is it good idea waste 1/4 of precious VRAM to the image?

Of course not. That's why I prefer a flat-coloured, 16-bit workbench screen ;-)

I should point out that these particular shortcomings are all down to the RTG implementation. Let's face it, under OS3.x Picasso96 and Cybergraphics are both nasty hacks necessitated by the fact that graphics.library is, frankly, diabolical from the point of view of hardware abstraction.

It isn't exactly anybody's fault, it's just the way things panned out.