Checksum is incorrect in "inserted logo.vbf"
Apply custom images to Ford Convers+
Re: Apply custom images to Ford Convers+
You do not have the required permissions to view the files attached to this post.
Re: Apply custom images to Ford Convers+
How do you calculate checksum? For only everything what is after the header or for the whole file?
Re: Apply custom images to Ford Convers+
Yes the data part is after header + 8 bytes and then before 2 last bytes, see https://mk4-wiki.denkdose.de/en/artikel/vbf/start
You can put the vbf here http://movinground.org/content/convers-lang/ and then just download it and the checksum will be recalculated.
You can put the vbf here http://movinground.org/content/convers-lang/ and then just download it and the checksum will be recalculated.
Re: Apply custom images to Ford Convers+
Thank you! Yes I know he did but I don't want fish, I want to get a fishing rod haha 
Understanding it is the point here like for everyone of us i think. Thank you for explanation. I know what I did wrong before and why my checksum was different.
Understanding it is the point here like for everyone of us i think. Thank you for explanation. I know what I did wrong before and why my checksum was different.
Re: Apply custom images to Ford Convers+
Ok now I feel more comfortable about everything, one more question as I can not figure that out.
Do I only save a pallette in BGR or also a picture should be in BGR saved?
Pictures looks like s******* on convers but I have seen for someones pictures are much better.
Do I only save a pallette in BGR or also a picture should be in BGR saved?
Pictures looks like s******* on convers but I have seen for someones pictures are much better.
Re: Apply custom images to Ford Convers+
Hi is the source code available for the CH
-
DGAlexandru
- Pro
- Posts: 364
- Joined: 04 Aug 2019, 22:47
Re: Apply custom images to Ford Convers+
Convers+ IMG Hacker v1.3.3
### Added
- Option to use a different size for the image in "Convert Image" (max selectable size is still 400 x 198 pixels). If you use option 1 or 2 for aspect ratio, one value might get changed in order to keep aspect ratio. The same values (width and height) will be automatically used for "Save Image" (BIN or VBF).
### BUG
- It seems that for images that have a width that is not a multiple of 4 it generates bad output. This BUG was present from beginning, but because there were no option to generate a different image size than 400x198 pixels it would not be seen. I've spent some hours trying to figure it out, but couldn't find the problem. If in the generated file (BIN or VBF) we increase the width in order to be a multiple of 4, CH can decode the image correctly. The images that are originally present in C+ FirmWare and have a width that isn't a multiple of 4 can be decoded correctly, so it's an encoding problem in CH.
When you import the image that you want to convert you also have the option to choose the aspect ratio: 0 - don't keep aspect ratio, resize the image to the chosen values.
1 - keep the aspect ratio within limits - it tries to use one of the chosen values as long as the other one, upon resize with aspect ratio, is still within the max. values: 400x198 pixels.
2 - keep the aspect ratio with no limitation - if the limits are breached, it won't be usable in Convers+, but you are free to test it
Example:
Input image is 400x198. You want it to be 200x198 pixels:
If you select 0 for AS the result image is 200 x 198 pixels.
If you select 1 or 2 for AS the result image is 200 x 99 pixels (200 = 400/2 so 198 is also divided by 2).
Input image is 200x198. You want it to be 400x198 pixels:
If you select 0 for AS the result image is 400 x 198 pixels.
If you select 1 for AS the result image is 200 x 198 pixels (height is 198 max, so if it keeps the AS then width remains 200).
If you select 2 for AS the result image is 400 x 396 pixels (400 is 200*2 so height will be 198*2).
This version is compiled with a different compiler version than the old versions of CH / IPC Updater so in the attached archive you also have the need library files.
### Added
- Option to use a different size for the image in "Convert Image" (max selectable size is still 400 x 198 pixels). If you use option 1 or 2 for aspect ratio, one value might get changed in order to keep aspect ratio. The same values (width and height) will be automatically used for "Save Image" (BIN or VBF).
### BUG
- It seems that for images that have a width that is not a multiple of 4 it generates bad output. This BUG was present from beginning, but because there were no option to generate a different image size than 400x198 pixels it would not be seen. I've spent some hours trying to figure it out, but couldn't find the problem. If in the generated file (BIN or VBF) we increase the width in order to be a multiple of 4, CH can decode the image correctly. The images that are originally present in C+ FirmWare and have a width that isn't a multiple of 4 can be decoded correctly, so it's an encoding problem in CH.
When you import the image that you want to convert you also have the option to choose the aspect ratio: 0 - don't keep aspect ratio, resize the image to the chosen values.
1 - keep the aspect ratio within limits - it tries to use one of the chosen values as long as the other one, upon resize with aspect ratio, is still within the max. values: 400x198 pixels.
2 - keep the aspect ratio with no limitation - if the limits are breached, it won't be usable in Convers+, but you are free to test it
Example:
Input image is 400x198. You want it to be 200x198 pixels:
If you select 0 for AS the result image is 200 x 198 pixels.
If you select 1 or 2 for AS the result image is 200 x 99 pixels (200 = 400/2 so 198 is also divided by 2).
Input image is 200x198. You want it to be 400x198 pixels:
If you select 0 for AS the result image is 400 x 198 pixels.
If you select 1 for AS the result image is 200 x 198 pixels (height is 198 max, so if it keeps the AS then width remains 200).
If you select 2 for AS the result image is 400 x 396 pixels (400 is 200*2 so height will be 198*2).
This version is compiled with a different compiler version than the old versions of CH / IPC Updater so in the attached archive you also have the need library files.
You do not have the required permissions to view the files attached to this post.
Last edited by DGAlexandru on 02 Jan 2021, 00:35, edited 2 times in total.
Re: Apply custom images to Ford Convers+
hey when i make image its not coding an image
image saved as just BIN
image with bgr,vbf
image i am using
from the image below you can see its only putting header and end of logo @DGAlexandru this i what i ment when i pm'd you
here is a bin of an image from previous version and as you can see the logo data is there screen capture below
image saved as just BIN
image with bgr,vbf
image i am using
from the image below you can see its only putting header and end of logo @DGAlexandru this i what i ment when i pm'd you
here is a bin of an image from previous version and as you can see the logo data is there screen capture below
You do not have the required permissions to view the files attached to this post.
Re: Apply custom images to Ford Convers+
Gwe89 wrote: ↑30 Dec 2020, 18:53 hey when i make image its not coding an image
CustomLogo_30-184935.bin
image saved as just BIN
CustomLogoAt_0x30120410_30-184653.VBF
image with bgr,vbf
smax2.jpg
image i am using
from the image below you can see its only putting header and end of logo
hex capture.PNG
@DGAlexandru this i what i ment when i pm'd you
here is a bin of an image from previous version and as you can see the logo data is there
CustomLogo_30-194446.bin
screen capture below
Capture2.PNG
i resized image with other tool before loading into CH and now it shows and when i save an flash to convers i get image same as in the screenshot below
You do not have the required permissions to view the files attached to this post.
-
DGAlexandru
- Pro
- Posts: 364
- Joined: 04 Aug 2019, 22:47
Re: Apply custom images to Ford Convers+
Load the Image.
Input 250 as width, 195 as height, choose 0.
Do RLE Convert.
Save image as BIN. Input again 250 and then 195 when it asks you for these values.
If you Cancel any of the questions then it won't save the image correctly.
Now I'm writting from my phone, but I'll have a second look. For testing the new version I went with 200x100, 200x198, 400x100.. maybe 250x195 is a "magic" combination that breaks things
Input 250 as width, 195 as height, choose 0.
Do RLE Convert.
Save image as BIN. Input again 250 and then 195 when it asks you for these values.
If you Cancel any of the questions then it won't save the image correctly.
Now I'm writting from my phone, but I'll have a second look. For testing the new version I went with 200x100, 200x198, 400x100.. maybe 250x195 is a "magic" combination that breaks things