 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I upgraded to the '268 version and noticed tonight,
Possible Parse Error: Text may not be displayed as expected. Please
refer to the user manual regarding changes in POV-Ray v3.8 and later.
Can someone point me to the docs for this?
The warning hits on the first 't' in 'text' in this construct I've used
for decades:
text {
ttf ArialFont
label
0.23,0
scale 0.02
translate <-0.080*inches, 0.088*inches, -0.001*inches>
texture {controlTextureOn}
}
--
dik
Rendered 23,533,286,400 of 40,928,716,800 pixels (57%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoft com> wrote:
> I upgraded to the '268 version and noticed tonight,
>
> Possible Parse Error: Text may not be displayed as expected. Please
> refer to the user manual regarding changes in POV-Ray v3.8 and later.
>
> Can someone point me to the docs for this?
The best I could find for this so far were these:
http://news.povray.org/povray.general/thread/%3C5c38071f%241%40news.povray.org%3E/
https://news.povray.org/povray.beta-test/thread/%3C5c2e6746%40news.povray.org%3E/
http://news.povray.org/povray.beta-test/thread/%3C5b17006b%241%40news.povray.org%3E/
I remember there was a lot of stuff going on trying to fix the long-standing
utf-8 bug.
Maybe use that as a hook? Check bug reports? Flyspray, git, readme, ....
Or just stop breaking POV-Ray. :D
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Op 13/11/2019 om 03:05 schreef Dick Balaska:
> I upgraded to the '268 version and noticed tonight,
>
> Possible Parse Error: Text may not be displayed as expected. Please
> refer to the user manual regarding changes in POV-Ray v3.8 and later.
>
> Can someone point me to the docs for this?
>
> The warning hits on the first 't' in 'text' in this construct I've used
> for decades:
>
> text {
> ttf ArialFont
> label
> 0.23,0
> scale 0.02
> translate <-0.080*inches, 0.088*inches, -0.001*inches>
> texture {controlTextureOn}
> }
>
I am not often using text, so I am probably wrong, but comparing to the
wiki: http://wiki.povray.org/content/Reference:Text I miss the double
quotes. Shouldn't one write: ttf ""ArialFont.ttf" "label" ?
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Op 13/11/2019 om 03:05 schreef Dick Balaska:
> I upgraded to the '268 version and noticed tonight,
>
> Possible Parse Error: Text may not be displayed as expected. Please
> refer to the user manual regarding changes in POV-Ray v3.8 and later.
>
> Can someone point me to the docs for this?
>
> The warning hits on the first 't' in 'text' in this construct I've used
> for decades:
>
> text {
> ttf ArialFont
> label
> 0.23,0
> scale 0.02
> translate <-0.080*inches, 0.088*inches, -0.001*inches>
> texture {controlTextureOn}
> }
>
I am not often using text, so I am probably wrong, but comparing to the
wiki: http://wiki.povray.org/content/Reference:Text I miss the double
quotes. Shouldn't one write: ttf "ArialFont.ttf" "label" ?
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tho### [at] degrootorg> wrote:
> I am not often using text, so I am probably wrong, but comparing to the
> wiki: http://wiki.povray.org/content/Reference:Text I miss the double
> quotes. Shouldn't one write: ttf "ArialFont.ttf" "label" ?
Good catch - I read right through that, as "I've been using it for decades"
makes me assume it's not the issue, and so I jump past the surface to something
deeper.
from:
http://wiki.povray.org/content/Reference:Text
The syntax is:
TEXT_OBECT:
text {
ttf "fontname.ttf/ttc" "String_of_Text"
Thickness, <Offset>
[OBJECT_MODIFIERS...]
}
Where fontname.ttf or fontname.ttc is the name of the TrueType font file. It is
a quoted string literal or string expression.
Maybe POV-Ray thinks that ArialFont is a string expression - an identifier - and
burps when it's not defined the way it thinks it should be?
Who knows what dark magic lurks in the Balaska scene files...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/12/19 9:59 PM, Bald Eagle wrote:
>
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>> I upgraded to the '268 version and noticed tonight,
>>
>> Possible Parse Error: Text may not be displayed as expected. Please
>> refer to the user manual regarding changes in POV-Ray v3.8 and later.
>>
>> Can someone point me to the docs for this?
>
> The best I could find for this so far were these:
>
> http://news.povray.org/povray.general/thread/%3C5c38071f%241%40news.povray.org%3E/
> https://news.povray.org/povray.beta-test/thread/%3C5c2e6746%40news.povray.org%3E/
> http://news.povray.org/povray.beta-test/thread/%3C5b17006b%241%40news.povray.org%3E/
>
>
> I remember there was a lot of stuff going on trying to fix the long-standing
> utf-8 bug.
>
> Maybe use that as a hook? Check bug reports? Flyspray, git, readme, ....
>
> Or just stop breaking POV-Ray. :D
>
>
Thanks much for those!
I was off minecrafting last January or I would have chimed in about
"multiple engines with one gui". (I always wanted to wrap hgpovray with
my gui.)
Looking at the povray source code, the solution is to change all of my
files to
#version 3.8;
and leave my text {} objects exactly as they are.
---------------------------------------------------------
On 11/13/19 7:05 AM, Bald Eagle wrote:>
> Thomas de Groot <tho### [at] degrootorg> wrote:
>
>> I am not often using text, so I am probably wrong, but comparing to the
>> wiki: http://wiki.povray.org/content/Reference:Text I miss the double
>> quotes. Shouldn't one write: ttf "ArialFont.ttf" "label" ?
>
> Good catch - I read right through that, as "I've been using it for
decades"
> makes me assume it's not the issue, and so I jump past the surface to
something
> deeper.
It is double quoted. My bad for not including the defines in my original
snippet. I thought it would clutter.
#declare TtRootDir="../"; // because I'm in a subdir
#declare TtCommonDir=concat(TtRootDir, "ttCommon/");
#declare ArialFont=concat(TtCommonDir, "arial.ttf");
equals
text {
ttf "../ttCommon/arial.ttf"
...
--
dik
Rendered 23,657,702,400 of 40,928,716,800 pixels (57%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/13/19 9:21 AM, Dick Balaska wrote:
>
> Looking at the povray source code, the solution is to change all of my
> files to
>
> #version 3.8;
>
> and leave my text {} objects exactly as they are.
>
Well poo.
Changing my SDL from #version 3.7 to 3.8 causes the image to be much darker.
I can't do that. I'd have to re-render 6 months worth of frames.
(and the annoying not-an-error "possible error" comes through as a
"mGenericStatus" message (normally the 'Rendered 10 of 20 pixels (50%)'
messages) so it shows up in the povwin status bar. This confuses my
renderfarm progress bars, which resize bigly to display the message that
shouldn't even be there.)
--
dik
Rendered 23,734,425,600 of 40,928,716,800 pixels (57%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
> (and the annoying not-an-error "possible error" comes through as a
> "mGenericStatus" message (normally the 'Rendered 10 of 20 pixels (50%)'
> messages) so it shows up in the povwin status bar. This confuses my
> renderfarm progress bars, which resize bigly to display the message that
> shouldn't even be there.)
Isn't there a message pane switch that can be toggled to shut things like that
off?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> Isn't there a message pane switch that can be toggled to shut things like that
> off?
http://wiki.povray.org/content/Reference:Text_Output_Options#Text_Streams
Post a reply to this message
|
|
| |
| |
|
|
From: William F Pokorny
Subject: Re: Hello darkness (was Re: 3.8 and text {})
Date: 14 Nov 2019 07:26:39
Message: <5dcd47ff$1@news.povray.org>
|
|
|
| |
| |
|
|
On 11/14/19 2:27 AM, Dick Balaska wrote:
> On 11/13/19 9:21 AM, Dick Balaska wrote:
>
>>
>> Looking at the povray source code, the solution is to change all of my
>> files to
>>
>> #version 3.8;
>>
>> and leave my text {} objects exactly as they are.
>>
>
> Well poo.
>
> Changing my SDL from #version 3.7 to 3.8 causes the image to be much
> darker.
>
One of the changes 3.7 to 3.8 was to take the default ambient to 0.0.
It's a funky color adder disconnected from gamma handling, and at 0.1,
it tends to brink near blacks way up in intensity with AG 1.0 - washing
out the contrast in the images. Your 1.7 AG is already compensating for
this effect to a large degree.
Have you tried changing the default ambient back to 0.1 when changing
your version to 3.8?
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
From: Dick Balaska
Subject: Re: Hello darkness (was Re: 3.8 and text {})
Date: 14 Nov 2019 15:49:32
Message: <5dcdbddc@news.povray.org>
|
|
|
| |
| |
|
|
On 11/14/19 7:26 AM, William F Pokorny wrote:
> On 11/14/19 2:27 AM, Dick Balaska wrote:
>>
>> Changing my SDL from #version 3.7 to 3.8 causes the image to be much
>> darker.
>>
>
> One of the changes 3.7 to 3.8 was to take the default ambient to 0.0.
> It's a funky color adder disconnected from gamma handling, and at 0.1,
> it tends to brink near blacks way up in intensity with AG 1.0 - washing
> out the contrast in the images. Your 1.7 AG is already compensating for
> this effect to a large degree.
>
> Have you tried changing the default ambient back to 0.1 when changing
> your version to 3.8?
>
> Bill P.
I'm trying to explore/understand this.
This,
https://www.povray.org/documentation/3.7.0/r3_4.html#r3_4_1
says the default ambient is <1,1,1>, not 0.1. Am I looking at the wrong
thing?
--
dik
Rendered 23,657,702,400 of 40,928,716,800 pixels (57%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
> I'm trying to explore/understand this.
> This,
> https://www.povray.org/documentation/3.7.0/r3_4.html#r3_4_1
> says the default ambient is <1,1,1>, not 0.1. Am I looking at the wrong
> thing?
This is why I hate "documentation" compared to direct access to the values and
parameters that something uses.
I think, after 25 years, there ought to be access through SDL, or at least a
text-stream command that regurgitates things that are hidden "under the hood".
And, you probably _are_ looking at the wrong thing, since we're on
3.8.something.
http://wiki.povray.org/content/Reference:Finish#Ambient
"In version 3.8 there has been a Change to the ambient default setting. The
default setting is now ambient 0 as opposed to the ambient 0.1 value used in
previous versions. Requires #version 3.8; or equivalent INI setting or
command-line option. See also: Version Directive."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/14/19 7:26 AM, William F Pokorny wrote:
>
> Have you tried changing the default ambient back to 0.1 when changing
> your version to 3.8?
The global ambient_light is silently ignored if the #version is 3.8
I used the Basic Scene 01 - Checkered Plane template
and added a Wire_Box. Then at the top changed these 3 lines:
#version 3.8;
global_settings{ assumed_gamma 1.7 ambient_light 5.0}
//#default{ finish{ ambient 0.1 diffuse 0.9 }}
If the version is 3.7, then that ambient_light 5.0 washes everything
right out. If the version is 3.8, it matters not what I set that number to.
So I tried
global_settings{ assumed_gamma 1.7 }
#default{ finish{ ambient 0.1 }}
This does look a lot like the effect I want, after a couple of tests on
my movie. However, I am greeted with a plethora of:
Parse Warning: Scene language version changed after a 'default'
statement. The changes in defaults normally associated with the language
version change are not applied.
because the standard includes push the version, change to 3.5, pop the
version.
sigh.
--
dik
Rendered 23,792,486,400 of 40,928,716,800 pixels (58%)
Post a reply to this message
|
|
| |
| |
|
|
From: William F Pokorny
Subject: Re: Hello darkness (was Re: 3.8 and text {})
Date: 15 Nov 2019 09:02:11
Message: <5dceafe3$1@news.povray.org>
|
|
|
| |
| |
|
|
On 11/14/19 11:58 PM, Dick Balaska wrote:
> On 11/14/19 7:26 AM, William F Pokorny wrote:
>
>>
>> Have you tried changing the default ambient back to 0.1 when changing
>> your version to 3.8?
>
> The global ambient_light is silently ignored if the #version is 3.8
>
> I used the Basic Scene 01 - Checkered Plane template
> and added a Wire_Box. Then at the top changed these 3 lines:
>
> #version 3.8;
> global_settings{ assumed_gamma 1.7 ambient_light 5.0}
> //#default{ finish{ ambient 0.1 diffuse 0.9 }}
>
> If the version is 3.7, then that ambient_light 5.0 washes everything
> right out. If the version is 3.8, it matters not what I set that number
> to.
>
> So I tried
>
> global_settings{ assumed_gamma 1.7 }
> #default{ finish{ ambient 0.1 }}
>
> This does look a lot like the effect I want, after a couple of tests on
> my movie. However, I am greeted with a plethora of:
>
> Parse Warning: Scene language version changed after a 'default'
> statement. The changes in defaults normally associated with the language
> version change are not applied.
>
> because the standard includes push the version, change to 3.5, pop the
> version.
>
> sigh.
>
Hey. Sorry, I should've written out 'default{ finish{ ambient 0.1 }}'
(1) to make clear what's needed if using #version 3.8 and wanting to
match the 3.7 finish ambient behavior.
The ambient_light color has an effect only when a texture's ambient
setting is > 0.0 and so has no effect anywhere the v3.8 default ambient
0 finish is used.
Those parse warnings showed up in one of the last updates and I join you
in not being a fan of the warning in it's current form. It's very noisy
in typical use. I worked recently a little in v3.8 with Norbert's
assumed_gamma scene which included stdinc.inc - and yuck. If the warning
could not warn when an alternate version is detected but the original
restored before exiting an include file - or the main file - it would be
better(2).
Bill P.
(1) - Christoph recommends using default {} over #default {}.
(2) - I recall no discussion around the addition of this parser check
and warning before its introduction. Perhaps Christoph was thinking all
the shipped includes would be updated to version 3.8 before any v3.8
release so those wouldn't be an issue for this warning. I don't know.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 2019-11-14 à 15:49, Dick Balaska a écrit :
> On 11/14/19 7:26 AM, William F Pokorny wrote:
>> On 11/14/19 2:27 AM, Dick Balaska wrote:
>>>
>>> Changing my SDL from #version 3.7 to 3.8 causes the image to be much
>>> darker.
>>>
>>
>> One of the changes 3.7 to 3.8 was to take the default ambient to 0.0.
>> It's a funky color adder disconnected from gamma handling, and at 0.1,
>> it tends to brink near blacks way up in intensity with AG 1.0 -
>> washing out the contrast in the images. Your 1.7 AG is already
>> compensating for this effect to a large degree.
>>
>> Have you tried changing the default ambient back to 0.1 when changing
>> your version to 3.8?
>>
>> Bill P.
>
> I'm trying to explore/understand this.
> This,
> https://www.povray.org/documentation/3.7.0/r3_4.html#r3_4_1
> says the default ambient is <1,1,1>, not 0.1. Am I looking at the wrong
> thing?
>
Yes, you are looking at the wrong thing.
This refers to ambient_light in the global_settings. This is not the
default ambient value but a multiplicator that is applied to every
ambient values in the whole scene.
If you set that value to <1,0,0>, then, ALL ambient, default and
explicit, will become red. Then, if you have an ambient value set to
something like rgb<0, 0.02, 0.1>, it will result in black.
You need to look in the finish section :
https://www.povray.org/documentation/3.7.0/r3_4.html#r3_4_6_3_1
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 2019-11-14 à 23:58, Dick Balaska a écrit :
> This does look a lot like the effect I want, after a couple of tests on
> my movie. However, I am greeted with a plethora of:
>
> Parse Warning: Scene language version changed after a 'default'
> statement. The changes in defaults normally associated with the language
> version change are not applied.
>
> because the standard includes push the version, change to 3.5, pop the
> version.
>
> sigh.
>
You can get rid of those warnings simply by moving the #default
statement after your includes.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/15/19 11:55 AM, Alain Martel wrote:
> Le 2019-11-14 à 23:58, Dick Balaska a écrit :
>
>> This does look a lot like the effect I want, after a couple of tests
>> on my movie. However, I am greeted with a plethora of:
>>
>> Parse Warning: Scene language version changed after a 'default'
>> statement. The changes in defaults normally associated with the
>> language version change are not applied.
>>
>> because the standard includes push the version, change to 3.5, pop the
>> version.
>>
>> sigh.
>>
>
> You can get rid of those warnings simply by moving the #default
> statement after your includes.
Yeah, but that's a hacky hacking hack.
I think really my only way out is to bite the bullet, surrender to
clipka, and rework the whole shebang to gamma 1.0.
It's only 90,984 lines of lovingly handcrafted SDL. (And 17,047 lines
of Java and 9,799 lines of c++ giving 68,245 separate images.)
How hard can it be?
[insert maniacal laughter here]
--
dik
Rendered 24,043,392,000 of 40,928,716,800 pixels (58%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
> I think really my only way out is to bite the bullet, surrender to
> clipka, and rework the whole shebang to gamma 1.0.
All that, only to suppress some parser warnings about `text`?
There had been some attempts to clean up character encoding related stuff (you
know, ASCII vs. Latin-1 vs. Windows-1252 vs. Windows-1251 vs. Mac OS Roman vs.
UTF-8 vs. UCS-2 vs. UTF-16 vs. Whatever-Have-You) that turned out to stretch its
dirty tentacles deep into the heart of the `text` code, revealing that the
POV-Ray default fonts are totally borked, etc etc...
The 2019 status of POV-Ray was right smack-bang in the middle of trying to get
to grips with all that madness. Unless I run away screaming again, the current
state of affairs with overzealous text-related warnings will settle down a bit.
For starters, I guess I could spare you a few warnings as long as you promise to
stick to ASCII characters only...
> It's only 90,984 lines of lovingly handcrafted SDL. (And 17,047 lines
> of Java and 9,799 lines of c++ giving 68,245 separate images.)
>
> How hard can it be?
>
> [insert maniacal laughter here]
Not too shabby. That's actually in a similar ballbark as the POV-Ray back-end
(22k Base, 48k Core, 23k Parser, 5k POVMS, 7k miscellaneous Backend, last time
someone counted; for a total of about 105k lines of code).
Indeed, how hard can it possibly be...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
