Missing support for renamed LinearMipmapLinearFilter
See original GitHub issueLinearMipMapLinearFilter 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 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...
Read more >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...
Read more >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.
Read more >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 ...
Read more >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"....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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 withpostprocessing
, both constants are available and can be imported.It’s just the
LinearMipmapLinearFilter
thing once andtoneMapped
warnung multiple times (2 at startup + many at animating an effect/pass by re-adding it to theEffectComposer
)Yeah, I now think this is some other internal bug. Thanks for clarifying!
Unfortunately I can’t upgrade
three
for internal project reasons. Downgradingpostprocessing
to6.10.0
didn’t do the trick: the warnings disappeared but the canvas stays black. But nevermind! I can use6.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 ofpostprocessing
?). Thanks a lot for your quick response!