for v-ray to be a true mass succes

[dalomar_cg]

Re: for v-ray to be a true mass succes

From the screen cap, you seam to like Fry's solution. It looks as though there isn't necessarily another material editor inside RDK, but rather a way to launch the fry mat editor and the fry materials are still kept track of inside the RDK mat editor. That seams like something we could do, but we aren't going to ditch our own material editor, so having an additional editor within RDK seams less likely.

As far as the future of Vray and RDK, the next full release should bring full support of RDK features to V-Ray. By that point, RDK should be either fully released or close enough to it that it shouldn't be an issue. At the moment a lot of the additional RDK features (curve rendering, edge softening) are going to be much easier to support as they don't require any additional UI on our part. As far as the RDK UI components (mat editor mostly), thats still up in the air as for how those will be handled (the RDK FB will most likely be allowed to be duplicated by the VFB).

The UI has definitely not been lost and is set to be an important aspect of the next full release. Hopefully the UI will make the betas, but at the moment we're dealing with upgrading to a newer version of WxWidgets which will allow us access to more of the things we need to do the things we want with the UI.

[ALTO]

Re: for v-ray to be a true mass succes

Thanks Damien, i think i like what you're saying....

PS: The "Fry-like" suggestion could be only a temporary solution (put the existing editor inside the RDK MatEd requires for sure less coding) but hopefully i'll wait for some beta releases.

Thanks

[dalomar_cg]

Re: for v-ray to be a true mass succes

PS: The "Fry-like" suggestion could be only a temporary solution (put the existing editor inside the RDK MatEd requires for sure less coding) but hopefully i'll wait for some beta releases.

Well, as I said, we won't ditch our (asgvis) material editor since that keeps the documentation, coding, and maintenance of each of our plugins (vfr, vfsu, possibly more in the future) manageable. As far as actually putting our UI into the RDK material editor, I don't know how plausible that is. I would make the not too large assumption that RDK is using MFC (standard Mircosoft UI components) and I'm just not sure if we could simply drop our wxWidgets code in there to make it work. If that is the case, then "copying" our UI to the RDK editor would be more a kin to making a completely new one, which of course, we would rather not do. So although it would be nice to have everything be in RDK, that will most likely not be able to happen and the "Launch" would possibly be the only real way to integrate with the RDK editor (which would probably be better than just leaving it alone).

On the other hand, SU currently deals with going back and forth between the SU material editor (native to SU...not us) and our editor, so if we could get the UI into RDK easily, then having both of them connected and talking to each other is not beyond the realm of possibilities. Ultimately, we aren't focusing on this at the moment so we haven't even crossed that bridge yet. We're looking to actually get the things we want to add working first, then make it all nice and purdy

[ALTO]

Re: for v-ray to be a true mass succes

...and the "Launch" would possibly be the only real way to integrate with the RDK editor (which would probably be better than just leaving it alone).

Oh yes sorry, i mean launch the existing one (or the new vers) via rdk...

[ALTO]

Re: for v-ray to be a true mass succes

Is there something new about the next full version UI (especially the MatEd) that could you share with us?

Demo, beta, preview, teaser, thought ....anything is welcome....

I'm sorry but after 2 years i really would like to know something.


Thanks

[40th]

Re: for v-ray to be a true mass succes

The developers at ASGvis updating the users on their blog http://asgvisdev.blogspot.com/

[ALTO]

Re: for v-ray to be a true mass succes

Thanks for the link.

So from what i understand, after rebuild the whole thing with wxWidgets, the development is full centered in SketchUp for OSX now...
But i don't see major improvement in general UI, only drag & drop layers in material editor (well personally don't like this, better options could be find to create "advanced" materials)

What about rhino integration (RDK)?

[merlik585]

Re: for v-ray to be a true mass succes

I agree with Alto on this,it has been a long time since we had improvement in Vray for Rhino.
Will these changes make their way to VRFR ?When can we expect something.
Looks like all the development is aim to SketchUP...
In 2 years a lot have happen in the rendering world,VFR is lagging behind,not a good thing!



Renee

[Micha_cg]

Re: for v-ray to be a true mass succes

I'm very frustrated too.

The blog link ... one and half month before the last news and the newsletters from ASGvis ... I think, new materials are not news. Every day hundred of Vray user create new materials, but chaosgroup dosn't send newsletters for it.

