Jump to content

GL ERORR


BigBrother

Recommended Posts

Just installed Forge via the installer and began playing. When I tried swimming, everything was foggy- couldn't see much past a few blocks. A friend suggested checking error log for something. I looked for the error log... the new error file... it was 2.5MB! nothing but:

 

2013-07-21 11:08:25 [CLIENT] [sEVERE] ########## GL ERROR ##########
2013-07-21 11:08:25 [CLIENT] [sEVERE] @ Post render
2013-07-21 11:08:25 [CLIENT] [sEVERE] 1281: Invalid value

 

Same friend turning on and off Advanced OpenGL and restarting between on and off. I can see a bit more clearly with it off but that error is still being fire-hosed out.

 

installer: minecraftforge-installer-1.6.2-9.10.0.789.jar

Link to comment
Share on other sites

yes, 1.6 introduces fog in the water which is mitigated by the helm's water-related enchantments. However, if these enchantments exceed vanilla values, the water becomes OVERLY foggy and really... fogs things up. Optifine's clear water option clears it up.

 

The log was too large for any paste sites so I put it on my dropbox: https://dl.dropboxusercontent.com/u/41147386/mc/Forge/output-client%20%282%29.log

Link to comment
Share on other sites

Try without Optifine.

That doesn't look like the standard launcher either...

And the log im referring to is the client log in the .minecraft folder created by FML.

The one you posted is useless as it doesn't tell me how you're launching it, or what mods are loading, or anything.

 

Humm didn't pay attention to the new enchantmnets.

So.. what you're saying, is that if you create a unnatural enchantment that goes beyond Resperation's max level, it screws up the fog..

That kind seems right considering it probably does some basic math to generate how 'clear' the water should be anything above what it takes to make 100% would probable fuck things up.

 

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

The installer gave me a false positive as an install. It installed, gave me a forge 'version' that I foolishly used. The 'X mods loaded' didn't show but I thought it was something new and disregarded it.

 

All that aside, however, the error is showing up in the FML log too... and bloating the file. 1.5MB plain text is huge.

https://dl.dropboxusercontent.com/u/41147386/mc/Forge/ForgeModLoader-client-0.log

Link to comment
Share on other sites

The installer gave me a false positive as an install. It installed, gave me a forge 'version' that I foolishly used. The 'X mods loaded' didn't show but I thought it was something new and disregarded it.

What do you even mean by that?

 

All that aside, however, the error is showing up in the FML log too... and bloating the file. 1.5MB plain text is huge.

https://dl.dropboxusercontent.com/u/41147386/mc/Forge/ForgeModLoader-client-0.log

 

Interesting, and what strength of Respiration do you have equipped?Screen shots of your equipment would be nice.

As you say that you are giving yourself beyond vanilla max enchants.. this still doesn't sound like a Forge issue.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

First part: I used the installer, got a "Forge version" option to select and played the game with that, not knowing it wasn't actually Forge really.

 

Second part:

width=369 height=172https://dl.dropboxusercontent.com/u/41147386/mc/2013-07-23_11.45.39.png[/img]

 

I'm not cheating, the admin is using a plugin that allows enchants to go past vanilla but it still costs exorbitant amounts of exp.

Link to comment
Share on other sites

Still nto sure what 'Forge version wasnt actually forge really' means..

If you select the Forge profile in the new launcher, you will be playing Forge.

 

 

ya, i'm not gunna call this a bug unless mojang says it is.

I think this is just user stupidity.

I was right when i guess what was happening.

It's doing a fog value of 0.1F - respiration * 0.03F;

With a level of 4 that makes the fog value -0.02F which is a invalid value.

There is NO BENIFIT to a respiration > 3.

Hence why Mojang set the max level to 3.

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

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.