Apply custom images to Ford Convers+

[DGAlexandru]

I did some resource allocation optimisations.. maybe from there
It does this with any image size or just with some of them?
I saw that sometimes if you generate a BIN Image and then go to and try to open it, it will crash, but couldn't find the reason.

[Drago]

I did some resource allocation optimisations.. maybe from there
It does this with any image size or just with some of them?
I saw that sometimes if you generate a BIN Image and then go to and try to open it, it will crash, but couldn't find the reason.

with every picture with me

[DGAlexandru]

I'm testing it only on Win10 64bit.. I5 gen3/4.
It crashes when opening an image or at RLE Encode or.. ?

L.E.:
In the deployment archive I forgot to add the needed libraries (DLL files) for image decoding / coding.
If the errors were generated by JPG images for example, then adding this files in the "installation" folder should do the trick.

I've replaced the archive with a new one that contains all the needed files.

[Gwe89]

I'm testing it only on Win10 64bit.. I5 gen3/4.
It crashes when opening an image or at RLE Encode or.. ?

L.E.:
In the deployment archive I forgot to add the needed libraries (DLL files) for image decoding / coding.
If the errors were generated by JPG images for example, then adding this files in the "installation" folder should do the trick.

I've replaced the archive with a new one that contains all the needed files.

when opening image mate and still does it with new archive
tried with other formats does same with all

[DGAlexandru]

Giving more details about the computer where you run CH would help us in finding out if the problem exists only on some environments... and so I could look for a fix.
I tested it on a Win 7 64bit also, Core2Duo - no problem.

Big images, 15-20mb each when in PNG / BMP format.. no crash, so it doesn't seem to be a memorry allocation problem / boundary.

[Gwe89]

Giving more details about the computer where you run CH would help us in finding out if the problem exists only on some environments... and so I could look for a fix.
I tested it on a Win 7 64bit also, Core2Duo - no problem.

Big images, 15-20mb each when in PNG / BMP format.. no crash, so it doesn't seem to be a memorry allocation problem / boundary.

[Gwe89]

Works on my other pc?

[Drago]

Windows 7 x64

[DGAlexandru]

OK .. it really was a problem on how it was allocating memory for some buffers.
I was able to find this by testing the application on a windows machine where it was crashing and so I could have a closer look on the error (0xC0000005 at address memory 0xFFFFFFFFFFFF) and some debugging information.

I updated my previous post with what I believe is a repaired version

[DGAlexandru]

By the way .. did any of you found useful the function that searches for the image offset in main firmware file?
Load VBF / BIN file 1 that contains images.
Load Main1 FirmWare and then let it search for those offsets.

This way if you want to replace a image with another by specifying in Main FW the new offset you know where to look for it. Of course, not all the combined bytes it finds are used as pointers to where the image is, but it is a start. And for sure if it only finds one mention, then that is all you need to change.