Mikey, not sure whether you're asking about the benefit of my question or Seldon's comments. Anyhow, in my case, I want to encrypt a .PNG file as it is saved to the disk so that any graphics program doesn't recognize it allowing easy modifications etc.
The benefit of being able to do this is that a file can be loaded from the disk into a memory bank and manipulated into a recognized PNG file in the process. Following this, the image can be loaded as an image into the video memory using a LoadImage command from a memory bank.
The reason why I want to avoid bundling files with my executables or as pak files is that the game is allowing custom addon packs (and there's over 100MB of graphics to begin with). My car / circuit editors would then export the images to the encrypted file format. Another reason for avoiding so called "packers" is that I believe they uncompress the files temporarily which means that if the computer crashes, the files may be left exposed (I think).
Stefan
The benefit of being able to do this is that a file can be loaded from the disk into a memory bank and manipulated into a recognized PNG file in the process. Following this, the image can be loaded as an image into the video memory using a LoadImage command from a memory bank.
The reason why I want to avoid bundling files with my executables or as pak files is that the game is allowing custom addon packs (and there's over 100MB of graphics to begin with). My car / circuit editors would then export the images to the encrypted file format. Another reason for avoiding so called "packers" is that I believe they uncompress the files temporarily which means that if the computer crashes, the files may be left exposed (I think).
Stefan