Ok....thanks. I updated the figures at the time of the last release. I don't use the walk designer at all so I could care less about that. In fact, I may have removed them entirely. Just do straight image rendering (no walking or other animation....no use for it). Frankly I can't remember if I've moved the P5 characters or not.....I may have them in subfolders by now under the path you provide. But if the path stated in your message is the correct one, it wouldn't be hard to move them back.....assuming I decide to update at all.

I uninstalled Poser5 and reinstalled it fresh. After reading about the possibility of downloading a corrupt sr3 updater file(which was giving me CRC failed error),I downloaded, after 3 tries, 20MB a piece, a GOOD updater file. I then attempted to download the sr3 figure updater(36.5MB) and after 5 downloads I have given up. All five tries still give me the CRC failed error when it hits the, Don Nude Hires. All five attempts were corrupt ? Sheeeeesh ! Guess I will try again at another time..........................

uli_k, my brain is running a tad slow today, so excuse me for asking a final clarification regardng whether or not to install the SR3 Figures Updater (per your message post #35): If I've already installed the SR1 Figures Updater (actually, I have installed all of the past SRs as they were released), then I do not need to install the SR3 Figures Updater, just install the SR3 Application Updater and I won't be missing a thing, correct?

I hope that th program now is faster and on a par with P4, I could still see a difference between the two programs with the last service release.

Badco, Try using GetRight for downloading. I haven't downloaded the patch yet myself, but in previous SRs CL's servers were configured to allow this. The options to continue after interruptions and lost connections make it pretty much a necessity for downloading files of this size (not to mention the automatic hangup, which lets you do the business overnight with a clear conscience). And of course it means less bandwidth use for the rest of us, if there are less people restarting corrupted downloads. Bill

I am not restarting a download. I can download the whole patch but once it is downloaded, I then find that it is corrupt, so I have to delete that one and download another one. The 3rd sr3 updater that I downloaded worked. The sr3 figure updater(after 5 tries) is still corrupt.

TerryMitchell, this is correct. Install SR3 App after everything else, and you'll be fine.

Are people reporting lockups experiencing actual lockups or is the program just so busy that it won't permit its own screen updates. I mentioned this back during the SR2 beta. Essentially tasks like rendering, hair draping, cloth draping, etc. are locking out the housekeeping tasks like screen updates. And the program still is and always will be a memory pig. That means it's very easy to get into a condition where your machine is swapping heavily. At that point your 2.2ghz machine is not much better than my 450Mhz machine because the throughput is governed by the disk controllers. The trick is to relearn some of the tricks we all knew when running P3 and P4 an smaller machines. Build a scene in layers and paste the layers to the background. This is even easy to do with animations now that a movie can be used for background in P5. But don't be too hasty to call the program "locked up" when it's using 100% CPU resources and has 100Mb or more free RAM. It's probably just working (as mine is right now draping hair in the background). So far the hair collision problem looks fixed. At least the first two drapes I did came out fine, without the "hairdo from hell" syndrome. Now I'm working on the last part of her hair and we'll see how that goes as it's draped over the shoulders and there is another figure involved. Should be interesting.... Even if the program says "not responding" in the Task Manager, that's not necessarily a lockup. Best way to test is put the program's window up front and wait about an hour. If it starts to update, then the program is actually still processing in there!

why does the P5 hair always have the high,balding forehead frontal, receding hair line look ????

P5 hair and high hairlines: there are two major reasons for this. (1) The "skullcaps" that many people use as the basis for their hair-growths often stop high up on the forehead. (2) Also, when you start hair lower down on the forehead, it's hard to get it to go back and over (or at least, it was pre-SR3; gotta do some new experimenting now). One can get around this by creating "bangs" or carefully arranging strands of hair in the front, but that takes a lot more work.

Doldridg, I know what a lockup is, there is no reason why in Poser 4 a rendering of a scene may take 7 minutes and in Poser 5 Firefly after 25 minutes its still adding objects. Not only that but if the program was still responding you should be able to cancel.

I know I'm probably talking to myself here but before the service pak and after I've had the experience were sometimes by rendering first with the Poser 4 renderer and then going to Firefly right after that render it will avoid the lock up, this workaround sometimes will work, sometimes won't.

""43. Re: Poser 5 Service Release 3 is now available by Jackson on 5/9/03 10:04 Word of caution: be careful using CorrectReference. It's nice but it can make mistakes and lose things that weren't lost to begin with." I must admit I haven't tried the program. There is of course one ideal way of ensuring that your poser-files structure doesn't need correcting, or cause long delays searching for files that aren't where specified:- don't corrupt the structure." First point, that is why I don't use Correct Reference, after awhile it starts changing references to incorrect ones. I have tried the program and it still does this even after the last upgrade. Second point, the worst problem I have with textures not found are those that are newly and virginly loaded. P 5 can't find those with both hands and a flashlight. I haven't corrupted a damn thing. ZIp paths are fine and DAZ unloaded their exe's correctly. Fine, I have too much in my folders and too many runtimes associated with P5, just give me an option to cancel on textures/objects unfound. It happens randomly so I can not tell if this is a genuine textures not found or simply an insufficient memory situation. I'm glad the Walk Designer was fixed, as I never use it, I dont need to both with this Service Release. Emily

That would be I dont need to "bother" with this Service Release. Emily

I must admit I haven't checked to be sure that DAZ installs have the correct references in - I've assumed that they are old masters at this and that they generally "get it right". I still belive that and until I start to doubt them can't be bothered to check. If you've got multiple runtimes (what Poser 5 user hasn't?) with too many file sin (what Poser X user hasn't? ) then have you considered re-ordering the libraries? I'm not sure to what extent - if any - this is possible, but having Pose5 check folders in the order of "most often used" to "least often used" might help, a bit. at CorrectReferance. I'm glad I've never tried it now! The problem with smart technology is that it's never quite as smart as a human being...

Well, I've tried to set it up so I only use one or max two libraries, but sometimes things go wrong and something I thought should have been in one runtime wasn't. Even given that, I've used everything out of one runtime, just one, and it stalled three times in a row and cold boots wouldn't help and defraging never has helped. I'm setting up a separate P 5 for a project on a portable and seeing if that will get me there-- only prob is I only have 512ram on the portable. Emily

I've only had a couple of problems with referencing and they were easy enough fixed by hand. I seem to have the problem with .bum files or any texture with the name .bump or .bum in it. If you don't find one of these you can expect Poser to lock up on ya. I've actually been able to cancel out of most others. The two problems I had with referencing were with those textures that were previously .bum files, were renamed to .jpg files later, but the code still contained the reference to .bum. That locked up as well and would not permit a cancel Once I changed the code manually, it loaded faster than grease lightning. There must be something in the Poser code that directs it to let no .bum file escape alive, because it goes after them as if it's very life depended on it!! :) A little less ferociousness where this is concerned would be in order. As Emily notes, when I hit cancel, just......stop looking! I have multiple runtimes as well, each containing it's own libraries, textures, etc. Has anyone tried to put all their runtime textures in the one native Poser runtime to see if that helps speed things up???

