On Sat, 21 Oct 2006 05:02:48 EDT, "Olaf I." <ola### [at] ewetelnet> wrote:

>
>Parse Error: Cannot open include file Lego_0.pov.
>File: C:LegoPovFilesGeneral_Lego_Renderer.pov  Line: 4
>Parse Warning: Check that the file is in a directory specified with a +L
>switch or 'Library_Path=' .INI item. Standard include files are in the
>include directory or folder.
>Please read your documentation carefully.
>--------------------------------------------------------------------------------
>

>help me.
>I need a simple explain what I make wrong or what I must do to make it
>complete for work.

In the master Povray.ini file (Tools > Edit master Povray.ini) you need to add a
line for every directory that you want Pov-Ray to search for include files, or
any other type of file. E.g.;

Library_Path="C:\Graphics\POV-Ray for Windows v3.6\INCLUDE"
Library_Path="C:\WINDOWS\Fonts"
Library_Path=D:\Moray Data\Udo\1

I hope this is one step further forward.

Regards
	Stephen

Post a reply to this message

On Sat, 21 Oct 2006 10:13:35 +0100, Stephen <mcavoysATaolDOTcom@> wrote:

>Library_Path=D:\Moray Data\Udo\1

Opps should be 
Library_Path="D:\Moray Data\Udo\1"

Regards
	Stephen

Post a reply to this message

Dear Stephen,

Near ready.
In the moment I have this error-notes:

(...)
File: C:LegoPovFilesGeneral_Lego_Renderer.pov  Line: 4
Possible Parse Error: Could not find file 'Lego_0.pov'
File: C:LegoPovFilesGeneral_Lego_Renderer.pov  Line: 4
File Context (5 lines):
#include concat("Lego_", str(frame_number,0,0), ".pov")

background { color rgb <1,1,1>} //however you want to redefine it...

Parse Error: Cannot open include file Lego_0.pov.
File: C:LegoPovFilesGeneral_Lego_Renderer.pov  Line: 4
Parse Warning: Check that the file is in a directory specified with a +L
switch or 'Library_Path=' .INI item. Standard include files are in the
include directory or folder.
(...)

Only when I change this row
#include concat("Lego_", str(frame_number,0,0), ".pov")
in
#include concat("1.pov")
it works.
But them I get not the file General_Lego_Renderer.bmp not 1.bmp!

Can you help me by this last (I hope so) problem?

Regards,

Olaf

Post a reply to this message

On Sat, 21 Oct 2006 07:09:51 EDT, "Olaf I." <ola### [at] ewetelnet> wrote:

>
>Can you help me by this last (I hope so) problem?


I will try

To help you debug what is wrong use #debug - Help section - 3.2.2.7.1  Text
Message Streams
This will give you a text message and if you use 
#debug concat("Lego_", str(frame_number,0,0), ".pov")
It will show you what Pov is trying to parse. You can also direct it to a file
by inserting this line in an ini file that calls the Pov file
Debug_File=My_Debugfile.txt
Or use +GDMy_Debugfile.txt in the command line 

Another thing you can do is to explicitly define the files you want, for
instance;
concat("C:\Graphics\My_Directionary\Structure\Lego_", str(frame_number,0,0),
".pov")

