- Sep 12, 2022
- 1,326
- 657
LMAO dev still partyAny idea if we'll get VAM 2 by the end of 2023?
LMAO dev still partyAny idea if we'll get VAM 2 by the end of 2023?
There is already an alpha I believe but I bet it is not fun to test yet.Any idea if we'll get VAM 2 by the end of 2023?
I think naturalis have to use soft body physics to work properly.Is there a way to add plugins and disable soft body physics by default, in addition to the regular embeded plugins, whenever I load a scene? I want to use Naturalis to increase FPS and make the physics look better but it's a hassle to have to manually do it every time.
You can turn off "Soft Body Physics" per default in VaM's "User Preferences":Is there a way to add plugins and disable soft body physics by default...
According toI think naturalis have to use soft body physics to work properly.
yeah when its off. than suckI think naturalis have to use soft body physics to work properly.
try restart vam or pc. and try restore setting default.Hey guys, recently I think I fucked up something in the menus, and in desktop mode I can't see the rotatino axis or control anything with the mouse. Anyone know how to fix this?
EDIT: I just figured out that they appear when I press ALT? Is there a way to change this? I still can't move points, just rotate them with alt
We'll see indeed but you can say that it's really bothers meshed and he is in bad/disappointment mood. It can affect to development and the time maybe but I don't think he will give up. Any case if it is happens, don't get surprised.Unity-CEO sold his shares of the company roughly a week before the anouncement. They know this is bad.
My guess is that a good chunk of the indie-dev-scene will just delete their projects and leave. Start somewhere else anew.
Mobile games will push more aggressive monetization-schemes.
As for VaM-Development, I am really curious what changes this will bring.
quote from meshedvr on the hub:
" 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 going to face a lot of legal battles, and I would join in on that if necessary. I'm hugely disappointed in Unity and this is killing whatever positivity the Unity brand had left. If I was starting over, I would not choose Unity for the project. I think Unity is going to have to rollback on this proposed change to save face. I don't think it will ultimately affect VaM or VaM2 because I can't see how they can possibly roll this out in the face of such negativity, and I also don't see how they can technically pull off accurate install and revenue numbers without companies self reporting. VaM2 moves forward on Unity. The VaM2 addon kit is Unity based and highly tied to that. I'm not throwing away years of work to start over on another engine. "
I guess we'll see.
ihave 24gb ddr4 3200mhz ram.. this vam eat all 97% .. sometime i load 5people it crash . eroor "to many hips" i plan to update 32gb or 64gb ram 3200mhz ddr4 letter.Is there some kind of trick to reduce RAM usage in VAM? It's taking 7GB without any scene on the background and 27-32GB on basically every scene I load... I already turned off caching and checked both RAM optimizations to unload unused assets.
It's annoying since it causes micro stuttering every 3 seconds due the RAM being fully occupied all the time.
We know that VaM isn't very optimized when it comes to dealing with memory, but those numbers seems to be high. So I've just tested this:It's taking 7GB without any scene on the background and 27-32GB on basically every scene I load... I already turned off caching and checked both RAM optimizations to unload unused assets.
I have 32gb - better update to 64gb right away.ihave 24gb ddr4 3200mhz ram.. this vam eat all 97% .. sometime i load 5people it crash . eroor "to many hips" i plan to update 32gb or 64gb ram 3200mhz ddr4 letter.
I moved a bunch of old "*.var"s to another folder, it helped much with this "too many heap sections" errorihave 24gb ddr4 3200mhz ram.. this vam eat all 97% .. sometime i load 5people it crash . eroor "to many hips" i plan to update 32gb or 64gb ram 3200mhz ddr4 letter.
yeah i think it good deal 64gb.I have 32gb - better update to 64gb right away.
yeah i have almost 2tb var. thas make loading for firstime launch about 10-15minute. second launch decress 5-10minute.I moved a bunch of old "*.var"s to another folder, it helped much with this "too many heap sections" error
Sheez! I bet you use less than 10% on a somehow regular basis, so why keep hoarding all the other unnecessary stuff? And 10-15 minutes starting time...?! Like what the actual fudge? It takes about 60 seconds to start VaM in Desktop mode and load the default scene on my end -- with a 4-5 year old rig!yeah i have almost 2tb var. thas make loading for firstime launch about 10-15minute.
Sheez! I bet you use less than 10% on a somehow regular basis, so why keep hoarding all the other unnecessary stuff? And 10-15 minutes starting time...?! Like what the actual fudge? It takes about 60 seconds to start VaM in Desktop mode and load the default scene on my end -- with a 4-5 year old rig!
Spoiler alert: those 64gb memory will not help you with that...
yeah looks like i will put old var or deleted permanently. on fresh vam it just take a view minute bout 10-30second for startup. but until i put all my 1.5tb var+++ it mess my loading . i will keep upgdrade my ram to higher . for another program and games too. hiksSheez! I bet you use less than 10% on a somehow regular basis, so why keep hoarding all the other unnecessary stuff? And 10-15 minutes starting time...?! Like what the actual fudge? It takes about 60 seconds to start VaM in Desktop mode and load the default scene on my end -- with a 4-5 year old rig!
Spoiler alert: those 64gb memory will not help you with that...
Thanks a lot for your detailed explanation and testing. I guess there is no use other than upgrading the RAM to 64GB to prevent the stuttering issues. Or maybe delete old vars but then again I would be scared to ruin dependencies of other scenes...kinda an odd spot rn.We know that VaM isn't very optimized when it comes to dealing with memory, but those numbers seems to be high. So I've just tested this...