How many incompatible versions are there of Windows 95, and of Windows 98? How likely is the affected user to damage his system, if e.g. the Qwertyuiop package moans that it can't run because zxcvbnm.dll is missing, so he transplants a copy of zxcvbnm.dll from another computer?

Its sails are not complete enclosed bags made of faces but open sheets of faces with loose edges all round. Thus the faces in the sails are clockwise as seen from one side and anticlockwise as seen from the other side, and they don't have "back faces". It seems that when Poser (at least my Poser 3) is making the ordinary quick view rather than a formal render, it ignores faces whose corners are listed clockwise as seen by the camera, as a quick way to ignore hidden faces.

Zorak likely modelled a left boot, and then he (or whatever graphical package he used) made it into a right boot by changing the sign of all the x's in the coordinates of the vertexes. That would leave all the faces with their corners listed clockwise instead of anticlockwise when seen from outside. Some rendering packages ignore faces which are clockwise as seen by the camera as a quick way to ignore hidden faces, assuming that all the faces are anticlockwise outwards.

The offending desktop has 6 logical hard drives (2 disks each partitioned into 3), and is getting a bit tight on free disk space on C: and E:, which are the two logical drives that I use mostly. Could that be why this fault is happening? How can I tell my Windows 95 to use F: for working space?, as my F: has much more free space on.

i.e. if the least squares fitted curve proves to be n=f(t) (n = number of accesses, t = time since downloaded), then, for each item, popularity = n/f(t).

Kevin wrote:- > And you will find that including eyes in the phi leads to problems later. In Poser 3, I read that the only valid way to get a human figure's eyes in correctly is: Leave the eyeballs out of the geometry and the .phi file. Create the .cr2 file in the usual way. Then add the eyeballs to the geometry, and copy in the eye matter to the .cr2 file from some other model's .cr2 file, but you have to be know what you are doing if you mess about with the insides of a .cr2 file. (Someone told me that Poser 4 behaves better with eyes when it makes a figure given a .phi file that mentions eyes.)

They are in the same folder with the Harley model! :: its .cr2 file's "where is the geometry" lines is this:- figureResFile :Runtime:Libraries:Character:New Figures:Harley.obj In the end I renamed Harley.obj to Harley_.obj, and altered the pointers in its .cr2 files accordingly. Also, the two .rsr files get into the same folder when someone copies all 4 files into the same folder to zip them together for uploading.

When I get Poser 4 or 4.1 I may try it. But all too likely I would find that Poser's equations / algorithms (as controlled by the joint parameters) that are adequate to describe the behavior of the flesh of his neck as his head moves, will act hopelessly wild when extrapolated to apply to a loop of breathing tube that may go out to 3 or 4 times the radius of his neck away from him. I have been on computers helping students with their projects since the late 1960's, and in that time I have had my fill of the misbehaviors and ornerynesses of extrapolated fitted equations. I had it in the last few days with my scuba set model's "stabbag0" part acting wild then I posed its stab-jacket, until I set it to "do not bend" to keep it under control.

It sounds like what for me is a very familiar and old pest from the late 1960's onwards in helping polymer science students with computer programming for their projects, namely: having to trust extrapolating a fitted equation. In this case it is the equation that describes how the model's flesh behaves as his joints articulate: extrapolating it out to how a garment would behave. Interpolating a least-squares or Fourier etc fitted equation: A-OK. Extrapolating it is like a ship without a rudder, and the more wildly inaccurate the further out you go into the void away from the zone of known values.

Go through the model's .obj geometry file with a text editor looking for lines starting with "g", to find what its groups are really called. Those lines set the groups. If your group names are on "usemtl" lines rather than on "g" lines, something is wrong somewhere.

how were the ropes done? - When I needed to pose a length of tube (part of his breathing apparatus) as part of my Gerry Anderson UFO alien model, I did this: Make the tube as a simple Poser model of 16 segments with the curve property. Import the alien's geometry as a non-posable prop. Pose the tube. Remember how many segments of the tube were needed. Delete the alien (since Poser 3 with props triangularizes meshes and removes g and usemtl lines). Export the tube as .OBJ . Resume editing the alien's geometry thus: Add and place and size the tube, and delete the surplus.

Do you have more details as to what keys{...} does? No. pz3 format is much like cr2 format, plus sections about lights and cameras, and everything is in one big tree of parts with "UNIVERSE" as its root part.

You write:- > 582 keys //Don't really know what this does. > 584.{ > 585.static 0 > 586.k 0 0 > 587.} The "keys" sections have more varied forms in animated .PZ3 files.

Likely such things as the girl's bra straps turning to spaghetti, as Allerleirauh complained about hereinabove, are caused by extrapolating out to the garment the equations that adjust the model's skin. In physics in general, extrapolating fitted equations is "um heap bad medicine", as I learned long ago over many years when helping students with computer programs as part of their degree projects.

two prop type boxes at the far corners of the scene (x,y & z) i.e. one at (xmax, ymax, zmax) and the other at {xminx ymin, zmin}. One thing useful would be, when Poser exports an .OBJ file and Bryce imports it, dor Poser to be able to prodice and Bryce to be able to read special .OBJ-language comment lines like e.g. #begingroup 1 man1 .... #endgroup 1 #begingroup 1 alien2 .... #endgroup 1 to make a tree structure of groups of groups. where the 1's are nesting levels.