INSTALLATION INSTRUCTIONS FOR 3DxWare FOR AIX 5.2 ML04 (and higher) - V 1.4.0 To install the files for 3DxWare for Unix to the corresponding directories and to run the driver you need root privileges. Make sure you fulfill the following prerequisites: AIX 5: AIX 5.2 or higher is required. For AIX 52 you will need ML5200-07 or ML5200-04 and APAR IY78349 (can only be applied to ML04 or above) For AIX 53 you will need ML5300-03 or APAR IY78350 The web site URL for IBM fixes is: For USB device support you will need the following AIX filesets: devices.pci.22106474 devices.pci.33103500 devices.pci.99172704 devices.pci.c1110358 devices.common.IBM.usb devices.usbif.03000008 The first four contain drivers for the four different USB host controllers that AIX supports. You only need the one that matches your hardware but having them all does no harm. 'devices.common.IBM.usb' is the USB System Driver and 'devices.usbif.03000008' contains the client driver for 3DConnexion devices.
Pilgway, Windows, Mac OS. Adobe Systems Inc. Adobe Systems Inc. Adobe Reader. Adobe Systems Inc.
Little Details Count is your Autodesk ® Revit ® Architecture custom family resource on the internet. This site was established to provide high quality Revit families to BIM professionals and 3D modelers. Our store addresses the need for families and models created in native Revit geometry. SpacePilot PRO is the ultimate professional 3D mouse, engineered to excel in today's most demanding 3D software environments 3Dconnexion patented six-degrees-of-freedom (6DoF) technology Smooth and intuitive control of 3D models and environments LCD Workflow Assistant.
The files for the driver are provided with the following archive: AIX 5: 3dxware-aix5-v1-4-0.tar.gz Please save the file 3dxware-aix5-v1-4-0.tar.gz into the /tmp directory and extract and run the script install-3dxunix.sh: gzip -cd 3dxware-aix5-v1-4-0.tar.gz tar xf - install-3dxunix.sh./install-3dxunix.sh If you don't choose during installation the possibility to start the driver during login from the /etc/inittab please make sure the driver is started before you launch your application. For the USB devices start the driver with the following command: AIX 5: /etc/3DxWare/daemon/3dxsrv -d usb For the serial devices start the driver with: /etc/3DxWare/daemon -d /dev/ where is the name of your serial port to which the device is attached. Example: /etc/3DxWare/daemon/3dxsrv -d /dev/tty0 For the start of the driver from the /etc/inittab the following line is added: 3dx:234:respawn:/etc/3DxWare/daemon/3dxsrv -d /dev/null 2&1 where is the name of the port to which the device is attached. Demos: After unpacking 3dxware-aix5-v1-4-0.tar you can find two demos: The cube demo: /tmp/xcube and a value demo: /tmp/xvalue Those are two simple demos that work with the setting 'Any Application'.
You may copy the binaries to your favourite location for binaries. INSTALLATION INSTRUCTIONS FOR 3DxWare FOR AIX 5.2 ML04 (and higher) - V 1.4.0 To install the files for 3DxWare for Unix to the corresponding directories and to run the driver you need root privileges. Make sure you fulfill the following prerequisites: AIX 5: AIX 5.2 or higher is required. For AIX 52 you will need ML5200-07 or ML5200-04 and APAR IY78349 (can only be applied to ML04 or above) For AIX 53 you will need ML5300-03 or APAR IY78350 The web site URL for IBM fixes is: For USB device support you will need the following AIX filesets: devices.pci.22106474 devices.pci.33103500 devices.pci.99172704 devices.pci.c1110358 devices.common.IBM.usb devices.usbif.03000008 The first four contain drivers for the four different USB host controllers that AIX supports. You only need the one that matches your hardware but having them all does no harm. 'devices.common.IBM.usb' is the USB System Driver and 'devices.usbif.03000008' contains the client driver for 3DConnexion devices.
The files for the driver are provided with the following archive: AIX 5: 3dxware-aix5-v1-4-0.tar.gz Please save the file 3dxware-aix5-v1-4-0.tar.gz into the /tmp directory and extract and run the script install-3dxunix.sh: gzip -cd 3dxware-aix5-v1-4-0.tar.gz tar xf - install-3dxunix.sh./install-3dxunix.sh If you don't choose during installation the possibility to start the driver during login from the /etc/inittab please make sure the driver is started before you launch your application. For the USB devices start the driver with the following command: AIX 5: /etc/3DxWare/daemon/3dxsrv -d usb For the serial devices start the driver with: /etc/3DxWare/daemon -d /dev/ where is the name of your serial port to which the device is attached. Example: /etc/3DxWare/daemon/3dxsrv -d /dev/tty0 For the start of the driver from the /etc/inittab the following line is added: 3dx:234:respawn:/etc/3DxWare/daemon/3dxsrv -d /dev/null 2&1 where is the name of the port to which the device is attached. Demos: After unpacking 3dxware-aix5-v1-4-0.tar you can find two demos: The cube demo: /tmp/xcube and a value demo: /tmp/xvalue Those are two simple demos that work with the setting 'Any Application'.
You may copy the binaries to your favourite location for binaries. INTRODUCTION.2 1.1 PURPOSE.2 1.2 TARGET AUDIENCE.2 1.3 RELEASE VERSION.2 1.4 DOCUMENT HISTORY.2 1.5 REFERENCES.2 2. RELEASE HIGHLIGHTS.3 2.1 SECOND RELEASE (MAY 6, 2009).3 2.2 FIRST RELEASE (MARCH 6, 2009).3 3. WINDOWS SOFTWARE (3DXSOFTWARE).4 3.1 DESCRIPTION.4 3.2 SUPPORTED OPERATING SYSTEMS.4 3.3 SUPPORTED 3DCONNEXION DEVICES.4 3.4 CHANGES TO 3DXSOFTWARE.4 4. MAC SOFTWARE (3DXMACWARE).7 5. UNIX/LINUX SOFTWARE (3DXWAREUNIX).8 5.1 DESCRIPTION.8 5.2 SUPPORTED OPERATING SYSTEMS.8 5.3 SUPPORTED 3DCONNEXION DEVICES.8 5.4 3DXWAREUNIX PACKAGES FILE NAMES.8.
Plug-ins (i386, x86-64) for Autodesk Maya 8.5 Linux Content 1. INTRODUCTION.2 1.1 PURPOSE.2 1.2 TARGET AUDIENCE.2 1.3 RELEASE VERSION.2 1.4 DOCUMENT HISTORY.2 1.5 REFERENCES.2 2. RELEASE HIGHLIGHTS.3 2.1 SECOND RELEASE (MAY 6, 2009).3 2.2 FIRST RELEASE (MARCH 6, 2009).3 3. WINDOWS SOFTWARE (3DXSOFTWARE).4 3.1 DESCRIPTION.4 3.2 SUPPORTED OPERATING SYSTEMS.4 3.3 SUPPORTED 3DCONNEXION DEVICES.4 3.4 CHANGES TO 3DXSOFTWARE.4 4.
MAC SOFTWARE (3DXMACWARE).7 5. UNIX/LINUX SOFTWARE (3DXWAREUNIX).8 5.1 DESCRIPTION.8 5.2 SUPPORTED OPERATING SYSTEMS.8 5.3 SUPPORTED 3DCONNEXION DEVICES.8 5.4 3DXWAREUNIX PACKAGES FILE NAMES.8. INTRODUCTION.2 1.1 PURPOSE.2 1.2 TARGET AUDIENCE.2 1.3 RELEASE VERSION.2 1.4 DOCUMENT HISTORY.2 1.5 REFERENCES.2 2. RELEASE HIGHLIGHTS.3 2.1 SECOND RELEASE (MAY 6, 2009).3 2.2 FIRST RELEASE (MARCH 6, 2009).3 3.
WINDOWS SOFTWARE (3DXSOFTWARE).4 3.1 DESCRIPTION.4 3.2 SUPPORTED OPERATING SYSTEMS.4 3.3 SUPPORTED 3DCONNEXION DEVICES.4 3.4 CHANGES TO 3DXSOFTWARE.4 4. MAC SOFTWARE (3DXMACWARE).7 5. UNIX/LINUX SOFTWARE (3DXWAREUNIX).8 5.1 DESCRIPTION.8 5.2 SUPPORTED OPERATING SYSTEMS.8 5.3 SUPPORTED 3DCONNEXION DEVICES.8 5.4 3DXWAREUNIX PACKAGES FILE NAMES.8.
INTRODUCTION.2 1.1 PURPOSE.2 1.2 TARGET AUDIENCE.2 1.3 RELEASE VERSION.2 1.4 DOCUMENT HISTORY.2 1.5 REFERENCES.2 2. RELEASE HIGHLIGHTS.3 2.1 SECOND RELEASE (MAY 6, 2009).3 2.2 FIRST RELEASE (MARCH 6, 2009).3 3. WINDOWS SOFTWARE (3DXSOFTWARE).4 3.1 DESCRIPTION.4 3.2 SUPPORTED OPERATING SYSTEMS.4 3.3 SUPPORTED 3DCONNEXION DEVICES.4 3.4 CHANGES TO 3DXSOFTWARE.4 4. MAC SOFTWARE (3DXMACWARE).7 5. UNIX/LINUX SOFTWARE (3DXWAREUNIX).8 5.1 DESCRIPTION.8 5.2 SUPPORTED OPERATING SYSTEMS.8 5.3 SUPPORTED 3DCONNEXION DEVICES.8 5.4 3DXWAREUNIX PACKAGES FILE NAMES.8. Plug-ins (i386, x86-64) for Autodesk Maya 8.5 Linux INSTALLATION INSTRUCTIONS FOR 3DxWare FOR HP-UX 11 (and higher) - V 1.4.0 To install the files for 3DxWare for Unix to the corresponding directories and to run the driver you need root privileges.
BrianJ: If you’re posting your Mac hardware info in answer to my last question? Sorry for the confusion, I didn’t mean the Mac itself but rather was curious if the 3D connexion device is the one listed as supported on the Rhino for Mac system requirements page. Or is the 3D connexion device being used when the problem is seen one of the larger models they manufacture. I want to figure out if what we say we support isn’t working well or if this is another device. Maybe I misunderstood I ^^.
I for my work with Rhino use this. I heard back from 3D connexion and they said they don’t see a problem on their end. Sorry, I don’t have anything more concrete to offer other than their latest driver.
Your description makes me think about the zoom target though, next time this happens, please try selecting what you want to work on and then using ZS and enter to zoom selected. Then see if the lag is gone.
My hunch is that the 3D device thinks the target is somewhere else and is not moving it to where you think it should be. Try the option to rotate about the camera in preferences or turn it off for that matter if it’s on as a test. I managed to do some testing with the latest version of Rhino.
The problem remained for me. In practice, as do I rotate or zoom in on the object, for about 2-4 seconds a freeze occurs. Roughly this problem occurs every 5 minutes. I can not send the file I’m sorry. Summary of the audit: Calculation tables: 90 levels 3 dimension styles 4 font 10 types of line 11741 render materials Calculation objects: 17768 normal objects 216 locked objects 761 hidden objects 192 objects deleted (in the undo buffer) 0 items framing block 0 objects reference standard 0 objects reference blocked 0 objects hidden reference 0 items framing block reference No error. Small update.
I used the command “Export selection” and I exported the whole model without the levels in which I held the scraps and background images, the time of freezing has dropped from 3-4 seconds to about 1-2 notes that closing Rhino and then the Mac, the next time you start Rhino, it happens that the Space Navigator may not be recognized. To return to normal proceed as follows: 1) Closing Rhino. 2) disconnect USB input of the Space Navigator. 3) Opening Rhino. 4) connect usb socket Space Navigator. Zsimon: for about 2-4 seconds a freeze occurs. Roughly this problem occurs every 5 minutes.
I think this is the clue. Autosaving happens roughly every five minutes, and an autosave can take this long for larger models. That’s why your delay after exporting takes less time. If you were manipulating your view with the mouse this will never happen. OS X pays attention to mouse events and will not initiate an autosave while you are using your mouse.
I confirmed that the 3DConnexion device does not work the same way. An autosave can happen while the 3DConnexion device is active, and the autosave will not be deferred. I’ve added a test for 3DConnexion activity and will defer a pending autosave until the 3DConnexion device is inactive. This will be in the next RhinoWIP and in Rhinoceros 5.1.
Spacepilot Mac
Marlin: I think this is the clue. Autosaving happens roughly every five minutes, and an autosave can take this long for larger models. That’s why your delay after exporting takes less time. If you were manipulating your view with the mouse this will never happen. OS X pays attention to mouse events and will not initiate an autosave while you are using your mouse. I confirmed that the 3DConnexion device does not work the same way. An autosave can happen while the 3DConnexion device is active, and the autosave will not be deferred.
I’ve added a test for 3DConnexion activity and will defer a pending autosave until the 3DConnexion device is inactive. This will be in the next RhinoWIP and in Rhinoceros 5.1. I suspected that it was automatically saved. I really hope this can be resolved because slows my work.
They are available for any test.