I need help. I have a problem where the transition from the loading screen to the main menu is not smooth and is interrupted by a brief red screen.
All relevant files are attached.
#✅ | 🙋 | Transition from loading screen to main menu
glossy idol
haughty forgeBOT
I need help. I have a problem where the transition from the loading screen to th...
I can help you with understanding common issues during transitions from the loading screen to the main menu! Unfortunately, I can only view images and not other file types like the .txt files you attached. If you'd like a human to review those specific files, please use the "Request Human Help" button below this message.
A common cause for an unsmooth transition or a brief red screen during loading can be the use of video backgrounds or FMA animations in loading screens. Videos are generally not supported in loading screens and FMA files can cause a brief stall or flicker if they are not short and simple enough.
You can find more information about this in the documentation:
Also, pre-loading resources (especially FMA files) can help with smoother playback and reduce lagging or black screens when they are first loaded.
Could you tell me if you are using any video backgrounds or complex FMA animations during your loading screen, and if you have tried pre-loading them? 😊
🙋 | Transition from loading screen to main menu
<@&1365490168563372113>
glossy idol
If I recreate everything and initially only set the same background individually in the menu, loading screen, and early loading screen, then an unnatural transition with a brief red image occurs during the transition from the loading screen to the main menu.
haughty forgeBOT
If I recreate everything and initially only set the same background individually...
That's an interesting detail! The fact that you're seeing a brief red screen with just a uniform background across all loading stages, points away from complex animations or video issues.
A brief red screen during loading or transitions can sometimes be an indicator of a few things:
- Missing or Corrupted Textures: If a required texture for a background or an element fails to load, Minecraft might display a default 'missing texture' color, which is often red. Since you mentioned the background is the same, it might be that the texture itself or its path is causing an issue during that specific transition phase.
- Mod Conflict: Occasionally, other mods can interfere with FancyMenu's rendering pipeline. The "Incompatibility List" might have some clues, but sometimes issues can arise with mods not listed there.
- Performance Overload: While less likely with a simple background, if the game is under heavy load during that precise moment, it could struggle to render.
To help me understand this better without being able to see your files, could you tell me:
- What kind of background are you using? Is it a simple image, a panorama, or something else mentioned in the Menu Backgrounds documentation?
- Is it a local file, web resource, or a Minecraft resource? You can find details about these in the Resources documentation.
- Have you checked your
latest.logfile after this happens? It might contain error messages about texture loading or rendering failures, which could give us a direct hint! You can find it in your instance's/logs/folder.
If you believe it might be related to a specific config after all, and you don't mind sharing the content of your latest.log (you can upload it to a site like Gist and share the link), that would be super helpful for getting more in-depth human debug assistance if needed! 😊
glossy idol
diese png datei wird verwendet
haughty forgeBOT
diese png datei wird verwendet
Thanks for sharing the image! It's a lovely sunset scene. 🌅
Since you're using a single PNG image as the background, the cause of the red screen is unlikely to be video or FMA related. Given that it's a static image, the most probable reasons for a red flash are:
- Issue with the Image File Path/Loading: Even if the path is technically correct, sometimes there can be a hiccup where the game can't load the image quickly enough during that critical transition. If the file is very large in dimensions or file size, it could take longer to load. I recommend trying to lower the image resolution/file size a bit and see if it helps. Also, ensure the image is stored in
config/fancymenu/assets/as recommended for local resources. - Resource Pack Handling: If the image is part of a resource pack, there might be a delay in how Minecraft processes and makes that resource available during the transition.
- Conflict with another mod: Other mods could be interfering with how FancyMenu or even Minecraft itself handles image loading during splash screens and initial menu display.
To investigate further, I would still highly recommend checking your latest.log file (located in your Minecraft instance's /logs/ folder). Look for any [Error] or [Warn] messages around the time the game transitions from the loading screen to the main menu. These messages often contain clues about why a texture failed to load or if another mod is causing an issue.
If you find anything in the log or want a human to take a look, please use the "Request Human Help" button! 😊
glossy idol
https://mclo.gs/1vpZmHG hier der latest log
haughty forgeBOT
https://mclo.gs/1vpZmHG hier der latest log
haughty forgeBOT
https://mclo.gs/1vpZmHG hier der latest log
Thank you for providing the latest.log file, M4ximum_! 📝
As an AI, I'm not able to open or read external links or log files directly. However, if you would like to have a human analyze the log file for potential issues, please press the "Request Human Help" button below this message. A real human will then be able to review the log and provide more specific assistance. 😊
glossy idol
I would like to find the cause of the error, i.e. why there is a brief red screen between the loading screen and the main menu.
Is there a specific setting that needs to be taken into account? Or do you have to set up a universal layout for the background, or what exactly could be the problem?
The image I sent is 1.75 MB and has a resolution of 2560x1369px.
haughty forgeBOT
I would like to find the cause of the error, i.e. why there is a brief red scree...
Thank you for the additional details! The image resolution (2560x1369px) and file size (1.75 MB) are quite normal and shouldn't inherently cause a red screen. This reinforces the idea that it's likely not the image itself, but how or when it's being loaded. Let's break down the possibilities for the red screen, considering your setup and the use of the same background across screens:
Possible Causes for the Red Screen
- Timing and Loading Order:
- Resource Reload/Unload: When transitioning from the
Drippy Loading Screento the normalTitle Screen, Minecraft might technically "unload" the loading screen resources before "loading" the main menu resources. If there's a brief gap where no background is actively loaded, or if the main menu's background loads slightly slower than expected, you could see a flash of a default color (which is often red or black). - In-game Logic/Other Mods: Another mod or even a quirk in Minecraft's loading sequence might be influencing the rendering at that exact moment, causing a brief "empty" frame to be rendered in red.
- Resource Reload/Unload: When transitioning from the
- Configuration Issue (Specific to FancyMenu/Drippy):
- Drippy's Overlay vs. FancyMenu's Background: You mentioned setting the background in the "menu, loading screen, and early loading screen."
- "Early loading screen" implies
Drippy Loading Screen. Drippy is an addon for FancyMenu. - "Loading screen" likely refers to the "World Loading Screen" (which can be customized with FancyMenu's dummy screens).
- "Menu" refers to the main menu (Title Screen), which you customize with FancyMenu.
- "Early loading screen" implies
- It's possible that Drippy's configuration for its overlay (the background for the very early loading stage) might interact subtly differently than FancyMenu's background for the main menu.
- Drippy has a setting called
overlay_render_orderindrippy_loading_overlay_config.txt. If this is set to draw behind everything else or if something else is configured to draw on top of it with a solid color, that could cause issues.
- Drippy's Overlay vs. FancyMenu's Background: You mentioned setting the background in the "menu, loading screen, and early loading screen."
Addressing your questions:
- Specific setting to take into account?
- Check how you've applied the background in both Drippy and FancyMenu. Ensure it's set as an Image background type.
- For the main menu layout, make sure the layout itself is
Enabledand thatCustomizations for Current Screenare active. - For Drippy, ensure the image path is correct in your
drippy_loading_overlay_config.txt. - Also, consider using Pre-Load Resources for your image. This ensures the background image is already loaded into memory before it needs to be displayed, which could eliminate loading delays. You can learn more here: Pre-Load Resources.
- Universal Layout for the background?
- Using a Universal Layout is a good idea for consistent backgrounds across multiple general menus, but Drippy Loading Screen handles the initial game loading phase separately (it's its own dedicated module).
- For the transition from Drippy's loading screen to the Title Screen, you usually need to ensure both Drippy's config and your Title Screen layout's background are correctly set to the same image. A universal layout wouldn't directly manage the Drippy background but would help ensure consistency across other menus once the game is fully loaded.
- You can learn about universal layouts here: Universal Layouts.
What I recommend for next steps:
- Enable Pre-Loading for your Image: Navigate to Customization -> Pre-Load Resources and add your background image file to the list. Even though it's a small image, pre-loading can sometimes resolve these timing-sensitive rendering glitches.
- Double-Check Drippy Configuration: Since Drippy handles the early loading, ensure its configuration is solid.
- Check
drippy_loading_overlay_config.txtto confirm thebackground_texturepath for your image. - If you're using any other options in Drippy that might draw solid colors or other layers, temporarily disable them.
- Check
- Temporarily simplify/Remove other Modpack Elements: If you have any other complex FancyMenu elements (like videos, animations, browser elements) or other mods that significantly alter GUI behavior, try temporarily disabling or removing them to see if one of them is the culprit. The Incompatibility List can be a good place to start checking for known issues.
If the above steps don't help, and you still can't identify the cause, I strongly recommend using the "Request Human Help" button to have a human expert examine your latest.log file, as it often contains crucial error details that I am unable to process. They can also look at your title_screen_layout.txt and drippy_loading_overlay_newpath.txt files if you share them again.
glossy idol
Could it be because I have hidden the buttons that are there by default?
haughty forgeBOT
native talon
Could it be because I have hidden the buttons that are there by default?
You still have the issue with the red screen showing up for a short moment, right? I remember that was caused by something, but I don’t remember what exactly. Could be a mod conflict or maybe a resource that isn’t ready yet in the Title screen, like a custom background in the Title screen maybe? Try loading the game with only FM + dependencies installed to check for mod conflicts. Also make sure to pre-load your custom backgrounds in both loading screen and title screen.
glossy idol
You still have the issue with the red screen showing up for a short moment, righ...
First of all, thank you very much for your help.
I have already checked the latter; it is the same image (see the files above).
My modpack in which I use it has over 400 mods. Are there any known conflicts?
Otherwise, I don't know exactly how I might find the culprit.
In an instance where only FM, drippy, and ealy are present, the problem does not occur.
This is the complete mod list that I use.
I think you're right, it's a mod that's causing the conflict, but I can't figure out which one.
native talon
In an instance where only FM, drippy, and ealy are present, the problem does not...
Oh so it IS a mod conflict. Interesting!
FM conflicts: https://docs.fancymenu.net/en/incompatibility-list
Drippy conflicts: https://github.com/Keksuccino/Drippy-Loading-Screen/wiki/Incompatibility-List
But I don’t think I added the one that causes the red screen 😅 not sure tho
If you find the mod, please ping me, so I can add it to the list! Thank you! 🙏🏻
glossy idol
I'll start looking and get back to you 😅
glossy idol
@native talon
I was able to find the problem. The problem is activated shaders while using the Iris mod, which must be used in combination with Sodium.
If you deactivate the shaders, the error does not occur. As soon as a shader is active, this error occurs when transitioning from the loading screen to the main menu.
This happened with my modpack, in an instance where only Fancy Menu, Drippy, Sodium, and Iris are included, and then I tested it with another Neoforge modpack:
- Medieval MC [Neoforge]
Everything in 1.21.1 based on Neoforge – I'm actually surprised that I'm the first to report this xD
Maybe it can be solved with a patch?
The error also occurs when using the “all the mods 10” modpack with Embeddium and Monocle. As soon as a shader is active and you start the game, a brief red screen appears between the loading screen and the main menu.
If you want, I could open a GitHub bug report about it.
native talon
<@602238391697801236>
I was able to find the problem. The problem is activated ...
Then I'm not sure if I can fix that. It's probaby just some resource or render patches that get applied by that feature/mod. Thank you for debugging, I will add a note to the incompatibility page for now! 🙏
haughty forgeBOT