LW Prefs

[Darth Mole]

Okay, I've installed LW on my new 12" PowerBook, and it's all running fine, it's recognising the dongle. But I can't get it to recognise my old Prefs files - and, weirdly, it won't write any new ones and I don't even get the old "LightWave has unexpectedly quit" message.

Any ideas?

The Prefs should be saved into my User>Library>Preferences folder, yes?

Well, nothing there...

[Darth Mole]

A-ha! I'd copied in the old Cmd line files and they had the wrong path in them, so LW couldn't see where the Prefs were supposed to go.

Thanks to Julian Johnson and one of his old posts...

[Beamtracer]

I don't know why it is necessary for Lightwave to use this method for preferences.

Other applications don't seem to need a command-line text file directing them to where the preferences are.

It's very DOS-like. Is it necessary? Are there any advantages?

[mlinde]

Originally posted by Beamtracer
I don't know why it is necessary for Lightwave to use this method for preferences.

Other applications don't seem to need a command-line text file directing them to where the preferences are.

It's very DOS-like. Is it necessary? Are there any advantages?

Beam, there are a number of advantages to the preference setting file, although it is also very archaic. First, I feel the default setting should not require a file, and should look in the ~/Library/Preferences/ directory of the currently logged in user. Now, the usefulness of the file.
1) In an educational setting, it is important that all students at shared computers start with the same (assumed to be correct) default preferences, and not be able to modify them permanently. Using the /Library/Preferences/ directory instead of the directory for a logged in user will keep the preference files unblemished.
2) In a network rendering environment, the ability to access shared preferences (via the network) without having to hunt down and copy all the various preference files to each computer is also beneficial.
3) There are a number of "undocumented" features of Lightwave (including modifying the appearance of the application). By creating multiple preference files, and referring to them as desired, you can change your configuration quickly and easily. In addition, the localization of preference files can be utilized to set up Mode 3 rendering (with one thread) while working in Lightwave with multiple threads. I have an LScript that allows me to do this.

[Darth Mole]

I just wish the manual was a little more forthcoming on the whole installation thing and why it does what it does. (When I first got LW many moons ago, as a Mac user it felt like I'd been transported into ancient computing history).

At some point, this Prefs/Cmd operation needs to be automated/accessible via the LW interface, and you should be given a choice of how you'd like it set up.

(How about a log-in style window, which asks which user you are, or which Prefs you'd like to load - I mean, how hard would that be??)

Ah, who am I kidding...?

[Beamtracer]

Hi Michael, thanks for your reply.
Originally posted by mlinde
Beam, there are a number of advantages to the preference setting file...
1) In an educational setting, it is important that all students at shared computers start with the same (assumed to be correct) default preferences, and not be able to modify them permanently. Using the /Library/Preferences/ directory instead of the directory for a logged in user will keep the preference files unblemished.
Well, in most other applications, if you want an unblemished preference file, you trash the current one and then launch the application again, producing a new default one.
Originally posted by mlinde
2) In a network rendering environment, the ability to access shared preferences (via the network) without having to hunt down and copy all the various preference files to each computer is also beneficial.

It must be possible to automate this sort of thing. Each network node should be able to automatically get "handed" any necessary settings from the host machine. A new network renderer for Lightwave should be able to do this.
Originally posted by mlinde
3) ...By creating multiple preference files, and referring to them as desired, you can change your configuration quickly and easily.
Can't this be done more easily in a normal situation when preferences are stored in the User Library? You just keep multiple preferences and drag them in when needed.
Originally posted by mlinde
In addition, the localization of preference files can be utilized to set up Mode 3 rendering (with one thread) while working in Lightwave with multiple threads. I have an LScript that allows me to do this. This is a useful feature, but there must be an easier way to do it! I imagine a new network renderer with a controller that allows you to see each machine and set the number of threads from this controller.


I just think there is unnecessary heartache caused by the current system of a preference file in the application folder with a command line file telling the application where to find it.