Recovered Filter bug

having burned up a motherboard and having built a new computer as a result and having subsequent, multiple problems getting this new computer to work, i've run into a somewhat odd little bug... or what seems to be a bug.

i just recently managed to salvage a harddrive that was giving me problems and which had a LOT of stuff on it, including some filter forge filters which i thought i had lost. on copying this filter over to the new install of filter forge on this machine and then trying to upload it to the library, i got a bug during the submission about having custom environments in the filter. i have no custom environments on this new install, but some of the presets might have still been recognized as having had some.

i also get this same message about custom environments when i call up the filter for use and a message saying a substituted stock environment will be used in its place.

all of that is fine and well, but this new install has NO custom environments on it. never did. so, i figured that one or more of the old presets was still looking for a custom. so, i updated all the presets to the new install and i still get the bug message when i try to submit the filter. i didnt wipe out and re-make the presets, i just ran each of them and then updated.

i dont know if this truly qualifies as a bug, but it sure seems like it. and if it can happen to me, it can happen to others.

so, besides giving this report, how do i remove this problem from the filter so i can submit it? is there a line in the filter i could edit manually with notepad maybe or is it even simpler than that?

Kraellin,
Are you sure that you change filter's main environment in Filter Editor, not in Main Window?

i'm attaching a copy here in the forum.

i tried running every preset and then updating it, thinking maybe that would erase the old part about the environments, but it didnt.

i tried deleting presets that were present from before i imported this filter onto my new machine. that didnt work.

i tried updating every preset from within the editor. that didnt work.

i made a copy of the entire filter from within the editor, ALL of the components highlighted and then did a 'copy'. i exited the editor and created a NEW filter and pasted the old stuff into the new filter. so, there were NO presets copied over, just the components and their connections. this worked. i get no message now about a missing lighting environment. but, i would have to make All new presets. so, it's pretty evident that whatever is going on here is/was resident in the presets portion of the filter.

i would like to save those old presets. i liked some of them. if there is a way for me to manually edit the errant file/preset with notepad, just point me to the right place and i'll do it....

ok, i just edited the file. it's fixed! works like a charm now i did a manual edit of the ffxml file. the old environment names were still in the file. i simply erased those names within the quotes and replaced them all with 'Church'. i then saved the file and closed it out and ran FF and the filter no longer gives me a bug message about missing lighting environments. i'm still attaching a copy of the file here so you guys can see it as well. this is an unedited copy with the original enviroment names still there.

but, the bug will still exist. if you make your own environments and use them in a filter and make a preset that uses one of these custom lighting environments and then manually copy this filter to an install of FF that does not have those environments, you'll get this error message that i got. so, there is apparently no routine for stripping out these environment names from the filter when that happens. and that's all that really needs to be corrected here.

i'm also guessing that you could just delete all of the presets or the ones that have the custom environment presets and it would work ok, but there's no way to update the preset so that it no longer has that old custom environment data within it.

ok, the file is 300 kb, so i cant attach it here.

Kraellin, thanks! We've fixed it. :afro: