Posts by Pete Chamberlain

Tim Williams - Ah ok. Thanks for letting me know this.

Stephen C. - This is actually a known bug in the latest version of Enscape.

You have two options:

Roll back to the previous version of Enscape.

Stay with the current version and observe the following procedure:

Set your resolution you want to render out at.

Restart ArchiCAD

Do not open the Visual Settings window before a Render, but if you do open it, don't close the window. You can make adjustments int he Visual Settings window which will take affect. If you close the Visual Settings window, that is when the bug becomes active, and you have to restart ArchiCAD.

Developers are fixing this.

guitarchitect - Valid point. I'll make sure that's done to make it clear and transparent.

bsfranza - it will most likely be an RTX issue if you are running 2.6.1. Advise that you roll-back to this version of Enscape whilst we fix this issue.

Paul Russam - Thanks for providing that extra info for CADLeo .

CADLeo for a 20x24 print you should have a minimum resolution of 1740x1420 pixels.

Here's a website to reference in the future.

RandyW - because we have to schedule this kind of thing in to the development sprint phases, before we even get to that stage we have to gather, analyse, and plan this kind of thing. It looks like this was requested Oct 23rd, so that is only just over a month ago.

So, when it does become scheduled for development, then it will likely be included in the Road Map that you can always find here.

bsfranza - We would need to see logfiles, that you can send via the Enscape Feedback button, before we can make any suggestion as to why this would be happening, and the appropriate solution. When submitting the logfiles, can you please reference this forum thread's URL so we can link the case?

It's likely that it will be a VRAM issue, but the logfiles will hopefully reveal all.

Thanks.

Santiago_Rivera - We have a story in our developer agenda regarding the possibility to load custom assets. I have up-voted that on your behalf.

In the meantime, I have also made a request to our 3D Artists for more Laboratory people.

DGD-Duane , eeblack - Noted. We are fully aware that this is problematic for some users. There will be improvements coming in version 2.7, but I think it may be something that you will see improve over time, and as far as I am aware, there is no magic bullet for everyone in regards to these loading times you are experiencing.

I'm sorry I can't give you any other information than that at the present time. All I can tell you is that the developers are fully aware of this situation and are trying to make improvements to this.

Tim Williams - I seem to remember that being a bug in previous version of Enscape, and having just tested this with the latest version, I can not reproduce that issue there. Can you please confirm that?

aharrell - I have added a feature request in regards to the use of the active construction plane as opposed to the the world construction plane when rendering with Rhino.

Thanks for offering up the workaround as well though, perhaps it will help some other users circumvent this current limitation.

wassem_hawary - What do you mean by QR motion? What is QR motion?

smisiurek - Actually this combined Enscape toolbar should be there by default now. If you find it isn't then it may be worth reloading the plugin, as explained here.

Also make sure you are running the latest version of Enscape available here.

DDM - not yet, no. Developers are working on it.

mattendler - So the system is caching for you. What version Enscape are you using?

Are you connecting to the internet via Wi-For via cable?

Do you have a Firewall enabled? If so, you may need to add some URL exceptions.

Can you provide some video of this slow loading, so the developers can see if this behavior is within tolerance?

Pieter   mattendler   guitarchitect   EmileeCee +4 for this feature.

Epix 3D   signpluspro   guitarchitect   yschindel   KMarren   mattendler   tmoracze Added 7 more votes to this.

damo3 - It might be that you will need to uninstall the driver for that device. Can you please try that to see if that resolves the issue for you?

laurence_cle - this is indeed a bug that has been very hard to just reproduce reliably, as you have also found yourselves, and unfortunately this makes it very difficult to find a solution for. Recording the screen may help, and if you can find steps that result in the issue being reproducible, then that can also be helpful.

The only thing we can advise at the present time, is again, in relation to 3rd party peripheral devices and their drivers, in that you should try uninstalling these.

BarryFishFinger - I replied to your Feedback via our Ticketing System.