Unity VaM 2 [v1.1.1 Beta] [Meshed VR]

[wagnington]

I have the oculus with steam vr and alvr. For the life of me I cant get the xr to work. Kinda sucks but the models look nice at least. hopefully they will implement a library functiion so we can test our own models.

 

[cyberpunkspike]

VAM 1.xx is a single-threaded app so its been severely limited by single core clock speeds since inception. It's always run poorly even on the best hardware, and there's almost nothing you can do about it since even a brand new high end CPU is maxing out at ~5ghz, not much faster than an overclocked 7700k from 5 years ago.

It's a very, very poorly optimized application, thus why VAM 2.x is a pretty significant rewrite. If it means all old content is dead it will be worth just for multithreading and async. It will be a painful transition, but perhaps there will be some tools to help convert old content. I'm sure even in the best cases lots of stuff will be broken on conversion, but the bandaid really needs to be pulled because VAM 1.xx is a shit show and always has been.

While old content will need to be refactored significantly, it doesn't mean that it couldn't be automatically converted in part or whole, once we know the new format structure. If I'm not mistaken, 2.0 is based on the Daz Gen8 model, it is possible to convert between Gen 3 and 8, it's just a PITA because not everyone has the same start and end point in any given process. However., we actually do share the same start and end points, when talking specifically VAM content. I suspect a script can be written without an insane amount of effort, because of that fact, but 2.0 would have to be ready first.

 

[Taylor 2047]

I really don't want to interrupt the helpful discussions above, but does anyone notice any significant improvements in rendering from this VaM alpha 2, compared with VaM 1? I really mean "significant".

 

[nevermesh]

I really don't want to interrupt the helpful discussions above, but does anyone notice any significant improvements in rendering from this VaM alpha 2, compared with VaM 1? I really mean "significant".

I'm not sure what you mean by improvements in rendering. For me things are much snappier and load faster, but this is most likely due to Alpha being so bare bones. The usage of G8 models look much better than what we currently have and though the lighting is pretty basic in the alpha, I feel like it is still a great improvement. The UI on the other hand hopefully doesn't stay the same.

 

[Blessuall]

I really don't want to interrupt the helpful discussions above, but does anyone notice any significant improvements in rendering from this VaM alpha 2, compared with VaM 1? I really mean "significant".

performce got improve but to tell significant it dont look like that.

 

[ddictsch]

I have the oculus with steam vr and alvr. For the life of me I cant get the xr to work. Kinda sucks but the models look nice at least. hopefully they will implement a library functiion so we can test our own models.

I have a different problem using HP Reverb G2. I'm not able to use VR. On the contrary, it works perfectly on normal version (1.x), in that case there are two separates executables, one for the desktop and the other for vr. May it be the problem? Is there any part of the code I'm missing? because desktop part works fine for the beta version

 

[ddictsch]

I have a different problem using HP Reverb G2. I'm not able to use VR. On the contrary, it works perfectly on normal version (1.x), in that case there are two separates executables, one for the desktop and the other for vr. May it be the problem? Is there any part of the code I'm missing? because desktop part works fine for the beta version

I answer myself. It is an option called xr. Now I'm able to use vr...

 

[lolmao500]

I really don't want to interrupt the helpful discussions above, but does anyone notice any significant improvements in rendering from this VaM alpha 2, compared with VaM 1? I really mean "significant".

VAM 1.0 runs like garbage on my rig, basically unplayable and it runs smoothly on Vam 2.0 so I would say yes

 

[wagnington]

pretty sure it runs better because vam 1x only uses one core on the processor.

 

[Blessuall]

can wait its support old plugin and vars file !! damn must be good for dancing. fingers now have more bones.

 

[Kniffo]

pretty sure it runs better because vam 1x only uses one core on the processor.

in desktop mode the performance on my i9 9900k is very bad. In V 1 I mostly have frames around 150, also with several people and in moving scenes. In V 2 I have just about 60 fps and that with one person and she doesn't move. So I don't have much hope in V2. And I can't tell that the graphic difference is sooooo big...

 

[wagnington]

The graphic difference is big....it uses g8. It uses more cores. G8 means it has greater potential. You say you cant tell the difference. Did you see the environment scene? It looks ultra realistic. You are capping at 60 you either need to tweak your settings, check your components, or wait because unity is annoying as hell. I have problems with xr so it probably is a unity problem. Don't sass me just because you're mad I was just stating facts.

 

