Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
Yes and No. Either way, this particular issue persists.
Have you disabled/removed all your mods and addons?
Yes
Brief description of the issue:
I Use the SDK Thumbnail Generator in Dev Mode to create new thumbnails for all my aircraft. What I have noted is that ALL Reno add-on aircraft (with two exceptions listed below) do not respect thumbnails I create for them unless I physically overwrite the originals. This can be done with OVGME, but it is a pain. However, it does work.
As with many other third-party add-ons, if you prefix a folder name with “ZZZZ” then place that folder in the “Community” folder within the sim, it will be one of the last folders the sim reads on loading the GUI and should use the files contained within instead of the original files read earlier in the GUI loading process. This is the case for all aircraft as all of the new thumbnails that exist in my “ZZZZ” folder work for them. However, None of the Reno add-on aircraft work and fail to display the new thumbnails in the sim. There are two exceptions but I have not been able to identify any difference between them and the other Reno aircraft. Those exceptions are the Pitts-S1-Aviators thumbnails and the Pitt-S1-XBox-Aviators thumbnails. They both work for some reason. All other Reno aircraft thumbnails do not work and are not respecting the new thumbnails.
Here’s the folder structure I am using as an example.
“Community\ZZZZ_Thumbnails\SimObjects\Airplanes\Asobo_Pitts_S1_Reno\texture\thumbnail.jpg”
Provide Screenshot(s)/video(s) of the issue encountered:
Here’s the Root of the Updated thumbnails and includes the manifest and Layout JSONs required for the sim to load the new thumbnail folders properly.
Here’s a view of ALL of the Reno based aircraft I have in a test folder. Note the two highlighted folders are folders that work as the new thumbnail.jpg files nested in them are properly displayed in the sim GUI for whatever reason.
And here’s a view of one of the Reno aircraft folders, which is named exactly as the original. The new thumbnail JPGs live in each texture folder as they should.
Detailed steps to reproduce the issue encountered:
-
Create a new folder and prefix it with “ZZZZ” e.g., “ZZZ_Thumbnails.”
-
Create the “SimOBjects\Airplanes” folders and then create an exact duplicate of one of the Reno aircraft folders within the “SimObjects\Airplanes” folder. I would do the Pitts S1 as it has two that are respecting the new thumbnails.
a. As a test to validate your folder does work, do the same of any other non-Reno aircraft.
Carenado or any other marketplace add-ons work as do the default Asobo aircraft. All third-party
aircraft work as well. -
Remove all files from the newly created aircraft folder with the exception of the “Texture” folders.
-
Delete all files within the “Texture” folders for the aircraft.
-
Place your new “thumbnail.jpg” and “thumbnail_small.jpg” files in each of the texture folders for the aircraft.
-
Once all folders are in place, create a new layout.json file in the root of your “ZZZ_Thumbnails” folder. You will also need to include a manifest.json file.
-
Place your “ZZZZ_Thumbnails” folder in your “Community” folder.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
1.29.28.0
Not sure as I recently began implementing this new method of displaying custom thumbnails when I was previously using OvGME to overwrite the originals. That worked just fine, but I would prefer this method as it is cleaner and effective for all other aircraft. All of them, not just some of them. And they all live in my ZZZZ folder, so I know it works.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video: