DESCRIPTION:

FUNGI this a tool for finding textures and images files into game archives and open raw image. With it you can open file, enter width, height, offset to image, zip algorithm and image codec and get image preview. If in prewiev window you can see image, this image can save in any formats from this list: BMP, PNG, DDS, JPEG, WEBP, TGA, TIFF and ICO. Also, you can use this tool for research image format and creation instruments for open and saving other image format. In this version supported 60+ image codecs, and This list will be expanded in the future.

HOW TO USE:

• Open the file in which you want to find a texture or RAW image. For example, let's select the file example1.dat, stored in the example folder in the root of the program.                         
  
• If the image cannot be recognized automatically, you will see the message “Not enough bytes to image creating!”. This means that you must select the image settings manually. 
  
• First, you need to try to find the length and width. You can roughly understand the length and width from the file size, and thanks to the message from the previous paragraph, we can understand that the image is most likely smaller than the default 512x512. We are trying to set the size to 256x256. Nothing much has changed, but in the process of entering the length and width parameters, you will notice that the contents of the file displayed on the screen do not look much like images, it is just a set of multi-colored ripples. If the codec matched the default RGBA, or was close to it, we would see a distorted image in which the outlines of what we were looking for would be guessed. In this case, we can assume that the codec is very different from RGBA and the like (RGB, BGR, ARGB, and so on). We are trying to set DirectX in the “Bits per pixel” section. 
  
• Now something has appeared. On the screen, among the stripes and squares, a distorted image of a mushroom can be discerned, which means we are close to the goal. What else can you notice? At the very beginning of the image, you can see a black stripe. This means that in addition to the image itself, there is some other data at the beginning of the file, most likely these are image parameters. Let's try to open it in a HEX editor. 
  
• You can notice that from byte 0x70, something similar to a description of pixels begins, and above it, we see mostly zeros. Most likely, 0x70 is the beginning of the image data. Enter this value in the “HEX offset” field. 
  
• The black stripe is gone! Let's now try to select a codec. 
  
• By simple search, we can understand that the codec we are looking for is BC3_UNORM. 
  
• Now, you can click on the “SAVE” button and save the image in a format convenient for you.
  
  

Now try to determine the file format example2.dat and example3.dat yourself Hint: You will also need to use the “Change Image” option to search for the image in example2.dat so that the image you are looking for is not upside down. The output should be this image: 


In order to get an image from the example3.dat file, you will already need to determine the data compression method. To do this, you need to start entering the name of the compression algorithms in the “ZIP method” field. Since it is almost impossible to understand which of the almost 1000 algorithms a file was compressed without some information about the compression method, I will tell you that this file is compressed using a method whose name begins with the Latin P. In the third example, the compressed file is a regular BMP file, therefore, as soon as the compression method is correctly determined, the program itself will receive all other parameters from the desired image.

Source code of this program you can find here: https://github.com/gmh4589/fungi

WORK IN PROGRESS:

Plane to add 50+ image codecs, among wich YUV, AYUV, 2BPP, KTX and other, add support for images with a palette, with the ability to select the number of colors and customize each color, add internal hex viewer for easy offset lookup and other.