[Pimpim]

in desktop mode the performance on my i9 9900k is very bad. In V 1 I mostly have frames around 150, also with several people and in moving scenes. In V 2 I have just about 60 fps and that with one person and she doesn't move. So I don't have much hope in V2. And I can't tell that the graphic difference is sooooo big...

Same for me around 60fps with a RTX 2080 at 100% load.
In the Scene with the 4 room appartment I get over 250fps before the GPU once again is the bottleneck.

Got a 3900x cpu and it is at 18% usage (7% from other applications). Uses mostly two threads. So the CPU requirements is pretty low as long as you have two cores that can handle a heavy load.
This could be subject to change when more physics and charactermodels is used.

Less than 8gb ram is used for the scene so maybe a little bit more with two people. So a system with 16gb memory should be more than enough.

But yeah if you want to run this game in 4K with frame rates above 60fps you are going to need a graphics card that is faster than a RTX 2080. This is a major bottleneck for me and I guess it is the same for you.

Compared to VAM I get around 45fps on a scene Im testing on. GPU is around 18%. No CPU core is above 30% load and entire load on the CPU is around 24%. I even have RTX turned on in VAM. My guess is that there is something with having a massive library of content in VAM that slows it down. Mine is currently at 655gb. Could also be something with the cache folder being massive and not wiped out for some time.
It uses 15gb ram for me so it is almost twice the ammout of VAM 2. Could this also be because of the massive content library?
Eitherway neither CPU or GPU is the bottleneck so it has to be something with the software.

I think it is way to early to really speculate. We don't know for sure what is going to happen once you add more content into a scene in VAM2. But after seeing the sample scenery I really want this update.... and a new graphics card.

It uses more cores.

I doubt it. From my limited testing it seems it would not even matter unless you are playing this game on an old or slow computer with 6 or 4 cores.

 

[wagnington]

You guys are giving me a headache. Unity is built upon the use of all cores in bursts. It is by nature. Old Vam can ONLY use one core. Im not understanding. The game is being constructed new in Unity. Never had a problem until the new Unity came out. old Unity games played well and then the new build came out with xr. So many problems after that. I dont want to see the same problems. So here is the official info.

You must be registered to see the links

 

[Pimpim]

You guys are giving me a headache. Unity is built upon the use of all cores in bursts. It is by nature. Old Vam can ONLY use one core. Im not understanding. The game is being constructed new in Unity. Never had a problem until the new Unity came out. old Unity games played well and then the new build came out with xr. So many problems after that. I dont want to see the same problems. So here is the official info.

You must be registered to see the links

This is before I start VAM1. As you can see I have other applications using the CPU but mainly only one thread is maxed out.
And some small random load on the other threads. No big deal.



And as you can see VAM1 uses all threads. Some more than others. But it is actually using all cores and all threads.



This is from VAM2. Used the scene without the girl to lower the use of the GPU and max out the use of CPU. But it seems the game is having problems going over 420fps so I can't get any higher load on the CPU.

Before we get to actually use the product we can't really test it out to see the difference in how well the cpu scaling is and my guess is that is is not going to matter at all. My biggest bottleneck is the RTX 2080 that gets maxed out long before my CPU does.

But the theory of VAM1 using only one core is debunked.

 

[damian50]

But the theory of VAM1 using only one core is debunked.

The *actual* developer disagrees with you.

You must be registered to see the links

In here he talks about benchmarking for 1.x being aligned with the single-thread benchmark.

 

[Pimpim]

The *actual* developer disagrees with you.

You must be registered to see the links

In here he talks about benchmarking for 1.x being aligned with the single-thread benchmark.

The developer wrote:
" VaM itself also uses a lot of threads and probably every core will be doing something."

He also wrote:

"The issue is there is a main thread bottleneck and many things in Unity cannot run on threads because they did not write them to be threadsafe. "

Meaning the game uses multiple cores but there is one core that is going to take most of the load. This is the issue with most games today. And when your cpu can't handle that single thread it is going to be the bottleneck.

 

[geogy22]

btw.. this is still a work in progress.

 

[scsi]

btw.. this is still a work in progress.

no way. this can't be

 

[Blessuall]

no way. this can't be

need 2year more i think.