Unless the Updates are provided with separate governing terms, they are deemed part of the Software licensed to you. You are solely responsible for ensuring that your hardware specifications meets BeamNG’s current recommended hardware and software system requirements.Ģ.3 BeamNG may, at its option, make available patches, workarounds, or other updates to this Software (“Updates”). BeamNG excludes responsibility for damages resolution from interaction of the Software with other software.
The Software is provided “as is”.Ģ.2 Also BeamNG cannot ensure the compatibility of the Software with other software. Make sure that you didn’t make an error and are precompressing the beam too much.2.1 BeamNG cannot ensure that the operation of the Software will be uninterrupted or error free or that errors can be corrected. It might also be caused by excessive or excessively quick beam precompression. To fix that issue, refer to the section about fixing instability. You should see vibration happening just as the car spawn. To confirm this, you can look at the stress debug just as the car spawn, using 100x slow motion. This can easily be seen by spawning the car with paused physics and using the stress debug, as the connected beams will appear stressed, even with no precompression.Īn other possibility is instability that stops after some level of deformation has happened. The first possible cause is a missalignement of slidenodes with their rail, causing them to violently return to position on spawn. Major deformation that happens just when the car spawns has a few possible causes. In all cases, the best solution is to include more nodes into the flexbodies nodegroups, or assign additional nodegroups.
If parts of the flexbody are located far away from any of the assigned node, the game will be unable to properly interpolate their position based on node coordinates. If the nodes are all in line or on a flat plane, the game might be unable to map the flexbody to the nodes, and give out a VY error.Īnd the last possible issue is if the nodes don’t properly cover the flexbody. The physics engine needs at the very least 3 nodes, preferably more, assigned to each flexbody to calculate deformation properly.Īn other possible issue is the position of the nodes relative to each other.
This means that the physics engine is unable to properly map the flexbody to the defined set of nodes This has a few possible causes. A VY node error can be seen in console as the following error :įLEXBODY ERROR on mesh MeshName: VY node not found
0 kommentar(er)
