Ok I know I know there is a bug reporting link but I thought it might be good for us to have a place to get squared amonst ourselves over the holiday weekend since we have been left alone with the new toy, which seems very nice btw. In the interest of sharing info.. These are things I encountered that seem like bugs: Probems encountered using default Egyptian scene: -Resizing document window created display error in view port until new setup is chosen. -Using spot render and then moving camera created hourglass icon that won't go away and replaces all other pointers -No escape from Spot renderer -Absence of selection silhouettes makes item selection in complex scenes very difficult unless user knows item's name and what child it is parented to (if any). To select anything parented to a figure you have to guess where it is parented and open the entire IK hierarchy one by one until you find it. Example:Cannot find "Fan" in listings of scene elements for Egyptian scene -Cannot move or resize palettes --Delete key not always working. Must use pull down before del key will work again -Deleting Figure sometimes removes textures from clothing. -Double clicking a Studio Alpha scene while a current scene exists crashes program - Trans not functioning in Real time. PC Win2K

Example:Cannot find "Fan" in listings of scene elements for Egyptian scene It's parented to the hand of the EgyptianSashMM.

Yeah I found it eventually. :) "To select anything parented to a figure you have to guess where it is parented and open the entire IK hierarchy one by one until you find it"

I have to admit, that wasn't the first place I looked, either. :/

I have yet to successfully import anything. Everything encounters an "unexpected )"m then imports only about 10% of the scene. Individual props import partially, but with about half the geometry missing.

Going to sit down and read more of the included docs before bed.

I usually get the "unexpected bracket" message, also. So far, I've managed to successfully (without error messages) load a very simple scene containing only the DAZ reindeer, sleigh, harness, and bridle, originally created in Poser 4 last Christmas. However, the bridle didn't conform properly on import, Poser's ground plane didn't load, and the materials on the sleigh seemed overbright.

Every prop I have loaded from my Poser folder (5 so far)gave me the "unexpected bracket" error and couldn't find the textures....

Hmm. SOme parented eyeballs in a cr2 are coming is but not rendering visible. I got everything perfectly placed but I closed program accidently. Save prompt would be a good thing down the road. Also there is currently no scale dial... there is x y and z but you have to do all three individually

No JCM support? Some clothes who support that, the figure pokes through. Mazak

I didn't even get that "unexpected bracket" error yet...DS freezes up my comp completely and I have to hit the reset button on my tower ;-( So far I tried to play with the egyptian scene, starting from scratch with the provided egyptian stuff, and tried to import a P4/PP scene. Same freeze up every time, just after a different amount of minutes... Comp: Athlon 1800 with 1 gig RAM and a 9200 Radeon gfx card. Am -not- too convinced of DS yet L

oh, OS is Win2k, too.

I had a crash too importing a simple scene. Instead import individual elements from your library. Didn't need to reset but I am Win2K as well.

I have the same issues as PheonixRising and I am using Win2K Pro on an Intel mb/proc with 512meg or rdram. It dies trying to load one of the egyptian jpg images. I seem to recall that the parenting issue is mentioned in one of the install files or the email from DAZ. Win2K Pro, 2.6 g proc, 512m Rdram, PNY Nvidia GeForce4 Ti 4600 graphic card and Poser 4. BabaLouie

On the whole, I like what I've seen from this being just an alpha release. These are just the glaring problems I'm having right now. I'm getting the same bracket error on every pz3 I try to load. I do mostly animations so all of my pz3 having animation data. I didn't expect it to import any of it except the first frame similar to what Vue does. I'm also having a problem with moving legs around. I notice that the feet have x, y and ztrans parameters so I figured there must be IK on the figures. Moving a parameter just moves the foot and nothing else. Winxp, athlon 2200 and a gig of ram Ed

It appears that the pz3 importer has a big bracket problem. Biggest headache for me is the fonts on the buttons, very hard to read. Yes, my display is set to DS specs. On a bright side the tutoral works.

I had the same Bracket error when opening pp2's.....

I hate to say this, especially as a hugh fan of DAZ, but there are far too many file and directory parsing errors for me to continue with this Alpha release. It seems like they have hard-coded some 'paths' into their importer and that is what is fouling up some but not all of the imports that I try to do. A lot of my stuff I have in custom dirs and this may be the problem. Me thinks, that when DAZ corrects what to me appears to be a hugh file/dir parsing error, they may well correct a slew of other problematic bugs. But then again I may be wrong, so if I am, somebody please let me know. :) BabaLouie

not sure if this happens to everyone, but gonna post it just in case, for mike2 anyway, arms can't be moved side to side, bend works fine but side to side does nothing

Here is part of a post I made under the 'lost here' thread, it may explain some of the loading problems I mentioned in item 18 of this thread ... /* Here is what I have found concerning .cr2 and .pz? files. If I have a .obj or texture file referenced with the path as such :runtime:geometries: ........ I am prompted to search for the needed file. If I put in the actual path of the object in the .cr2 file such as below ... h:poser4runtimegeometries ...... then the file is automatically found and loaded without any intervention from me. */ HTH BabaLouie

Well, I am experiencing the identical types of errors the rest of you are.....importing, bracket, problems finding files, etc. I loaded D/S on an older computer that does not have Poser, so I had to simulate a Poser 5 runtime and throw a few things in it to experiment. It's either reading the scene files and not finding the stuff where the code indicates it's suppose to be, or it's been programmed to look for Poser 4 and it's file structure. BabaLouie's post would suggest that. If that's the case, that needs to go! The only .pz3 I could load without an issue was an IW4 dino....the Stegosaurus. Yay Pamola! Another .pz3 designed for Poser 4, loaded, but some of the textures were messed up. Had no luck with .cr2's at all. That's where I got the missing bracket error and ultimately an illegal action crash. One nice thing is that D/S doesn't freak out when it can't find an .obj file and lock up on you. It lets you browse for it and if you can't find something, simply forgets about it. I too hate those god awful buttons. The font is too dark and does not contrast well with the redish purple button color. I suppose another good thing is that it loads and renders the egyptian picture on a PIII runing Windows 98 with 256 mb of ram and a Raedon card with 64 mb of ram. Pretty old hardware. It takes a long time to "process and optimize" the images though and about 10 minutes to render the thing. Given this is an alpha, I do not plan to install on my poser machine :) I would say that the program has real potential. Some of these issues (like the buttons) are cosmetic. Others are pretty serious (like the missing bracket thing and the errant application of textures). But I'm impressed that it even runs on that old computer....Poser won't! :) Finally, the log file does a good job of recording everything done during a session.....a good way to report any problems....just send them the log file!

To avoid the errors I started importing items from my libraries and not using Pz3 scene files. I found it helped alot. I saved my elements in Poser and impoted them individially as .cr2, pp2, etc

/* If that's the case, that needs to go! */ Sandoppe .. I agree completely, I would really hate to get locked in to set folders and directories. For me Poser had a limiting folder structure and I really did not care for it. I hope DAZ adds some flexibility in this area. I will keep a model and all parts related to it in its own folder. Makes it a lot easier when exporting to another app, however, DS appears to not handle this type of 'custom grouping' very well. BabaLouie