Jump to content

Recommended Posts

Posted (edited)

Hey !

I'm trying to render an entity (for example a cow) just above a custom block entity. Of course, the renderer is correctly registered.

final EntityRenderDispatcher entityDispatcher = Minecraft.getInstance().getEntityRenderDispatcher();
final BlockRenderDispatcher dispatcher = this.context.getBlockRenderDispatcher();
//        pPoseStack.pushPose();
//        pPoseStack.translate(0.5f, 0.5f, 0.5f);
//        dispatcher.renderSingleBlock(Blocks.GLASS.defaultBlockState(), pPoseStack, pBufferSource, pPackedLight, pPackedOverlay,
//                EmptyModelData.INSTANCE);

//        pPoseStack.popPose();

Entity entityToSpawn = EntityType.COW.create(pBlockEntity.getLevel());
//        LOGGER.debug("ENTITY TO SPAWN " + entityToSpawn.getName());
//        pPoseStack.pushPose();
pPoseStack.translate(0.5f, 2f, 0.5f);
pPoseStack.scale(2f, 2f, 2f);
entityDispatcher.render(entityToSpawn, pBlockEntity.getBlockPos().getX(), pBlockEntity.getBlockPos().getY(), pBlockEntity.getBlockPos().getZ(),
                0.0f, pPartialTick, pPoseStack, pBufferSource, pPackedLight);
pPoseStack.popPose();

Is there something I do not correctly ?

Edited by Sweetmimike
Add info
Posted

I finally solved the problem !

If anyone is interested on how render an entity, you can find the code I used just below

final EntityRenderDispatcher entityDispatcher = Minecraft.getInstance().getEntityRenderDispatcher();
Entity entityToSpawn = entityType.create(pBlockEntity.getLevel());

float scale = 0.3f;
pPoseStack.pushPose();
pPoseStack.translate(0.5f, 1f, 0.5f);
pPoseStack.scale(scale, scale, scale);

entityDispatcher.render(entityToSpawn, 0.0D, 0.0D, 0.0D, 0.0F, 1.0F, pPoseStack, pBufferSource, 15728880);
pPoseStack.popPose();

 

Posted
22 minutes ago, diesieben07 said:

Do not create a new entity instance every time.

Right.

I modified the code just as follows

	final EntityRenderDispatcher entityDispatcher = Minecraft.getInstance().getEntityRenderDispatcher();
        Entity entityToSpawn = pBlockEntity.getEntityToDisplay();
        if(entityToSpawn == null || entityToSpawn.getType() != entityType) {
            LOGGER.debug("NEED TO CREATE A NEW ENTITY");
            entityToSpawn = entityType.create(pBlockEntity.getLevel());
            pBlockEntity.setEntityToDisplay(entityToSpawn);
        }

        float scale = 0.3f;
        pPoseStack.pushPose();
        pPoseStack.translate(0.5f, 1f, 0.5f);
        pPoseStack.scale(scale, scale, scale);

        entityDispatcher.render(entityToSpawn, 0.0D, 0.0D, 0.0D, 0.0F, 1.0F, pPoseStack, pBufferSource, 15728880);
        pPoseStack.popPose();

So the entity I want to display is stored in a block entity

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, Recently I have been hosting an RLcraft server on Minecraft Forge Version 1.12.2 - 14.23.5.2860 I originally had lag issues and I chalked it up to playing on less than perfect hardware so I moved the server to better hardware(i9-9900k with 64GB of RAM for 1 player.) After lots of troubleshooting I discovered a couple of things. World saving was causing the MSPT to spike to over 2000Miliseconds and was happening every minute. This kind of makes sense as the world was pre-generated and is over 100GB. I learned that I could turn off world saving and just schedule that and that resolved that issue. After that issue was resolved I discovered another issue. It appears that when exploring chunks, any chunks explored stay loaded. They persist. I was originally thinking that this had to be a mod issue, but it didn't seem like anyone was talking about it. This isn't really a problem on packs with few worldgen mods or just few mods in general, but on beefier packs it becomes a problem. I went through forge changelogs and found this line. Build: 1.12.2-14.23.5.2841 - Thu Aug 29 01:58:50 GMT 2019 bs2609: Improve performance of persistent chunk checks (#5706) Is this a related item to what I am dealing with or just something else?   I went ahead and created a new dedicated server with Just Forge 14.23.5.2860, spark reforged, and it's core mods. I was able to replicate the issue and log it with spark. Hopefully you're able to see this spark profile. It basically shows that as I explored the chunk loading persisted(2000 chunks loaded over 10 minutes with one player)The view distance is set to 10 so that should be 200 chunks per player. If I don't move the loaded chunks are 200. I was however able to fix the persistent chunk issue if I save the world more frequently. My question is, is this intended function of the game or is this a bug? Everywhere I read seems to indicate Minecraft servers save every 5 minutes and not every minute. Can chunks not unload if the world does not autosave. Additionally. Autosave specifically appears to fix this issue. Manually running save-all does not resolve the issue.   I realize this is kind of a log one, sorry. Please let me know if you require further information. Thanks in advance for your time. https://spark.lucko.me/NvlMtC39Yt https://imgur.com/a/K0oyukx https://pastebin.com/z0qGu1Vh  
    • Thank you so much, I had originally tried to allocate 16 gb of ram but still had the same issue with the lag, 12 was perfect.
    • Something related to shaders - check the config file of this mod - maybe you can disable shaders there
    • Add -Dfml.earlyprogresswindow=false to your JVM args
  • Topics

×
×
  • Create New...

Important Information

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