Jump to content

Recommended Posts

Posted

Hi, i think adding the hook in my title would be helpful to modders trying to draw something to the screen when they cant use the tile entity special renderer.

 

Currently there are two relevant hooks which are useful when you want to render to the screen, onRenderTick.pre and onRenderTick.post, and while they're useful, sometimes they're not enough.

 

For example if i render something to the screen during onRenderTick.pre, it will not show up on the screen, since the screen is cleared after the hook.

And if i render something in onRenderTick.post, it will render over the GUI (when they render the gui they don't use depth so you cant draw "behind" it).

 

Rendering using the tile entity special renderer is obviously the best solution to this since yoy can render pretty much whatever you want in there? but i can't use it in my case.

 

I'm making a "portal" mod, similar to iChun's "doors", which means i have to render the whole screen again. I do this by calling "renderWorld" and using the stencil buffer to mask out what i don't need. But i can't call renderWorld from inside the tile entity special renderer, it raises an exception about the vertexbuffer already drawing.

So i have to render from outside of tile entity special renderer and currently i am doing it from onRenderTick.post which causes me to draw over the GUI.

If there was a hook in place after the screen was cleared and the camera position was set, i would be able to draw what i want without drawing over the GUI.

 

I would be happy to hear any suggestions/opinions if you have them, especially about getting the rendering from inside the tile entity special render to work, because then i won't need the hook.

 

Writng from my phone so sorry about typos.

 

Posted (edited)

Thanks! I think that would solve my drawing over the GUI problem.

 

Edit: i still think having a hook after camera setup and before world render would be useful in general for working with the stencil buffer since it's is easier to do and less taxing on the gpu when you don't have to depth check against existing terrain.

Edited by LRocket
Posted

I think adding this event deserves further consideration.

 

Like i've said before, i've implemented drawing my portals before the GUI render happens but now i face another issue, which i think also needs this event.

 

everything that's rendered through my portal has to "fight" with what already been rendered by the game beforehand.

here is a screenshot of how it looks:

U9MXQpP.png

 

 

see how the diamond blocks on the ground are Z-fighting with the grass.

The diamond blocks are actually behind the portal, the village that you see  through the portal should have overwritten them entirely.

 

Why this didn't happen before, when i was rendering after the GUI is drawn, is because after the GUI was drawn, minecraft clears the whole depth buffer, so there were no depth values to anything when rendering the portal.

 

in my case, i can't clear the whole depth buffer before drawing the portal because if there are several portals on screen, and i clear the depth after drawing each one, the portals being drawn second and after, will override the world, they would always be drawn on top even if there are blocks in front of them that should have been hiding them from view, they will just render over it.

 

The problem is that i haven't found a way (not sure if there even is one) to clear the depth buffer of just a single part of the screen (the portal).

 

but if i could draw the portals before the world gets drawn, i wouldn't have to worry about this.

i would just draw my portals on a clear screen, assign a correct depth value from them, and then just let minecraft render normally and because of the depth values i put, everything should render correctly.

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hello, I am trying to make 2 recipes for a ruby. The first one is turning a block into a ruby and the other one is 9 nuggets into a ruby. But I keep on getting a error java.lang.IllegalStateException: Duplicate recipe rubymod:ruby   Any help would be great on how to fix it
    • Hello everyone, i'm new with programing Mods, and will need a lot of your help if possible,  Im trying to make a new GUI interface responsible to control the Droprate of game, it will control de loot drop and loot table for mobs and even blocks, but i try to make a simple Gui Screen, and wenever i try to use it, the game crash's with the error message in the subject, here is the code im using to:  IDE: IntelliJ Comunity - latest version Forge: 47.3.0 Minecraft version: 1.20.1 mapping_channel: parchment mapping_version=2023.09.03-1.20.1 Crash report link: https://pastebin.com/6dV8k1Fw   Code im using is:    package createchronical.droprateconfig; import com.mojang.blaze3d.systems.RenderSystem; import net.minecraft.client.gui.GuiGraphics; import net.minecraft.client.gui.components.Button; import net.minecraft.client.gui.screens.Screen; import net.minecraft.network.chat.Component; import net.minecraft.resources.ResourceLocation; import java.util.HashMap; import java.util.Map; public class ConfigScreen extends Screen { private static final ResourceLocation BACKGROUND_TEXTURE = new ResourceLocation("droprateconfig", "textures/gui/config_background.png"); // Mapa de mobs e itens com seus respectivos drop rates private final Map<String, Integer> dropRates = new HashMap<>(); public ConfigScreen() { super(Component.literal("Configurações de Drop Rate")); // Inicializa com valores de drop rate padrão dropRates.put("Zombie", 10); // Exemplo de mob dropRates.put("Creeper", 5); // Exemplo de mob dropRates.put("Iron Ore", 50); // Exemplo de item dropRates.put("Diamond", 2); // Exemplo de item } @Override protected void init() { // Cria um botão para cada mob/item e adiciona na tela int yOffset = this.height / 2 - 100; // Posicionamento inicial for (Map.Entry<String, Integer> entry : dropRates.entrySet()) { String itemName = entry.getKey(); int dropRate = entry.getValue(); // Cria um botão para cada mob/item this.addRenderableWidget(Button.builder( Component.literal(itemName + ": " + dropRate + "%"), button -> onDropRateButtonPressed(itemName) ).bounds(this.width / 2 - 100, yOffset, 200, 20).build()); yOffset += 25; // Incrementa a posição Y para o próximo botão } // Adiciona o botão de "Salvar Configurações" this.addRenderableWidget(Button.builder(Component.literal("Salvar Configurações"), button -> onSavePressed()) .bounds(this.width / 2 - 100, yOffset, 200, 20) .build()); } private void onDropRateButtonPressed(String itemName) { // Lógica para alterar o drop rate do item/mob selecionado // Aqui, vamos apenas incrementar o valor como exemplo int currentRate = dropRates.get(itemName); dropRates.put(itemName, currentRate + 5); // Aumenta o drop rate em 5% } private void onSavePressed() { // Lógica para salvar as configurações (temporariamente apenas na memória) // Vamos apenas imprimir para verificar dropRates.forEach((item, rate) -> { System.out.println("Item: " + item + " | Novo Drop Rate: " + rate + "%"); }); // Fecha a tela após salvar Screen pGuiScreen = null; assert this.minecraft != null; this.minecraft.setScreen(pGuiScreen); } @Override public void render(GuiGraphics guiGraphics, int mouseX, int mouseY, float partialTicks) { this.renderBackground(guiGraphics); guiGraphics.blit(BACKGROUND_TEXTURE, this.width / 2 - 128, this.height / 2 - 128, 0, 0, 256, 256, 256, 256); super.render(guiGraphics, mouseX, mouseY, partialTicks); } }  
    • Also add the latest.log from /logs/
    • I was hoping I could get some help with this weird crash. I've hosted many servers before and never had this issue. Now and then the server crashed with "Exception ticking world". Everywhere I looked I rarely found any info on it (usually found ticking entity instead). Any advice I did get (mostly from the modpack owner's discord) was "We don't know and it's near impossible to find out what it is". Here is the crash report:   Description: Exception ticking world java.util.ConcurrentModificationException     at java.util.HashMap$HashIterator.nextNode(Unknown Source)     at java.util.HashMap$KeyIterator.next(Unknown Source)     at net.minecraft.entity.EntityTracker.sendLeashedEntitiesInChunk(EntityTracker.java:386)     at net.minecraft.server.management.PlayerChunkMapEntry.sendToPlayers(PlayerChunkMapEntry.java:162)     at net.minecraft.server.management.PlayerChunkMap.tick(SourceFile:165)     at net.minecraft.world.WorldServer.tick(WorldServer.java:227)     at net.minecraft.server.MinecraftServer.updateTimeLightAndEntities(MinecraftServer.java:756)     at net.minecraft.server.dedicated.DedicatedServer.updateTimeLightAndEntities(DedicatedServer.java:397)     at net.minecraft.server.MinecraftServer.tick(MinecraftServer.java:668)     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:526)     at java.lang.Thread.run(Unknown Source)   If you want the full version, I can link a pastebin if needed. Modpack link: https://www.curseforge.com/minecraft/modpacks/multiblock-madness Some helpful information is that: It seems to only happen when I leave my void world to enter the overworld. Only happens 5-10% of the time. Only happens when leaving the void world, and only the void world. I know it's a slim chance someone could help, but it'd be greatly appreciated.
    • thanks a lot bro i knew i shouldve gone on the actual website instead of the discord
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.