Quote: "There are several issues with the videobank transfer because of the way video files can be stored in many different files, including referenced by the entity, included in video scripts and now referenced as video textures, and I'm wary of making things worse by only transfering some files (which to me seems worse than none, as at least most developers know which videos are included in their game but may not notice if a couple are missing.).
Maybe the creation of a gamevideo folder which would behave in a similar way to the databank folder, in which all of the contents are transfered would help, but it would still put some responsibility on the developer to ensure all video files where included in this folder."
I'm not (hopefully) driving you to the edge with my previous comments. My take on it is that if scripts can copy huds and such properly, then I failed to understand why videos would not copy. So when I still see the "odd" issue, I have to take time to test it in v1.20 to ensure it is in fact an issue before I report it, which takes time away from developments. We have already addressed the skybox copying issue, and this was the only other "copying" issue I have found to exist for quite some time.
In any event, I have actually made a "gamevideo" folder and have added the path in the "file collection" section for the build per your suggestion. This way I can keep the videos used for the "video texture" separate from the actual videobank folder, and we can reference our notes per development to make sure the required videos are present. I recognize that the engine does get temperamental when we coders adjust something to eliminate an issue, so I will have to take what I can get.
Thanks. We do appreciate the effort you make.
There's no problem that can't be solved without applying a little scripting.
