ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-12-16T08:25:58-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22289Plugin for projecting Latitude Longitude grids into other forms: Robinson, Me...2023-12-16T08:25:58-05:00John PatchettPlugin for projecting Latitude Longitude grids into other forms: Robinson, Mercator, Stereographic, Lambert Conformal Conic@berkgeveci We, @linneapalmstrom , LANL, RAPIDS2, would like to see a new plugin, Latitude Longitude reproject that leverages the new default superbuild inclusion of vtkGeovisCore. Our uses have requested Robinson, Mercator, Stereograp...@berkgeveci We, @linneapalmstrom , LANL, RAPIDS2, would like to see a new plugin, Latitude Longitude reproject that leverages the new default superbuild inclusion of vtkGeovisCore. Our uses have requested Robinson, Mercator, Stereographic, Lambert Conformal Conic projections. In addition they requested a cartesian projection on a sphere (which we will add a separate issue for).John PatchettJohn Patchetthttps://gitlab.kitware.com/paraview/paraview/-/issues/22288add_pv_test testing function undefined but still used2023-09-08T03:18:01-04:00Louis Gombertadd_pv_test testing function undefined but still usedThe CMake function/macro `add_pv_test` does not seem to be defined anymore even though it is used 4 times throughout the file [Clients/Testing/XML/CMakeLists.txt](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Clients/ParaVie...The CMake function/macro `add_pv_test` does not seem to be defined anymore even though it is used 4 times throughout the file [Clients/Testing/XML/CMakeLists.txt](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Clients/ParaView/Testing/XML/CMakeLists.txt), which could indicate dead tests and unused CMake code paths.
It is probably a leftover from this cleanup commit https://gitlab.kitware.com/paraview/paraview/-/commit/2c00d068f8d523e494d2173399980f8ce647e1a3
cc @mwestphal @ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22287information/FileProperties section does not display correct filename correspo...2023-09-07T03:28:29-04:00이상준 / 학생 / 에너지시스템공학부information/FileProperties section does not display correct filename corresponding to the one being rendered.In the <Information> Panel, the Name section under <File Properties> should have displayed the file that is currently being rendered. However, the most new release 5.11.1 only shows the very first file of the series.
At least up to Para...In the <Information> Panel, the Name section under <File Properties> should have displayed the file that is currently being rendered. However, the most new release 5.11.1 only shows the very first file of the series.
At least up to ParaView 5.6.2, it was showing the correct file.
Related forum post is https://discourse.paraview.org/t/file-name-does-not-appear-in-information-fileproperties-section-y/12821https://gitlab.kitware.com/paraview/paraview/-/issues/22286TemporalParticlesToPathlines is broken in nightly build2023-12-01T10:50:45-05:00Jean M. FavreTemporalParticlesToPathlines is broken in nightly buildThe TemporalParticlesToPathlines produces lots of erroneous lines because of what seems like an indexing error. The attached Python script works very well with the nightly build ParaView-master-5.11.1-1587-geefb004e84-MPI-Linux-Python3.9...The TemporalParticlesToPathlines produces lots of erroneous lines because of what seems like an indexing error. The attached Python script works very well with the nightly build ParaView-master-5.11.1-1587-geefb004e84-MPI-Linux-Python3.9-x86_64 (see Good_TemporalParticlesToPathlines.png), but is totally broken with the next nightly, i.e. ParaView-master-5.11.1-1595-g499dc238e8-MPI-Linux-Python3.9-x86_64 (see Bad_TemporalParticlesToPathlines.png)
![Bad_TemporalParticlesToPathlines](/uploads/9ec80ba0bce924a8d504d07773c82ee8/Bad_TemporalParticlesToPathlines.png)
![Good_TemporalParticlesToPathlines](/uploads/b67025f25e0473f34803c21ef688a560/Good_TemporalParticlesToPathlines.png)
[pvTemporalParticlesToPathlines.py.gz](/uploads/f5f718fb89715775c98c8a5b4112e316/pvTemporalParticlesToPathlines.py.gz)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22285ProcessIds cannot be shown in ParaView when using local rendering2023-09-06T04:58:24-04:00Mathieu Westphal (Kitware)ProcessIds cannot be shown in ParaView when using local renderingProcessIds are a recently introduced attributes data, similar to GlobalIds. The filter `GenerateProcessIds` can generate such ideas,
however, they are not copied to the client when using client/server with local rendering.
Step to repro...ProcessIds are a recently introduced attributes data, similar to GlobalIds. The filter `GenerateProcessIds` can generate such ideas,
however, they are not copied to the client when using client/server with local rendering.
Step to reproduce:
- run pvserver, run paraview
- Connect to pvserver
- Make sure remote rendering threshold is higher than 20Mb
- Sphere, Apply
- GenerateProcessIds, Apply
- Try to color with ProcessIds, no data is visible and solid color is used, this is a bug
- A simple work around is to use calculator to copy the array in a non ProcessIds arrays
This is probably caused by the copy of the surfacic data from the server to the client which probably ignore the ProcessIds
Note: The following tests are impacted by this bug and should be modified whenever this bug is fixed:
- DistributePoints
- GenerateProcessIds
- GhostCellsGeneratorSynchronizehttps://gitlab.kitware.com/paraview/paraview/-/issues/22284Issue while reading data from lagrangian particles generated by OpenFOAM usin...2023-09-05T11:42:41-04:00franco otaolaIssue while reading data from lagrangian particles generated by OpenFOAM using the OpenFOAM readerHello,
when opening a simulation with lagrangian particles done in OpenFOAM, there is an issue with the time stamps of the particles which blocks the possibility of using for example the temporal particles pathlines filter to create the ...Hello,
when opening a simulation with lagrangian particles done in OpenFOAM, there is an issue with the time stamps of the particles which blocks the possibility of using for example the temporal particles pathlines filter to create the path that the particles followed during the simulation, even though the data 'is there'. Here is the discussion of about the issue: https://discourse.paraview.org/t/lagrangianparticletracker-example-file/571 , the error that I am getting (using paraview 5.11.1 with OpenFOAM 2306) is the following:
```
ERROR: In vtkTemporalPathLineFilter.cxx, line 343
vtkTemporalPathLineFilter (000001E683425760): The input dataset did not have a valid DATA_TIME_STEPS information key
ERROR: In vtkExecutive.cxx, line 741
vtkPVCompositeDataPipeline (000001E692199690): Algorithm vtkTemporalPathLineFilter (000001E683425760) returned failure for request: vtkInformation (000001E690439420)
Debug: Off
Modified Time: 2518182
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FROM_OUTPUT_PORT: 0
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
```
here the files of the case with some data can be downloaded, the data was to large to upload directly to the gitlab [link](https://filesender.utc.fr/filesender/?s=download&token=30fc3d13-37cb-47d4-aab3-d82b8632b53e)
best regardshttps://gitlab.kitware.com/paraview/paraview/-/issues/22283DSP: SoundQuantitiesCalculator can produce uninitialized values2023-09-12T21:46:58-04:00Mathieu Westphal (Kitware)DSP: SoundQuantitiesCalculator can produce uninitialized valuesSoundQuantitiesCalculator can produce uninitialized values:
- Load DigitalSignalProcessing plugin
- Sphere, Apply
- GenerateTimeSteps, generate 10 ts, apply
- GenerateSpacioTemporalHarmonics, Apply
- TemporalMultiplexing, uncheck normal...SoundQuantitiesCalculator can produce uninitialized values:
- Load DigitalSignalProcessing plugin
- Sphere, Apply
- GenerateTimeSteps, generate 10 ts, apply
- GenerateSpacioTemporalHarmonics, Apply
- TemporalMultiplexing, uncheck normals, Apply
- SoundQuantitiesCalculator, For destination mesh choose Sphere, Apply
- Color by Mean Pressure.
- Value on point 0 is uninitialized (eg: 4.7e-310)
![image](/uploads/272c7aeef11e481f9261dcf3c7e962c0/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22282ParaView backward compatibility framework does not support deprecating proxy2024-03-18T04:53:50-04:00Mathieu Westphal (Kitware)ParaView backward compatibility framework does not support deprecating proxy**TLDR: ParaView backward compatibility framework does not support deprecating a proxy while keeping retro compatibily by using another proxy.**
First lets fix some vocabulary:
- Deprecation: Flagging a component or service as outdate...**TLDR: ParaView backward compatibility framework does not support deprecating a proxy while keeping retro compatibily by using another proxy.**
First lets fix some vocabulary:
- Deprecation: Flagging a component or service as outdated and slated for removal in the future, so that user can adapt their process.
- Backward compatibility: Make modern version of a software working with old process.
ParaView has deprecation and backward compatibility framework and they usually works quite well.
There is one simple usecase that is not supported by the backward compatibility framework, the **removal of an existing proxy**, like a filter.
1. Deprecating a filter
A proxy can be tagged as `deprecated` using the following syntax:
```
<SourceProxy class="vtkMyFilter"
name="MyFilter">
<Deprecated deprecated_in="5.10" to_remove_in="5.12">
This has been replaced by 'ProbeLine'. Please consider
using that instead.
</Deprecated>
```
Using this filter will warn the user that it is deprecated and that it should change its processes before it is ultimely removed
2. Replacing a filter by another with the same name using backward compatibility mechanism
An existing proxy can be replaced by another as long as they keep the same name, it is handled in `vtkSMStateVersionController.cxx` for XML and in `_backwardscompatibilityhelper.py` for python.
The XML approach is very generic and give all latitude to the developer.
The python approach **requires a proxy** to exist before being able to modify anything on it.
It means this is possible to swap a filter by another **as long as the first proxy actually exist**, eg for plot over line:
```
if compatibility_version <= (5, 9):
if key == "PlotOverLine":
# in 5.10, we changed the backend of Plot Over Line
# This restores the previous backend.
probeLine = builtins.getattr(module, "PlotOverLineLegacy")(**kwargs)
return probeLine
```
3. Deprecating an existing proxy and replacing by another proxy
In this simple case, the python approach breaks as the compat code cannot be reached as the previous name does not exist anymore.
This is a strong limitation of the approach and should be fixed.
- A simple fix would be to have a .xml file dedicated to store old proxy name that would only be accessible when using backward compat mode in python,
- another fix would have all python calls go through some logic to see if a specific name existed at some point and trigger some compat code.https://gitlab.kitware.com/paraview/paraview/-/issues/22281Issue with representation type selection with Qt6 on Arch Linux2024-01-25T10:27:58-05:00Yvan FournierIssue with representation type selection with Qt6 on Arch LinuxHello,
On Arch Linux, building ParaView with Qt6, I have an issue with a the representation mode selection:
```plaintext
When right-clicking on a mesh ans selecting the representation type with th checkbox selection, everything is fine...Hello,
On Arch Linux, building ParaView with Qt6, I have an issue with a the representation mode selection:
```plaintext
When right-clicking on a mesh ans selecting the representation type with th checkbox selection, everything is fine.
When using the combo box (either on the toolbar or in the properties tab), nothing changes (the default remains at “Surface”).
```
The latest version I compiled (a few days ago) is:
```plaintext
Client Information:
Version: 5.11.1-1525-g2c4973080c
VTK Version: 9.2.6-4140-g40c19ea4e8
Qt Version: 6.5.2
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /usr/lib/python3.11
Python Library Version: 3.11.3 (main, Jun 5 2023, 09:32:32) [GCC 13.1.1 20230429]
Python Numpy Support: On
Python Numpy Path: /usr/lib/python3.11/site-packages/numpy
Python Numpy Version: 1.25.1
Python Matplotlib Support: On
Python Matplotlib Path: /usr/lib/python3.11/site-packages/matplotlib
Python Matplotlib Version: 3.7.2
Python Testing: Off
MPI Enabled: On
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: Sequential
SMP Max Number of Threads: 1
OpenGL Vendor: Intel
OpenGL Version: 4.6 (Core Profile) Mesa 23.1.6
OpenGL Renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
Accelerated filters overrides available: No
Connection Information:
Remote Connection: No
```
I have the same behavior with the NVIDIA driver (under optirun).
```plaintext
OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 3.2.0 NVIDIA 535.98
OpenGL Renderer: NVIDIA GeForce GTX 1050 with Max-Q Design/PCIe/SSE2
```
Other combo-box based settings seem to work fine
I do not observe it when building against Qt5.
Best regards,https://gitlab.kitware.com/paraview/paraview/-/issues/22280Paraview 5.9.1 on MacOS version 10.15.7 (catalina) does not add text2023-09-01T15:14:58-04:00John XiaParaview 5.9.1 on MacOS version 10.15.7 (catalina) does not add textClick Sources -->Alphabetial-->text creates the text object - but does not put it on the window - either in interactive mode or by specifying window co-ordinates. Text Prop Mode == 2D Text widget (default).Click Sources -->Alphabetial-->text creates the text object - but does not put it on the window - either in interactive mode or by specifying window co-ordinates. Text Prop Mode == 2D Text widget (default).https://gitlab.kitware.com/paraview/paraview/-/issues/22279Catalyst State files do not capture extracted cells2023-10-23T10:32:20-04:00Phil SmithCatalyst State files do not capture extracted cells* Sphere, Apply
* Select a cell, Create Extract Selection filter, Apply
* Save Catalyst state -- it's missing the selection source.
This works almost as expected if you save Python trace instead. See issues: [20538](https://gitlab.kitwa...* Sphere, Apply
* Select a cell, Create Extract Selection filter, Apply
* Save Catalyst state -- it's missing the selection source.
This works almost as expected if you save Python trace instead. See issues: [20538](https://gitlab.kitware.com/paraview/paraview/-/issues/20538) and [21372](https://gitlab.kitware.com/paraview/paraview/-/issues/21372)
This also happens if you use the find dialog to extract the cells as well.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22278The window arrangement dose not load the main window in the proper place when...2023-08-24T12:02:46-04:00Phil SmithThe window arrangement dose not load the main window in the proper place when recalled on Windows and MacWhen saving a window arrangement on Mac and Windows( Linux appears to work properly), if you have you views that are detached from your main window, it will not load the main window in the proper location. I tested this on ParaView v5.11...When saving a window arrangement on Mac and Windows( Linux appears to work properly), if you have you views that are detached from your main window, it will not load the main window in the proper location. I tested this on ParaView v5.11.1 Master on all three platforms. When you load the window arrangement, that has been saved, the main window will load in the center of the current display. The detached views load in the locations where they were saved. Here is an example of what I saved( I have used my Mac in this example):
![image.png](/uploads/9652f827ae25c048019c693ceaee044c/image.png)
And then this is how it Loaded:
![image.png](/uploads/148c57e4e47510966a9fb1e8ddbf21a5/image.png)
If you will notice the main window stayed where it was when ParaView was loaded, however the rest of the views loaded where they saved at. The main window should have shifted to where it was originally saved at.
I have a suggestion that will make this potentially easier to manage. We can stack the windows vertically on either side within the main window. However we can only have one column on each side of the main window. How hard would it be to be able to stack the windows side by side as well? This would correct this problem. Typically a monitor is wider than it is tall, so this would make the best use of the screen real estate.
In addition, when opening ParaView with all of the views detached, only the main window opens up. In order to get the views to appear, Load Window Arrangement or selecting each view that you want is necessary. The solution that I have suggested above will fix this problem as well, because I have noticed when you close ParaView and then re-open it, the views will remain where they were the last time they were used, as long as they are docked within the main window. This way the user will not have to perform the additional step of loading the window arrangement when he re-opens ParaView.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22277Add regression test for LAMMPS dump reader (in VisItBridge) for multiple time...2023-08-23T14:50:36-04:00Kenneth MorelandAdd regression test for LAMMPS dump reader (in VisItBridge) for multiple time stepsThe LAMMPS dump format supports holding multiple timesteps, and the VisIt reader can read through these timesteps. There was a bug in the VisIt Bridge that prevented all but the first timestep to be read. This problem was fixed in MRs !6...The LAMMPS dump format supports holding multiple timesteps, and the VisIt reader can read through these timesteps. There was a bug in the VisIt Bridge that prevented all but the first timestep to be read. This problem was fixed in MRs !6454 and https://gitlab.kitware.com/paraview/visitbridge/-/merge_requests/101. The regression test currently only tests a file with one timestep. A regression test to test for multiple time steps should be added.
Here is a small, simple LAMMPS dump file with 2 timesteps.
[lammps-multitime.dump](/uploads/9df3b301f5bf33766c7c99a28c94483d/lammps-multitime.dump)https://gitlab.kitware.com/paraview/paraview/-/issues/22276MapDataArrayToMultiTextureAttribute not wok in paraview 5.11.02023-08-24T03:25:18-04:00ydu yduMapDataArrayToMultiTextureAttribute not wok in paraview 5.11.0I made a filter to texture a model multiple images.
In representation of the filter, I used MapDataArrayToMultiTextureAttribute to implement this feature.
But MapDataArrayToMultiTextureAttribute texture nothing on model.
I tried MapData...I made a filter to texture a model multiple images.
In representation of the filter, I used MapDataArrayToMultiTextureAttribute to implement this feature.
But MapDataArrayToMultiTextureAttribute texture nothing on model.
I tried MapDataArrayToMultiTextureAttribute by vtk console program. It worked fine.
One clue I found that vtk console generated vtkOpenGLPolyDataMapper but paraview generated vtkCompositePolyDataMapper2.https://gitlab.kitware.com/paraview/paraview/-/issues/22275Volume rendering and Ray Tracing are SLOW2023-08-24T16:51:24-04:00W. Alan ScottVolume rendering and Ray Tracing are SLOWVolume rendering and ray tracing are painfully, ridiculously slow. Here is how to replicate.
* ParaView 5.11.1, Linux, builtin server.
* Settings/ Advanced/ RenderView/ Show Annotation. All we need is the framerates.
* Open g1s1-10fps...Volume rendering and ray tracing are painfully, ridiculously slow. Here is how to replicate.
* ParaView 5.11.1, Linux, builtin server.
* Settings/ Advanced/ RenderView/ Show Annotation. All we need is the framerates.
* Open g1s1-10fps.e.16.[0-15] Apply. Color by ids. Note dataset is only 20,000 cells and 28,000 points. Not sure if that is relevant.
* > Frame rate on my workstation is about 560 fps. Way nice.
* Volume Render.
* > Frame rate on my workstation is about 16 fps. Usable, but ouch.
* Turn off Volume Rendering, turning on Surface. Turn on Ray Tracing.
* > Frame rate on my workstation is about 22 fps. Usable, but ouch - especially as we are only ray tracing the outside surface.
* Change Surface to Volume Rendering.
* > Frame rate on my workstation is about 3-4 fps. Not really usable.
For real datasets with many, many more cells this would be basically unusable. I believe we would multiply time spent by the area (which isn't impacted by cell count) and depth (which would be impacted by cell count).
The other issue is that these renders happen every time someone changes something in state, such as changes visibility of filters.https://gitlab.kitware.com/paraview/paraview/-/issues/22274New defaut colormap2024-03-23T23:51:52-04:00W. Alan ScottNew defaut colormapPlease make the colormap named Fast on the Presets dialog the new default map.
Issue # 22271 created the Fast color map.
Showstopper for 5.13.0.Please make the colormap named Fast on the Presets dialog the new default map.
Issue # 22271 created the Fast color map.
Showstopper for 5.13.0.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22273New default palette2024-03-23T23:51:57-04:00W. Alan ScottNew default palettePlease make the palette background color named Warm Gray Background (98,93,90) the new default.
#22270 created the palette.
Showstopper for 5.13.0.Please make the palette background color named Warm Gray Background (98,93,90) the new default.
#22270 created the palette.
Showstopper for 5.13.0.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22272Find Data Panel should be able to find all points using coords instead of jus...2023-08-25T09:24:54-04:00Phil SmithFind Data Panel should be able to find all points using coords instead of just one point per blockWhile it may be useful to find only one point per block in some cases, using the Find Data Panel, when finding data this way there should be an option to find all the points that are within the epsilon value, on all blocks. To test this ...While it may be useful to find only one point per block in some cases, using the Find Data Panel, when finding data this way there should be an option to find all the points that are within the epsilon value, on all blocks. To test this I used the can.ex2 and v5.11.1 master. Here are the steps:
1. Open can.ex2, apply
2. Select View-\>Find Data
1. Data Producer: can.ex2
2. Element Type: Point
3. Select: Point, nearest to, 0 ,0 ,0 50 for the epsilon value.
It only found one point per block
There should be an option to enable finding all points on all the blocks within this epsilon from a given starting location.
The way the Find Data Panel operates now is great for some applications, and maybe this should be the default, but there should be an option to be able to select all the points within that epsilon value.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22271New colormap2023-09-12T20:50:02-04:00W. Alan ScottNew colormapPlease add the attached color map to the Presets dialog. It is to be called "Fast".
What we did and why: This map is from Francesca Samsul, the color map master behind sciviscolor.org. The Cool to Warm map is a very good map as it is...Please add the attached color map to the Presets dialog. It is to be called "Fast".
What we did and why: This map is from Francesca Samsul, the color map master behind sciviscolor.org. The Cool to Warm map is a very good map as it is very linear and color blind friendly. However, there are other maps that have better discriminating power. This new map is one of them.
[Fast.xml](/uploads/c611b8f4c4bb0259fdc1ec932d4aa0b8/Fast.xml)
Here is an image of the new color map, Fast:
![Fast](/uploads/da8394caac6506f428f485630204015b/Fast.PNG)
Please rearrange the Presets dialog as follows. Note that this is a prototype (i.e., not polished), and probably shouldn't be cut and pasted in for the actual preset. Also, I am trying to not have to update this page twice. Thus moving the new default for 5.13.0 at the top of the list.
What I did and why: Of all of the presets, I like "Gray and Red" the least. (If someone feels otherwise, I'm good with a different arrangement.). Next, I wanted "Cool to Warm" and "Cool to Warm (Extended)" next to each other. Thus, the left column went down one row. The right column also went down one row, with my favorite rainbow moving to the top, "Turbo". I figure that if we are going to have people use a Rainbow, lets encourage a decent one.
![New-Presets](/uploads/9135f44dad4f4668ef2254a585fef923/New-Presets.png)
The details of the discussions concerning this change are in this discourse post. https://discourse.paraview.org/t/replacement-default-color-map-and-background-palette/12712.
Marking as showstopper for 5.12.0.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22270New palette2023-09-12T20:42:17-04:00W. Alan ScottNew palettePlease create a new background palette. Note I changed this issue to split it into two parts - adding the palette, ad making it default. This new palette will NOT be default for 5.12.0. We will move it into master right after 5.12.0 dr...Please create a new background palette. Note I changed this issue to split it into two parts - adding the palette, ad making it default. This new palette will NOT be default for 5.12.0. We will move it into master right after 5.12.0 drops. The palette color will be 98, 93, 90. It shall be referenced as Warm Gray Background" below. For the palette menu:
* Rename "Warm Gray Background" to "Dark Gray Background".
* As the second item in the list, add new "Warm Gray Background", as defined as 98, 93, 90.
Thus, the new Palette list is:
* Blue Gray Background (Default)
* Warm Gray Background
* Dark Gray Background
* Light Gray Background
* White Background
* Black Background
* Gradient Background
* Edit Current Palette ...
For screenshots of what this new background will look like, see https://discourse.paraview.org/t/replacement-default-color-map-and-background-palette/12712.
This is a showstopper for 5.12.0.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikis