BakedQuad Fix Problems about loliasm HOT 20 OPEN

I'll take a look, thanks for the info provided.

from loliasm.

Np! If you want any more just ask. I tried to provide as much as I could because the bugs were pretty elusive and having too little info is never fun.

from loliasm.

verified/ seems related
crash-2021-10-17_04.30.55-client.txt

but this is with Quark, CCL, and IF - crash when playing around with the tank, updated loli config with new bakeQuads and crash upon world load.

removing Loli let me load back into my world. Removing the line from the config might have achieved same result but on next load it would be auto added back i guess.

EDIT: Will test now with version 3.2.1

from loliasm.

Update: All looks good so far.

from loliasm.

Update: #1 and #4 seem fixed with 3.2.1. I now actually have a crash for the item frame thing, which is gotten with the above config/modlist/etc on 3.2.1. Report is here
Secondary update, grass thing affects all block colorizers, not just grass. So AR crystals/LV blocks/etc

from loliasm.

also noticed this while playing. creativecoreMD added multiple times and still trying to add itself

from loliasm.

Update: #1 and #4 seem fixed with 3.2.1. I now actually have a crash for the item frame thing, which is gotten with the above config/modlist/etc on 3.2.1. Report is here Secondary update, grass thing affects all block colorizers, not just grass. So AR crystals/LV blocks/etc

@Silfryi try launching with this: loliasm-3.3.zip (unzip bc GitHub doesn't allow .jar uploads). Beware there will be verbose logging, but hopefully it'll give me more info of why its failing to render the quads when the item frame is being rendered.

from loliasm.

@SilverBackSpartan that'll be fixed in 3.3, just need to handle heuristic edge-case

from loliasm.

@Rongmario here's the new log upon rendering the item frame and crashing: log

from loliasm.

@Rongmario here's the new log upon rendering the item frame and crashing: log

Just noticed: org.spongepowered.asm.mixin.transformer.throwables.InvalidMixinException: The specified mixin 'zone.rong.loliasm.client.models.bakedquad.mixins.NewBakedQuadCallsRedirector' was not found,

very weird; since earlier in the log:

[LoliASM]: Defining NewBakedQuadCallsRedirector Mixin. With these mixin targets: [malte0811.industrialwires.client.render.TileRenderMechMB, mekanism.client.render.MekanismRenderer, blusunrize.immersiveengineering.client.models.SmartLightingQuad, codechicken.lib.render.buffer.BakingVertexBuffer, zone.rong.loliasm.bakedquad.SupportingBakedQuad, forestry.storage.models.ModelCrate, codechicken.lib.util.VertexDataUtils, net.minecraft.client.renderer.block.model.FaceBakery]

I have no clue what it could be, debugged this to make sure it worked very well before... Damn.

from loliasm.

3. and 5) Seem to be fixed with 4.2!
4. however is still a bug, I still can't see the outer flywheel bits

from loliasm.

@Silfryi 4 as in the 4th one in OP? I haven't gotten that crash yet in my test env

from loliasm.

Sorry, I must've mistyped; I meant # 2. # 2 in OP is the only one still broken.

from loliasm.

@Silfryi mind just testing 4.4.1 when it gets released on CF? Just so we can try consolidate and find what the status is of this problem now.

from loliasm.

Yeah, will do. I've mostly moved on to 1.16 atm but it should be no issue.

from loliasm.

What a shame :'(

from loliasm.

AR's big enough I can only support one version, and the one I need to support is 1.16. I'll still test, I just won't be doing large amounts of playtesting to see if it's fixed fixed,

from loliasm.

It's fine, np

from loliasm.

Just tested, and 4.4.1 does not seem to fix # 2, which is the last problem still standing for this issue. Unsure what the cause is, but the quads still are not rendering.

from loliasm.

Just tested, and 4.4.1 does not seem to fix # 2, which is the last problem still standing for this issue. Unsure what the cause is, but the quads still are not rendering.

Thanks for testing, I'll consolidate a fix for 4.5.

from loliasm.