🔍 /
42,334 Topics · 300,445 Posts
Search Archive

Custom .PIM Image Application

By ohlarikd · Feb 22, 2006in Custom Backgrounds💬 42 posts👁️ 24,332 views
Page 2 of 2
Posted May 15, 2006 · 22:01 UTC#26
Any chance someone can put together an F-150 background? I'm not 100% sure how to edit these pims but I love that custom Mustang one on the equalizer background.

Thanks!
Posted May 15, 2006 · 23:04 UTC#27
Since you like the Mustang one I made, I tried to keep it as close as possible.
Let me know if you want something else.
Attached Files (1)
f150.jpg
f150.jpg
Posted May 15, 2006 · 23:17 UTC#28
VERY NICE! Much thanks! Could I bother you to make an adjustment? Same pic but without the Ford oval. I would like to see how both look onscreen.

Thanks again!
Posted May 15, 2006 · 23:21 UTC#29
Here ya go. Thank god for Photoshop Layers. :wink:
Attached Files (1)
f150 copy.jpg
f150 copy.jpg
Posted May 15, 2006 · 23:23 UTC#30
You the man!
Posted May 16, 2006 · 02:55 UTC#31
Those are AWESOME! Can you do one like that with the Ford oval and the new F-150 logo?

Thanks,
mikebaby
Posted May 19, 2006 · 22:05 UTC#32
Can you please post that parametric EQ blue background image alone? I want to Photoshop my FJ into it for my startup screen.

Can I have multiple .PIM files with the single background JPG on the same DVD? Does it browse the .PIM files from DVD or does it load them into RAM as well? How many can you have?

Thanks a million for this. I was REALLY hoping this would work on the D1... I already did XM Nav/Traffic and backup cam. Great unit.

Adam
Posted May 19, 2006 · 22:09 UTC#33
Here ya go! You can have up to 10 pims in the folder I think.
Attached Files (1)
DIGITAL.jpg
DIGITAL.jpg
Posted May 19, 2006 · 22:13 UTC#34
Man you're fast!

Thanks a million.

Only question.. to do the PIM files do you have to burn a Nav DVD and replace the files in the correct folder or can you have a PIM only DVD?

Thanks!
Posted May 20, 2006 · 01:42 UTC#36
Ok I got it... had to do a SAVE after making the changes and it was all good. The JPEG to PIM conversion wasn't perfect but we knew that already (and beggars can't be choosers!)

Only question... what did we delete? Is it anything we're gonna miss?


Adam
Posted Jun 02, 2006 · 15:47 UTC#37
I was trying to load a new boot screen and one instruction I don't understand is how to resent the D2 unit so it will load up the modified .bmp. How is this done? Will it affect any other settings?
Posted Jun 04, 2006 · 05:09 UTC#38
When changing .PIM's for XM icons, does the burnt disc have to stay in the drive or, like with bootscreens & backgrounds, can the disc be removed once the icon has been opened? I'm guessing that the disc will have to stay in BUT I haven't tried it yet. I just didn't want to burn a DL disc if I didn't need to.

Attached is my 1st (successful) attempt at a custom bootscreen. Thanks for all the help in getting the information to play with that!
Attached Files (1)
FX4.jpg
FX4.jpg
Posted Jun 04, 2006 · 15:03 UTC#39
ckelly33 said:
When changing .PIM's for XM icons, does the burnt disc have to stay in the drive or, like with bootscreens & backgrounds, can the disc be removed once the icon has been opened? I'm guessing that the disc will have to stay in BUT I haven't tried it yet. I just didn't want to burn a DL disc if I didn't need to.

Attached is my 1st (successful) attempt at a custom bootscreen. Thanks for all the help in getting the information to play with that!


For XM, the disc needs to stay in. The bootscreens and backgrounds disc can be removed.
Posted Jun 06, 2006 · 23:40 UTC#40
will any of this work on an n2?
Posted Jun 19, 2006 · 15:29 UTC#41
charliex said:
ohlarikd said:
I don't think this PIM color issue is going to be easy to fix.

In a PIM file, white is 39 67. In PIM Manager, white is naturally assumed to be FF FF.

Derek


hope you don't me butting in, i've just found this forum and only read a couple of messages, so i might be repeating stuff already known, but white is not 3967, you're looking at it in the wrong format.
example

take the 3967 in hex 0xF7F, well its obvious the ordering (probably just little endian) is in the wrong order (and from the screen shots i've seen people post with the odd coloured greyscales, it would match) , its really 0x7FF which is a normally bit white RGB.

so if you treated the 0xF7F as RGB at 555 or 556 it'd appear strangely.

seems like its more 443 or something, making a test image should be easy enough

also i noticed you talking about translucency problems, well its really ARGB or some combination thereof, and you're building the RGB triplets in the wrong order, or you're using the wrong endian, you'd end up writing into the alpha values, i dont know if its a single mask bit for on off transparent alpha or a few bits for translucent alpha. (this is easily check my making an image with 0xF7F + 0x10 * level of translucency or such., so a band of 0xF8F 0xF9F 0xFAF etc, this should should either on off transparency or blended translucency



again sorry if this is all old news, or i missed something else.

cheers,
charlie




Charlie,

Thanks for thinking about this. We have tried to decipher the bit scheme, and we thought we had it when we were able to read the PIM file using Irfanview. However, when you create a JPEG image in photoshop, then use the JPEG-to-PIM converter that someone wrote, it will not create the proper bit scheme to get it to appear correctly on the AVIC itself. I still haven't figured it out.

Please feel free to try out all the different suggestions you have made - it is time consuming for one person to do. I have tried many things to no avail, so I would welcome another pair of hands to decipher this.

Derek
Posted Jun 19, 2006 · 15:37 UTC#42
ohlarikd said:
charliex said:
ohlarikd said:
I don't think this PIM color issue is going to be easy to fix.

In a PIM file, white is 39 67. In PIM Manager, white is naturally assumed to be FF FF.

Derek


hope you don't me butting in, i've just found this forum and only read a couple of messages, so i might be repeating stuff already known, but white is not 3967, you're looking at it in the wrong format.
example

take the 3967 in hex 0xF7F, well its obvious the ordering (probably just little endian) is in the wrong order (and from the screen shots i've seen people post with the odd coloured greyscales, it would match) , its really 0x7FF which is a normally bit white RGB.

so if you treated the 0xF7F as RGB at 555 or 556 it'd appear strangely.

seems like its more 443 or something, making a test image should be easy enough

also i noticed you talking about translucency problems, well its really ARGB or some combination thereof, and you're building the RGB triplets in the wrong order, or you're using the wrong endian, you'd end up writing into the alpha values, i dont know if its a single mask bit for on off transparent alpha or a few bits for translucent alpha. (this is easily check my making an image with 0xF7F + 0x10 * level of translucency or such., so a band of 0xF8F 0xF9F 0xFAF etc, this should should either on off transparency or blended translucency



again sorry if this is all old news, or i missed something else.

cheers,
charlie



Oh... I see what you are saying now. Interesting. They are using decimal notation in the file, potentially. Strangely, if you interpret it as hex using Irfanview, it comes up ok.

Either way, I will try to find some time to see if I can correlate some other non-white colors to figure out the bit order. If the last bits are levels of translucency, that would be interesting as well.

Jason, we would need the unknown contact to make a new version of PIM converter, could you ask?

Thanks for the new angle!

Derek
Page 2 of 2