2 threads found!
Thread | Author | Replies | Views | Last Reply |
---|---|---|---|---|
hpdrag | 14 | 264 | ||
hpdrag | 1 | 124 |
32 comments found!
I didn't have this problem, but i would guess, Poser is searching your harddisk for the needed texture-files. Maybe there were some registry-entries that helped Poser to do this faster before you have reformatted your harddisk.
Thread: My first P6 weirdness - PLZ Help?!? Clothing going nuts once figure loads!!! | Forum: Poser - OFFICIAL
I have similar problems with DAZ-Tunic and pants for V3; worked fine, when loaded from library and conformed, but is distorted, when i open a saved file or the dressed cr2. P6 even crashs then. I still don't have any idea, what the reason could be, it looks like some points from the mesh would be transformed to infinity.
Thread: Poser - mysteries and conspiracies | Forum: Poser - OFFICIAL
Thread: Poser - mysteries and conspiracies | Forum: Poser - OFFICIAL
I have critized P6 rather hardly in former posts, but meanwhile i like it more and more, even if the bugs are still there. But i have rather complicated scenes, a lot of figures, background stuff, lights, and i think that people who are doing more portrait- and single figure pictures will rarely run into the memory bug. Furthermore it seems to me, that P6 works much better with scenes build up from the scratch in P6, but with scenes imported from P5. Another point: to work with P5 and P6 without too much frustration you should carefully read the manual-chapter or tutorials about the render-settings. Things like the 'minimum shader rate', 'pixel-samples' and so on have an enourmous effects on quality, speed an stability of the firefly-renderer. And there is a third thing: many characters like V3 use rather dirty tricks to 'abuse' the poser-data-structure in a way, that most likely wasn't planned from the developpers (or maybe planned, but then stopped, because they recognized that alle those inner morph-chains were too buggy). It must be a hell for the programmers to look for bugs in structures, that they would like to throw to the garbage, only to keep the very popular products from a competitor alive ;-)
Thread: BVHair and Poser 6 - Crash!!!!! | Forum: Poser - OFFICIAL
Meanwhile I have got the feeling, that P6 works much more stable with scenes build up from the start in P6 than with old P5-files. It is more a feeling, but maybe there are some incompabilities in the file-version.
Thread: Poser 6 compatibility problems | Forum: Poser - OFFICIAL
This is no bug, sometimes it is not a waste of time to read the manual ;-) Just go to the preferences menu, look there for a check box 'use external binary morph targets' and uncheck this box. Then the morph-data will be included in the pz3-file like in P5 and you will have there, if you open the file.
Thread: Poser 6 Poll - Glad I Bought It? -or- Wish I'd Waited? ... Please Respond | Forum: Poser - OFFICIAL
As my answer, here is the beta-test-report i sent to CL; not that i'am an official beta-tester, but i feel like being one, whenever i get a .0 version of Poser :-( ********* I'm a Poser-user since Poser 1, so you can see that i'm as well a fan of this software as i am a rather experienced user of it. I was very disappointed from the first release of P5 like almost each other of us paying beta-testers, but i was naive enough to hope, that you have learnt your P5-lesson and that you wouldn't repeat the mistakes with it in P6. Well, i was a fool - it is almost the same piece of quite useless software as the .0 version of P5. Oh yes, i like the new things, really love that you finally have pointlights, i like the IBL-lights, the wacros, the improvements of the Dyn-hair, Open-GL support and other new things. BUT...again you haven't changed this historical Mac-based core-code at all. All the annoying P5-bugs are still there, as well as some new, really deadly bugs. Your memory-management is still nothing but a crap, and i wonder if your beta-testers did not find it, or if you are not able to correct it. Bad enough, that in times when pcs have 2Gigs ram and swapspace of several Gigs, a software reports me 'you are low in memory' when working with a file of about 100meg. But that this software suggests me then to save the file, and if i follow this friendly hint, it just writes an empty file, destroying all the work done before, this is not a good joke at all. How can such a bug be in a final version? And please don't tell me anything about 'it is your configuration, it happens only on your pc'! First, me pc is a very well-configured high-end machine with uptodate-drivers, 2 Gig Ram, 50 Gig swapspace running with XPpro. I can work with P5 meanwhile quite well with this machine, and all the bugs i mention here, happened with poser-scenes, that were working fine in P5. Second, one look into the numerous forums shows me, that i'm not alone at all. The only ones who didn't run in this bug are obviously your beta-testers and developers; maybe they 'tested' everything with a scene with one P4-figure, 3 lights and nothing else? Hmm, maybe in such a scene you will never run into a memory bug. But hey - users sometimes do a little bit more with poser! I have heard, that there are people who are using this Vicky 3, sometimes even with clothes, with hairs and with more figures and some background. Oh, and they also are using big textures, not only 512512 images! Is it possible, that you never had heard of this? Or that you say, people who are trying to use figures from our competitor Daz like V3 shall suffer as worse as possible? Let me give you a short list of things you should correct with your sp1 - at least i'm a beta -tester who pays good money for this honour to make your software run. 1. the memory bug - no need to say much, you're certainly drowning meanwhile in bug-reports to this topic. 2. the animation pallette: it is incredible slow. Try to select the keyframes from frame #1 and copy it to frame #120- you have to wait some minutes until Poser has completed this easy task! And this with a not very complicated scene - one V3, 3 clothed p4 male, some background stuff and ten lights. All characters collapsed on the left, so that there are about 12050 rectangular cells to draw into the table. And the same work done with the same scene in P5 doesn't need more time than i need to light my cigarette! In P6 it needs longer than smoking the cigarette to end! 3. an old bug still untouched since P5.0, not dangerous, but annoying enough to mention it: Whenever you leave the material-window, the library is resetted to the Pose-section. It would only cost your programmers two lines: oldLibrary=currentLibrary ....doMaterialRoomStuff... currentLibrary=oldLibrary Easy to do,right? But it spares your paying customers thousands of unnecessary mouse-clicks. 4. Also a very annoying bug imported from P5: WHenever you load a file, Poser adds keyframes for each spotlight in the last touched frame of your animation. And to make this really funny: all spotlights are resetted in this new keyframe to AngleEnd=70, DistantEnd=0.0. In P5 it was annoying: always after loading i have to remember this bug, go to the animation-window and remove those unwanted keyframes of the lights before i try to render again. In P6 in combination with the slow animation-window this bug is a true torture, because it needs some minutes until Poser has deleted those wrong keyframes! 5. An old bug, that is part of your software since P4: take any human figure like P4 female for example. Add any other character and parent it to a forearm of this figure. Then enable IK! Maybe you know what is happening then, if not - try it, and then remove this bug finally! 6. Collision Detection: well, it looks nice, if you have this in your feature-list. And it works quite well, if you collide a primitive cube with a primitive sphere. But again: Poser users usually are more interested in collision detection between two human characters! So if the system locks for one minute if you have ColDet enabled for a V3 head and only try to bend this head, the collision detection is absolutely useless for the users of your software! And one last hint, once you have corrected the most deadly bugs: the wacros in the material room are a very good idea. Why not giving us some wacros for the clothes room? It would be great to have some prefix settings for silk, wool, cotten, leather, steel, maybe even wet cloth or similar more sophisticated stuff. Same for the hair room: some meaningful prefix-settings would make it much easier for your customers to become handy with the controls. You have a really wonderful base for a great software, so use it finally and don't spoil it with releases of bug-diseased beta-versions that enrage even your most honest fans!
Thread: p6 animation window is SLOOOOOOW! | Forum: Poser - OFFICIAL
We are using QT from Trolltech, this is a C++-library and ressource-kit that works quite well in cooperation with the VisualStudio. You see, I also use VisualStudio - it is not completely useless, but if you deal with such filesizes and memory-demands like in 3d-programming, you may not use the VS-library classes, but have to write your own. And yes, it is our big advantage that there are no guys from a marketing or financial division who force us at pistol point, to give them something that they can sell tomorrow :-)) Sometimes such guys are necessary that we programmers find an end, but more often they are the reason that users become unpaid beta-testers.
Thread: p6 animation window is SLOOOOOOW! | Forum: Poser - OFFICIAL
Thank you, jjsemp - now i know, that i'm not alone, and that there is no need to throw my pc away :-). @thefixer: the poser-problem is based on the fact, that it is a 'grown' software, originally developped at times where p4-figures and textures were huge things and when real raytracing was a thing for SGI-workstations, not even dreamable for pcs. For P5, when people cried out for raytracer, collision-detection and similar stuff, CL sticked on some bought software like firefly and the clothes- and hair-engine to this obviously almost unchanged P4-kernel. This was a very bad choice, because certainly all of those external engines need to be fed in their own data-formats - a constant waste of memory, speed and an endless source of possible bugs. Just look at the collision-detection of Poser - unfortunatelly in P6 as uselessly slow as in P5. Have the developers ever tried to enable collision detection for a V3-head and then make any posing? One minute later, something moves on the screen - if you are lucky! And it is really not a big deal to write a software that can do this in real time on a high-end-pc like mine. But the data have to be structured to be able to do so, certainly it is not possible to make it faster with P4-data-structure From my own experience i know, that it is not impossible at all to deal with huge files, if you write a software and organize the memory with the knowledge, that V3-sized figures are normal and textures can easily be 4000*4000 files. At least if you are not so lazy to use the comfortable little memory-management toys from the MS-Visualstudio, who often still live in the good old 64k world, where 1Gig is somewhere far beyond infinity ;-)
Thread: p6 animation window is SLOOOOOOW! | Forum: Poser - OFFICIAL
@alvon: not the animation is the problem, but the incredible slowness of the animation window, that needs several minutes to copy or move keyframes! @operaguy: i will not make promises, because we work on this software not fulltime, but part-time only. As i wanted to see P6 before investing more time in a (maybe) unnecessary program, the development stopped for some time, but now i know, i can go on. I think, beta-testing can begin in summer; i will inform people here, when it is time.
Thread: p6 animation window is SLOOOOOOW! | Forum: Poser - OFFICIAL
I think they can fix the worst follow-ups of this bug, like writing zero-sized or otherwise unreadable files. But i doubt, that Poser6 will ever allow to render complex scenes in a good quality. Somehow the Poser-programmers seem to be unable to deal with complex memory-stuff. I don't want to blame anyone with this, but my experiences with Poser tell me, that they don't want or don't can fix memory-problems. So i would be content, if they at least succeed that the program doesn't crash, when running low in memory, but allows the user to save everything for the next try. I know that it is not easy to program, but in the software i write at the moment, it is no problem to render ten V3s, and the OpenGL preview is as fast as i can move my mouse. So it IS possible, but certainly not with an 10year old kernel that is filled with countless bugfixes, add-ons and python-driven (and therefore interpreted!) scripts.
Thread: p6 animation window is SLOOOOOOW! | Forum: Poser - OFFICIAL
oh yes, this is a file that i made Poser 5 - not a problem here. The speed is absolutely okay in the animation window of Poser 5. to 2.To the 'memory-fix': here i'm not so hopefully than the most people here. Since P4 Poser has this memory problems; it seems to be an integral part of the Poser-engine; i had hoped that with P6 and the giving-up of the support of the older OS this kernel would be made new from the scratch, but it is more or less the same as it was before. So i only hope that they are able to improve it a little bit as they did with P5. to 3. yes, this was first i tried - no change. Also my first verdict, it could be the new morph-organisation was wrong; with or without this checked in the preference-window didn't make any difference. to 4. no - everything is very slow in the animation pallet, even a selection is a pain. It also doesn't make any difference, if i have OpenGL-mode enabled or not. My guess is, that with each mouse-action in this animation pallet, Poser makes one or even several redraw(s) in the pose-window itself. I'd be curious, if other people have the same problem with more or less complex scenes.
Thread: Memory Bug Advice From CL (not that much help) | Forum: Poser - OFFICIAL
It seems that the 'Keep textures Loaded'-feature dramatically increases the memory problem. I have rendered the same scene immediately after the Poser start; one time with and one time without this feature. Without it everything worked fine, with it Poser had 'forgotten' a lot of objects when i changed back to the Preview window and i had to quit Poser before i could continue to work. Has anyone made the same experience?
Thread: No guarantees fo compatibility between Poser 6 and DAZ products?!? | Forum: Poser - OFFICIAL
Okay, here my specs: Maxdata Processor: GenuineIntel 3,1 Ghz ASUS-Bios 2 Gig Ram 60 Gig diskspace free on swapdisk Video: NVIDIA GeForce4 MX 440, 64 mb RAM i have to add that i'm a power user, that means i have a lot of rather huge scenes at the limits that poser5 could render. i loaded one of those scenes in p6 (2 V3, 2 M3LE, all clothed, some easy background stuff, 3 lights). This should become the first serious test of p6. Loading and OpenGL-Preview worked fine. But the render locked up while 'loading textures', the render window became gray and nothing happened for a long time. I reduced the scene, checked all texture stuff and so on, and so some hours of work later i found, that the only problem were V3Tunic and pant - without those everything worked fine. I made another test: one V3, one Tunic, one pant; conformed the clothes, and it rendered without any problem. Then i saved this V3 with clothes to the library as cr2. When i try to import this cr2, i always run in one of two problems (randomly): 1. poser locks and doesn't show anything; it's ctrl+alt+del-time or 2. poser opens the file, but the clothes are shifted along the x-Axes away from the V3 and seem to have one point somewhere at x->infinity. Poser locks as soon as if i try to move the camera or select anything. ctrl+alt+del-time again Did you make a new scene and rendered this, or did you import a v3 that is clothed with pants/tunic? I don't think that it is anything on my system, because meanwhile i have done some serious tests with p6. Beside of the wellknown memory bug :-(((, i don't have problems with it. I really can say, that once this bug is corrected, i will love Poser6 - compared with the first P5-version it is like heaven :-).
Thread: No guarantees fo compatibility between Poser 6 and DAZ products?!? | Forum: Poser - OFFICIAL
@Deecey i agree, that they cannot update each of their products. As far as i found so far, it is not necessary, because most of them are running fine in P6. I only think at the 'standard products' like V3Tunic, pant and similar. Those clothes have a lot of value for DAZ, because they are not only selling the 'plain sets', but also numerous texture sets. So updating Tunic/pant would allow them to sell not one, but a dozen or more products to P6-users. BTW i wonder, that not more people are telling about such incompabitilities. Maybe it is not a general bug with V3pants and tunic, but a damaged file on my system? I would be interested, if this problem also happens to other people, and maybe if there are more problems with other products. Or are there easy workarounds, cr2-editing? I have the verdict, that this new 'center-of-mass'-part could be the source of the problem.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Thread: P6 Behaves Weirdly After Re-format (Take 2) | Forum: Poser - OFFICIAL