We updated to 2023.2 to take advantage of the Lumen system (an excellent upgrade in the quality of our work - no going back now…), and I notice that Panoramas now take an exponentially longer amount of time to process than when we were using 2023.1. I did an experiment with an older 2023.1 project, (just 4 panorama scenes, 4K resolution, no “Max Lighting”, no Path Tracing), and it took about 10 minutes to fully render them all and upload to the cloud. When I opened/converted the same project to 2023.2.1, and processed the same 4 panorama scenes (same workstation, no Lumen rendering, mind you), the same process took 87 minutes!! Were there new settings introduced in 2023.2 that increase the rendering time? I notice the “Max Lighting” checkbox is no longer an option for panoramas on the Export screen - is it possible that this setting defaults to “on”, without the option to disable? Might just be a bug that needs reporting… An 8x increase in processing time is a tough pill to swallow, especially when we’ve staked our product on including excellent Twinmotion panorama tours. Worse still is that our newer 2023.2 TM files appear not to have down-save function, so I can’t just hop into the old version to save rendering time. Anyone else feeling the panorama pain yet?
Check your panorama settings to see if you are exporting in .jpg or .png. .png’s seem to take much longer to render, maybe because it is a lossless format?
My apologies - I meant to mention that I’m talking about Panorama Sets that upload to the Twinmotion Cloud, not the individual Panoramas that export locally to images. As such, there aren’t any output filetype options, and results upload directly to the cloud. I did however try my same experiment with local panorama outputs, and the even with jpeg option, the process appears to be just as slow.
Quick follow-up for posterity (not sure if this was ever an issue for anyone else) - After updating to version 2024.1, everything seems back to normal with processing time, so I’m assuming a glitch was discovered and fixed in the update. Only other variable I can think of, is that I switched the folder location for my custom content, but I can’t imagine that would’ve caused the initial slowdown… Yay Epic!