Posts by Simon Weinberger

    Just wanting to share our roadmap with you, so that no one has the wrong ideas.


    Right now we are shipping a few assets (people + vegetation) with every installation, but they are only used in the Revit plugin when you place ArchVision RPCs and they are replaced by our assets.


    In a first step we want to provide you with the means to place these assets in a controlled manner. Originally we wanted to start with Revit only, but seeing how easy it is we implemented it for SketchUp and Rhino, too. We already started working on supporting ArchiCAD, but are facing technical challenges right now. Of course we'll try our best to make it happen, but it's too early to make promises.


    From there on there will be several paths to follow, nothing final has been decided about them:

    • Some of you have 3rd party assets that you want to use with Enscape. We can provide you with the means to import your own models into our system.
    • We can expand our asset library. This probably comes with some kind of web download because we don't want the installer size to explode.
    • We can allow you to share assets using some kind of web platform. But this needs a huge effort and comes with it's own set of challenges.

    We're starting with the first step in the next release. Everything else depends on too many factors. One of these factors is the feedback and requests we receive from you.

    tas_1985 The difference between 2.3.2.4 and 2.3.3.0 should only be the AMD driver compatiblity. Both these versions are missing the speed improvements introduced in the preview version. So your reports are not surprising me.


    If you have problems/crashes during rendering/screenshots I would suggest to send feedback, but it seems like you already have done that (#61979). We will try to solve this via our ticket system.


    Regarding your performance problems: Loading your scene should not last longer than 1 minute with the 2.3.3.1234 version. If it does, please send another feedback regarding performance.

    Micha


    we tried to switch to the API introduced in Rhino 6, which is the preferred way if you ask McNeel. With this implementation we get edge softening works, decals and better material IDs without any code from our side. We really want to make the switch ourselves.

    Unfortunately there are serious shortcomings regarding live updates when editing blocks. You can see the same problems when using Cycles (switch to Cycles, edit blocks, end editing, see how Cycles renderer gets out of sync). In our opinion it's better to have a synchronous rendering, even if this means to miss out on a few other features. You can try it out for yourself and give feedback. How serious are these sync problems in your opinion?

    McNeel is aware of the bugs in the API, probably it's not as easy to fix as it might seem. I'm not aware of any ETA for the bugfixes.

    tas_1985


    Thanks for the model. I could locate one performance bottleneck, but at a different point in time: After the progress bar went to 100% the Enscape loading screen didn't vanish for a long time. We'll try to fix this for the next preview. Exporting the data took 20 seconds on my machine with the model you provided, no lag at 18%.

    - Please confirm that the lag happens while the progress bar is below 50%.

    - Please confirm that you see the model correctly in Enscape (especially the tree), it "only" takes too long.

    - There is one very large component (tree) which might be the culprit. Have you tried without it?

    - Have you already tried to load the model without any extensions beside Enscape? Might be a compatibility problem.

    - Please send feedback if you haven't already. I want to take a look at your log files.

    Hi Nuge,


    Thank you very much for your honest feedback which is very valuable to us.


    Our goal is to provide the same level of quality and usability in all our supported products. But because these are very different to each other we have to find individual solutions. Sometimes this means that certain features don't work with every plugin right away or that new plugins don't have every feature from the start. Even if not all parameters available in ArchiCAD are used from the get go, Enscape with its basic functionality should already be worth its price.


    If our statements previous to the release were misleading, we're sorry for any inconveniences.


    Thank you for your understanding

    Nuge Sorry for not answering instantly. As a software developer I try to invest more time in improving the software than in customer communication.


    Let's take a look how the material editor for the SketchUp plugin came to life: Enscape for SketchUp was officially released in May 2017 (version 2.0), with some kind of a beta phase since March (version 1.9.6). At that time only the Revit plugin supported the full potential of our materials. SketchUp had only very basic materials, even less than ArchiCAD has today - Albedo texture with keywords for specific reflectivity settings and for special materials like water. Of course, many users wanted more control ("Look at what the Revit plugin can do!"), and they were right. But it's also wrong to say, that the SketchUp plugin was useless without it.

    In December 2017 (after a short closed beta) the material editor was released in preview versions, followed by the official release in March 2018 (version 2.2).


    Of course we could have adjusted our priorities to release the material editor earlier, but that wouldn't be fair to our existing customers using Revit. So we happened to implement area lights, the presentation mode and many other small improvements, before investing huge amounts of time into the material editor for SketchUp. There have been many SketchUp users complaining about it, but I still think it was the right decision.


    Today we face the same dilemma. Prioritizing feature requests is never easy. We decided to work on two topics that are highly requested and can benefit most of our users. You can find them on trello, the board is still regularly updated and read. We also wanted to include a material editor for Rhino in the next release, but postponed it because of bugs on the McNeel side. Believe me, we are not happy about it. Rhino users have to live without proper material support since November 2017.


    At the moment we try to release every 3-4 month, meaning version 2.4 should be released in September/October. Then we'll decide what to do next. If we schedule this topic for the 2.5 version, this means a release in Q1 2019, probably a preview in late 2018. I don't want to make any promises. Besides better material support for ArchiCAD there are a few topics on our agenda, that are highly requested, just take a look at the Trello board. You should know, that we are aiming for feature parity between all plugins, and that is a strong argument for providing better materials in Rhino and ArchiCAD.


    Short summary: This topic is not yet scheduled, but we are trying our best to bring it to you as soon as possible.