[1.8] Need something stronger than ignorefrustrumcheck

[gummby8 26]

So my mob is quite large. Normally ignorefrustrumcheck would suffice but for some reason it does not seem to be doing its job now. It appears after the player turns its back on the bounding box and goes 10-20 blocks away, it stops rendering regardless.

 

Screenshots

 

 

front

https://dl.dropbox.com/s/cky3wzxzn6gewb8/Screenshot%202016-07-29%2023.08.44.png?dl=0[/img]

from side, not looking at bounding box, frustrum check working

https://dl.dropbox.com/s/t7xm15jdofkh0fs/Screenshot%202016-07-29%2023.09.01.png?dl=0[/img]

looking at bounding box from the side of mob

https://dl.dropbox.com/s/frebihlemfxnkkl/Screenshot%202016-07-29%2023.09.12.png?dl=0[/img]

looking away from bounding box

https://dl.dropbox.com/s/kagrrph9td9aik7/Screenshot%202016-07-29%2023.09.20.png?dl=0[/img]

Looking away 2 degrees more and it dissapears

https://dl.dropbox.com/s/n7uiby6g1x4g2yn/Screenshot%202016-07-29%2023.09.24.png?dl=0[/img]

 

 

 

Entity Class

public class EntitySandWorm  extends EntityMob
{

    public EntitySandWorm(World worldIn)
    {
        super(worldIn);
        this.setSize(4.0F, 4.0F);
        this.isImmuneToFire = true;
        this.experienceValue = 5;
        this.targetTasks.addTask(1, new EntityAIFindEntityNearestPlayer(this));
        this.ignoreFrustumCheck = true;
    }

    @Override
    @SideOnly(Side.CLIENT)
    public boolean isInRangeToRender3d(double x, double y, double z)
    {

        return true;
    }

    /**
     * Called to update the entity's position/logic.
     */
    public void onUpdate()
    {
        super.onUpdate();
        this.ignoreFrustumCheck = true;
        
        
        
        
        
        
        
    }









    


    


}

 

 

 

Render Class

@SideOnly(Side.CLIENT)
public class RenderSandWorm extends RenderLiving
{
ResourceLocation rec = new ResourceLocation("mb:textures/mobs/SandWorm.png");

    public RenderSandWorm(RenderManager renderManager, ModelBase model, float shadowSize) {
	super(renderManager, model, shadowSize);


    }
    
    @Override
    public boolean shouldRenderLiving(EntityLiving p_177104_1_, ICamera p_177104_2_, double p_177104_3_, double p_177104_5_, double p_177104_7_)
    {
    	return true;
    }

    @Override
    public boolean shouldRender(Entity entity, ICamera camera, double camX, double camY, double camZ){
    	return true;
    }


@Override
protected ResourceLocation getEntityTexture(Entity entity) {

	return new ResourceLocation("mb:textures/mobs/SandWorm.png");
}

@Override
public void doRender(EntityLiving entity, double x, double y, double z, float p_76986_8_, float partialTicks) {
	super.doRender(entity, x, y, z, p_76986_8_, partialTicks);

	GL11.glPushMatrix();
	float scale = 5F;
	GL11.glScalef(scale, scale, scale);
	GL11.glTranslatef(0.0F, -10F, 0.0F);
	GL11.glPopMatrix();
}

}

 

 

[Animefan8888 490]

Did you use the entity registry code.

[gummby8 26]

Did you use the entity registry code.

 

Are you asking if I registered the entity? Yes otherwise it would not appear at all. Hence the screenshots

[LexManos 1470]

If the chunk the entity is in get culled there isnt much you can do about it, why is your entity so big, could you not try making it multiple parts and making sure that those sub-parts are in chunks that dont get culled?

[gummby8 26]

If the chunk the entity is in get culled there isnt much you can do about it, why is your entity so big, could you not try making it multiple parts and making sure that those sub-parts are in chunks that dont get culled?

 

How far does one need to be for a chunk to be culled? I am only 20 or so blocks away.

 

I could make it multiple entities. It may actually solve a few animating problems I was going to run into

[LexManos 1470]

It needs to be outside your frustrum

[gummby8 26]

why is your entity so big,

could you not try making it multiple parts and making sure that those sub-parts are in chunks that don't get culled?

 

Why so big? Shock value, it eats the player and transports them into a "dungeon dimension" of sorts. Where the player kills the beast from the inside.

 

Can I make it multiple parts? I am not sure in which way you mean. Do you mean a multi part entity like the dragon? I have recreated a few multi part mobs before, none quite as large. Will the extra parts or EntityDragonPart(s), ensure the whole creature stays rendered so long as 1 EntityDragonPart is close to the player?

 

Or do I need to make a Multi-Entity....Entity? Where it is a grouping of separate entities each with their own renderer?