Jump to content

[1.12] setting lightmaps for entities and blocks [Solved]


nil

Recommended Posts

The context depends on the context, naturally, but I think what you're looking for is generally going to be the BufferBuilder#lightmap() method, if you're using the Tessellator. Otherwise, more specific questioning would be appreciated.

Fancy 3D Graphing Calculator mod, with many different coordinate systems.

Lightweight 3D/2D position/vector transformations library, also with support for different coordinate systems.

Link to comment
Share on other sites

I have also been trying to figure this out to no avail. I had code that worked back in 1.7.10 but I don't know when it broke because I took a long hiatus from modding with only a few short returns in that time. I hope you can find something that would work for you. I have some code that could work, but is very inefficient and actually breaks lighting within 16 blocks of the entity.

Link to comment
Share on other sites

I'm trying to set lighting for a custom projectile entity.

18 hours ago, SerpentDagger said:

but I think what you're looking for is generally going to be the BufferBuilder#lightmap()

Is there somewhere i can check the correct usage of this? I can't decifer what int p_187314_1_ and int p_187314_2_ do / how i have to set them.

 

5 hours ago, saxon564 said:

I have some code that could work

Does this contain BufferBuilder#lightmap()?

Link to comment
Share on other sites

1 hour ago, nil said:

Is there somewhere i can check the correct usage of this? I can't decifer what int p_187314_1_ and int p_187314_2_ do / how i have to set them.

It's used within Minecraft's rendering code, one example being located within BlockFluidRenderer#renderFluid().

I personally haven't used it extensively, so I'm not the best one to try and explain this, but the two ints seem to correspond to brightness, and range from 0 to ~220. I think they're (u, v) coordinates on Minecraft's lightmap texture.

In the fluid class I pointed to earlier, though, they result from the manipulation of the value returned from IBlockProperties#getPackedLightmapCoords().

What I've done with them is contour 3D graphs, which is independent of the world's lighting, so I'm not sure how to do that myself. In my work, I used the first as a sort of "base" brightness, and manipulated the second to alter it from there. I don't know if that's the generally used method, though.

 

It's worth noting, in case you're unfamiliar with the Tessellator, that this method should be used in accordance with the vertex format at hand, which is something you should learn a little about if you haven't already.

Edited by SerpentDagger

Fancy 3D Graphing Calculator mod, with many different coordinate systems.

Lightweight 3D/2D position/vector transformations library, also with support for different coordinate systems.

Link to comment
Share on other sites

On 11/28/2019 at 9:30 PM, saxon564 said:

I did notice my last working code was actually in 1.12.2 and included entity lighting.

The method you use works almost perfectly, however, the lighting effect doesn't get removed even after the entity is long dead. Do you use any methods to clear the created lighting?

On 11/28/2019 at 1:12 AM, SerpentDagger said:

It's worth noting, in case you're unfamiliar with the Tessellator, that this method should be used in accordance with the vertex format at hand

I have never used a tessellator, are there any examples i can look at to get a better understanding of this? Also what do you mean by vertex format?

Link to comment
Share on other sites

7 minutes ago, nil said:

The method you use works almost perfectly, however, the lighting effect doesn't get removed even after the entity is long dead. Do you use any methods to clear the created lighting?

You need to call a block update for the block the chicken occupies when it dies. I handle that in the livingUpdate method at the end of the method by having a check for if the chicken is dead and running the code.

Link to comment
Share on other sites

1 hour ago, nil said:

The method you use works almost perfectly

Ah, in that case you need not worry about the Tessellator or BufferBuilder#lightmap(), they're applicable in different scenarios than the one you seem to be dealing with. Sorry about that.

 

1 hour ago, nil said:

I have never used a tessellator, are there any examples i can look at to get a better understanding of this? Also what do you mean by vertex format?

The Tessellator is a commonly used method of rendering things directly in the world. In using it, you first apply various settings using the GlStateManager, then add vertices into the Tessellator's buffer, draw the buffer with Tessellator#draw(), and then reset the necessary settings with the GlStateManager.

A VertexFormat is applied when beginning to add vertices to the buffer, and it dictates what information each vertex requires. For example: you might use DefaultVertexFormats#POSITION_COLOR, in which case you would need to add position information, followed immediately by color information, to the vertex you're building.

Some general information about how the Tessellator works can be found here, but it's a bit outdated, so you should refer to my answer here for exact steps. Here's a simple example, but that was back when I was just learning about this stuff, so I got the translation wrong (as explained in the answer I followed up with). The rest's fine.

 

Like I said, though, it seems you've got a different situation here, so that's mostly just in case you have an insatiable thirst for MInecraft rendering knowledge.

Fancy 3D Graphing Calculator mod, with many different coordinate systems.

Lightweight 3D/2D position/vector transformations library, also with support for different coordinate systems.

Link to comment
Share on other sites

On 12/3/2019 at 12:37 AM, saxon564 said:

You need to call a block update for the block the chicken occupies when it dies

I assume you mean  this.world.checkLightFor(EnumSkyBlock.BLOCK,new BlockPos((int) x, (int) y, (int) z));

 

The issue is that my entity is a projectile, which means that it creates light at loads of different x,y and z positions. So i tried to remove the light the following way:

        if (this.emitsLight)
        {
        	double x = 0;
        	double y = 0;
        	double z = 0;
        	if(hasPrevLight)
        	{
        		removeLight(x,y,z);
        	}
            	this.addLight(10);
            	x = this.posX;
            	y = this.lastTickPosY;
            	z = this.lastTickPosZ;
            	this.hasPrevLight = true;
        }

with hasPrevLight set to false when the entity is spawned and

	private void removeLight(double x, double y, double z)
	{
		this.world.checkLightFor(EnumSkyBlock.BLOCK,new BlockPos((int) x, (int) y, (int) z));
	}

Sadly this doesn't remove the lighting along the path.

Link to comment
Share on other sites

The lighting updates its previous position as it moves. Unless the entity, or in your case projectile, is moving at over 1 block per tick then you don't need to track the last position. If you really need to, you can check every block in the 3x3 cube centered around the chicken but the need for that would be very rare as that would mean the entity would go perfectly between the corners of 2 blocks and not touch a mutual block. Share your whole class so I can see what you have setup.

Link to comment
Share on other sites

21 minutes ago, nil said:

Since the class is rather large what would be the best way to share it here?

Github is the best way to share code. If you upload it correctly, the it will allow others to fork your code and try to do their own debugging to help you, as well as they won't have to ask you to also share other classes, as all your classes will be available.

Link to comment
Share on other sites

You are setting x y and z back to 0 every tick, so it doesn't matter how many times you set it, you are always going to update the block at 0, 0, 0. I would declare x y and z at the top of the class instead of the method, this way you won't reset them back to 0 every tick.

Link to comment
Share on other sites

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

    • They were already updated, and just to double check I even did a cleanup and fresh update from that same page. I'm quite sure drivers are not the problem here. 
    • i tried downloading the drivers but it says no AMD graphics hardware has been detected    
    • Update your AMD/ATI drivers - get the drivers from their website - do not update via system  
    • As the title says i keep on crashing on forge 1.20.1 even without any mods downloaded, i have the latest drivers (nvidia) and vanilla minecraft works perfectly fine for me logs: https://pastebin.com/5UR01yG9
    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
  • Topics

×
×
  • Create New...

Important Information

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