And since these tools are real-time display, being able to control some aspects of Display Modes that influence the performance (Advanced Lighting, Shadows,Scene Lighting type, Line Thickness etc) is important.
#Rhinoceros 6 vs 5 software
These software have big differences in speed and smoothnessdepending on the PC in which are installed. First pc is a 5 years old core-i5 desktop, with 8 gb ram and a pretty old invidia Gt 220, Second pc is a 1 year old notebook acer aspire f5, i7 core, 8 gb ram, geforce gt 940 video. This is all related to some scripted interactive tools I have been working with where objects get placed at the cursor in the model or the cursor drives the camera, so many times I want to bypass the command-line input and rely on at-cursor UI input boxes and lists (PopUp menu is the only one that has built-in control where it shows up). Hi, I currenty use Rhino 5 in 2 pc, and recently downloaded and used Rhino 6 wip and beta. Also, I need to be able to control where the RhinoScript UI dialog boxes show up. ini file and importing it back, which is currently possible via RhinoScript but takes a while. So: I need to be able to change very specific display mode settings ‘on the fly’, ideally without exporting the mode to. This is what I am doing now in V5 and registry for dialog positions and it works well. What might be useful is a method to be able to force Rhino to re-read the xml file, so if I make some changes to it via script (display modes, dialog positions) they would get updated. So yes, this is may not be the most reliable way to dealing with it.
#Rhinoceros 6 vs 5 update
All running Rhino’s watch this file and update settings when the file changes.įrom what I have tested, the Display Settings update every time something changed in Rhino, but Dialog Positions (at least UI methods of RhinoScript) only get updated when exiting Rhino. The settings files are updated at runtime by Rhino and not just when Rhino shuts down. I am basically looking at the best way to read/modify display mode settings from the script while exporting display mode to *.ini, changing *.ini and reimporting usually takes noticeable time in script runtime. If so, is that a standard file name on each user’s computer? I guess I am looking for V6 equivalent of “HKEY_CURRENT_USER” & Rhino.RegistryKey(2) " that used to work in V5.Īre these settings in XML file dynamically written every time display mode changes or saved only on Rhino exiting? This used to be the case with registry but not sure if with xml there was any change. What file should I look at for Display Mode Settings - would that be the one with all of them?ĪppData\Roaming\McNeel\Rhinoceros\6.0\settings\settings-Scheme_Default.xml Is that still correct location to red/set their screen position? Looks like RhinoScript UI dialog positions are still added to Registry once initiated. The concept of XML is a new thing to me, so trying to look at parsing them via RhinoScript, is using “Microsoft.XMLDOM” the right way to go about it?
Thanks, that’s exactly what I was looking for.