Fri, Nov 22, 3:14 PM CST

Renderosity Forums / Poser - OFFICIAL

All Forums

Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)

Poser Gallery - Poser Freestuff

Subject: mapping V3 to V3 prob

artbyphil opened this issue on Dec 24, 2002 · 6 posts
Back to Forum Print
artbyphil ( ) posted Tue, 24 December 2002 at 7:35 AM · edited Fri, 22 November 2024 at 10:22 AM

Hi there Just had a go at the re-mapping of vic 3 to vic 2 I followed the instructions I found here. I did the obj file with no problems and then I did the cr2 editing in Notepad. I called the file Victoria 3-2uv.cr2 as in the instructions and all seems correct. However poser isnt seeing it and when I look in the folder its still being seen as a text document and not a cr2. what am I doing wrong here, do I have to save it differently? Im new to doing this type of thing and probably missing something obvious! cheers

 

VI_Knight ( ) posted Tue, 24 December 2002 at 7:43 AM

Check and make sure that you have the View Extensions property set in your folder options in your windows explorer. It may be appending the .txt to the end of the filename after you edited and renamed it. If that is the case then rename again and take the .txt from the end.

artbyphil ( ) posted Tue, 24 December 2002 at 7:48 AM

VI Knight that was the problem, didnt think of looking there. windows being too clever for its own good again! cheers

 

VI_Knight ( ) posted Tue, 24 December 2002 at 7:56 AM

Glad you got it fixed. Happy mapping.

rain ( ) posted Tue, 24 December 2002 at 1:12 PM

Where can I find the instructions, please?

PabloS ( ) posted Tue, 24 December 2002 at 3:21 PM

.

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.