Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Missing support for renamed LinearMipmapLinearFilter

See original GitHub issue

LinearMipMapLinearFilter was renamed in three@v0.107.0

I’m using three@0.104.0 (obviously <0.107.0) which – according to your Relases-Log – should be compatible with the latest version of postprocessing, as it’s in range 0.102.0 ≤ x < 0.116.0.

But the console states:

WARNING in ../node_modules/postprocessing/build/postprocessing.esm.js 10510:15-39
"export 'LinearMipmapLinearFilter' was not found in 'three'

Should be fixable by a simple LinearMipMapLinearFilter || LinearMipmapLinearFilter I think! Maybe I’ll find the line and submit a PR.

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

vanruesccommented, Apr 20, 2020

Am I missing something?

The constant was renamed in a backwards-compatible way; the old constant still exists in the current version of three. So when a new version is used together with postprocessing, both constants are available and can be imported.

1reaction

guischdicommented, Apr 20, 2020

How often and where do you see console spam?

It’s just the LinearMipmapLinearFilter thing once and toneMapped warnung multiple times (2 at startup + many at animating an effect/pass by re-adding it to the EffectComposer)

It shouldn’t. If it did, there would be an error message.

Yeah, I now think this is some other internal bug. Thanks for clarifying!

only way to get rid of this warning is to upgrade three to 0.108.x or downgrade postprocessing to 6.10.x.

Unfortunately I can’t upgrade three for internal project reasons. Downgrading postprocessing to 6.10.0 didn’t do the trick: the warnings disappeared but the canvas stays black. But nevermind! I can use 6.13.3 and if I know it’s safe, I can ignore those warnings. (Maybe you could document which warnings to expect when using the current version of postprocessing?). Thanks a lot for your quick response!

Top Results From Across the Web

Folder Missing after Renaming it in the Pipeline Releases

Hi, I renamed one of our folders in the Azure Releases Pipeline. It does not contain a special character. As you can see...

Missing iCloud files - Apple Community

I tried renaming the folder back to Documents and it's telling me that this folder can't be renamed because there's already a folder...

Image disappeared when I renamed it... - Microsoft Community

I renamed a picture- jpeg- from the camera img00332 or whatever to a real name that I could find, and it disappeared.

Rename Symbol Missing Some Uses · Issue #949 · microsoft/AL

Using Rename Symbol to rename a field doesn't rename their use in: Event subscribers e.g. OnAfterFieldValidate subscription Field properties ...

Repair moves/renames - TortoiseSVN

The following screenshot shows how the file TSVN-Support.ods was renamed to ... They show up in the commit dialog as "missing" and "non-versioned"....