Plug in is broken with latest VAM updateHello, could anyone please help with parameters for:
11th Gen Intel(R) Core(TM) i7-1195G7 @ 2.90GHz2.92 GHz
I appreciate any help.
Some still use previous may be?Plug in is broken with latest VAM update
[threads]Hello, could anyone please help with parameters for:
11th Gen Intel(R) Core(TM) i7-1195G7 @ 2.90GHz2.92 GHz
I appreciate any help.
Just dropping in to say thank you for your amazing work. Take your time and enjoy yourself.no, this patch will just revert back to the old vam version, dont use it until I update it
Does anyone know if I install the latest VAM update, how that will impact this?
Can you copy and replace the patch? I assumed it would overwrite the file, but was curious if I could copy it back into the VAM folder once updated.The performance patch modified the 1.22.0.3 version of Assembly-CSharp.dll ([VaM_root]/VaM_Data/Managed/Assembly-CSharp.dll). The latest VaM-update again overwrites that .dll file.
TL;DR - It kills the patch dead. Kaput. Fini.
Does anyone know if I install the latest VAM update, how that will impact this?
Creator was notified about the update by Meshed in advance. He will update in the future. Just wait patiently.Can you copy and replace the patch? I assumed it would overwrite the file, but was curious if I could copy it back into the VAM folder once updated.
Can you copy and replace the patch? I assumed it would overwrite the file, but was curious if I could copy it back into the VAM folder once updated.
got it. It's not a big deal for now. I can wait until it's updated. I haven't done the upgrade yet but am also very particular about plugins I download.Nope. Assembly-CSharp.dll is (a big part of the) the actual program - vam.exe is just the ... ignition? If you update to 1.22.0.7 and then overwrite with the performance-patched 1.22.0.3 version of Assembly-CSharp.dll, you've effectively rolled back to 1.22.03 (In a crude, likely unsafe way, but still).
Mind you - that contraption will actually start, but it still has the security vulnerability. It gets neither faster, nor safer.
TL;DR - it's one or the other.
Doubt it will be much better, I would not. (Running 5600 myself)Do you guys think an upgrade from a 5600x to a 5700x3d is worth? Was considering getting a 5800x3d but just discovered it was discontinued so the price is much higher for the few places you can find them at this point.
I think it's acceptable, as only CC-BY-ND cannot be modified. However, it would be better to contact the creator to avoid any redundant work.Would it be acceptable to mod this patched dll with the changes made in the latest vam dll? That will bring the security up to match the current version.
So post it here on the site! Otherwise we may not see the author anytime soon! Otherwise he can rest until old age!I have created an updated version of this patch for 1.22.0.7. Let me know how I can help with the review.
With permission, of course. This isn't an ordinary plugin.So post it here on the site! Otherwise we may not see the author anytime soon! Otherwise he can rest until old age!
Yes, it's the same. It's from v12 of this patch. v13beta1 was giving me stability issues. I've been using iterations of this since the security patches came out.Does it work the same way?
It would be interesting to take the opportunity and test it!)Yes, it's the same. It's from v12 of this patch. v13beta1 was giving me stability issues. I've been using iterations of this since the security patches came out.
I brought those fixes into this version.
I am also using the v12 as this seems to be the most stable for me compare to 13 beta so i am glad you chose it.Yes, it's the same. It's from v12 of this patch. v13beta1 was giving me stability issues. I've been using iterations of this since the security patches came out.
I brought those fixes into this version.