Posts by Simon Weinberger

    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.

    Nuge  MartenE Right now, we have not started working on this feature yet, and it is not planned for the next release (possibly September/October). This does not mean we have canceled our plans to support more advanced materials for ArchiCAD users in the future. It simply means there are other features, that have a higher priority for us right now.

    There might be small differences for different texture file formats, but more importantly, there is a possible format conversion when the filename of the texture does not have an extension. Then Enscape needs to guess and SketchUp might need to convert it.

    But this is not the case with this model. I was able to read all data in 13 seconds, a few more seconds until the scene was ready in the Enscape renderer. There is some heavy geometry in the scene, but I can't imagine that the difference between two machines can be so huge. Please send feedback if you haven't done so already. Do you have these long loading times with all models, or only this specific one?

    tas_1985 Five minutes is extraordinarily long. The steps requiring the most time in my experience are:

    - Textures: It takes roughly 100ms for each texture (even small ones). So if you have lots of unused materials you should clean them up.

    - Geometry: High-poly geometry is taking some time to read.

    Above the loading bar you can see whether it's geometry or textures. Looks like geometry in your case. You can also send us your model (with link to this forum post) and we will try to analyze it. And you should send feedback, so we can take a look at your logfiles. Sometimes strange things are going on.

    Pieter The version we are currently working on uses normal revit families, with some 3d geometry automatically filled in (but content is completely ignored by the Enscape renderer). So in theory you should be free to change these families to your liking.

    You still need a little patience until we show our work in the preview version.

    Micha A quick word from a developer: We have adapted our code to the new Rhino API (ChangeQueue) a few weeks ago, which also improves the material IDs. Unfortunately there are bugs on the Rhino side, which we have reported to McNeel a while ago. This prevents us from releasing at the moment. I'm sorry for the delay, but the schedule is not entirely in our hand.

    Micha  Demian Gutberlet This is actually the intended behavior. We don't want you to play around with the settings while a video is rendering and thereby destroy your video by accident.

    Do you wish do re-open the settings window after the video export is finished, or do you want to modify settings during the video export or do you simply hate if windows pop in/out automatically? Please describe your use case in more detail.

    justlark In SketchUp, when setting a custom resolution, you can use the aspect ratio from the SketchUp viewport. Not exactly what you were asking for, but might help you.

    Do you mean integrated inside the Enscape window (like the presentation mode or the settings in the standalone), docked inside the Enscape window, or docked inside SketchUp? Or have materials/lights/settings all in one window? Not sure every solution is technically possible, just want to understand your idea.

    TowerPower I tried it with Thea once, when we started working on the SketchUp plugin. After a few minutes I encountered a bug with the live updates and the geometry of Thea and SketchUp was different. These kind of bugs totally destroy the usefulness of such a feature. Suddenly you can't select the things you see anymore and there is no indicator that something is wrong.

    Considering the quality of SketchUp's notification API I dare to say: Every render plugin for SketchUp with live updates has to find a compromise between speed and accuracy, therefore there will always be the risk to be out of sync. And with that risk, rendering inside the SketchUp viewport is a no-go for me.

    What's your opinion?

    TowerPower It was changed when introducing the VR screenshot feature. For obvious reasons we don't want any save dialogs for screenshots while in VR, and we didn't want to have several different screenshot folders/mechanisms. But a lot of users don't find this option, so might want to change it again.

    TowerPower Take a look at settings / capture / default folder.

    Please continue reporting bugs in the geometry export or live updates. The cutout live update problems are noted, but I can't yet say when we will fix it. The faces turning black are fixed in the preview version