The Blender exporter does export a texture now on both the Single Image and Image Sequence, however, when rendering an animation the frame of the Image Sequence hangs on whatever frame is currently selected in the Blender animation Timeline window. Like if it were on Frame 4, it exports only that image texture's 4th frame on all rendered animation frames. In summary, it does not advance the exported image of the image sequence in sync with the current rendered frame in the animation. Is this related or is it correct protocol to submit a new bug report? Please let me know. Thanks very much.

While doing more tests about this problem, I had a serious issue in Blender 2.79 / Linux 64bit with yafaray_v3

If I opened a file and Blender could not locate it, sometimes while manually changing from one frame to the next, I got this error message in Blender and all the objects in the scene dissappeared from the scene!!!

"DAG zero... not allowed to happen!"

During that test, I saved the .blend file and when I opened it it was completely empty! This is a very serious risk and could lead the user to lose all their work in the .blend file.

I don't know whether this is a Blender bug or a YafaRay induced bug, but it would take a long time to debug this problem and the risk is just too high. Therefore I will leave this feature request postponed for now, sorry.

I'd noticed that all the objects disappeared in the object hierarchy tree, but wasn't sure what it was due to. I am unfamiliar with Yafaray's exporter and it's interactions with Blender, so I cannot offer any possibly reasons why. I do appreciate the effort to get it working. If you decide to pick this up later, I would be glad to help test it further. Thanks.

However, I'm quite concerned with that strange problem in Blender (I had it with v2.79 in Linux 64bit). I've used some debugging programs on the YafaRay core code and I could not find any issues there. So, this could be either a Blender bug or perhaps some kind of weird bug caused by the Blender to YafaRay Python interfacing :-( This problem is very difficult to replicate and will be even more difficult to solve, and it's really a critical issue (users could lose all their work!!!!)

I've tested it with several simple scenes including the .blend file I originally submitted. I would feel more comfortable having other users test it as well before making it live, though it may be a 2.79 issue possibly unrelated to the texture sequence code changes? I saw there was another bugtracker submission for the vanishing scene data in relation to 2.79 as well. I'm using the patched "yaf_texture.py" from the above github link in this thread. I'm not quite sure how the scene vanishing happened before, but, as of now, I have not been able to get the scene data to disappear in 2.79 on Windows 10. Thank you.

The image sequence texture is working for basic texturing, so that's a thumbs up for that functionality. :)

I did some more testing and managed to get the scene data collapse again, but an ALT-Z undo reversed the scene data collapse. Again, I am unsure if this is an Exporter/Blender 2.79 incompatability or from the changes to the code for the image sequence texture. The data collapse happened when I rendered an image using F12, then clicked the world tab in the Properties editor panel. The time it happened before was right after I rendered an image then clicked something in the Properties panel for the scene as well. It seems to happen rarely and I cannot get the bug to trigger on demand. Has anyone reported any issues with the original unmodified code and Blender 2.79 yet? Hopefully this is helping. Thank you.