 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The current winpov betas 11 and 11a both seem to make only BMP files
regardless of INI or command line setting.
Didn't see any mention of file output problems or changes so thought I
should say something. I hadn't been checking these latest betas much so I
hope everything is going along okay. Very little traffic here in this group,
too. Must be the time of year or whatever.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob Hughes wrote:
> The current winpov betas 11 and 11a both seem to make only BMP files
> regardless of INI or command line setting.
>
> Didn't see any mention of file output problems or changes so thought I
> should say something. I hadn't been checking these latest betas much so I
Thanks for pointing this out, I'll fix it in 11b which I'm about to release.
I've been very busy recently and haven't had the time to properly update the
release notes. Basically the only notable change in beta 11 vs 10 is the fact
that I've ripped apart and re-assembled the way the windows code talks to the
backend of the program. This has caused a number of problems like the above
which I just didn't detect before release.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Oh, beta 11 released? I didn't know, seems like you didn't announce it here.
That or my newsreader sucks.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Alvarez wrote:
> Oh, beta 11 released? I didn't know, seems like you didn't announce it here.
> That or my newsreader sucks.
I didn't. Partly because it didn't fix any bugs, and partly because I haven't
had time to write the release notes.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello !
It seems too that the "path" option has no more effect in beta 11 and beta
11a...
I explain :
When you set a path in the POVRAY.INI file, it has no more effect in Beta 11
& 11a, forcing me to drop all my include file and image maps in the
standard include path, since only this one and C:WindowsFonts seem to
work...
Are they hardcoded now ?
Thanks for reading !
Regards,
Laurent aka Tartiflette :-))
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Edit !!
Forget what i said in the post above ! I just saw that a Beta 11b has been
posted and it resolves this problem !
So Kudos to the developers ! And a BIG thank you for this wonderful piece of
software that has become POV-Ray over the years !
Regards,
Laurent aka Tartiflette :-))
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tartiflette" <nomail@nomail> wrote in message
news:web.439838dfd7ee52d21866f6fc0@news.povray.org...
>
> So Kudos to the developers ! And a BIG thank you for this wonderful piece
> of
> software that has become POV-Ray over the years !
I'd like to share that sentiment. Much has been done. Thank you Chris and
others.
Yes, 11b solved the image output file trouble... now if I can just get used
to the change about gamma.
;^)
I didn't use beta 10 much, when that way of doing image gamma became
different, and actually haven't been doing much rendering since around beta
7 or 8. Trying to check into the betas more again since those all-important
things such as radiosity, photons, dispersion are being added back in.
Which, BTW, I rendered the example scene file newdiffract.pov with and
without photons and I guess photons isn't working right yet. Only makes
black shadows, as if the objects become opaque instead of remaining
transparent.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
mensaje news:43972300@news.povray.org...
> I didn't. Partly because it didn't fix any bugs,
It doesn't fix bugs but it has a new expire date. So it's still useful since
beta 10 expired a bit long ago.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
