Im creating a VR build right now with lots of interactive parts and text labels that use code (making their performance cost a minimum of ~36). Is there any cheap way to reduce performance cost on VR parts without losing functionality or detail?
Im creating a VR build right now with lots of interactive parts and text labels that use code (making their performance cost a minimum of ~36). Is there any cheap way to reduce performance cost on VR parts without losing functionality or detail?
@iPilot none, just scale it to be thin
I think the most disadvantageous one is the hinge as there is no clear way to tell where the actual axle is on it, otherwise all 3 work perfectly fine
the only reason I'd want to use the small rotator is if I want the rotation axis in a very specific location that's floating out in space and not inside the build as the way the part relates connections to its rotation axis is unique
@BaconEggs Besides the size and shape, whats the disadvantages of the old rotator?
I use the old block rotator in most places I can, they have far less perf cost than the others (though there are good reasons to use the other two types)
otherwise just be part efficient that's kinda all you gotta do lol
Is performance cost an actually accurate reflection of impact on performance? I know that turning off calculateDrag helps performance quite a bit, but does performance cost calculation factor in that?
@jamesPLANESii One console panel in my build has a performance cost of 991... To create the labels for the switches on the entire console I used a single text part... the vr parts destroy the performance
Essentially be as part efficient as you can