SteamVR

SteamVR

SteamVR Workshop
Customize your SteamVR experience by finding new backgrounds, 3D environments, controllers and base station models.
Learn More
Function Rotating Entities Lose Axis After Starting On Correct Axis
I've been working for several months with func_rotating entities parented to other entities. These have worked without problems until yesterday when every one of them in every test version map that previously worked fine now lose there axis after a few seconds and rotate on some other axis, sometimes switched around 180 degrees, sometimes some other totally uncorrelated axis. I'm at a complete loss as to why this is happening out of the blue after several months with no problems on maps I have not altered for weeks and weeks.
< >
Showing 1-5 of 5 comments
Puffy 32 9 Aug, 2022 @ 4:13am 
For things like that I have been using a pro_dynamic_override. Ticking the "scripted movement" and add a velocity to one of the rotation axis. Not sure why func_rotating has broken for you though.
I just tried loading SteamVR on a different machine and built the test map and it worked there. The I went back to the original machine, built again, and once more the test map worked. I had already tried a reboot on the original machine which did no good. So why it works again on the original machine after doing nothing is crazy! I'll just hope the problem doesn't reappear. I had windows update turned off for the month by the way.
Unfortunately this issue resurfaced again. It shows up randomly after a 12 hour map build. I'm assuming it has something to do with using an enormous number of entities and is therefore probably rare. I'll hope that it will not undo this map and allow me to finish.
Puffy 32 11 Aug, 2022 @ 6:58pm 
Give the prop_dynamic_override a try and parent it to what you want spinning.
The Evil Elvis™ 2 15 Aug, 2022 @ 12:13am 
Thanks for the suggestion. I was able to complete it though without changes. I think the issue is brought about my making changes while a map is compiling. This is something I've done all along and I'd always assume the map was read into another file for the compile. But this problem seems to correlate to this action so I'm assuming that's the culprit.
< >
Showing 1-5 of 5 comments
Per page: 1530 50