I have found the following issue. Could anybody help here?

1) I create a background image and initialize the screen -> OK
      g_BGTopMap = Screen.LoadTileBG()
      g_BGTopMap:LoadPalette( "./img/splash1.pal" )
      g_BGTopMap:LoadTiles( "./img/splash1.raw", 256 )
      g_BGTopMap:LoadMap( "./img/splash1.map", ( 256 / 8 ), ( 192 / 8 ) )
      Screen.Initialize( SCREEN_TOP, g_BGTopMap )

2) Later on, i want to change the background screen and i do: -> NO OK
      g_BGTopMap = Screen.LoadTileBG()
          g_BGTopMap:LoadPalette( "./img/snowBG.pal" )
          g_BGTopMap:LoadTiles( "./img/snowBG.raw", 256 )
          g_BGTopMap:LoadMap( "./img/snowBG.map", ( 256 / 8 ), ( 192 / 8 ) )
      Screen.Initialize( SCREEN_TOP, g_BGTopMap )

3) But if i use a new variable, it works!!: ->OK
      g_BGTopMap2 = Screen.LoadTileBG()
          g_BGTopMap2:LoadPalette( "./img/snowBG.pal" )
          g_BGTopMap2:LoadTiles( "./img/snowBG.raw", 256 )
          g_BGTopMap2:LoadMap( "./img/snowBG.map", ( 256 / 8 ), ( 192 / 8 ) )
      Screen.Initialize( SCREEN_TOP, g_BGTopMap2 )

Why i cannot reuse use the old variable? do i have to free it before reusing it? how?
I does not make sense to use different variables all the time (and consuming scarce memory...)

Thanks in advance
Angor

Tested and:
a) just reseting the variables (=nil) does not work -> black screen
b) reseting the variables and forcing garbage collection -> it works but a noticeable screen blink (screen goes  black and then initializes with the second image)

So, all clear to continue using multiple screens for the Snowball battle game (the new version i am working on is far more attractive!!). Thanks a lot for the fast and effective feedback!
 
It would be nice in the future to have a more elegant solution (than the garbage collection). Examples:

- to add a .free() function to the screen variable or
- to allow overwite of screen variable palettes/tile images/maps with the currently existing funtions

Angor

Tested both in Dualis and hardware

1)  By using the Screen.LoadTileBG() funtion only the first time, the black screen does not longer appear. There is still however a noticeable image blink in the change between the old image and the new one

2) The blink can be minimized greatly by adding a Screen.WaitForVBL() just before the change.

Thanks for the feedback!!

Angor

Fade out can be done just by modifying the palette's RGB value (unfortunately, there isn't one with TileBackGround yet).  I can add palette access/fade function in the future versions.

Another thing I can do is to separate out the cf/gbfs read access from palette/tile/map setting, that should reduce the "blink" in theory.

Thanks,
Waruwaru