- #Networkview rpc functions are deprecated how to#
- #Networkview rpc functions are deprecated update#
- #Networkview rpc functions are deprecated code#
This was very inflexible and made it awkward to add or change which user adjustable parameters a part behaviour exposed. Up until now each part behaviour has had a specific pre-created UI with all of its elements (key bindings, sliders, checkboxes, etc.) laid out ahead of time. sloped plates) to make things clearer for the user. I've added a new indicator to show the selected part's bounds during resizing, this was particularly needed for parts that can resize along all three axes (e.g.
#Networkview rpc functions are deprecated how to#
I think I now have a solution for how to handle parts that have multiple linkable behaviours, but I need to start implementing it to really see if it'll work out. I've continued work on the linker tool, creating the first pass implementation of an indicator for it, this can be seen below with some pulleys (notice also the automatic belt routing, sweetness!) And finally, I've lowered the minimum speed for servos and steppers to 1 RPM, as I think it's sometimes useful to be able to go that low. I've also fixed a bug that would sometimes cause a servo motor's centre "resting" angle offset to be incorrect after loading a saved game. Here are a couple of examples, one with a step angle of 45 degrees, one with a step of 180 degrees. Likewise, the stepper motor's step angle can also now be set up to 180 degrees. Now a servo motor's max angle can be set to +/- 180 degrees.
#Networkview rpc functions are deprecated code#
I've now completely re-implemented the angle interpolation code to work a different way, so that it maintains the correct rotational direction. Which meant that for a range of greater than 180 degrees it could easily end up rotating in the wrong direction towards the target angle. It's been suggested that you should be able to set the servo motor target to angles greater than +/- 90 degrees, this was a perfectly reasonable request and sounds like it should have been an easy thing to do! However, due to the way I was interpolating between the servo's current and target angle, it would always rotate through the smallest possible angle. I'm currently working on overhauling the collision impact system to make the sounds behave better, and the plan is that this will improve the damage system at the same time. On a related note, the collision impact sounds have been a source of complaint for some, and I agree! There are too many collision sounds when parts are merely sliding past one another. It still needs more work, but here's an example of the damage system in action as it is right now. This means that adding or removing parts from large constructions is now noticeably faster, but there's still more optimisation work to be done in this area.īeing able to quickly break attachments without causing frame rate drops is a requirement for the damage system, and I've been revisiting this too, fixing a few bugs that had crept in.
I've simplified and optimised the construction modification code and the way attachments are handled.
#Networkview rpc functions are deprecated update#
Here's an update on what's been happening, there's a lot to talk about! Sorry for the radio silence over the last couple of months.
0 kommentar(er)