It should definately be faster - most Vicky3 issues (with Poser5) seem to be cured by installing her directly in the Poser5 Runtim so that people don't get huge delays. I'm not aware of the algorythm being used at present (it isn't the original unpublished algorythm) for searching the runtim folders, but let's imagine the following: A charatcer in a PZ3 file (in "My Documents" folder) that has several materials that point to a "relative" texture address of "Runtime:Textures:My New Textures:V3HeadFishTex" Let's assume just 3 runtimes... Poser 5 Poser 4 Victoria3 ONE way for the program to search for the texture would be to check the folowing locations in order: My Documents Poser 5:Runtime:Textures:My New Textures:V3HeadFishTex Poser 4:Runtime:Textures:My New Textures:V3HeadFishTex Victoria3:Runtime:Textures:My New Textures:V3HeadFishTex Possibly searching all other subfolders of the various "Textures" folders in each Runtime too (either as it does that Runtime, or at the end if all the "exact" relative addresses fail). That's a fair bit of searching. Withj all programming there's a balance between speed and ease-of-use. This function has been "adjusted" towards what people have requested once so far - but a number f issues are outstanding. For example, if you press cancel that's probably interpreted as "Cancel" for that search. The next group that needs that material is likely to search for it again... unless code is in place to remember "cancelled" texture searches. ...and so on and so forth. But, fairly blatantly, if you HAVE only 1 runtime then it'll be faster because in the case of missing textures there'll be less work to do. If you have 7 Runtimes but think you're only using 2 at any given time then I suggest that while you INTEND to only use 2, any missing textures or geometry will likely cause all 7 Runtimes to be searched. Cheers, Cliff PS SR3 pulled a nasty on me last night - about 30 frames into a 141 frame animation it started rendering blank, black bitmaps instead of the glorious groundbreaking animation I thought it'd finished. It'd be rather nice if, after rendering an animation, Poser didn't auto-close the last frame - to give an indication of what it had rendered.

I learned about V3 a long time ago and put her right back into the native runtime.....actually an "injected" item only works right if it's in the original runtime (i.e., RDNA's Microcosm) I have 3 runtimes right now. The only reason I split them up was to reduce the number of characters to try and search through, but putting the textures all in one might help. Who knows! Has anyone tried using the "Download" runtime that gets set up by Poser for anything or is that strictly reserved for their silly "Content Paradise-Lost"?

I use Download runtime for most new stuff-- except V3 clothing and fairy plus cute stuff those both have their own runtimes. I keep only the injectables in the Poser 5 runtime because the bigger it got the slower it got until it didn't want to run at all. Then there's my old Poser 4PP runtime. I notice that Poser 5 seems to load only one runtime and I'm not sure how to set this-- sometimes it's Downloads, sometimes 5 sometimes Poser 4. I think it has to do with what is loaded last in the last scene before quitting. I do know that when Downloads or Poser 4 have not been the primary runtime loaded at Poser's boot, they take forever to load-- this makes me think, they are not on the list to be searched at rendering. My fastest render on Poser 5 was using only the Fairy runtime. It is also the smallest lightest runtimewith the lightest textures as well. It rendered in under a minute-- 1500 by 1500 at 72 dpi. I never render anything at any higher dpi. 2000 by 2000 is the highest I've rendered in Poser 5. I rendered up to 4000 in 4PP. Often I will drop a render in 5 to 1200 if I think Ive jammed too much stuff in. For awhile, when I had my Poser5 runtime the lightest, I could pose without the boxes obscuring my view, I can never do that now. Its very wearying trying to work under these conditions. Emily

Correct Reference WORKS. The only two things you have to be careful of are: generic texture names such as black.jpg (CR will use the first one it finds). But this is very uncommon and will not result in Poser not finding the texture. It just finds the wrong one. But as I said this is not very common. .bum files. If the vendor did not include the .bums and you are using Poser 4, then you should convert the .jpg to .bum before running CR. If you are using ProPack or Poser 5 you can use the .jpg and if the .jpg exists CR will change the reference from .bum to .jpg for you just fine. If the .jpg does not exist or has another name, CR will tell you it can't find the file and you can locate it right from CR and fix it. If you have multiple runtimes, just point CR to the correct Textures directory before running it.

SimonWM That's just my point. The program is not handling priorities right and it tends to lock out the mouse and screen updates (basically the whole UI thing) when those should be at the TOP of the program's internal priorities and background things like rendering and draping should be on the bottom of it. The priorities have been assigned upside down. And there's no cure for it short of going into the source code, setting them properly and recompiling it. You guys at CL hearing this?

'I must admit I haven't tried the program. There is of course one ideal way of ensuring that your poser-files structure doesn't need correcting, or cause long delays searching for files that aren't where specified:- don't corrupt the structure.' then please refrain from commenting on a program until you do use it, since as of right now, you are not qualified to comment on it at all. I've used CR a lot with no problems at all.

"74. Re: Poser 5 Service Release 3 is now available by Kaibach on 5/11/03 03:06 then please refrain from commenting on a program until you do use it, since as of right now, you are not qualified to comment on it at all." If you read my post/s you may well find that I've been commenting on corrupting the file structure of Poser content (something people seem to do a lot of) and ways to avoid it, rather than comment on the usage of CorrectReference. The quote (that you have repeated out of context) was in direct response to a challenge to my suggesting it might be valuable for this purpose on the basis that some have difficulties with it. I do not see how the quote you've posted in any way even comments on the program, beyond saying that I can neither vouch for its wonderfulness nor list specific problems. I apologise for trying to help people find solutions to their problems via a program much touted as being useful without having examined the source code minutely, and further for trying to make it clear that I cannot offer a personal recommendation. Cliff Bowman

Well I have used Correct Reference and, as I said earlier, it IS nice but it does make mistakes. And I didn't "corrupt" my structure, Correct Reference did. It misdirected pointers to at least two items that were correct and working. I can't remember which items they were and I'm not about to run it again to find out, as it took a long time to fix them. I do remember one being from Awful Soul, though. But the program is nice when it works. It's just the user should have a fair knowledge of files and directory structures so they can fix it when it doesn't.

What I would really like is a program like Correct Reference, except it doesn't change anything automatically. It just gives you a list of stuff that is misdirected and gives you the option to change them. I would also like the option of just stripping out the path name and having only the filename, so that I can move stuff around at will without worrying about confusing Poser (and also don't have to worry about the path size limit when sharing with Mac users). I personally haven't had problems with Poser taking forever to find textures, but just finding the wrong ones. Likewise, I'd love a program that would find multiple files with the same name and tell me about it, maybe even let me change the name and fix the references from there, instead of having to do it round-about and by hand. Just my two cents.

FyreSpiryt: All good ideas, and practical too. The only problem being that it takes time to actually write such software (I'd like to add support for .BUM files as I still use Poser 4 as well as 5)... Have you tried contacting the author of CorrectReference? Because I know when I actually find time to write utilities I want my program to be really useful to me, if no-one else... so he/she might welcome ideas on improving the program. Cheers, Cliff Bowman

can we get a new forum for sr3? i'd like to see all the topics in one area so i don't have to scan for them. thanks!

Never really gotten around to it, Cliff. It just hasn't been a high priority to me.

Jackson, Which version are you using? If 1.0 then there was a small problem which occasionally bit. It was addressed in 1.1, but not everyone found the update - I didn't until I reported the problem, and Howard pointed out I was running an old version.