Posts by snowyweston

Please cast your votes in our two ongoing feedback polls here and here!

    solved it, Enscape "lookAt" is relative to the camera position where as in 3ds Max it is the absolute position. Really Enscape should just write an fbx exporter


    could you not reverse engineer the (normalised radian vector) of the LookAt values (with their YZ swap) from the Poisition values to "project" to 3DS' required absolute position?

    + whilst doing so you could also set the vector length (to target) to define the DOF (if so desired)

    Hi Demian, thanks will do, my person was away yesterday and I was tied up - but will jump on it Monday (will send logs for 3.5.2 and then again if it persists still after update)

    Didn't try tbh rifkin, got 10 of these machines exact same spec (13900K w/ 12gb 3060 +64gb) and only one other is complaining (about rhino in another thread)

    noted about the .exe woe tho boo

    One of our people has encountered an issue, potentially a bug, with Enscape 3.5.2+ running on Revit 2023 (, where/when renaming a saved view, using the backspace-delete key, in the Enscape GUI, leads to a Revit crash.

    This is reproduceable, in models big and small, templated or otherwise. Windows & Graphics drivers are up-to-date.

    Is this a known issue? We will proceed with renaming views in-browser (in Revit) but would like to see this functionality made good/stable. Please advise.

    I have just deployed a bunch of new machines to some of our people and its been reported that Rhino (sr35) models with V-ray (3.60) materials are rendering white-only using the latest (7 June) Enscape 3.5.1

    Full disclosure, I haven't the foggiest of ideas about v-ray, and yes, multiple variables have changed with the upgrade (6th gen cpu now 13th gen, QuadroK2000 now 12GB RTX3060, win10 now win11, graphics drivers etc)

    Yesterday, on the aforementioned older spec. machine, all was running fine w/ Enscape 3.3.1.

    Has something changed in 3.5 that changes how V-Ray materials are read? Cos if so, I'm going to need to rollback the version deployed - because I certainly am not asking my entire team to turn their material world upside down.

    I can't recall, or find, any previous similar query so here goes...

    Last night's work drinks had us joking about putting ourselves in our visuals - we've done this in the past with flat photochop work - but it'd be much cooler if we could get ourselves into our Enscapes - and we were thinking getting scans of us all would be a fun team social day-out!

    So three questions really:

    First, when reaching out to scanning services what should I be asking them? Specifally what formats would be a best "fit" for creating Enscape-ready custom assets? From my initial investigations, as expected, most showcase very-high detail outputs on their websites, so I'm wondering if there are specific terms/phrases re: "degrees of scan detail" that I should be pitching for.

    Second, has anyone done this, or similar. and know of / could recommend a service in the London area?

    Third, has anyone explored doing this themselves, perhaps using a more manual (cheaper?) workflow with prosumer reality capture tools?

    nope spoke too soon, those Block ID: values are internally Rhino based, but exploding one of the asset blocks and reaching to the mesh does give us/me:

    UserData ID: & Plug-in: fields that look promising... but I've (presently) no idea how to get at those...?!


    ...yeah so (as I probably should've expected) this is a bit more involved in Rhino than it is in Revit... I'm certainly not conversant in C# and API to tackle this looks to be leading me down:…ods/user_data_methods.htm

    so I'll have to park this curiosity for now.


    HNY all!

    after what feels like forever I've finally managed to entice some of our Rhino wranglers away from their beloved Vray to play with Enscape. Good news!

    Bad (?) news - their enthusiam for assets (ootb and custom) has led to considerable geometry bloat, stalling both Rhino & Enscape on (fairly) decent machines.

    Disclaimer, I'm not all that au fait with Rhino, so I'm shooting a little in the dark here - but....with Revit we've got around the mesh geometry weight/mess of the enscape assets by using the GUID asset parameter in simple volumetric proxies - and I'm digging around an asset block here in Rhino right now to see if we might do the same... but I can't see where Enscape might be fetching the proxy value (that I'd hope to point our GH peeps at so they can rip them out) - perhaps Enscape-for-Rhino thinks/works different?

    Either way, has nay one any ideas / solutions for approaching the same?


    (further to my email to support)

    Windows Defender has just flagged an .exe (of our making) contains a Trojan:

    the system in question:

    the named trojan appears in Microsoft Answers search returns to be (potentially) a false-flag

    but I'd like to get your assurances please - because this will greatly impair our ability to use, and more importantly share these files with others (which we regularly do) - and would ask what remediation Enscape will undertake to ensure this be countered.

    a thought... instead of doubling up the Enscape asset library content with low-poly variants of models -

    forcing users to swap out low-to-high and vice-versa in a a tedious merry go round,

    why not enable a switch in settings (global, or ideally view) that offers: "read asset Y/N"


    Y=all the details

    N=the facetted model we see whilst in our native applications

    (which are effectively the low-poly version, no?)

    Almost entirely sure someone, perhaps even me, has asked this before - but to double-down AND BUMP

    (speaking to Revit here, but I'm sure other platforms would benefit from this)

    can we please please please get the descriptors used in the asset library thumbnail previews

    injected into a parameter in the family please?

    I use a Dynamo script that parses the geometry* of placed Entourage Planting asset

    *culling the ones that are "only" mesh, or "just" surfaces

    that defines a type definiton (and catalog) of the widget family we use to place in our models - however, the "only" useful information to mine is the family name, leaving us with:

    now that'd be fine if I had a content management tool like Kiwi Browser to better search/filter these for "walking", "elderly", etc - and add tags for "day time use only", and such - but we don't - and I imagine a great many others don't either.... whereas, if the Asset library description (and potential other useful tags) were included in the .rfa, raw, from Enscape, a one-time date-push activity by yourselves could save hundreds/thousands of hours of customer time sifting and sorting the assets into an applicable resource.