StevieJ
![]() |
1) Lighting/height being flattened on high resolution renders...
![]() 2) Image resolution being changed to 72 ppi on all images rendered...with image size being adjusted to keep overall resolution... There is no loss...but FF should not be adjusting resolution to something different at all...creates problems for people who need their images to remain at the same size and don't catch the change... ![]() Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||
Posted: January 10, 2013 5:21 pm | ||||
StevieJ
![]() |
I know that I'm not the only one seeing these things... Shello...
![]() Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||
Posted: January 11, 2013 2:18 pm | ||||
Crapadilla
![]() |
||||
Posted: January 14, 2013 3:19 pm | ||||
Vladimir Golovin
Administrator |
StevieJ, could you elaborate on this? |
|||
Posted: January 15, 2013 10:27 am | ||||
StevieJ
![]() |
First, having big problems even getting large images (5000 x 5000 pixels and larger) to start rendering now...and makes Phototshop non-reponsive if I use FF as a PS plugin... See submitted bug reports...
Second, when I was able to render large images...height, reflectivity, and metallic were being lost...matting the lighting effects... Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||
Posted: January 22, 2013 12:27 am | ||||
StevieJ
![]() |
Would running FF on x64 system have anything to do with these problems??? Any virtual memory tweaks that will help remedy these rendering problems???
Anyone??? Beuller??? Beuller??? Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||
Posted: January 22, 2013 10:14 am | ||||
Vladimir Golovin
Administrator |
When you experience matting on resolution changes, are you using any bitmaps in the bump / height subtree? |
|||
Posted: January 24, 2013 1:44 am | ||||
StevieJ
![]() |
Hey Vlad... No, I'm not... Render at low res fine... Seems to be happening with 5000 x 5000 ppi images and above...
Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||
Posted: January 25, 2013 8:21 pm | ||||
StevieJ
![]() |
This is getting extremely frustating...
![]() "Bad Allocation" errors before even starting to render high res images...drop resolution, starts to render, then stops with the same error...and if I can get an image to render, the lighting effects are totally gone... ![]() I can't get anything to look like what it does on the display with lighting involved at high res anymore... Only comes out right at low resolutions... Totally frustrating!!! My computer is more than adequate to render these images... What is going on with FF...and is there any solutions to this coming??? Will setting virtual memory to static at 3 times or more than computer's RAM work??? I really need this program to render the way I see it on display and without all the errors...which is wasting alot of my time... ![]() Images below 5000 x 5000 ppi seem to be rendering okay... Everything above that resolution either won't start rendering or stops rendering with the "Bad Allocation" error... If by some rare chance it does finish a render above this resolution, the lighting effects are totally gone...and ends up as a matted render... ![]() Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||
Posted: January 28, 2013 10:43 am | ||||
StevieJ
![]() |
||||
Posted: January 29, 2013 12:49 am | ||||
Sharandra
![]() |
Have you tried reinstalling FF?
I had a similar issue on a filter a while ago, it went away after an update. |
|||
Posted: January 29, 2013 1:21 am | ||||
StevieJ
![]() |
Fully updated in v3... Three big problems with all surface result filters...loss of lighting effects with greater resolution...not rendering as displayed...and not completing renders at high resoltions... I'm bumming...
![]() Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||
Posted: January 30, 2013 2:25 pm | ||||
Sharandra
![]() |
||||
Posted: February 7, 2013 10:13 am | ||||
Skybase
![]() |
Is the preview what's supposed to be portraying the filtered result or is it a problem?
|
|||
Posted: February 7, 2013 10:25 am | ||||
Sharandra
![]() |
Well I kinda expected to get what I see in the preview, just in a higher resolution, lol. But what I got looks totally different.
|
|||
Posted: February 7, 2013 10:39 am | ||||
Skybase
![]() |
Yeah, previews kinda get a bit biased with final renders, especially when you have a bunch of fine details. Pretty sure I encountered this trouble before as well. In these cases, I just edit the filter to make it look like the preview and that typically is the only solution so far.
But... well.... maybe you're actually encountering a bug. I shouldn't just suggest things really. ![]() |
|||
Posted: February 7, 2013 11:53 am | ||||
Sharandra
![]() |
Dunno, I usually get what I see. In this case the output looked almost like the original image, just blurred a bit. that was my embroidery filter btw, and in the left image you can see how it´s supposed to look. It has something to do with the image I feed into it, I guess. It works fine with other examples lol. Not tragic, as I was just messing around, but still weird.
Oh and remember that little pond scene I made? I wanted to make that bigger, but when I changed the resolution and applied the Ivy preset, the preview would look the same as before, but the output was completely different. And that is really not supposed to happen. And with my wattle and daub filter, I had some presets, which wouldn´t render correctly at bigger then 1024x1024, similar to stevies problem above, but as I said, it went away after an update.
Yeah we can do that, but what about the ppl who only got the basic edition, or don´t know how to? |
|||
Posted: February 8, 2013 3:00 am | ||||
Vladimir Golovin
Administrator |
This fix may improve the situation:
http://www.filterforge.com/forum/read...&TID=10903 |
|||
Posted: February 8, 2013 10:20 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,711 Registered Users
+18 new in 30 days!
153,531 Posts
+39 new in 30 days!
15,347 Topics
+72 new in year!
35 unregistered users.