I've found that often what I want is not what I write. But then for me every
line of code is a struggle :-( So I make use of debug a lot just to make sure.

BTW you will find that on this news group people will often point you in the
right direction rather than give a definitive solution. This is not badness but
helpfulness, as everyone learns better if they find the correct solution
themselves. And it is more satisfying. 


Regards
	Stephen

Post a reply to this message

> I will try
>
Sorry, but I understand nothing. :-((

I work now 3 days near around the clock on an solution for this sh...
(sorry)!

The best way I think is when I search an expert who write for me the files.

I thank all really very much who try to help me!!
It seems I must be to stupid to understand this programm.

Best wishes to all,

Olaf

Post a reply to this message

On Sat, 21 Oct 2006 11:21:09 EDT, "Olaf I." <ola### [at] ewetelnet> wrote:

>> I will try
>>
>Sorry, but I understand nothing. :-((
>
>I work now 3 days near around the clock on an solution for this sh...
>(sorry)!

>The best way I think is when I search an expert who write for me the files.
>
>I thank all really very much who try to help me!!
>It seems I must be to stupid to understand this programm.
>
>Best wishes to all,
>
>Olaf
>

Take a break Olaf. Driving yourself mad and falling out with your family is not
worth it. 
What you want to do is not really beginners work so don't be downhearted, too
much. I've been using Pov-Ray for about eight years in hobby mode and I have
never attempted to do what you are doing. I would spend a night laboriously
using "Find and Replace". At least it would get done that way :-) But as I said
I can't programme for toffee :-)
Unless it is vitally important to you, I suggest putting it on the back burner
and get to know Pov better then come back to it. Which remind me I only started
using Pov-Ray all those years ago so I could make an animation flying through a
fractal landscape. I found Pov and never got back into using Fractint again.  
And the people here are nice (mostly :-)

BTW there is an international group on the news server if that is of any use to
you.

Regards
	Stephen

Post a reply to this message

Olaf,
I know you've got real-life stress going on but don't give up now. Take a
break from it for a bit first as Stephen suggested, but I think you'll be
able to do this and when you do it'll be worth it.  Anyway sorry about the
confusion.  I didn't know how exactly your lego brick files were named so I
gave an example.  I should've made it clear that if your files look
something like "Lego_123.pov" (for example) the general approach will work.
 If your files don't start with "Lego_" you need to remove that and change
it to whatever it is.  In your case there is no word portion before it, so
you can just delete "Lego_",.

A quick mention of some of the things in that line:
The purpose of concat() is to combine multiple text strings.
str() converts a number into a string which can, eg, be used in concat().
#include just needs to be followed by a string, and it better match a real
file name.  So, there is no difference between #include "1.pov" and
#include concat("1.pov")

The tricky part about using str() when dealing with numbered files is to get
the  0-padding right.   If for example, the numbers are like "001.pov"
"002.pov" you need to set str() differently than if it's "1.pov" "2.pov"
Details on that are in the docs.  Anyway I think, based on how your files
are actually named the line should look like:

#include concat(str(frame_number,0,0), ".pov")


Now about the names of the rendered images...  If you can compromise a
little on the name it might be easy, or it might not be as easy. To use the
above approach and get "1.bmp" etc would be trickier than if it were ok to
get for example "Brick_1.bmp" etc.   So first of all you can change
General_Lego_Renderer.pov to something closer to what you want the final
name to be, again this is if something like "Something_1.bmp" rather than
"1.bmp" etc is acceptable.



If Pov-Ray is using the animation feature it'll add numbers to the end of
the image file name before the ".bmp" extension. If your master .pov file
is "Brick_.pov" and you have 400something individual brickfiles you need to
render, then add the following to the .ini file.:

Initial_Frame=1 ; starting at 1
Final_Frame=450 ; change to whatever it should be
Initial_Clock=0 ; clock not needed for today but it's here
Final_Clock=1   ; clock not needed for today but it's here

Pov-Ray will create "Brick_001.bmp" as the first image. Note that it's
padded by 0's. And it'll create "Brick_450.bmp" as the last image. (That
is, depending on what your main .pov file is named.)

BTW if you're currently using the Quickres.ini file (i.e. the dropdown menu
in windows), make a new .ini file just for this project and use it instead.
Put it in the directory with what you're trying to render. With the new
..ini file open in Pov-Ray's editor hit "Render". Here's an example of what
it might contain:

;----------

;note that comments in .ini files are after any ";"
Antialias=Off
Width=400
Height=300

;Anti-alias settings only relevant if AA is on:
Jitter=On
Sampling_Method=2
Antialias_Threshold=0.2
Antialias_Depth=2

Input_File_Name="myfile.pov" ;change to whatever...

;Another way to change the output, if desired, but I recommend not here:
;Output_File_Name=

;if changing background:
Declare=Color_R=1
Declare=Color_G=1
Declare=Color_B=0

Initial_Frame=1
Final_Frame=450
Initial_Clock=0
Final_Clock=1

;uncomment if you want to re-render certain frames:
 ;Subset_Start_Frame=1
 ;Subset_End_Frame=27

;This changes the clock slightly to make loops work better,
;but leave it off or commented-out normally:
;Cyclic_Animation=on

;You can add paths here as well as in POVRAY.INI:
;Library_Path=c:p-scenesmy_inc

;--------------


A side suggestion/option would be to use .png rather than .bmp   +fn in the
...ini will change that.  It's a lossless format but a lot more compressed.

Anyway, goodluck!

Charles



"Olaf I." <ola### [at] ewetelnet> wrote:
> Dear Stephen,
>
> Near ready.
> In the moment I have this error-notes:
>
> (...)
> File: C:LegoPovFilesGeneral_Lego_Renderer.pov  Line: 4
> Possible Parse Error: Could not find file 'Lego_0.pov'
> File: C:LegoPovFilesGeneral_Lego_Renderer.pov  Line: 4
> File Context (5 lines):
> #include concat("Lego_", str(frame_number,0,0), ".pov")
>
> background { color rgb <1,1,1>} //however you want to redefine it...
>
> Parse Error: Cannot open include file Lego_0.pov.
> File: C:LegoPovFilesGeneral_Lego_Renderer.pov  Line: 4
> Parse Warning: Check that the file is in a directory specified with a +L
> switch or 'Library_Path=' .INI item. Standard include files are in the
> include directory or folder.
> (...)
>
> Only when I change this row
> #include concat("Lego_", str(frame_number,0,0), ".pov")
> in
> #include concat("1.pov")
> it works.
> But them I get not the file General_Lego_Renderer.bmp not 1.bmp!
>
> Can you help me by this last (I hope so) problem?
>
> Regards,
>
> Olaf

Post a reply to this message

> Take a break Olaf. Driving yourself mad and falling out with your family is
> not worth it.
> What you want to do is not really beginners work so don't be downhearted, too
> much.




block in my brain.

> I've been using Pov-Ray for about eight years in hobby mode and I have
> never attempted to do what you are doing. I would spend a night laboriously
> using "Find and Replace". At least it would get done that way :-) But as I
> said I can't programme for toffee :-)
> Unless it is vitally important to you, I suggest putting it on the back burner
> and get to know Pov better then come back to it. Which remind me I only
> started using Pov-Ray all those years ago so I could make an animation flying >
through a fractal landscape. I found 
Pov and never got back into using

I understand what you mean.
But I need Povray only for this one work!

find the right order for the files.
Every day I say "Nothing is impossible!" But here I near to belief this is
not true.

> Fractint again.
> And the people here are nice (mostly :-)

I know!!! :-))
All the trials are very nice!

> BTW there is an international group on the news server if that is of any use
> to you.

Thank yo but no!
When I not find an expert who can write me an solution I must search another
program or I must accept the unrendered pictures.

Regards,

Olaf

Post a reply to this message

Dear Charles,

> I know you've got real-life stress going on but don't give up now.

Sorry, but I must stop!


> Take a break from it for a bit first as Stephen suggested, but I think you'll be
> able to do this and when you do it'll be worth it.  Anyway sorry about the
> confusion.

Maybe I have describe the problem not clear.

I search an expert or another programm to render the pictures or when I
found nothing I accept my defeat and use the pictures unrendered.

Thank you for your help!

Regards,

Olaf

Post a reply to this message

Olaf I. wrote:
> Maybe I have describe the problem not clear.

> I search an expert or another programm to render the pictures or when I
> found nothing I accept my defeat and use the pictures unrendered.

My experience is that these types of problems are rarely insoluble. Even if
POV can't do what you need, a simple perl (or similar) script could probably
auto-process the files suitably. (Of course it helps if you know perl ...)

If you are able to, why don't you zip up the project and post it here for
some of us to look at ? It will be easier to understand the issue if we can
actually run the files ourselves.

-- Chris

Post a reply to this message