Posts by Simon Weinberger

    Do I understand you correct? You want to hide the lights in SketchUp (so they don't disturb you while doing your work), but see them in Enscape?

    I see two ways to achieve that:

    A) You hide single lights. To select a light for editing you would use the outliner or enable "show hidden objects" and select by clicking. These lights are still shown in Enscape, but if a light is hidden because it's in a hidden component instance, or because it's in a hidden layer, it nevertheless is hidden in Enscape. Enscape simply ignores the hidden flag for lights.

    I would not add a global setting (in Enscape Settings window). Still unsure whether I would add an "always show" flag for the lights (in Enscape Objects window).

    B) You assign all lights to a layer and toggle visibility in SketchUp this way. We would add support for a keyword in the layer name (like "enscape_always_show") to overwrite the hidden flag of the layer.

    hellmanna Are you using camera synchronization? In this case the field of view is calculated from the SketchUp viewport, which is not 100% reproducable (toolbar layout, display resolution). Also make sure to set a fixed capture resolution for exact replication.

    Wow, thanks for that amount of suggestions. Let me try to comment on them:


    - As a shortcut to save time and file size I often use a flat colour as a base and apply a bump map to it - (floor tiles, coping stones, smooth cement render, ridge tiles, ...etc)

    It would be really handy if you could apply an off-set to any of the material textures (Texture, transparency, bump & reflections) so that they can be aligned properly without having to use the albedo texture or assign a texture to that material.

    We thought about adding more texture transformation controls like known from Revit/Rhino, which are already supported by the rendering code (Offset, Rotation), but we didn't because we liked that you see the albedo texture in the SketchUp viewport. Adding more than SketchUp can handle means to have different views in SketchUp and Enscape, and that's not goot in our opinion. Of course that's not a problem for bump/reflections, but having more controls in these sometimes less important can also feel weird. So we didn't add them at all.


    - When assigning any texture it would be nice if the program actually looked at the image it's importing and pulled in a width/height from it (and had a button to re-set, and another to lock proportions so that changing one size automatically scaled the other). It would also be useful to see the width/height of the texture without having to tic the "explicit texture transformation" box.

    Looks like it can be done. Although resetting to the original texture size is ambiguous - textures do not have a real size, only pixels. I guess using the DPI setting from specific file formats is the wrong way, because most textures are quite large in real. So you would have to reset the proportion, and afterwards adjust the size.


    - The other settings for enscape materials would be good to replicate within the relevant tab for the image (eg bump amount slider within the tab where you see the bump image)

    We thought about that, but didn't want to have the same control on several locations. What are you doing so often in the bump tab? We hoped that users spend most of their time in the general tab.


    - The Colour selection (seen on the Albedo and Illumination sections): Could a pipette to 'select colour from screen' be added? (As per the one in the SU materials editor)

    We have never thought about that one, but I can see how it can help. Unfortunately we use a 3rd party library for the color selection dialog. Don't know how easily we can integrate the screen color pipette function.


    - If the material window could float above the enscape render window like the settings window does, it would be easier to change materials and see the effects of these changes "live".

    Would be only one line to change it, but there are also some users, who complain about the same behaviour regarding the settings window. So I think we won't go down this road unless it's somehow configurable.


    If this is possible, putting a pipette button on the same window to select a material from the render window would be really useful...

    Do you want to select color/texture from another material for use in the currently open material? Or do you want to change to another material? For the latter you can use the SketchUp paint bucket tool (press P, hold down Alt).


    as would be a way to roll it up/down and hide it. (Same with the settings window: a way to hide it other than closing it or dragging it off-screen would be handy)

    Would be on done in combination with a configurable "floating on top of everything" behaviour.

    Sorry, buggy forum, can't use any more quotes. My text in red.

    Window title - could the title be populated with the name of the current material? (eg "Enscape material: Chris_Hair")

    That should be possible.

    Type - Would be nice if it highlighted that a keyword was selected (eg "General - metal") and/or be able to select these keyword presets.

    These presets are only used if you have never modified a material using the material editor. Otherwise you wouldn't be able to adjust them. Do you think it helps if you see a line of text for untouched materials, that tell you what preset was detected (and that is hidden after the first change)?

    - (requested elsewhere) If you could add your own presets to this list it would be great; perhaps a "save current material settings as preset" option somewhere?

    Sounds easy, but is not. Would you like to have that preset bound to a keyword that we detect (and work only on untouched materials), or would you like to have it in a dropdown for manual assignment?

    Self Illumination - (requested elsewhere) Since there are textures for the other settings, it would be nice to apply an illumination texture with white = 100% bright, grey = 50% black = 0%

    Every texture slot, and every slider added, increases the complexity of the rendering and therefore might have a negative impact on the performance. We'll think about it.

    - It would also be nice to be able to type in a value for the Luminance instead of relying on a slider.

    You are not the first to want text input in addition to the slider.

    Transparency - Tint only affects the objects seen through the glass; it does not apply any colour to the light as it travels through the glass (eg a stained glass window would not show coloured patches on the floor/wall)

    - Glass does not cast a shadow (this is related to the above) and the opacity does not affect the transmittance of light through it.

    These things are easy using raytracing, but are a lot more complex in real-time rendering.

    The window doesn't show the higlight.

    That's still the case with So the fix between and did not help? Then it might have another reason. I don't have the faintest clue, because Enscape does absolutely nothing in regard to selecting.

    The modify tab starts to "grow" as I try to click on different elements of the project. It opens the modify options of a door, but if I click on a floor it will keep showing the door options and won't let me accept the changes i make (it's a bit difficult to describe, so i'll attach an image of the bug to demonstrate). It only happens if I have enscape open and live updating.

    This is a behaviour we haven't heard of before.

    Please use the feedback button so we can take a closer look at your log files and system configuration. Please be so kind to attach Revit Journal Files to the ticket afterwards, that correspond to the time you observed this behaviour. You can find them in "%LocalAppData%\Autodesk\Revit\Autodesk Revit 2015\Journals"

    Just to be sure: The behaviour you described happens with every model you open, is that correct?

    That's a weird wall you have there. I can reproduce the issue, but I'm afraid there is not much Enscape can do, because it get's wrong materials from Revit.

    Take a look at the wall in a realistic 3d view in Revit. Only one side has the correct material applied to it, the other one appears in default material.

    In the Revit API there are two methods in retrieving the material. Normally it doesn't matter which one we use. But in this instance it does. One has the default material, the other has some 99% transparent material. We could switch to using the other method, but that wouldn't be correct either.

    If I create a new wall of the same type, it works correctly. Only a few existing walls have this problem. I suggest you delete and recreate the problematic walls in revit, because they are somehow broken. Might be a bug in Revit - feel free to report it to Autodesk. I tried it with Revit 2018 and the current Revit Preview, but the problem persists.

    The correct side (you can see the assigned bump map):

    The wrong side:

    The wall structure:

    Jorgensen Regarding hosting panoramas yourself using VR View.

    If you have the old version of VR View, you need to include it the way it's documented:

    1. <script src="build/vrview.js"></script>

    But if you are using the new version of VR View, you need to include other files:

    1. <script src="build/three.js"></script>
    2. <script src="build/embed.js"></script>

    If you use the former code snippet the screen stays blank. We had to learn this ourselves when upgrading the library.

    The panoramas hosted by Enscape use the "VR View" library from Google for rendering. At the time we made this choice, most browsers and mobile devices (including Internet Explorer) were supported. Then new phones came out, that were not compatible anymore. And a new version of VR View came out, that is compatible with the new devices, but no longer with Internet Explorer. We made the choice to update to the new version of VR View, knowing that Internet Explorer is no longer supported.

    You have several options:

    1. Do not use Internet Explorer. There are plenty of alternatives, even one from the same company (Microsoft Edge).
    2. Save your panoramas as image files and host them yourself using the old version of VR View.
    3. Use 3rd party hosting providers.

    Gadget Try out the newest preview version - mouse wheel is working now. You should need around 100 wheel clicks to move through each slider.

    There are a few sliders that are working on a logarithmic or polynomial scale, to allow for better precision along the whole value range.