Attempt to unpersist an external Lua function

I tried to look up the error on Google, but it seems to be Filter Forge specific - what does it mean?

Ok - the error is not related to the initial include call:

in Map Script script I tried:

Code
dofile("C:\\Users\\Sphinx\\test.lua");

where "test.lua" contains:

Code
function prepare()    -- This function is called once,    -- before the rendering begins.    -- Use it for querying non-mapped    -- inputs and precalculation. end; function get_sample(x, y)    -- Image generation code goes here.    local r = x    local g = y    local b = (x + y) / 2    local a = 1    return r, g, b, a end;

This works just fine. I guess the error is related to actual script code in my external files. However the scripts used to work, so I need to know what that (new?) error message is about..

I can't do that as the whole "application" use several lua libraries .. to much to set up for a simple test case.

I just want to know what triggers that error message in general (and what it means.. "unpersist" is not very clear to me). Then I can debug the actual problem myself...

Alright I located the problem - it is related to a change in global variable visibility..

The testcase is rather simple:

1. Create a new lua file, test.lua, with the following content:

Code
function prepare()    t = 1 end; function get_sample(x, y)    --t = 0.5    return t,t,0,1 end;

2. Create a new filter and drop a new Map Script, enter:

Code
dofile("C:\\test.lua")

Or the path to where you put the test.lua file (remember "\\" as directory delimiter format, e.g. "C:\\Users\\GMM\\test.lua"

FF will now complain because global variable t is not registered properly (this used to work earlier).

Comment out t assignment in prepare and enable t assignment in get_sample - now it works.


The unpersist error is just a more complex version of this problem. I can send you a testcase for the unpersist error (I can't attach here due to file attachment restrictions), where should I send to?

You should have a complete example in your inbox now

The developers are still unpersisting your test case We'll try to fix this by the release of the 3.0 beta.

Should be fixed in 5.011 – please check.