Search results for query: *

Thank you for all that you do here on the Hub! And congratulations on earning the well deserved Hero badge! It is amazing to have you contribute here consistently for such a long time and at such a high level. The Hub would not be the same without you. I'm truly grateful for your contributions.

You are not entirely wrong, and VaM2 will be similar in some regards. I do very much rely on things like Unity's asset management, UI system, VR integration, and rendering system. But where Unity fails, I'm try to go further. Part of what made VaM different than others is I didn't rely...

That is interesting. I didn't realize that it was possible to get data from Physx on a thread. Yes - anything you can take out of FixedUpdate will directly improve performance! Awesome! If I could officially roll in 3 changes, it would be this, the zip read fix, and the memory/runtime...

There is a setting called Physics Update Cap. This setting specifies the maximum number of Physics Updates that can run per rendered frame. If your FPS is low enough that this cap gets hit, you could experience time slowing down, which will make everything look slo-mo. This is just an...

I'll try. I have another pending request from another user I would like to put in as well. Knowing this is how the zip reader works, I'm tempted to review the rest of the binary reads I do. But I suppose the worst offender is the morphs since there can be a lot of them.

I think the best path is probably you keep developing this and work out the kinks, and possibly at some future point I can roll into application if you are willing to let me do that. If not, it can live on as a side patch. Seriously great work and I'm very impressed!

Each vertex can be processed independently and safely. The skinning sub-threads are split on a range of vertices to operate on. There is no conflict or bug here. If you have come up with a faster method that makes it so using sub-threads with vertex range is faster, that is great, because this...

I can't move original VaM to newer version of Unity which has a much better jobs/burst compile system. Without burst, jobs is useless. Without reorganizing everything into proper structs with proper jobs it is useless. Hence VaM2. And yes using il2cpp breaks the plugin system. It can't work...

Reading the whole var at once needs to be avoided. Some of these are huge. Zip allows random access and is optimal for memory and runtime with large var files. I see in this case it is not optimal if the zip library is not buffering the read blocks with each Read call as I thought it would be...

Wait you are telling me ReadInt32() and ReadSingle() in the original code is actually opening the file every single time? That's insane and I had no idea the zip library would work like that. public void LoadDeltasFromBinaryFile(string path) { //Debug.Log("Loading...

Would you like to join my team?!? :ROFLMAO:

I would consider rolling this back into the main release if you are willing to allow me to do that. I would have to review in case you missed corner cases. It may be dependent on your CPU, but generally my wait time on the side threads is 0. I won't complain about optimizations to the side...

Thanks for doing this! I mentioned on the other thread as well before I realized you had a dedicated one. We reached out to you to see ask to move this to resources where we can flag it for providing a replacement dll. I considered rewriting the morph iteration code you mention but...

I appreciate the effort here. It is very cool what you are doing! A couple of things though. Some of things you are optimizing are running on an asynchronous side thread away from the main thread, and in most scenes the side threads complete before the next physics update and ultimately don't...

Oh I am angry too, but I'm also too far into VaM2 development to change directions. VaM2 will likely be my last Unity project, but VaM2 might also be my last project before retirement anyway if it meets my 10 year lifetime goal.

Oh and to answer your question I do like UE's features like Nanite (not really applicable to VaM, but very cool), Lumen (again it works with static and mostly static objects so not the best case for VaM with moving models as the focus), and MetaHumans (cool, but adding genitals is not that...

I want VaM2 to have at least a 5 year lifetime, and hopefully more like 10. So I don't think there will be a VaM3. By that time AI software will be providing us with holodeck like experiences. :)

I posted this over on Discord this morning in response to the same question: We are way too deep into VaM2 to switch engines now. A change to UE would cost years in development time. This move by Unity is ridiculous and they are facing huge backlash already. If they keep moving forward they are...