Problems rendering an overlay

[PlanetTeamSpeak]

My gui overlay is not being rendered. I tried rendering it using an overlay registered in the RegisterGuiOverlaysEvent and with both RenderGuiOverlayEvent.Post and RenderGuiEvent.Post and in every case, adding a print statement does in fact say it is being rendered, but in not a single case am I actually seeing my overlay. The overlay works fine on Fabric, however (my mod is an Architectury mod and comes from Fabric). The source code of my overlay can be found here and it's supposed to look like this.

P.s. this is on 1.19.2

Edited September 16, 2022 by PlanetTeamSpeak

[warjort]

This thread has a working forge gui overlay:

https://forums.minecraftforge.net/topic/116247-119-detect-if-the-player-is-looking-at-the-sun/#comment-513544

 

I tried to build your project but I got some error about a java module conflict when I ran forge:runclient

Exception in thread "main" java.lang.module.ResolutionException: Module generated_d81a3f9 contains package com.ptsmods.morecommands.compat.client, module generated_846f3c3 exports package com.ptsmods.morecommands.compat.client to generated_d81a3f9
        at java.base/java.lang.module.Resolver.resolveFail(Resolver.java:901)
        at java.base/java.lang.module.Resolver.failTwoSuppliers(Resolver.java:807)
        at java.base/java.lang.module.Resolver.checkExportSuppliers(Resolver.java:736)
        at java.base/java.lang.module.Resolver.finish(Resolver.java:380)
        at java.base/java.lang.module.Configuration.<init>(Configuration.java:140)
        at java.base/java.lang.module.Configuration.resolveAndBind(Configuration.java:494)
        at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.ModuleLayerHandler.buildLayer(ModuleLayerHandler.java:75)
        at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.TransformationServicesHandler.buildTransformingClassLoader(TransformationServicesHandler.java:60)
        at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.run(Launcher.java:104)
        at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.main(Launcher.java:77)
        at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26)
        at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23)
        at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:141)
        at net.fabricmc.devlaunchinjector.Main.main(Main.java:86)
        at dev.architectury.transformer.TransformerRuntime.main(TransformerRuntime.java:217)

 

From what I can gather you are not really using anything from forge for this.

You are using architectury's loom fork instead ForgeGradle, you aren't using the forge api directly you are using the architectury api and you are using the yarn mappings.

The only part where forge is used is indirectly here to fire the event: 

https://github.com/architectury/architectury-api/blob/64c1f05efad05a9ef056a7db857065700fe00083/forge/src/main/java/dev/architectury/event/forge/EventHandlerImplClient.java#L61

[PlanetTeamSpeak]

That is correct, I have also been having this issue, but it's because I have multiple compat projects that all share the same package name. It's not that much of an issue tho as I only debug on Fabric and can do Forge-specific debugging with MultiMC.

I'll have a look at that thread tho and see if that solves my issue.