cedarwolf, Judy shares UV mapping with V1/2, so any victoria 1/2 texture will work, except for the eyes which have their own texture file.

I don't think it's random - it always seems to accurately divine and delete the figure on which you've done the most work since the last save ;-) It does not care about capitalization in the .obj path on a PC.

Attached Link: http://www.curiouslabs.com/articles/articleview/215/1/65

Just for information, when Poser searches for textures as described in prior posts it searches the entire Runtime, starting at the begining. Everything, that includes Python, even the dll's, all of the !Daz stuff, and even searches past the Textures folder if it doesn't find it. That's why it takes so long...

There was a directory on the 2nd CD that came with P5, called Bonus Content, containing Don and Judy in .pz3 files (!?!), which had more morphs. I'm guessing this was their way of hiding those from those who didn't want them?

Attached Link: http://vim.sourceforge.net

Partial workaround... Click on the "compass direction" icon on the toolbar (2 double headed arrows in a plus sign). This replaces the (opaque in our case) sphere with an axis-only move icon. Kinda big and distracting - but at least it's transparent, so the actions of the dials are visable... Meanwhile we ALL need to submit this as a bug, 'cos they claim to be fixing bugs based on volume of reports per bug (shudder) - way too much like CL's Poser5 approach (BIGGER SHUDDER) Trouble is I for one can't submit bugs, OS Platform is a required field with only one choice - "Not Set" - so it fails entry validation.

Rob, Thanks for the response. Understand impossibility of featuring support for every card's OpenGL issue - and in this case if it is indeed lack of hardware overlay planes, there's probably no real fix, at best just lifting the level of pain, until it bites anyway at a higher level of scene complexity. But what about the idea of just making the controls optional via a Preferences setting? That way Studio would still be usable on all of these cards. Of course the option would have to prevent all calls to overlay routines, not just make the controls entirely transparent ;-) But then Daz' message on OpenGL would be that you need a later OpenGL card implementation to fully support mouse manipulation of scense, vs. current message which has to be, you need later OpenGL card to even use Studio.

{Sssssh, this old forum software! Attempt 3 - hopefully not eaten this time... } OK, did some Googling... Transparency is an issue with graphics packages it seems, particularly if they support ray tracing correctly. It puts a large load on the graphics card to display alpha transparency. (There is a kludge used in games to get transparency to render easily, but it impacts lighting results - so isn't the choice in 3D graphics packages.) Result may be transparent surfaces displayed as solid surfaces. Seems to fit. Per Alias' support pages for Maya, cards without Hardware Overlay planes give poor performance in OpenGL on Maya. Their sample list of cards is interesting as it correlates exactly with cards peeps are reporting having this problem with Studio: - NVIDIA TNT/TNT2/GeForce/GeForce2 - ATI Rage 128/Rage 128Pro - Matrox G400 - etc. All this is circumstantial of course, but it looks as if Studio may depend on overlay for rendering the "control balls" - it would certainly seem reasonable. And then any card resorting to software Overlay would have a harder time of it, whether due to lack of raw processing power, or card memory I was not able to glean. [Agreed new cards are not that expensive, even for PCI only systems. But my problem is a Matrox G400 3D-Flex card tied at the chip level to the expensive video capture card in my system.]

It occurs on Matrox cards too. And it appears on .daz figures in the supplied content (but in white), so it's not the Poser import. Rob W felt it was related to lack of memory on the OpenGL card (I've 32MB), but I didn't get him to give guidance on how much was enough.

Also in my case it remains transparent if I only have 1 (smallish in file size), add a second or use a larger character and it goes red or black - always same colour for given characters.

My hunch is that it's a coding error in Studio (Matrox OpenGL implemenation is used in many workstations), but if not it's unlikely to get fixed per se, as the response would be a simple (from Daz perspective) upgrade your card/driver (not possible in my case).

However, all may not be lost - there have been requests from the outset for those "control balls" to be made optional, via a prefrences or a hot key, from those users without this bug. They just want to be able to look at a clean image in the scene window. IF that enhancement was added, then the solid spheres could be hidden by those of us experiencing them, and adjustmenst made using the dials. Otherwise, as indicated, even using the dials is not an option - unless you like making adjustments to hidden actors :-O

