Hey dgud,
I do have Wings3D installed in the default location. I have manually added the YafaRay.beam file to the import_export foldler under plugins.
But it doesn't appear on any menus. My Wings is 1.5RC.
Is there anything else to do when 'installing' a beam file ?
There doesn't seem to be a magic number at head of beam files to identify them...
--------later-------
OK it must be the mlab version.
If I drop the beam file into that folder on a regular 1.5 like Wings 3D (x64) 1.5.pre1.78.gdd6c then it shows up on the menus.
So now I have that plugin working it looks like the registry again.
Building it by hand isn't working so well for me
I'm typing something wrong
--------later-------
OK its because I have a 64 bit OS. so I needed to add the registry key into a weird looking WOW6432 key which is where the keys live when mixing 32 bit s/w on my machine.
So on the positive side - a render occurred. YAY!!!
On the negative side it said "No image rendered"
I do have Wings3D installed in the default location. I have manually added the YafaRay.beam file to the import_export foldler under plugins.
But it doesn't appear on any menus. My Wings is 1.5RC.
Is there anything else to do when 'installing' a beam file ?
There doesn't seem to be a magic number at head of beam files to identify them...
--------later-------
OK it must be the mlab version.
If I drop the beam file into that folder on a regular 1.5 like Wings 3D (x64) 1.5.pre1.78.gdd6c then it shows up on the menus.
So now I have that plugin working it looks like the registry again.
Building it by hand isn't working so well for me
I'm typing something wrong--------later-------
OK its because I have a 64 bit OS. so I needed to add the registry key into a weird looking WOW6432 key which is where the keys live when mixing 32 bit s/w on my machine.
So on the positive side - a render occurred. YAY!!!
On the negative side it said "No image rendered"