 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello,
It seems that you can't use font symbols in Moray. I found a really cool ttf
font called Bach30 that allows you to create any musical notes or symbols
using the alt key and various 4-digit codes on the numeric keypad. I tried
it out and it showed the note correctly in all four Moray views, but Povray
(3.1) renders different notes than the ones showing in Moray. I tried it in
Megapov, and it wouldn't render it at all. I can post the font file on Moray
Binaries if anyone is interested in trying it to see what the results are on
their machine. Any comments on this would be appreciated.
Thank you,
Steve Shelby
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi steve,
the problem you describe is allready known. the circumstances why this
error appears is too complex for me to describe...
the brandnew (and still in beta-testing) povray version 3.5 will solve
the problems.
and -what is more- the new (and available) moray version 3.3 solve the
problem even with povray v3.1 !
get it !)
alex wolff
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alex,
I already have Moray version 3.3. When you say the new version 3.3, are you
referring to the Maintenance Release that was announced last month?
Steve
Alex Wolff <ale### [at] gmx de> wrote in message
news:3BFEF3BA.DEB7AD5C@gmx.de...
> hi steve,
> the problem you describe is allready known. the circumstances why this
> error appears is too complex for me to describe...
> the brandnew (and still in beta-testing) povray version 3.5 will solve
> the problems.
> and -what is more- the new (and available) moray version 3.3 solve the
> problem even with povray v3.1 !
> get it !)
> alex wolff
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alex,
Ignore my previous reply. I downloaded and installed both the Moray 3.3
Maintenance patch and the Povray 3.5 beta. The problem is still there, same
as before.
Steve Shelby
Alex Wolff <ale### [at] gmxde> wrote in message
news:3BFEF3BA.DEB7AD5C@gmx.de...
> hi steve,
> the problem you describe is allready known. the circumstances why this
> error appears is too complex for me to describe...
> the brandnew (and still in beta-testing) povray version 3.5 will solve
> the problems.
> and -what is more- the new (and available) moray version 3.3 solve the
> problem even with povray v3.1 !
> get it !)
> alex wolff
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi steve,
the new povray 3.5 is not yet supported by moray. maybe you will have
success by hand-coding your scene in povray 3.5.
about moray 3.3: one of the new features in 3.3 is described as:
>Added character mapping for TrueType objects. MORAY.INI contains a
section where you can change mappings for the high ASCII characters. It
contains mappings for all the base characters. Moray will now make
POV-Ray render text with high-ASCII characters (umlauts, etc.)
correctly.<
i don't know what changes you'll have to make. maybe lutz can explain...
i tried some umlauts (a, o or u with two dots above) and the results are
very... well funny: with some ttfs all is working well, othertimes only
one dot is rendered and othertimes nothing of sense comes out.
sorry for my too fast answer. i did only read the features without
trying out...
alex wolff
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I solved it!
There's a file called Moray.ini that has a chart for all the possible
character map codes, what they are in Moray, and what they are converted to
in Pov. For some reason, at least for this particular font, the conversion
numbers are wrong, but if you change the Pov number to be the same as the
Moray number, it works correctly. Unfortunately, I wasted a lot of time last
night not getting results, because I found out this morning you have to
*re-start the computer* before the changes will take effect. I also found
out that it works with either Povray 3.1 or 3.5 ( I installed the Moray
patch, build 7025, which is supposed to make it compatible).
Thanks for your input.
Alex Wolff <ale### [at] gmxde> wrote in message
news:3C006A6F.21FC96E0@gmx.de...
> hi steve,
> the new povray 3.5 is not yet supported by moray. maybe you will have
> success by hand-coding your scene in povray 3.5.
> about moray 3.3: one of the new features in 3.3 is described as:
> >Added character mapping for TrueType objects. MORAY.INI contains a
> section where you can change mappings for the high ASCII characters. It
> contains mappings for all the base characters. Moray will now make
> POV-Ray render text with high-ASCII characters (umlauts, etc.)
> correctly.<
> i don't know what changes you'll have to make. maybe lutz can explain...
>
> i tried some umlauts (a, o or u with two dots above) and the results are
> very... well funny: with some ttfs all is working well, othertimes only
> one dot is rendered and othertimes nothing of sense comes out.
> sorry for my too fast answer. i did only read the features without
> trying out...
> alex wolff
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi sshelby, you recently wrote in moray.win:
> For some reason, at least for this particular font, the conversion
> numbers are wrong, ...
It could be that for that font the encoding is not the normal expected
one.
> you have to *re-start the computer* before the changes will take effect.
That can't really be. You would need to restart Moray, yes. But
certainly not the computer. You might also need to shutdown POV-Ray.
Regards,
- Lutz
email : lut### [at] stmuccom
Web : http://www.stmuc.com/moray
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lutz,
Thanks for your comments. I won't agrue with you on that re-starting issue,
I'd have to go back and try it both ways to be sure, and I'd rather not.
Here's an irony: After I got the problem figured out, I tried other
character map codes for that font, and they all worked correctly. The two
that I had originally picked at random were the only ones that needed to be
changed!
Steve
Lutz Kretzschmar <lut### [at] stmuccom> wrote in message
news:imj50u8ggdrgi1sh4sm9sdstt80merkfat@4ax.com...
> Hi sshelby, you recently wrote in moray.win:
>
> > For some reason, at least for this particular font, the conversion
> > numbers are wrong, ...
> It could be that for that font the encoding is not the normal expected
> one.
>
> > you have to *re-start the computer* before the changes will take effect.
> That can't really be. You would need to restart Moray, yes. But
> certainly not the computer. You might also need to shutdown POV-Ray.
>
> Regards,
>
> - Lutz
> email : lut### [at] stmuccom
> Web : http://www.stmuc.com/moray
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi steve,
could you tell me, what changes you made exactly with the
moray.ini-file?
i want to ry out, if these changes solve my problem with the german
umlauts.
alex
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alex,
Here's an example of what I did: One of the symbols I was having trouble
with was alt-0182. The table in Moray.ini skips the zero, so I looked for
182 in the left column. It had its corresponding number in the right column
as 166. I changed the 166 to 182, and, after re-starting the computer, it
rendered the symbol correctly. I hope that will also work for you.
Good luck,
Steve
Alex Wolff <ale### [at] gmxde> wrote in message
news:3C0415B5.9D4E9E83@gmx.de...
> hi steve,
> could you tell me, what changes you made exactly with the
> moray.ini-file?
> i want to ry out, if these changes solve my problem with the german
> umlauts.
> alex
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