Hey guys, this is the line you should be focussing on: "... on the abilities of D|S with its eventual native content." - MallenLane. It's entirely commonsense (business-sense) for Daz to go in this direction. And have you looked at a .daz file? Nothing to see! Think about what will happen when Daz starts shipping products in .daz format... Yeah, they'll keep .cr2 around in parallel, but their brokers will have to follow suit. And then what happens to 3rd party add-on products at other brokers? A fractioning of the community is (unfortunately) a question of when, not if. Someone can - and probably will - write a tool that will take internal props and spit out external objects so they can load in Studio and Poser. But a native .daz format figure is destined to stay Studio only (a HUGE benefit to Daz). And have you seen Rob W's Xmas day statement on Daz Forums that Studio will not support injection as we know it? It'll be dynamic morph loading in a future release. Let's hope that it's entirely backward compatible with Daz series 3 figures (i.e. that V3.cr2 will load in Studio exhibiting extactly the same feature set as a V3.daz will). I'd like to hope it would be, but it's more likely that it won't be long term, even if it is on first release. IMHO Daz see Studio as a Poser replacement as they have said all along, but NOT in the way that Poser users seem to interprete that statement. I believe their goal is to replace Poser in the marketplace, which means a very different approach - perhaps even an othogonal one - to the replacement of the Poser application for the average Poser afficianardo.

Ditto on the every-time-I-try-something-it-crashes with a matrox card. Seems that Daz use predominately gForce nVidia graphics cards judging by the problems encountered by older Vanta-based (TNT2 et al) nVidia, ATi and Matrox users... A solid (vs transparent) adjustment sphere in front of every selected actor is a real deterrent to successful posing! Hopefully they'll make the adjustment spheres a configurable option for a cleaner interface for those who prefer to just adjust dials, then perhaps I can use it. Looked fairly good otherwise. I note that you can move all windows other than the scene window onto a 2nd monitor as free-standing windows in order to get a huge scene window. Unfortuantely the ui settings aren't saved (yet?) - and all the .daz file formats are binary so no way to easily cheat that. This latter design decsion may turn out to be an ultimatly limiting factor for the product - where would Poser be today if the file formats had all been proprietary rather than open Wavefront Obj stored in simple text???

Single click on the tools (not the title a la P4) with Alt held down works too.

I'll second Little Dragon on the heat function that comes with Poser. While working on silencing the fans on my PC, I noted that just loading and having Poser 5 as the foreground task I could raise the temperature of the CPU by a recorded degree F (i.e. ~0.5 degree change). If that seems improbably then check the CPU utilization of an idle Poser 5, then move your mouse over it's user interface ;-) Rendering injects a minimum of 2 degrees F into my well-cooled CPU - as it's pegged hard at 100% usage.

This seems to be a change of direction by CL again. When the CEO came here he said that Poser 6 would not include new features but just make Poser 5 work. (Which caused a few "should be free then" type of comments.) So question is, is this survey for new features INSTEAD of oft-promised fixes, or additional? If the former (which is same ol', same ol' for MetaCreations/Curious Labs) then they owe us an SR5 (there's just not been enough wall clock time for SR4 to have fixed everything ;-) And if it's new features as well as fixes it'll mean even looooonnngeer before we have a working product :-( Interestingly the link to CL's CEO visit here disappeared from the top of the Poser Tech/Python forums just this past week... Re the dials-as-bad-as-my-golf-swing comment, this would mean re-implementing the Poser 5 parameter dial panel as part of the Poser interface again (a la P4) rather than a separate Windoze task. The "throttle lag" is due to Windows interprocess communciation - which was never designed to handle full real-time interprocess communciation when requires a x-windows feedback loop! This 'bolt on window' was an OK solution on MacOS and OSX where it's all treated as part of the same task by the OS, but a dumb design for Windows. (BTW, if you haven't removed Content Parasite, this can help - but not cure - this lag.)