4DVista2.0 is available for the following operating systems
Windows 2000 / XP
Linux - We currently support: RedHat Enterprise 4. 4DVista may run on other distributions of Linux, however we have not fully tested on any other distributions.
What are the hardware requirements for running 4DVista2.0?
Please check below to ensure you have at least the minimum specification before installing 4DVista2.0
The following list of models and components are illustrated as a general guide only, if your system configuration is different and are unsure of its capability to run 4DVista2.0, then please email
with your system details for further information.
The hardware requirements greatly depend on the size of data sets you are using. If you are working with large data sets we would suggest the "ideal" recommendations.
Nvidia NVidia Quadro FX GO/M series Nvidia NVidia Quadro FX GO/M series(5)
Screen
14.1" XGA
15" SXGA or similar
15/16/17" UXGA or similar
All CPUs should be x86 or AMD64/Intel64 compatible, i.e. Intel Pentium/Xeon or AMD Athlon/Opteron.
4DVista Performance version will make use of multi-threading capability on dual-core or multi-cpu systems.
For optimal video performance with OpenGL when using an NVIDIA video card under Linux, it is recommended that you use the accelerated drivers provided by NVIDIA on their website www.nvidia.com/drivers. These drivers deliver a performance increase of 5-10 times the default drivers that bundle with a standard Linux install.
The speed of development of graphics cards is so rapid that it is becoming difficult to stay up-to-date. If you have any questions regarding new graphics cards, contact
.
We have experienced a number of issues with machines using ATI based graphics cards under Linux, many of which have caused the machine to crash. We had not experienced the same problems running on any systems using NVIDIA based graphics cards and would therefore strongly recommend the use of NVIDIA.
4DVista is dual screen capable with a single desktop spanning two physical screens. This is recommended as it only additionally costs the price of a second monitor. You must purchase a graphics card that is advertised as dual display capable and has two CRT/DVI outputs.
Windows XP - Service Pack 2
Upon installation of Service Pack 2, when you open 4DVista a 'Windows Security Alert' window may pop up asking:
'Do you want to keep blocking this program?'
The user should NOT click on the 'Keep Blocking' button if they want to use interoperability. 4DVista does need to accept outside connections in order to communicate with order MVE applications.
What type of license can I have?
To run 4DVista2.0 a FLEXlm license key is required.
The two types of licenses available are:
local license
network license for 10 users
These licenses are permanent, they controls what feature level are available:
Essential Feature Level is free of charge and provides access to basic features and common import formats.
Performance Feature Level is available at an extra costa and provides enhanced visualisation, support for geocellular models, additionnal imports formats, etc.
For further information on feature levels, please visit our website or contact
.
If you require support to install your network license, you will be charged an administration fee, please contact
for further information. Maintenance contracts are available; please contact
for more details.
Note 1: Triple Redundant Network licenses are also available, but you must contact
to obtain one. This will incur an administration fee.
Note 2: It is possible for the system administrator to use environment to control licensing. Please see online help, visit the FLEXlm End Users Guide at http://www.macrovision.com/pdfs/flexlm_licensing_end_user_guide.pdf, Section 2.1.1 - Setting the Path with an Environmental Variable, or contact
.
How do I obtain a license for 4DVista2.0?
Once you have completed your request for a license of 4DVista2.0 you will be sent an email containing a hyperlink, which will take you to the page where you can obtain your license key.
Select Local or Network License.
If you are planning to install a local license you will be prompted to enter the FLEXlm hostid of the machine you have installed 4DVista2.0 on.
To obtain your hostid:
Run 4DVista2.0
You will be prompted with an error message: "Unable to find license. Please configure"
Click OK.
The FLEXlm hostid will be displayed in the Configure License Manager dialog box.
If you require a network license you will be prompted to enter the hostname and hostid of the machine that you have your FLEXlm License Manager installed on.
To obtain your hostname and hostid, you can download and run lmtools or lmutil from the FLEXlm website.
Once you have entered the required information click the Download Key button.
Your 4DVista2.0 license key will be emailed to you.
How do I install my Local License?
Copy the license.dat you have been emailed to any location on your computer.
To install the license:
Run 4DVista2.0
You will be prompted with an error message: "Unable to find license. Please configure"
Click OK.
The Configure License Manager dialog box will be displayed.
Select Local for License Mode
In the Locate Local License File field browse to the location of you license.dat file.
Click OK.
4DVista2.0 should now be licensed.
How do I install my Network License?
Network licenses are available to users who are familiar with FLEXlm licensing.
If you require support to install your network license you will be charged an administration fee, please contact
for further information.
To run your network license you will require the mvfd vendor daemon, which is supplied with your 4DVista2.0 download. Once you have installed 4DVista2.0 the mvfd daemon can be found at the following locations:
Windows:
C:\Program Files\4DVista2.0\license_daemon
Linux:
/opt/4DVista2.0/license_daemon
Within the license_daemon directory you will find the mvfd vendor daemon for Windows, Irix, Solaris and Linux.
Copy the mvfd daemon in to the FLEXlm License manager's bin directory.
You may also need to download lmgrd daemon, which is FLEXlm's main daemon. To allow 4DVista2.0 to run from a network license you will require version 8.4a or higher of lmgrd.
The latest lmgrd daemon can be downloaded from the following location:
We recommend that you use the FLEXlm's default port, which is 27000. However if you are running other Midland Valley licenses, which have the port set to 1574 you may need to edit you license files.
If you want to continue using 1574, you can copy the feature line from the 4DVista2.0 license that we have sent you into your current Midland Valley license.
For example:
Your 2DMove license:
SERVER ulva 0050ba25c81e 1574 VENDOR mvfd USE_SERVER
FEATURE 2dmove mvfd 5.0 permanent 1 45C37CC0F9AA
Copy in your 4DVista2.0 FEATURE line
SERVER ulva 0050ba25c81e 1574 VENDOR mvfdUSE_SERVER
How do I locate my network license from a workstation?
4DVista2.0 can only run if it can locate the license across the network.
To locate the license server:
Run 4DVista2.0
You will be prompted with the following error message
Click OK.
The Configure License Manager dialog box will be displayed
Select Network for License Mode.
There are two methods of directing 4DVista2.0 to a network license - Specify Server and Specify port@host. We would recommend that you use the Specify Server method.
To Specify Server:Select Specify Server for Configure Network License. Enter the hostname of you license server in the Server Name field and the hostid of you license server in the FLEXlm Hostid field.To Specify port@host:Select Specify port@host for Configure Network License. Enter the port number you are using in the Port field and the hostname of your license server in the Host field
Click OK
4DVista2.0 should now be licensed.
What happens if the Data Link data transfer is interrupted/cancelled by the user mid-transfer?
If the transfer is cancelled by the user at either end of the communication, or if network connectivity is lost during the transfer, the Target application will display the data that has already been received.
What happens when the document being transferred through Data Link is already open in the target application?
When applications exchange documents through interoperability, they do not send along the location from which that data was originaly loaded (since that data might be on a totally separate machine).
Each document however is tagged with a unique key when it is first sent through interoperability. That key is then stored and re-sent along with the document each time it is send back and forth. When receiving a new document the applications will search for existing documents matching the key it is receiving. If it finds one, it will ask you if you wish to close the existing copy of the document or choose to have multiple copies.
If changes have been made to a file since it was opened, what will be transferred through Data Link?
The document that the user sees "live" in the source application window is the document that will be transferred. This means that any changes that have been made since the document was opened will be transferred.
Why can't the source application connect to the target application?
They are two reasons why two applications may not be able to connect to each other:
Check the settings to see if everything is configured correctly. Make sure host names, server ports and user names are correct. Use the buttons to test the connection
The machine or network may be setup to block connections on the port ranges used by MVE products. In particular, a firewall may be blocking connections. Please check with your system administrator.
What happens when the source application cannot open the target application?
If the connection does not succeed, the source application will attempt to launch a new copy of the target application. Note: This can only be done on the local machine. For instance, 4DVista on Windows will not be able to launch a copy of 3DMove on a remote Linux system.
When the new copy of the receiving application has started, the sending application will attempt to connect to it directly.
Why does Data Link require the username that I logged in with?
The target application will verify that the user name it receives matches the login of the user running that application. This ensures that data is not sent to another user on shared hosts.
What happens when data is transferred that is not supported in the target application?
When opening an MVE file or receiving data from another application, objects that are not supported will be dropped. When dropping data the applications will display appropriate warnings. Sending data through interoperability will not modify any of the original files. For more information about which objects are supported, please refer to the online manual of either of the applications.
I can't find an object by id when sending data from application to the other
When opening MVE files or receiving data through interoperability, 4DVista will not preserve object ids. Object names will however be preserved.
I sent a file from 3DMove to 4DVista and I see to have more objects than I had before
3DMove and 2DMove have single objects which are composed of several individual components (like a patch being made of a polygonal surface and boundary polyline). 4DVista does not support such structures and each component will appear as a separate object. The original complexe objects can be identified by it's name, which will have two parts separated by a column (:). 2DMove and 3DMove will use that name to rebuild the composite objects. Since these names are meaningful, 4DVista will prevent the user from renaming those objects.
