Regressions next vs stable

[gchoqueux]

Resize rendering issue

@Desplandis

When I resize the browser window, the view becomes pixelated

next version	stable version

Wrong color in pole

@Desplandis

The pole color is white instead of color define with noTextureColor

// Define poles texture
view.tileLayer.noTextureColor = new THREE.Color(0x95c1e1);

Outer glow is disappeared in no realistic lighting

next version no out glow	stable version

Inner glow size change with distance in no realistic lighting

@Desplandis @airnez

big inner glow	little inner glow

Clipping issue

see #2619

Atmosphere issue

@Neptilo open a ticket to three-geospatial

Handle collision camera/terrain issue

@Desplandis

To reproduce in globe view : navigate across the mountains,
the option to enable collision is handleCollision in planar and globe controls.

Color layers issues

With 2 colors layers ( see example misc_colorlayer_visibility), some textures appear white.
There is an issue with the ColorLayer handling in LayeredMaterial.
The console shows the message: Texture image not loaded or has zero dimensions.
This issue might be older than the introduction of WebGLComposer

Examples issue

Examples broken, the issue comes : The error often comes from the lack of definition of setupLoadingScreen

• source_file_from_methods
• source_file_from_fetched_data
• source_file_from_parsed_data
• misc_custom_controls

Other reasons

• customColorLayerEffect
• effects_split
• misc_collada globe is black

[jailln]

@gchoqueux thanks but next time could you add more details and better reproduction please? Your issue is quite hard to understand... We managed to do so thanks to a discussion with @ftoromanoff though and we will break this issue into sub issues and address them separately.

[gchoqueux]

@jailln I added some details, let me know if there are still any unclear issues.

[Neptilo]

Regarding "Atmosphere issue":
I had not seen this before. I did a git bisect and figured this started from the upgrade to Three v182.
But upgrading three-atmosphere/three-geospatial doesn´t help and adds even more regressions.
Disabling logarithmicDepthBuffer in the renderer fixes those issues, but then that option was probably useful for something else...
Finally, this issue might be related, although it only refers to an orthographic view.

[Neptilo]

@gchoqueux I was told you may have some insights about our use of the logarithmic depth buffer. Would it be ok to disable it?

[airnez]

I tested it, it seems that z-fighting occurs between tiles when disabling logarithmic depth buffer. It is hard to capture using an animated image to post it here. I suppose this is the issue.

[Neptilo]

Reported takram-design-engineering/three-geospatial#100.