I saw it today but didn't bookmark it. I wanted to do it now and can't find the thread. :( Please someone point me in the right direction.

here it is I was looking on the wrong site lol

Wow! What a fantastically useful thing! I've been wanting to get rid of that for ages. Thankyou!

Hey, I wonder if you can use a similar approach to remove other slow rooms you don't use. I could get rid of the face room and the setup room for example. I'll have to try that.

If you remove anything but the CP room it makes poser not work, LOL. The other rooms are tied into the prorgam to a point they can't be taken out. I did the CP removal and it really made a difference, I am back to using P5 again, LOL

if someone knew how to do that as well... :) i would like the p4 mode for quickie changes. fyi i removed content room cos i keep on clicking it accidentally and it takes forever to load and get back out of again. i know the poser stores, i don't need the content room to show them to me. ;) (the idea of it attracting industry pros into the poser "communities" is cool by me though.) i haven't noticed if it speeded up p5 starting or anything else besides that.

Under render options can't you switch to the P4 render'er that should gave you the old material box. But to me the Material and cloth rooms are the only new ones worth keeping, LOL

Yeah, material room and cloth room are the ones I like too. The hair room can be useful too, if you need grass for example ;-)

I did not really notice any change in performance from doing this, but I do like to streamline, yes. How is the performance benefit supposed to manifest? Less time for program startup? Better response time in the pose room, or switching between rooms? Or... a faster Firefly? (I wish....)

You're supposed to see faster response in the pose room. For some people it makes the difference between using full tracking and fast tracking. It seems to make the most difference for people with relatively low RAM - 512 Meg for example. I think I'm seeing slightly smoother posing on my 1 gig machine, but I'm not 100% sure. However, not going through that agonising wait when you accidently click the content room tab is a huge improvement. My P5 is on a machine that isn't connected to the internet and it gets upset every time I accidently click that thing.

The "adjustment" of Poser 5 to remove the Content Room, should speed up your load time (both initial and subsequent reloads within 1 OS session if you have SR2/3 installed with this pre-load feature). Presumably it's because it doesn't have to load that room, nor the IE system level DLLs (we all know CL loads everything up front). But's what 15 to 20 secs off the load time of this monolith - you'll notice it, but it won't be life changing ;-) It would follow that this should mean more memory available for the scene, but how to measure/quantify that? If you have one of the later Poser 5's, which came on a CD with one or more SR's already installed, likely this is the only benefit you'll see - you'll know this as you'll have a line containing this "PSDFile name="./runtime/ui/"1701_ContentStuff.psd" near the front of the file. However if you have one of the original Poser 5 versions patched to SR3 and you had dismal, nearly unusable parameter dials in Poser 5, then you should find that the parameter dials become much more responsive. Not as good as Poser 4, but back to a level of response that is at least usable - i.e. the same as everybody else has. OTOH, if you didn't have this crippling parameter dial problem, it's not clear to me that the "adjustment" will buy you anything in terms of performance improvement (beyond the load time). Why do/did some people have this parameter dial problem in the first place? Dunno, and I'm not about to uninstall/re-install Poser 5 to find out now that it kind of works after all this time. But my hunch is that it occurs if you have Poser 5 cut off from the Internet via a personal firewall, and/or similar restrictions on IE. On Windoze the Poser 5 parameter dial window is a seperate task, and all Poser versions run with Poser at a high enough execution priority to hold off some otherwise important OS functions (e.g. screen update). So if IE's system dll's are thrashing on the firewall trying to get to the Internet, it's entirely possible that it's hampering the inter-task communciation between the parameter dials and the main Poser 5 task. (This theory is borne out some by the fact that the dials are reportedly very responsive on OSX, which would not treat the parameter dial window as a separate task - or have it's browser functions entwined with the guts of the OS.) This is all hypothesis admittedly, but would imply little opportunity for further perfomance improvement due to this "adjustment". Just trying to moderate peeps' expectations... It's a small change, but probably only worth doing if you couldn't bring yourself to use Poser 5 before due to the unresponsive dials. As always, YMMV.

So this means that deleting the CP room in Poser 5 OS X wouldn't make any difference in param dial response.

That's my suspicion, but I would be interested in the result. Only way to learn about Poser really is try-it-and-see ;-)