Viewport issue using Canvaslayer and viewportsprite.

[0nepixel]

Runing under Windows 7
When you place a viewport as a child of a canvas layer the render target breaks and you can't use the viewportsprite to render the viewport's texture.

1. Create a new Canvaslayer, after that create a new viewport inside the canvaslayer and set a sprite as a child of the viewport node.
2. Create a new viewportsprite and assing the viewport (inside or outside the canvaslayer is the same).

At this point the viewport stop working and the viewportsprite can't access to the viewport's texture, also you can't call the viewport's texture from other canvaslayer using the viewportsprite (this method works just fine in versions before 2.1 stable).
Test Case Project:
https://drive.google.com/open?id=0B3mjAjcuXnKqZzBJQWlhQ2xrRm8

[ghost]

First of all thank you for your report and sorry for the delay.

We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.

We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?

For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.

Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.

Thanks in advance.

Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

[MeiHouwang]

The issue is still persist and greatly annoying in version 2.1.5
Will it be ever fixed?
Just please don't try to push it to 3.x branch, it is completely unusable by now and there is no sign that it will be usable in the following two years.

[akien-mga]

It's fixed in 3.1-dev, and will eventually be fixed in 3.0.x too if @RandomShaper's pull request is merged.
For 2.1, a cherry-pick could be considered.