#Rhino 7 student driver#
#Rhino 7 student license#
#Rhino 7 student windows#

#Rhino 7 student windows#

Windows Main Display using connection #0 > Remote Desktop display device with 16 connection(s)

#Rhino 7 student driver#

Primary display: Microsoft Remote Display Adapter (Microsoft) Memory: 0MB, Driver date: 6-21-2006 (M-D-Y). Windows 3 SR0.0 or greater (Physical RAM: 32Gb)Ĭomputer platform: DESKTOP (Hosting Remote Desktop session)

#Rhino 7 student license#

License type: Educational Lab License, build The Rhino SystemInfo report is as follows: I am not interested at all in being able to view in Rhino the geometry I create for input to LBT - I am only interested in the LBT visualisations of the objects. I have created a youtube demonstration of the phenomenon (not a solution, but a way of working around the issue, so if this provides insights into what Rhino settings we need to change, I would be ever so I am wondering what internalise something in Grasshopper means?

All the objects appear AND zooming in an out has no effect on visibility. In the past 24 hours, we have discovered an apparent cure: draw any object in the Rhino window. Zooming in and out amongst the various graphics produces oddly variable visibility. Turning these on and off seems to trigger the visualisation of the other objects. a graphic representation of the rooms and their R-values). The script has a bunch of model visualisation tools provided to help the users visualise the model prior to running the model (e.g. In this situation, controlling what we see in the standard Rhino ports is something over which we have limited control. I have created a small animated visualisation to show what we encounter.Įssentially, the LBT 1.3 script creates all the input geometry, runs the analyses and outputs the graphics to Rhino 7. I have made a small discovery which I think centres the visibility problem in the mix of settings for Rhino 7 that we have created in running through the standard install, and the use of LBT 1.3. So, when I run the script I produce these graphs: On the student computers the issue was worse in that no matter what we did the graphics, mesh, wires annotation etc did not appear.īecause I have, in the process of implementation of LBT 1.3.0 added some room/surface visualistions to enable the students to check their models prior to simulation, and because I have used the gate option to control when these visualisations are visible, I discovered that turning these on and off made all the output graphs, output text and heat loss per surface outputs from LBT visible! I could sometimes fix the issue by switching from wireframe representation in the Rhino window to Rendered view, and then back. I put this down mostly to my amateur status as a Rhino user. We could find no solution in the display commands / view controls for Rhino. In perspective view we could see slices of the grahics on the XY plane, reminiscent of what I used to experience with AutoCAD/3DS Max in terms of cutting planes associated with a view camera. What we found was that on some machines (mine at home for example) if we were zoomed back from the XY plane in Rhino all the objects - graphs, annotation and model shaded with heat loss etc were visible, but as we zoomed closer to a particular graph it disappeared. And in the process also developed the script we are using to run with version 1.3.0 of LBT. Kia ora have recently upgraded the student system to Rhino 7. I offer this first as a work around for this visibility issue, and then as a query to and in case this triggers some kind of inspiration as to what viewport settings might need to be set in Rhino 7 so they match Rhino 6. What we have just discovered is that if we use one of the room or face attribute displays, that I have now added to the student modelling script to ensure a certain level of Quality Assurance, then switching these via a gate command fed through a custom preview, then the base model is made visible and the Rhino view settings are altered so all our graphs are visible! On our student machines, the issue was even more frustrating. I had no idea what to search for in a visibility or camera setting n Rhino. Switching view mode from wireframe to render and back again mostly solved this.

When I first did this on my home development machine there seemed to be issues with what I would interpret from my AutoCAD days as a front and back cutting plane within which the graphs sometimes were visible. This is the visibility of my LBT 1.3 graphics in the Rhino screens.

I have in the last couple of days dealt a significant Rhino 7 frustration.