Mon, Nov 25, 2:27 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 25 12:38 pm)



Subject: wonder why poser takes so long to say i can't find that texture?


Tucan-Tiki ( ) posted Sun, 01 July 2012 at 9:58 AM · edited Mon, 25 November 2024 at 2:25 PM

sometimes I find I am missing a texture and poser then freezes up for like 10 minutes while it conducts a search then finally when my blood starts to boil that the program waisted 10 minutes of my time it finally gives me the damn pop up screen asking me to go find it, why can't they just design the program to quckly ask you if you want to look or skip it?

 

 

that would be too easy....


willyb53 ( ) posted Sun, 01 July 2012 at 10:04 AM

Try setting search depth to shallow, that will limit where it looks for the texture

Bill

People that know everything by definition can not learn anything


foxylady1 ( ) posted Sun, 01 July 2012 at 10:05 AM

Go to Edit/General Preferences

In the Library tab under File Search you will see three boxes.  Click the Shallow, then it will not search all the runtime/texture folders.


TomMusic ( ) posted Sun, 01 July 2012 at 10:06 AM

No one likes the delays when a texture is missing. Never had a lengthy 10 minute wait. For me it's about a minute or less wait for the window to open for starting a search. -TOM-


moriador ( ) posted Sun, 01 July 2012 at 10:59 AM

What I don't understand is why it has to search for textures that it found the week before with no problem. Maybe my Poser has Alzheimer's.


PoserPro 2014, PS CS5.5 Ext, Nikon D300. Win 8, i7-4770 @ 3.4 GHz, AMD Radeon 8570, 12 GB RAM.


LaurieA ( ) posted Sun, 01 July 2012 at 2:29 PM

Yeah, mine is set to deep and it takes about 30 seconds to say it can't find it.

Laurie



wimvdb ( ) posted Sun, 01 July 2012 at 2:51 PM

With deep it scans all the texture folders in all your runtimes. That might take a while when you have a large (set of) runtime(s).

Search first tries to be intelligent and queries first the current folder, the root textures and some other locations. Then it parses the pathname and tries various mutation. Then it starts the full search. If it locates a texture, it then adds that folder to the set of locations to search in before it does the full search - finding the other textures with the same incorrect reference in that folder.

Settting it to shallow eliminates the full search. Setting it to narrow does not do any seach at all.

 


Privacy Notice

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.