![liftoff simulator running way slow liftoff simulator running way slow](http://clean-swift.com/wp-content/uploads/2018/03/Edit-Scheme.png)
Finish off your car in any color and enjoy a selection of rims on the house. The brakes, weight, gearbox, turbo, and engine can all be upgraded with superior parts. You can fully modify these values to find the best tuning for your drifts.
![liftoff simulator running way slow liftoff simulator running way slow](https://vhojan.nl/wp-content/uploads/2019/07/vdi-logon-simulator-view-1024x646.png)
TuningĮvery car you buy can be fully tuned turbo, brake balance, front camber, rear offset, and more. There are 26 fully customizable cars available to buy. You can use the points to buy exotic motors like the high-performance Porsche 911 GT. but dForce can't (yet) handle that.See how long you can keep up the drift! The longer you drift, the more your points multiplier increases. The result won't be quite perfect, as the sword would have pushed the clothing as it passed through. To do that without triggering a dForce explosion of the unfortunate character's clothes, you'll need to hide the sword during the simulation.
![liftoff simulator running way slow liftoff simulator running way slow](https://learnassets.getfpv.com/learn/wp-content/uploads/2019/02/22033823/drl-1024x582.png)
Similarly, if the character is sitting or lying on an object, you'll need an Animation Timeline with intermediate keyframes that ensure the character's limbs never pass through the chair, sofa, bed, etc.Īnd sometimes you want a mesh to pass through another mesh, e.g.: if a character has been run-through with a sword. So, for example, if you pose a character with his/her legs crossed, you'll need to do an Animation Timeline with intermediate keyframes that ensure the legs never pass through each other. But the idea is the same: you need to minimize the moving bits in each simulation.Īnother point I left out: dForce will 'explode' if meshes pass through themselves or other meshes. Indeed I don't even bother to set rigid props and other scene elements as Static Surfaces, because dForce treats them as such by default. As for the Start From Memorized Pose option, I only see that if a figure has been set as a dForce Dynamic Surface, and rigid props won't be. Will the curtains, or Adam's or Betty's clothes, collide with that prop as they move during their simulations? If not, you can hide that prop rather than memorizing its rigging. I left out that option because it's context-dependent.
![liftoff simulator running way slow liftoff simulator running way slow](https://forums.flightsimulator.com/uploads/default/original/4X/a/d/7/ad791d1c8837dc9c3a6429ae075936e5762ca0cf.jpeg)
Yes, you can also hide rigged-and-posed props by clicking the Hide Eye switch in the Scene list, or with the Parameters>Simulation>Visible in Simulation switch. That may seem like a lot of extra steps, but the processing time you save by doing individual simulations will more than make up for the set-up time. When you show the CurtainGroup and the AdamGroup, the effects from their simulations will still be there, so you're ready to render! Yet again, Betty and her clothes should be the only visible moving bits. Keep the CurtainGroup hidden, hide the AdamGroup, and show the BettyGroup. Again, Adam and his clothes should be the only visible moving bits. Hide the CurtainGroup, keep the BettyGroup hidden, and show the AdamGroup. I also close DAZ and reopen the scene, to make sure I've cleared the cache. Your curtains should be the only visible moving bits. Hide the AdamGroup and the BettyGroup, then run your simulation. Parent the curtains to the CurtainsGroup, Adam and all his stuff (hair, clothes, props, etc.) to the AdamGroup, and Betty and all her stuff to the BettyGroup. Create three new groups: CurtainsGroup, AdamGroup, and BettyGroup. Hiding a Group will hide every object parented to that group. Now those props are no longer posed, so dForce won't process their movement-to-pose in your simulations. So, do a Memorize Figure Rigging for the half-open door, the half-open window, Betty's shotgun, and any other rigged-and-posed prop that would be static in that moment of your scene: a rigged desk chair that you have tipped back, a rigged clock on the wall that you've posed for the time, a rigged desk with a drawer pulled open, etc. This step matters because a dForce simulation will process every visible rigged-and-posed figure, and that can easily overtax your memory. (1) Memorize Figure Rigging for any rigged-and-posed prop that shouldn't 'move' in your scene. In a scene like this, you would want to do three separate dForce simulations: one for the curtains, one for Adam's clothes, and one for Betty's clothes. Betty is also carrying a rigged prop that you have posed, perhaps a pump shotgun with the slide pulled to chamber a round. Your scene also includes two characters - Adam and Betty - each wearing dForce clothes. If you have multiple figures, even rigged props, you need to hide any that aren't part of a specific simulation.įor example, let's say your set includes a rigged door that you want halfway open, and a rigged, half-open window with curtains that you want blowing outward. I've found dForce is very slow - and crash-prone - unless you limit the simulation.