Slipping custom lot' icons in menu

[tariely 4,498]

I just finished relotting Paeng's WSP park (for lighting...) and I assigned it a new order so that the (numerous) pieces would show up near the beginning (0xFFFFFF20) of the park menu in my working plugins folder. (The order assigned by Paeng puts them at the very end of the park menu, which I find inconvenient, considering the length of my playing park menu !). I noticed there seems to be some slippage (can't find another appropriate term !) from one icon to the next : i.e the icon of a lot does not correspond to what is plopped but to what is before, or after. I verified that the icons where the right ones. I also noticed that the menu presents with the Momentarily Missing Icon Syndrome, i.e. at some point down the list, the icons only show up if scrolling down (and then stay correctly in their place, but before that I only get the orange tongue of the menu, without icons.)

Is there somebody out there who would have an idea why this is happening and how to keep it from happening ? 

[twalsh102 1,601]

This is usually an indication that the the icon (PNG) subfile for one or more lots are missing or corrupted.  The immediate suspects are the lots you just modified.  A quick way to verify that would be to temporarily remove the folder containing the lot(s) from your Plugins folder and then see how the Park menu reacts.

If the menu reacts normally, then it's almost certain that one or more of your recent relots is the culprit.  To determine which ones, you need to open each SC4Lot file in Reader, find the PNG file with the group ID of 6A386D26.  This is the menu icon.  Click on the PNG to view the icon.  If the subfile is either empty, or shows something other than an icon, there's your culprit.  The fix is usually to just delete that PNG file, and then copy/paste from the original Paeng file to replace it.  While you're at it, I would also check any other PNG files as well as any LTEXT files.

I've run into this on numerous occasions with both older versions of Reader, as well as the latest version.  I traced the cause in each instance to saving the SC4Lot file multiple times during the same editing session (i.e. making a change to any of the subfiles, and then save; make another change to the same or a different subfile, and then save).  This almost always causes corruption (in my experience), most often to one or more PNG files, and sometimes to one or more LTEXT files.  The way I've found to avoid the problem is to not save until I've made all intended changes to the SC4Lot file.  If I decide I need to make an additional change after already saving the first time, I close the SC4Lot file and then re-open it before any additional editing.