If I try to render more than one thing at a time for the online version, it errors out.
Can you post a screenshot of the error? Does this happen consistently?
Seems to be related to the options checked on above the prompt: when I unchecked all except aerial view and turbo nature it started working a little better (still some errors)
Scratch that last one: still having the same problem / error even if only two options checked.
@brockett - based on the first error, it seems like it could be an internet connectivity issue.
- From what country are you trying to access Veras?
- Are you using a VPN? does it work by enabling or disabling the VPN?
- Are you able to connect do a different network (different wifi, cellular hotspot, etc)?
@Ben: interesting. I don’t think our internet connection is super fast. We’re in the USA (Vancouver, Washington), no VPN
37.1 Mbps download speed this morning.
Haven’t run into any errors today.
OK @Ben,
Working from home today, where I’ve got 600+Mbps speeds, but I’m still getting the errors whenever I try to do multiple renders, and sometimes even when I do a single render. Any advice?
Still in the USA, no VPN, on a new network.
Brockett
@Ben still getting errors, even for single renders.
This is the web interface BTW.
Thank you for reporting this and the additional details. We are doing two things to address this:
- Expanding our GPU pool - meaning we are enabling more data centers to process renderings
- Releasing an update that more intelligently check for completed renderings
Both 1 & 2 are in-progress of being rolled out. I’ll update this thread when the rollout is complete.
The updates are now rolled out: Veras - Release 2.1 - Veras inside Veras - #2 by Ben
Please let me know if the problems persist.
Hi @Ben, unfortunately, the problem is still here, even with the new version.
@Anto - thank you for the quick feedback. We’ve added additional logging to track this error. Can you please try to render again? It most likely won’t work, but it will help us better find what the issue is.
Hi @Ben, unfortunately, it’s still here.
Thank you for checking! I think we pin-pointed the issue. The issue in on the back-end, and we will just deploy an update. Once deployed, we’ll update this thread.
The backend update is now deployed. This might fix the issue you were having 
Let me know how your test goes.
Can you send a screenshot of the entire property pane in the COMPOSE tab. I’d like to see the settings that you are using.
Example:
