Can't open files in 5.3.1 (5D193) os x 10.9.5 (13F1911)


#1

I have a Mac Pro (Mid 2010, 20GB) and a MacBook Pro (Late 2008, 6GB) running 10.9.5 (13F1911), and also a MacBook Pro (Mid 2015, AMD Radeon R9 M370X 2048MB) running 10.11.6 (15G1217). All three are running 5.3.1 (5D193).

Here’s the problem: I can’t open and get a View on the MacBook Pro (10.9.5) on any of my files. I get a brief, half-size preview of the Top View then a Rhino document with no Views. (The Mac Pro (10.9.5) opens the files with no problems.) I’ve tried adding Views via the menu, but the Views never appear. If I open/manipulate layers I’ll get a revert/save option when I go to close the file. This is the View-less screen:

Here’s the cut-n-paste from Rhino Info

Software information

Software versions
Rhinoceros version: 5.3.1 (5D193)
IronPython version: 5.1.2015.131
Language: en (MacOS default)
macOS version: Version 10.9.5 (Build 13F1911)

Plug-ins
None

Third party kernel extensions
com.pgp.iokit.PGPwdeDriver (1.2.0d1)
com.pgp.iokit.PGPdiskDriver (9)

Hardware information

Computer hardware
Hardware model: MacBook5,1
Processor: Intel Core2 Duo CPU P8600 @ 2.40GHz
Memory: 6 GB
Architecture: Intel 64 bit

Video hardware
Graphics: NVIDIA GeForce 9400M 256 MB
Memory: 256 MB
Screen size: 1280 x 800
Displays: Color LCD (114dpi 1x)

USB devices
Apple Inc.: Built-in iSight
Apple Inc.: Bluetooth USB Host Controller
Apple, Inc.: Apple Internal Keyboard / Trackpad
Apple Computer, Inc.: IR Receiver

Bluetooth devices
None

OpenGL information

OpenGL software
OpenGL version: 2.1 NVIDIA-8.24.17 310.90.9.05f01
Render version: 2.1
Shading language: 1.20
Maximum texture size: 8192 x 8192
Z-buffer depth: 24 bits
Maximum viewport size: 8192 x 8192

Implementation settings
Use texture compression: No

Appearance settings
Antialiasing: 4x
Mip map filtering: None
Anisotropic filtering: None


(Marlin Prowell) #2

To paraphrase:
You have two computers

  1. running the exact same version of OS X
  2. running the exact same version of Mac Rhino
  3. opening the exact same 3DM model (exact copy!)

and you get different results.

There must be something else different about the two computers. I don’t see how this can be Rhino’s fault.

You have a couple of third party extensions installed. Are they on both computers? If not, what happens when you remove them from the problematic computer?

Try resetting your Rhino preferences. I don’t see how preference settings could cause this, but it is the only place where Rhino customizations are kept.

Lastly, I cannot duplicate what you describe on a MacBookPro 5,3 (pretty similar hardware), OS X 10.9.5, and Rhino 5.3.1. I’ve customized the Rhino interface in the same way you have, and I have no problem with showing views.


#3

I’ve written customer-facing software for a couple of decades now, if you put that in an internal bug report, I’d be responding to your manager, not to the bug. That is probably one of the lamest, not-our-fault responses you can give to a customer. (See also, “why we don’t let engineers do customer support”.)

Removing the preferences fixed the problem, so it probably IS a bug in Rhino that needs to be fixed. If the preferences file can’t be parsed, throw an error in the UI with some suggestions for the customer. Maybe an older version of Rhino could write corrupt pref files. Maybe the customer had to downgrade from WIP to a released version and the pref files are not backwards compatible. Maybe it was corrupted by gnomes. It really doesn’t matter, failing to read a pref file should not make the product inoperable.

You didn’t ask me to make a backup of my preferences and post them to the ticket, I did it anyway because it’s good engineering practice.

com.mcneel.rhinoceros.plist-save.zip (10.7 KB)


(Marlin Prowell) #4

Thanks for the .plist file. I was able to duplicate the problem. The width of the center modeling section was effectively zero, and that made the modeling views disappear. It’s one of those “cannot happen” problems that the program already tries to prevent. I’ve added additional checks when the preferences file is read to keep this from causing a problem in the future.