2019/2020 update for FIFA Manager 13 and FIFA Manager 14.

Post tutorial Report RSS Custom 3D Loadscreens

How to: creating custom loading screens for 3D-match.

Posted by on - Intermediate Textures

Since Season Patch version 2020 1.0, it's possible to add custom 3D loading screens for each club. In Season Patch, stadium tunnel images are used for this purpose. In this article we'll try to add one.

Step 1. You need to find club's Unique ID value. You can find it in the Editor:


Step 2. Find or create the image you want to add. The image size must be 1920x1200 pixels and the format is .bmp. You can use Photoshop or GIMP to give an image proper dimensions and save it to .bmp. I'm using this image:


Step 3. Name this image with club's UID. In this case the name for the image will be 00150008.bmp

Step 4. Now, craete a folder (if it's not already created)

stadiums/tunnel in your FM folder and put this image there. Here we are:

And here we can see the result in-game:


Some more facts:

  • If you have custom loading screens in the Documents folder (Graphics\3DMatch\LoadingScreen), they will have a higher priority than any other loading screens. So if you want to see loadscreens from the "tunnel" folder, you will need to delete custom loadscreens from the Documents folder.
  • If there are no loadscreens in the Documents folder and there are no loadscreens for specific club in the "tunnel" folder, then a stadium image (1920x1200) will be used (if it's exist for the club).
  • The Patch already contains loading screens for some clubs, but they are packed into .big archives and that's why they are not seen in the "tunnels" folder.
Post a comment
Sign in or join with:

Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.

Follow Report Profile
Icon
FIFA Manager 14
Contact
Send Message
Release date
Mod watch
Follow
Tutorial
Related Games
FIFA Manager 14
FIFA Manager 14 Football
Related Groups