Search results for query: *

- Rebuilt Version 13beta1 to include security fixes for VaM 1.22.0.12

- Rebuilt Version 12 to include security fixes for VaM 1.22.0.12

janie fails to load because of a race condition somewhere in the scene loading, but only occurs if a morph fails to load while the character is loading. You should get some error like "file could not be found .... xxx.vmi" or something. For me it was some weird unrelated .var that contained...

90fps means 1000/90=11.1ms per frame. If your CPU finishes the physics in 3ms, your GPU has 8.1ms to render the scene to not exceed the budget for 90fps. If you have a slow CPU that finishes in 6ms, your GPU must finish all it's work in 5.1ms. So if you have a 7800x3d or 9800x3d with 6000MT/s...

no, this patch will just revert back to the old vam version, dont use it until I update it

since I dont have the source code of vam itself I just hotpatched the dlls and thats actually how I keep my code changes haha

increasing resolution doesnt increase CPU load, but rendering same resolution in VR does. In VR unity has to render each frame twice for each eye, making twice the draw calls which cost CPU. So a CPU is kinda important for it to work well in VR.

king

Just checked the VAM2 alpha2 and it didn't have Single Pass VR Rendering enabled. I guess because it breaks all non-unity shaders and you get a grey screen on one eye and a black screen on the right eye for every shader used. What it does: In VR every frame needs to be rendered twice from two...

you are correct, documentation even states that you can assign 64 CPU cores. Beyond that you need to put the cores into groups and then assign groups of up to 64 cores each to threads.

no, since windows vista you can use more than 32 threads but you need to use another API to assign threads to cores above 32. Also some CPUs are on different NUMA cores and you need to be careful to not split workloads between different NUMAs. I didnt bother to use the other API since I cant...

windows only supports a 32bit mask, so 32 cores. Beyond that you need to use numa and a different API. I didnt expect anyone to have more than 32 cores to use vam since those CPUs have horrible single thread performance.

Intel said that the new platform will be almost exactly the same performance as the last one, but at up to 50% less power usage. Ryzen 9950x3d might actually beat it once it's released in january

exactly as predicted, thanks for confirming my predictions of the X3D-Cache

8000MT/s ram, sheesh, that's not possible on AMD

I really dont think its the matter of GPU. Baseline1 had a frametime of 3.27ms avg, which means out of 1000ms of a second it took just 3.27ms to finish a full vam frame, corresponding to 305fps. The actual fps in baseline1 however was 70fps, here is a chart: The benchmark measures the time...

It's not just about ST score, for VAM it's about memory latency. The unity engine does a lot of physics which is wasn't designed for. The physics simulation does a lot of memory reading/writing in a non-optimized memory layout. Crazy memory speeds or huge caches lower this latency and that's why...

Huge improvement in frame times, the worst is 7.93ms avg in baseline3, which translates into 126fps. You have configured something wrong in your oculus drivers which lock the framerate to 45fps. VAM creates atleast 126fps in all your benchmarks, but only 45fps arrive in your headset for some...

I created a scene with 2 girls, naturalis, some dance animation, 6 lights, softbody and dreamstreetbedroom and I get around 100 fps. The dreamstreetbedroom has no impact on fps for me. If you give me a var I can do some profiling, maybe there is some weird interaction that spins the CPU for some...

you could try previous versions that dont replace the mono runtime.