Hernan

@JoelL Any chance of getting a version of the file? Thanks

@designit Could you share a file with us? You could send me a private message if you like. Thanks.

@drock019 If this is happening on VW 2024 we have identified an issue with some wall geometry generation that has been fixed for 2024 Update 1. If you have a file you could share with us that shows the problem we might be able to try it and make sure this fix addresses it. Thanks.

Hi @Narelle could you share a file with us? Thanks!

@Kaare Baekgaard This was implemented as an optimization to catch cases when users would attempt to update a raster viewport that might result in a very large image, e.g. if the viewport has a very large scale (much larger than the page bounds) or would otherwise result in an image over 150 Megapixels (actually a full "US Arch E" 36"x48" page at 300 dpi). We left the option to answer "Yes" in case the user knows what they're doing, maybe they're only slightly over the size, or have a massive amount of RAM or VRAM. Is one or more of your viewports resulting in such a large image?

This is likely an issue that was fixed for SP5, sorry for the inconvenience.

@Phsion thanks. By any chance do you have the "Save viewport cache" option UNCHECKED in the document preferences (under Display)? Once a preview is created it should have been saved with the file and re-open quickly without being re-created unless this option is off. In our testing having sheets with several viewports drawing the wireframe fallback for un-updated viewports used more memory than these previews... thanks.

@Phsion We introduced viewport previews in SP4 since these image previews will typically use less memory than the old wireframe preview and should only be built when the viewport changes projection or render mode, or the very first time when there was no previous preview. It should not re-generate with every change to the document... Could you provide a file or example where this happens, and what operation makes the previews re-generate? Thanks!

We have disabled the adaptive detail adjustment for VW 2023 SP5. It will be investigated further for VW 2024. Sorry for the inconvenience.

@Aneesh Carvalho One possible workaround might be to create a DESIGN LAYER SECTION VIEWPORT, and then a SHEET LAYER (non-section) viewport of that, which can be in perspective and you can reposition that camera at will: Above, a Sheet-Layer viewport in perspective (Shaded render) with arbitrary camera, of a Design-Layer Section Viewport. You can also use the clip cube on design layers if the cut is simple and axis-aligned: Above, a perspective shaded SLVP of a design layer with the Clip Cube.

I believe a section viewport in perspective gets the camera calculated automatically from the bounds and can't be changed like a non-section viewport. While not ideal, one could use a "trick" whereby adding an object to displace the view, and then it could be cropped out (not ideal I understand). (Orthographic section viewports can be cropped to show the intended area since the view doesn't change with height).

@MGuilfoile Could you provide us with a file? Does this only happen when Sketch is applied, or also in regular Hidden-Line? Thanks!

@willofmaine @JuanP We have added this fix to 2019 SP5 in build 498299.

@willofmaine 1. and 2. above have been fixed for VW 2020 build 495452. I can consult with management about possibilities for the next 2019 SP.

This has been fixed for SP2.

I tracked this down to the viewport having the "NonPlot" class invisible. Apparently the viewport's section cache is stored in a group belonging to that class. I will open a bug and look into it soon.