You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to help an acquaintance get VJolt working on their TF2 server (which is hosted on a machine using an Intel Xeon E5-2690 v2, which doesn't support AVX2) I noticed that the binaries output by the SSE2 and SSE4.2 projects use AVX2 instructions, as shown by elfx86exts in the attachment below.
I believe this is caused by the joltphysics_avx2.vpc script setting the VOLT_AVX2 conditional and not unsetting it, causing the SSE2 and SSE4.2 projects to also use the AVX2-specific settings defined in jolyphysics_settings.vpc
The text was updated successfully, but these errors were encountered:
It doesn't seem like any of the forks have fixed this in their releases or "action builds" yet. Is this something easy to do for a novice or can someone explain the basics?
While trying to help an acquaintance get VJolt working on their TF2 server (which is hosted on a machine using an
Intel Xeon E5-2690 v2
, which doesn't support AVX2) I noticed that the binaries output by the SSE2 and SSE4.2 projects use AVX2 instructions, as shown by elfx86exts in the attachment below.I believe this is caused by the
joltphysics_avx2.vpc
script setting theVOLT_AVX2
conditional and not unsetting it, causing the SSE2 and SSE4.2 projects to also use the AVX2-specific settings defined injolyphysics_settings.vpc
The text was updated successfully, but these errors were encountered: