If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Hello Karba
I tried this version on max 2017 and hair and fur are not working yet, i think in version 2.6a its ok
Isnt a little too early for Fstorm going paid version? because i think if we pay we want something more robust and complete... i love Fstorm and im certainly going to buy it, but not now its far from finishied...
I will fix hair and fur.
It is up to you to use or not.
however there are 3 things (and kind of easy things to implement) you should include in the release.
all other things can come later but think about those 3 please:
1- background switcher
2- shadow catcher
3- dome radius
these are really fundamental features of every engine
hope you understand my point
i'm happy you are going to release the "final version"
thanks
cdb
1,2 will be implemented in a commercial version (not in the first one)
3 - What is this?
It looks like Fstorm doesnt cleans the memory or something like that after rendering. When I open the scene it ocupies 1.2gb but after working a while that same scenes fstorm says it ocupies 2.4gb!
That shows fstorm, but with "Sisinternals - Process explorer" it shows that 3ds max consumes all the 6gb of ram of the video card- Look at the screenshot
And I can't work in 3ds max and photoshop at the same time because it won't open because there isn't 500mb free video memory. In Octane with the same scene or heavier scenes I work in photoshop and after effects without problem.
I am using v0.3.8a and last nvidia driver.
On your screenshot fstorm says it takes only 1.37Gb
1,2 will be implemented in a commercial version (not in the first one)
3 - What is this?
ok, thanks for the reply (neither a solid color for replacing the alpha channel?)
the dome radius is the radius of the sphere or the emisphere in which an hdr environment is mapped to
sometimes (eg interior hdris baked hdris etc) the dome should'nt be "infinite" to cast proper lighting so for example if i make an hdr out of a room i'd need to map it to a dome which is 3 meters radius for example,
that's it
thanks
all the best for the release
ps do you have an eta for that?
Thanks! this version works.
This is a dump for previous version.
Dump File: FStorm3dsmaxSetup_0_3_8a.exe.11660.dmp : CrashDumps\FStorm3dsmaxSetup_0_3_8a.exe.11660.dmp
Last Write Time: 08.11.2016 12:28:00
Process Name: FStorm3dsmaxSetup_0_3_8a.exe : FStorm3dsmaxSetup_0_3_8a.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present
System Information
------------------
OS Version: 10.0.14393
CLR Version(s):
it's just me or this one is slower than the 3.7a?? I have 8 different scenes to compare and this version is about 3 ~ 5 seconds behind in a period of 40 or so seconds, which for me is a lot... is there any reason to keep this one and not going back to the 3.7a? what would I gain with this version?
That's a too short time to compare and can even be only due to a fresh reboot of your PC. You should compare with files that take over 20 minutes (10, at very least).
PS: for me, it's 20 seconds faster in 14 minutes scenes.
yes but I do animation and try to keep render times low, 5 minutes or lower and with the same 8 different scenes I have noticed how the render time is just the same or decrease with each fstorm version, with this one it just don't
I installed the .3.7a again to compare and indeed is faster around 5 or 6 seconds in a secuence of about 36 seconds the frame, in the other 7 scenes the difference is smaller, the one with less noticeable difference is about 3 min 20 seconds the frame and still is 10 seconds behind
I see. Well, I think it can vary between versions, yes. If the software is fast but we ask for quality improvements in certain things and Karba add them, probably the render times will be slightly slower, and it will get slower with other improvements too, until we arrive at a point where Karba, instead of adding a new function, use his time to review the code, make improvements on it and boost the render speed. I think this is a common cycle.
Добрый вечер! Извините, английского не знаю, поэтому пишу по русски. Андрей, понятно, что ориентируясь на зарубежный рынок, делать русский интерфейс для своего рендера вы не собираетесь... но, - планируете ли сделать, для таких пользователей как я, русскую справку по своему рендеру? Планируете ли портировать свой рендер на Cinema 4D и когда?
Добрый вечер! Извините, английского не знаю, поэтому пишу по русски. Андрей, понятно, что ориентируясь на зарубежный рынок, делать русский интерфейс для своего рендера вы не собираетесь... но, - планируете ли сделать, для таких пользователей как я, русскую справку по своему рендеру? Планируете ли портировать свой рендер на Cinema 4D и когда?
Non English messages are not allowed. Please check your private messages.
Comment