5 wip

[ilay]

What about 5 version of Rhino?
Have any changes in developing of vray-port for it?

[dalomar_cg]

Re: 5 wip

No because Rhino 4 plugins will still work with Rhino 5. There's no need to port. The only hiccup might be if you're using a native 64 bit version of the Rhino 5 WIP, but other than that everything should work fine.

[dalomar_cg]

Re: 5 wip

I realized that my response above is a little misleading. There is no need to port the CURRENT version of VfR as it already works in v5. Future development of VfR will take v5 into consideration. Although McNeel has said that there will not be any breaks in the SDK for v5 there will still likely be some additions to the v5 SDK that we will look to take advantage of. As of right now, future development of VfR will be for both v4 and v5, although chances are the v5 will not be released by the time we are ready for releasing the next full version of VfR.
Once we start having betas of the next full version of VfR there will likely be separate VfR4 and VfR5 builds as well as 32 bit and 64 bit builds of VfR5. Sorry for any confusion from my previous post.

[kylefoster]

Re: 5 wip

I think that the biggest change to Rhino 5 from V4 is the ability to use more ram when using the 64 bit version. Due to this, shouldn't this be the highest priority when considering what features will be added to the next version of VFR?

Could you hazard a guess as too when this might be achieved? Might it be in the next few weeks or the coming months? I don't mean to sound so impatient, I'm simply excited to be able to render and more importantly animate larger models but I'm slightly surprised that ASGVIS and MCneel haven't 'teamed-up' to bring beta versions of both V5 and VFR5 at the same time.

kyle foster

[Micha_cg]

Re: 5 wip

Could you hazard a guess as too when this might be achieved? Might it be in the next few weeks or the coming months?

I prefer continous improvements of current final releases instead to much beta testing of brand new releases. It's a pity, that it's not a general goal to get bug fixes releaes within a few weeks only. Working around bug for months is quite annoying. But what I learned about software developement is (better - I try to learn ), don't expect anything and be happy if something is moving.

[dalomar_cg]

Re: 5 wip

Kyle,

I'm not sure how a WIP build of Rhino 5 being available for 64 bit means a change in our priorities for V-Ray development. The ability to use more RAM really doesn't affect what is a useful feature or not. Considering that the large majority of Rhino users aren't on 64 bit systems, and are not very likely to move towards them, we can't assume that our users will have infinite memory to use for rendering. There are practically no barriers for us to have 64 bit builds of V-Ray in the future, we just aren't in a place to be able to create a 64 bit build of older versions.

No I can't guess...that's why I didn't. I've gotten myself in trouble by guessing in the past, so I have generally tried to refrain from liberal guessing since then. Regardless of what I tell you, it will be out when its out. Its just a matter of build up or hype before it. Some people like the 2 week media frenzy before the Super Bowl...some don't. I don't seen any reason to throw timeframes out there when I honestly have no idea. Generally though, if I don't have an idea it is definitely not be on a timescale of "weeks"

There is no practical business reason why McNeel and ASGvis should coordinate our development cycles. We are structured differently, approach development in different ways, have different timeframes in terms of development, and have different goals in terms of our development. That's not to say we haven't known about McNeel's development cycle or communicated on aspects of our development cycle, but there really isn't a need for us to coordinate those efforts. For what its worth, knowing McNeel's development cycles and ours, it will likely be that VfR2 will be released before V5 will.

Micha,

You've expressed this before and I understand where you coming from with this. The hardest thing to understand about software development is that its extremely context driven and that that context changes from company to company, platform to platform, application to application, feature to feature, and developer to developer. A number of those things that I listed are changing right now...all for the better. You may not be able to point a figure at one thing to see the benefits, but they will certainly shape V-Ray in the builds to come.

[Micha_cg]

Re: 5 wip

If I would be a software tester, than I would use this general criteria:

* time for critical bug fixes
* time for little improvements without big coding (like move some buttons at the UI for workflow improvement or fixing website problems)
* time for adding new features
* general quality&stability
* development by "thinking like an user or like a programmer"?

I'm curious, where we can see improvements.

[Micha_cg]

Re: 5 wip

Today I have seen this thread:

http://forums.cgsociety.org/showthre...5&page=1&pp=15

Quote: "Yes, all are 3d plants and poly count is 900,000,000 triangles"

We are so far away from this polycount.

[dalomar_cg]

Re: 5 wip

* time for critical bug fixes
* time for little improvements without big coding (like move some buttons at the UI for workflow improvement or fixing website problems)
* time for adding new features
* general quality&stability
* development by "thinking like an user or like a programmer"?

All those areas should have anywhere from some improvement to a very large improvement....most of them towards the very large end of the spectrum. The website is not ]
Quote: "Yes, all are 3d plants and poly count is 900,000,000 triangles"

We are so far away from this polycount.
[/quote]

I'm not sure exactly how this is a part of this discussion, but I guess the answer would be yes. Since a 64 bit version will have access to as much memory as possible, then if you've got the memory to do it you can render that many polys. I've also stated a number of times that Proxies are at the very top of the list for features in VfR2, which will also should allow for that many polys to be instanced around the scene.

[farined]

Re: 5 wip

Hello:

Speaking of V5; after first reading that Vray would work on R5, I jumped the gun and tried to install Vray for R5. I ended up sort of breaking Vray for R4; now every time I start R4, I get the following message:

"unable to locate or load "RHRDK.10.V40.DLL".

I read the postings regarding that issue, however, I am not sure there is a clear answer to the problem.

Some of my following questions may have already been answered, but here it is:

If I uninstall Vray, can I simply re-install it(on the same machine), and will it cause problems with the validation?

If I uninstall the RDK, and re-install it; will it cause problems for Vray?

The above questions would not be an issue if the validation could be done online as it is with some software companies (I am not sure what the reason is for not deploying such a system? from my point of view, I could uninstall and re-install as many time I need to in the event I were having problems with my system or anything else.

The following is OT although very important from a support stand point.

I read somewhere that the website is undergoing some modification/improvements.

Question:
Any ideas when those changes will be implemented? I realize that you guys are in the business of improving Vray, and not designing sites. However,it is currently very difficult to navigate the site ( I had to Google to find the download page (repository).

Regardless of the little problems I am having at the moment, I still think that Vray is class 1 renderer.

Farid

[dalomar_cg]

Re: 5 wip

Installing the V5 WIP should automatically find all of the v4 plugins that you have loaded and load them up in v5. Therefore, there should not be any reason to "reinstall" for v5 as V-Ray should just be there. The other thing is that RDK is now installed as part of V5, so if you had an older build of V-Ray with an older build of RDK, that may be the issue.

The dialog that you're seeing was from back when we were having conflicts with RDK, so I'd some how try and check to see what version of V-Ray your running

As to the OT, the website is in the final stages of development and should be released very soon. I'm not the one working on it, so I don't have an exact ETA, but I believe it should be within a few days to a week. I'll see if I can find out a specific launch date tomorrow.

[farined]

Re: 5 wip

Hi Damien:

Thanks for your answer. I went ahead an uninstalled both the RDK and Vray. I re-installed the latest RDK, then did a custom install (unchecked the RDK). The process went pretty smooth. Rhino4 starts without any trouble.

Regarding R5, I went to the render menu to see if I could select Vray instead of the default Rhino Render, but it was not available. I checked the Plugin under the Rhino Option window, but I did not see it listed. Any ideas on how to load Vray in R5? If it is not possible, I'll keep using R4 to render.

Back to the OT conversation; I think that is great news. Not to worry about the exact release date, as long as we know that it will be available in a soon future.

Thanks

Farid