FBlit hates me

[NovaCoder]

I also get the garbage lines, but only if I switch it between "graphics" and "other" after WB is loaded... if you set it to "other" and reboot, hopefully you won't get those. Indivision won't have anything to do with the lines btw, it's just some kind of software bug.

Yep I covered this in my original post, I've found it's best to choose 'graphics memory' when using FBlit to prevent a conflict and let FBlit do it's thing.

[NovaCoder]

There's zero conflict if you take the extra steps as outlined in the FBlit docs, then icons are rendered in fastram instead. (This was a very common thing to do back when lots of people still used AGA.)

Anyhow, obviously don't do it if it causes problems, though it's always worked great for me.

*edit* Just to quote myself from the other day:



If you don't do the above, and choose "other memory" in WB prefs, you will get the nasty lines when opening drawers. Otherwise it should work fine - there will be a little speedup when opening drawers (icons are displayed faster), and icons will use very little chipram.

Hiya,

But doesn't Fblit work by copying everything that needs to be rendered to FASTRAM and then blitting to CHIPRAM only what needs to be redrawn each time?  If that is the case, it would make no-sense (eg no performance increase) to make another copy of your icons in FASTRAM.

[NovaCoder]

No, everything is not automatically rendered in fastram. In fact, by default FBlit runs in "include" mode, which means only tasks added to the include list are promoted. :rtfm:

 

Yeah that would be silly, but again there's a section in the FBlit docs pertaining to this issue as icons are NOT rendered in fastram by default.

It's simple: Open a bunch of windows, and watch your chipram disappear as the icons are displayed. Now make the changes as noted in the docs, set the WB prefs setting to "other memory", and voila - totally different story.

Ok, I'll give it a go

Update: Yep, that worked...thanks Damion.