On 22/03/2018 20:55, Alain wrote:
> Le 18-03-22 à 04:33, Stephen a écrit :
>> On 20/03/2018 23:42, Alain wrote:
>>>> I ran into the same problem myself, last week.
>>>> It was from using machine generated code that I was rendering 
>>>> manually from a different directory than where it was created.
>>>>
>>>
>>> When using those machine generated scenes, check if it contains any 
>>> hard coded paths and other full files paths.
>>> Those are totally non-portable, even within a single machine.
>>
>> For once I cannot agree with you, Alain.
>> If I am using image_maps or df3s and don't use the full file paths. I 
>> would gave to copy the images or df3s into the current directory. In 
>> the past when I did not use the full file paths. I ended up with 
>> multiple copies of the same file in scores of locations. Considering 
>> the number of image maps Poser can use. It is a waste of space and be 
>> confusing.
>>
> 
> My approach to that is to have a central repository that is refered to 
> from the master ini file.
> You already have a central repository for the inc files, just create one 
> for the image maps, one for the machine generated meshes,...
> Then, you have a single place to look for.

I would hazard a guess that you do not frequently use modellers to 
generate your scenes. If you do, like me, you have to work with what 
they give you. I look forward to when the Pov team can start working on 
the replacement for Moray, as promised all those years ago. Then we 
might get a program that is both functional and sophisticated.
I am not whinging btw. Just giving my opinion.

-- 

Regards
     Stephen

Post a reply to this message