41 replies to this topic

[mikebaby]

Those are AWESOME! Can you do one like that with the Ford oval and the new F-150 logo?

Thanks,
mikebaby

[JasonH]

Here ya go! You can have up to 10 pims in the folder I think.

Attached Files

•  DIGITAL.jpg   76.78K   803 downloads

[JasonH]

See this guide:
http://avic411.com/f...wtopic.php?t=99

Short answer: you need a (allmost) full nav dvd.

[adam12hicks]

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

[ckelly33]

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

•  FX4.jpg   106.51K   658 downloads

[JasonH]

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.

[radie842]

will any of this work on an n2?

[ohlarikd]

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

[ohlarikd]

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