Hello Will consider the update, as I've had a few other requests. The only problem is, every time I've updated that tutorial, Bryce or Poser is upgraded which means another tutorial update :-) That 180 reverse was for a specific combination of Poser/Bryce and you had to invert the texture map for it to work, but I forget which combo - but with the versions of Bryce/Poser you are using it should not enter into it at all. Another 2 possibles to try. If you have UVMapper. First would be to run UVMapper and load the OBJ mesh - if there are any out of range UV co-ordinates UVMapper will let you know. I doubt this, but that can result in mapping problems. The other thing to try out, is to apply just the bare black and white) template to the armor, preferably in Solo Mode and zoom in. Look at the template for the shoulder section of the armor that you are having trouble with and compare it to what's happening in Bryce. Like I've shown in my tutorial, the heads with just the template applied, it may offer a clue to what is happening - if it shows up as a 'mesh' it should be mapping fine, if it smears it isn't mapping correctly. regards John Spirko

Another suggestion - see if you can isolate the problem - -export only the armor from Poser -import into Bryce -apply textures It might narrow down where the problem is occuring - which appears to be a mapping problem, as far as I can tell. One of the things that I don't like about the Poser/Bryce combo is the way Bryce has to use the MTL file and as noted, the settings in the Material Lab are altered drastically. As an example, apply the Default Grey from Simple and Fast and you'll see the default settings are different. Don't know if this will help either. You mention that you visited quite a few tutorials. I have an older Poser to Bryce tutorial up, in case you haven't seen that one : http://www.iaw.on.ca/~jspirko/tutorial_poser_characters.htm good luck John

Well, the curious thing about the Mayan calendar, is that it ends either October 28, 2011 or December 21, 2012, depending on how it's interpreted. So there's plenty of time :-)

Well, not to disillusion people, it's my experience that no one has ever created a Gold Master just for a patch. The one and only Carrara patch was 835Kb - hardly worth the expense of a Gold Master. So, indirectly we know where Eovia's efforts have been directed - a new version of Carrara. The post does not indicate if this is version 1 or 2 - pardon me if I'm not optimistic, but I suspect it's version 2. Antoine's line: "Carrara is back and this time it is ours!" maybe happy news to people who never had Carrara. But as far as I'm concerned, the version of Carrara that I have, has never 'left' and it's 'mine' and already paid for. Eventually, I'll find a suitable modeling program (not Carrara 2 or Amapi) and Carrara will be gone from my hard drive. Antoine also says: "It is now time for the Carrara Team to go get some sleep!" and most likely well deserved! Except for those of us who are still waiting for a patch - are.... well... still waiting for a patch! By my rough calculation, it's been 18 months since Carrara was released, and I'm still waiting for a patch. Even the Energizer Bunny would be running low on optimism.

Hello! I agree - start the FAQ after the patch comes out and concentrate on the patched version where possible. I'd also suggest that you create a rough template or format for reporting bugs/workarounds - similar to what many companies use for beta testers/bug list. Ideally, it would list platform(s), a specific area of Carrara, ie VM, Spline, Assembly Room, etc. so the user can more easily locate the bug/workaround. As well as posting bugs with no known workaround, other than frequent saving - simply to make the user aware, or the possibility that someone does find a decent workaround later on. And perhaps, just do a small trial run concentrating on one area first and ask for feedback to see if people are making use of it. regards John Spirko

Not trying to discourage you from creating a Carrara bug list, but with a supposed patch coming out soon, some of it may be irrelevant shortly. You may want to hold off putting a lot of effort into this until the patch arrives. To make the list useful, it would have to be categorized ie to allow anyone to locate and match up a bug they are experiencing with what's on the list. Part of the difficulty would be categorizing the bug list - ideally there should be 2 - 1 PC and 1 Mac version for bugs that are present only on one platform. Then to categorize by area, such as the VM, Spline, etc. which would be a lot of work. Some of the bugs have good workarounds, some don't, but the workarounds would be useful - but for anyone already using C, they probably have figured a lot of them out. As far as Eovia fixing them, this may be another difficult area to assess. I've sent in quite a few bug reports, mostly serious/crash types directly to Eovia, without any response. Secondly, Antoine specifically pointed out some time ago on the Carrara list (Yahoo) that the bugs should be posted directly to the Eovia site - stating to the effect, that if they weren't reported, they couldn't fix them - your bug list may get ignored. Although I never saw any, there were previous bug lists prepared and you may only be duplicating what someone else has already tried to do. Given that we've only had 1 patch in over a year and that Eovia is working on Version 2, the bug list for Version 1 might be only useful to someone who choses not to upgrade. Pardon, if this isn't what you wanted to hear, but I wouldn't want to see someone spend a lot of time and effort in a large undertaking as this and find it largely ignored or unused. It's a fine application. But I won't recommend it to anyone due to the bugs. I know a couple of users on both platforms who couldn't get it to run at all. regards John Spirko

The appearance of that message was enough for me to unsubscribe from the Carrara egroups list. It appears to me that the calendar has been rolled back one year and I may as well forget that I sent in any bug reports and enhancement suggestions. The comment "a complete and structured beta-testing will be started later on" sounds ominous (to me). 'Later on' is not a good time to start beta testing this product. For the last year, on and off, I've been trying to learn this program (which I still believe has potential) but I could have used that time to learn another program and be growing with that program - poor choice on my part to stick with it. Even if I stick with Carrara and it does merge with Amapi, I suspect the end result will be considerably different for both programs - resulting in having to start from scratch learning yet another application. I'm still using Carrara - I've learned a lot of the workarounds. And I plan on trying out Amapi, but I'm uncertain about that direction, since it could be the same destination as Carrara. But that is a long way off and there are other modeling applications - maybe a year from now I'll be more proficient in one of them. John

yes - check this out: http://www.vanlippe.com/waterfall/movie.html it also has a tutorial John

Lattices/structures are good for detailed wall structures. For simpler walls, another option is to use 2D faces and apply a picture texture/materials. They can be booleaned. I've used them both for indoor and outdoor walls. The Mill here consists of 'cube' beams, but all the walls, roof are 2D faces. The glass windows are 2D faces, booleaned within a cube/negative cube window frame. http://www.iaw.on.ca/~jspirko/swan_mill.htm The swans started out as greyscales on lattices, exported as OBJ files so I could use UVMapper to create texture maps. John Spirko

Thanks for the tip. I'd probably find moving the eyebrows in Poser easier to control than in Bryce. Never thought to look in Poser for the solution. Also, I did delete the front set to see what happened - not a good solution by itelf :-) In the screen shots, I've selected both sets of eyebrows together for the sake of visibility. Thanks again. John Spirko