[Micha_cg]

Re: for v-ray to be a true mass succes

... I have a suggestion - release the old VfR plugin with the latest version of Vray. That would fix some bugs and maybe the speed is enhanced. That is what I would call a small news.

[merlik585]

Re: for v-ray to be a true mass succes

So nothing....from ASGVIS... not even a little glimmer....something to entertain the hope of new things to come !

[dkendig]

Re: for v-ray to be a true mass succes

Hello everyone,

Sorry that we've been kind of silent lately. We've been busy working on the latest version of our product. You are correct, we are currently working on V-Ray for SketchUp for OS X, and Windows. I would like to clear up some of the concerns that have been voiced here. First I would like to mention that the majority of work that has been done lately, has been dealing with rewriting our entire core plugin. We use that core plugin in both Rhino and SketchUp. Then there is a second part of our plugin that deals with interfacing with the host application. Once our rewrite of the core plugin is complete, we will have the bulk of our work done for the rewrite of V-Ray for Rhino.

So from what i understand, after rebuild the whole thing with wxWidgets, the development is full centered in SketchUp for OSX now...

Well, you almost have it right. Our rebuild is actually abandoning wxWidgets, in favor of QT. The real important thing that is being done, is our plugin is being rewritten in Python. Python is a very powerful scripting language, which we now use to automate MANY things that used to take us days, weeks, or months to do in our previous product. So the main thing to take away from this, is that it takes is MUCH less time to add new features, fix bugs, etc. Also, the main focus was getting our core plugin to a point where it was cross-platform compatible, not just V-Ray for SketchUp.

But i don't see major improvement in general UI, only drag & drop layers in material editor (well personally don't like this, better options could be find to create "advanced" materials)

To avoid getting stuck and slowing down our development process, while rewriting everything, we decided it would be best to stick to the UI that everyone is familiar with, making as few changes to the UI as possible. Since we were switching from wxWidgets to QT, and from the majority of our plugin being written in C++, to the majority of our plugin being written in Python, we didn't want to introduce too many new things that could cause bugs or workflow issues. Our UI has been designed with change in mind though. We just chose to keep things simple until we are sure the new core works as it is designed to work. So far, tests show that things are going according to plan, which is great news.

... I have a suggestion - release the old VfR plugin with the latest version of Vray. That would fix some bugs and maybe the speed is enhanced. That is what I would call a small news.

Just linking to the latest V-Ray SDK doesn't automatically make new features available through our plugin. It would be identical to the old release in every way.

[Micha_cg]

Re: for v-ray to be a true mass succes

... I have a suggestion - release the old VfR plugin with the latest version of Vray. That would fix some bugs and maybe the speed is enhanced. That is what I would call a small news.

Just linking to the latest V-Ray SDK doesn't automatically make new features available through our plugin. It would be identical to the old release in every way.

No new features - right, like I wrote, I don't expect so much. Some bug fixes and a little speed by the optimized core could be the benefit.
Example: the not working z depth channel for transparency mapped objects like trees in an architecture scene. Vlado sayed september last year "The ZDepth channel works fine with transparency in newer builds of V-Ray." One year before today!!!
This little bug fix could help to get a fog effect or post effect DOF in arch scenes:
http://forum.asgvis.com/index.php?topic=6263.0
For user, who try to get realistic renderings, the light fog effect is essential. Little feature, little bug, fixed since one year for Vray user at 3dsmax ...when will it appear at VfR (no beta)?
I have the feeling, I read somewhere, that Vray got a speed increase within the last year. This could be the other benefit. Maybe there are more benefits, for example it could be possible that the mysterious "Bitmap "(null)" returned an invalid color" bug is be fixed.
It seems to be a full SR is far away (no beta). So, maybe the latest Vray can be integrated within a few hours, a little present for the long waiting users, a little step forward to continuous bug fixes.

[dkendig]

Re: for v-ray to be a true mass succes

Our old code base doesn't provide us with enough flexibility, and makes the update process take much longer than it should. That's why we've chosen to rewrite our plugin, so it will be more flexible, faster to update, easier to integrate new features, plugins, etc. We hope that we will be able to start working on a new release of VfR soon. We appreciate your support and patience as we go through this process.

[Micha_cg]

Re: for v-ray to be a true mass succes

I would like to give my best to find all bugs and optimize the workflow.