Hi I made a scene yesterday, saved it to come back to it today. Now P7 SR2.1 is looking for a file NO_MAP ! I can only find in the pz3 NO_MAP where it should be i.e. textureMap NO_MAP, bumpMap NO_MAP, reflectionMap NO_MAP, transparencyMap NO_MAP I tried making a small jpg name NO_MAP.jpg but that didn't help - short of rebuilding the scene anyone have any helpful suggestions? What's caused this? PS. Just tried loading it with P6 SR3 and it loads with no complaints (weird)

Every post like this reinforces my decision to NEVER move on to P7.  Wish I could help you but my only advice would be "go back to P6"  =)  Good luck.

This rings a bell. Try putting NO_MAP in quotes (a 30-second job using a text editor).

i.e. NO_MAP -> "NO_MAP"

Mike

(And I'm sorry if I'm wrong)

hi, i am using P6 but has been encountering "no map" msg b4 rendering. however, my version did not crashed. am still wondering why the "no map" msg

The only think I can think of is maybe one of your textures has an image map node attached to it but no image actually assigned to it.
Just a wild guess though, have not experienced that problem first hand..

Had this problem a few times myself, and 7 has always crashed after the error hit.  I think the only way to avoid this problem might be to strip models of their textures before saving them, (especially those created in older Poser versions) then reapply them on loading. It's a pain in the neck, but it works.
So far.

P7 SR2.1 may have been a bug fix for SR 2.0, but all of these SRs have caused problems for some users. a typical line in a node declaration in P7 (file "NO_MAP") should cause poser to do nothing. if one of said occurrences in yer pz3 file had some syntax error preceding it, P6 would also search for file "NO_MAP". hence I'm guessing that there's nothing wrong with the PZ3 file, and a search for all occurrences of "NO_MAP" would yield no syntax errors in the vicinity.

Thanks guys, Still no luck with the solution except use P6 :( There are no file "NO_MAP" statements in the whole 250+ MB of the pz3 file - that's the first thing I checked - there are no missing textures, etc according to CRPro - Usually when Poser can't find a file and you click cancel and no to keep looking it'll load with the missing texture blank - this won't even load just closes to the desktop gracefully. Challenge of the day is to find the syntax error that may be is even a line above or below - or just a simple bug.

o.k., then - apparently SR2.1 differs considerably from what I'm using (SR 0.0), as in my typical pz3 files, in the material sections, any channel or node that can use a map (but doesn't) has got the line [file "NO_MAP"] in it. almost as if, were I to apply SR2.1, poser would then delete all the [file "NO_MAP"] lines on resave. maybe they decided (in SR2.1) that having no line in that place in the file would save space over having hundreds of [file "NO_MAP"] lines.

Sorry Miss Nancy - my misleading statement There are no file "NO_MAP" statements in the whole 250+ MB of the pz3 should have been There are NOW no . . . as I removed them all.

o.k., thx fr the clarification. something in P7SR2.1 must be mis-interpreting the file. I'd expect such misteaks to disappear on cold restart, after clearing out all the RAM, but I reckon that's not happening in yer case.

You may a kick out of this - I rendered ny file in P6 so I could then mess about with it - saved it in P6 everything fine. Cold reboot - loaded the file into P7 -- Poser opens the open file dialog box file NO_MAP click on dialog box cancel then clicked yes to continue looking for file - file loads no more dialog boxes. Close file re-open follow the same to dialog cancel Poser closes down gracefully. It must be SR2.1

I haven't dug to far into this problem, and my poser runtimes are across town. P7 2.1 Mac. Same issue No_Map errors. But had them with 2.0 also. In glancing at some other cr2's and mat pose files early this morning, I looked at the ones that worked out of a set I pruchased vs the ones that did not work and the ones where it was "" (a pair of quotes) instead of No_Map worked with out a hitch...don't take that as solid gold. But I would test that and see what happens. The ones that are really driving me crazy are some recent purchased items that have "NoMap"""....(thats a triple quote on the end). FYI again my runtimes are across town. But the 2.1 patch readme covers this issue or makes a statement claiming what is right and what is wrong.