ystem so screen objects get scaled properly:
http://www.danantonielli.com/adobe-app-scaling-on-high-dpi-displays-fix/
The tweak requires adding a line to the Registry and then adding a text file named <application exe file name>.exe.manifest to each directory containing the executable program you want to have re-scaled. The contents of the manifest.txt file are shown here:
http://www.danantonielli.com/wp-content/uploads/2014/03/manifest.txt
Overall this looks pretty simple to do. The feedback seems to all be positive. Looks like it's time to get out the old checkbook.....…
, HVAC, blah blah).
BIM is NOT a parametric process at least having in mind graphical editors the likes of GH (or stuff the likes of Generative Components): it's a holistic data management approach. Some concepts used in BIM apps (for instance in AECOSim etc) the likes of "walls"/"openings" etc are "parametric" in the sense that allow auto perforation of this with that. On the other hand AECOSim is feature driven (since Microstation works in that "mode" as well) ... a thing that complex things even more with regard what is actually "parametric" and what not.
BIM is as good as the meta data structure is (especially the spec related aspect - Goggle MasterFormat and the likes). BIM AEC apps are notoriously incapable to work (without a lot of lines of code) with proper RDBMS. On the other hand Bentley Systems ProjectWise ... well ... but that's another animal (by no means a topic for the inexperienced).
In descending order or importance a contemporary AEC practice should use:
1. A general information "controller" like ProjectWise (who said/did what/when/why).
2. A Specs (say CSI - not the TV soap opera) management app.
3. Several Meta data RDBMS.
4. A BIM suite of apps.
5. Optionally some parametric thingy.
PS: For AEC ... when inviting the parametric thingy to the party you have only 2 options:
ProjectWise + AECOSim + Generative Ciomponents (my choice).
?? + Revit + Dynamo.
…
to the native pixel size for software that support high DPI screens, and only Rhino 5 is scaled x2 looking exactly as in my previous 1080p laptop.
I'm not applying this fix to Rhino 6 as it does support high DPI (and maybe at some point I might want to look at a high res Grasshopper canvas despite the tiny toolbars and unaligned, cropped text).
Rhino 6 and Rhino 5 side by side in the same screen set at 2160p:
…
Added by Vicente Soler at 1:30pm on November 28, 2015
th a graphic editor (GH) hosted in a CAD app that has primitive assembly/component capabilities and/or feature driven ops (Rhino). Did I've mentioned that Rhino is a surface modeler? (meaning the obvious).
3. Imagine a "seed" collection of assemblies related with various membrane components made in SW. Say: geometry (prior solid ops) and parameters (the feature driven part of the equation, in most of cases managed with some RDBMS). You should port these to GH (a variety of ways exist for that) and create the bare minimum of "solids" in GH as instance definitions. There's 2 main reasons to do that: (a) effectively communicating back on an assemply/component schema (via STEP) and ... (b) achieving manageable collections when in GH. These are critical for clash detection (when outlining some topology in GH, therefore NEVER work just with "curves") and "variation" control of some sort (up to a point). Of course for high class designs (where the devil hides in the details) this is NOT the best imaginable solution ... you'll need CATIA for such an integrated (all in one) procedure. On the other hand many could (wrongly) argue that CATIA is expensive (rather naive argument if a company has a certain turnover).
4. So, in general I would strongly suggest to use instance definitions of items in some sort of "intermediate state" of detail (an 100% undoable task without code) structured in such a way (classic assembly/component MCAD mentality blah, blah) that SW could take benefit of a possible modified "base topology" and proceed by finishing variations of the given assembly (feature driven stuff as usual).
5. Then export (STEP 214) back portions of the assemblies (and parameters used) to R/GH if and when this is required (for instance for BIM disciplines ... but Rhino is not a BIM app, nor it would ever be).
6. If you are familiar with code matters ... start thinking the whole puzzle that way, if not my advise is to find someone to design such a "procedure" (say an "app") using solely code, but this is not a task for the inexperienced by any means.
best, Peter…
are using rhino 5 planktonMesh (http://www.grasshopper3d.com/group/plankton) and starling (http://www.food4rhino.com/app/starling) are good options when modelling just with polylines with n vertices.…
ror that there are three unrecognized objects in the file and it prompts me to locate the following components:
ZombieKangaroo
SpringsFromLine
PullToSurf
But it also says these are in Kangaroo Components v1.000. Are these not also in Kangaroo2? If not, which version of Kangaroo must be installed? The Kangaroo project on food4rhino (https://www.food4rhino.com/app/kangaroo-physics) doesn't have a v1.000.
Any help would be MOST welcome. Even if that just means telling me where to find those components to load manually into my Library. Thanks!
I'm running Peacock 0.99.4.3 in Rhino 5, 6 and 7.…
depends on that data.
So, for instance, if my component is receiving 3 strings and at some point that data changes (structurally or "physically") I have to know it to wipe the old data in my third app and send the new one.
I know that with my clunky method I'm counting more events than necessary but at least I'm on the safe side, avoiding data collision on the third app. If you have any suggestion to improve the performance and the general behaviour of the event listening system I'll appreciate it.
Thanks.
Ángel.…