Installing LW 9.5 64 bit and 32 bit on Vista x64

[Andrewstopheles]

Pop quiz:

1. Can I install both 32 bit and 64 bit on Vista 64?
2. Do I use the same installer and run it twice?
3. Do I need a different key, or is that ONLY for LW 9.3?
4. Can anyone point me in the right direction for the readme/tutorial on adjusting config files?

(I always ignored the config files issue in the past without problems but I want to make sure I get it right this time.)

Your help is always appreciated.

Give yourself 5 points for each correctly answered question.

Total:
0 Points - Thanks for nothing, ya yellow-bellied-sapsucker ya.
5 Points - Thanks for your help!
10 Points - Without you I don't know what I would do.
15 Points - You are an uber user and I worship the ground at your feet.
20 Points - I am not worthy of the dirt upon the sole of your shoe. Thou art truly deserving of my gratitude and worship.
25 Points or More - Clearly you are having problems with basic mathematics skills.

[RTSchramm]

Anwers to op quiz:

1. Can I install both 32 bit and 64 bit on Vista 64?

Yes,

2. Do I use the same installer and run it twice?

Yes, but install the 64 bit version first and select custom install. Make sure that the Sentinel driver and LW program is selected. If you want to develop your own plugins select ALL of the options.

When you install the 32 bit version, select custom and uncheck the sentinal driver, this is the 32 bit version, you have already installed the 64 bit version. Check the SDK option if you want to develop 32 bit plugins.

3. Do I need a different key, or is that ONLY for LW 9.3?

Yes, go to the Newtek site and click on the "Customer Care" link and select the "Registeration" menu option to get the 64 bit and 32 bit keys. You will need to register your product to get these keys.

4. Can anyone point me in the right direction for the readme/tutorial on adjusting config files?

The config files are stored at the root of your USER profile and are configured automatically as you change a configuration in LW. It is not recommended to modify these files directly. Often before updating to a beta version, some users will delete these files so that the beta version of LW will have a clean installation. I usually don't delete them, and so far I haven't had any problems, but I just a casual LW user so I don't push the software to its limits like many of the other users do. I haven't seen any tutorials on modifying the configuration files.

Rich

[Andrewstopheles]

Thanks Rich. That gets me started. I'll be all over that like a fat boy on a cupcake when i get back to my PC.

[arsad]

For 4.

you are better off doing custom config files for each version in its own folder.

BEFORE YOU RUN LIGHTWAVE (RIGHT AFTER INSTALLATION) DO THIS:

a. Make a folder called "config" in your Lightwave program folder

b. then make a shortcut for layout and for modeler.

c. Then point these to the config directory. Just do a right click on the shortcut and select properties

d. you add "-c" followed by the path to the config directory you just created (no space between -c and the path!!!) to the "target" field.
If you have empty spaces in your path, which I disencourage you to have, the the whole thing must be in upper quotes ("")
For no obvious reason the standard installation path of lightwave contains empty spaces, so be carefull!


mine for layout64 look like this:

C:\LightWave3D9.5_64\Programs\lightwav.exe -cC:\LightWave3D9.5_64\Programs\configs


you have to do this for each version of Lightwave you want to have installed side by side without interfering!

And RULE No 1. is:

ALWAYS START LIGHTWAVE WITH THESE SHORTCUTS AND CLOSE LAYOUT, MODELER AND THE HUB BEFORE YOU LAUNCH ANOTHER VERSION!!!


If you follow this, you should have no problem running several versions of lightwave side by side.

[Andrewstopheles]

thank you this worked for me

[Adrian@Stufish]

In our office - with four up to people using LW and passing jobs back & forth & throwing them on to the render farm (using butterfly), we all use the Same LW install and the Same config files (all located on the server) just have to make sure that if someone installs a plugin, everyone else is out of LW.
It gives us very consistent results, and if someone ever goes 'this just isn't working' then odds-on their machine has thrown a wobbly and made it's own config files. Cause sure as eggs is eggs, if there are confog files in the default location LW uses them instead of the ones specified in the shortcut!