FStormRender for 3ds Max v0.3.8a, Hot fix.

[Karba]

Any further info?

1. There will be other restrictions? Time, resolution, anything else? Please don't be crazy agressive like Octane, which can be very disappointing.
2. When can we expect the first commercial version?
3. Whats coming next? Are there any plans?

1) Just water marks. No other limitations
2) In 1-2 weeks, I hope.
3) First commercial version will not have many new features, mostly bug fixes.

[Sylk]

3) First commercial version will not have many new features, mostly bug fixes.

Please, can you just release the hot fix, without the new features, before the commercial version?

[m17a4y]

Please, can you just release the hot fix, without the new features, before the commercial version?

That would be awesome if it happens!

[gvman]

1) Just water marks. No other limitations
2) In 1-2 weeks, I hope.
3) First commercial version will not have many new features, mostly bug fixes.

Absolutely love to hear that. Thank you for the screenshot. It's a very gentle watermark, to be honest it's the best I've ever see so far. And I'm glad to see, you did a lot of user's attention.

[Sylk]

I agree with that

[Sylk]

Looks like driver check doesn't work sometimes. I have removed it. Please redownload it again.

For the first time since i test Fstorm, with this 0.3.8a v2 the console stay always visible and it keeps Max open after closing main max windows!! (see pix)... Not occurs with the 0.3.8a v1.

Please hide it like previous versions. Or reupload 0.3.8a v1.


HOWEVER, closing of this console correctly close Max process, WHILE the 0.3.8a v1 keeps Max process in background!
In both cases FStorm prevents proper Max closure.

The 0.3.8 version doesn't occur any of these issues.

[Karba]

For the first time since i test Fstorm, with this 0.3.8a v2 the console stay always visible and it keeps Max open after closing main max windows!! (see pix)... Not occurs with the 0.3.8a v1.

Please hide it like previous versions. Or reupload 0.3.8a v1.


HOWEVER, closing of this console correctly close Max process, WHILE the 0.3.8a v1 keeps Max process in background!
In both cases FStorm prevents proper Max closure.

The 0.3.8 version doesn't occur any of these issues.

You probably downloaded 0.3.8a long time ago. I have reuploaded 0.3.8a 2 times.

[Sylk]

You probably downloaded 0.3.8a long time ago. I have reuploaded 0.3.8a 2 times.

Right, anyway 0.3.8 v3 only solve v2 issue but not the v1 issue...

Edit: "0.3.8 without issue" looks to just be lucky during tests. 99% of time Max not closing properly. Previous test confirming the issue is caused by VRay seems to be true.

[Iskánder ivp87]

Hi, I downloaded the 0.3.8a the 8th of this month, I installed it but ended going back to the 0.3.7a since it gives me faster results and in a consistent way, and the difference in render quality is almost not noticeable if there's any at all

since then (8/11/2016) have this version been updated?

thank you

[Sylk]

Yeah, the last update was uploaded on 9/11

[Iskánder ivp87]

ha! downloading again then... thank you

any clue what the differences could be? or if this last update is at least as good as the 3.7a?

[Sylk]

At least it fix this bug http://www.fstormrender.ru/forum/for...=6773#post6773

Next you can make some tests to check the better for your works.

[adams]

I'm getting issues with material shader ball (black)on latest 376.19 driver - anyone else having issues? Suggestions for fix, I know there have been problems in the past with black shader balls, I'm sure were driver related