Had some issues with the update from Obi Rope 6 -> 7 in a project that used Obi Rope 6.  Luckily it's a scratch project.

1.  I tried upgrading on top of the old version but saw script errors so I removed all Obi files and installed fresh instead.  Of course, I have scripts and prefabs that depend on the older Obi files, so all of those break in the process of installation.  Even after the other issues were patched below, my existing code runs into Index Of Of Range errors on trying to load my existing rope blueprints, so now I have to see if it's a code issue or a blueprint schema change issue.  [Edit: I see the forum update guide says you have to regen blueprints.  I'm creating them from code, see below.]

2.  The demo scenes use a resource script called FPSDisplay.  It does not use a namespace, so it conflicted with another script I already had called FPSDisplay.  This caused compilation errors and breaks the script references in scenes that used either one (my existing scenes, as well as your demo scenes.)  Even after I added a namespace to my existing FPSDisplay, the script references were broken, so I had to add a namespace to your file and re-add it to the demo scene objects.  I thought Unity demanded all assets used namespaces to avoid this sort of conflict.  [Edit:  Similar breakage on SlowmoToggler which does not have a namespace (I have no such script but your demo scene had a broken link to it and Unity couldn't find it until I added one).]

3.  Many of your demo scenes use a built-in diffuse material for many objects.  Please define your own material for these objects, so that when I update all materials to URP these objects don't remain pink.

4.  There is no longer a type for ObiFixedUpdater.  I had a script that expected this type to force a regeneration of ropes (as I would deactivate and reactivate ropes in proximity to the player).  The CHANGELOG says all ObiUpdater types have been removed.  No guidance on what to do about scripts that referenced them.

Quote:NullReferenceException: Object reference not set to an instance of an object
Obi.ObiRopeCursorEditor.DrawGizmos (Obi.ObiRopeCursor cursor, UnityEditor.GizmoType gizmoType) (at Assets/Plugins/Obi/Editor/RopeAndRod/ObiRopeCursorEditor.cs:75)

Quote:IndexOutOfRangeException: Writing to index 0 is out of range of '0' Capacity.
Obi.ObiNativeList`1[T].set_Item (System.Int32 index, T value) (at Assets/Plugins/Obi/Scripts/Common/DataStructures/NativeList/ObiNativeList.cs:98)
Obi.ObiActor.LoadBlueprintParticles (Obi.ObiActorBlueprint bp) (at Assets/Plugins/Obi/Scripts/Common/Actors/ObiActor.cs:995)
Obi.ObiActor.LoadBlueprint (Obi.ObiSolver solver) (at Assets/Plugins/Obi/Scripts/Common/Actors/ObiActor.cs:1161)
Obi.ObiRope.LoadBlueprint (Obi.ObiSolver solver) (at Assets/Plugins/Obi/Scripts/RopeAndRod/Actors/ObiRope.cs:187)
Screenplay.TightRope.Generate () (at Assets/__SHARED__/Scripts/For/Obi/TightRope.cs:109)
Screenplay.TightRope.Start () (at Assets/__SHARED__/Scripts/For/Obi/TightRope.cs:45)

Good morning,

I created a code to grasp an obiRope. It is not the first time i use it and untill now it worked fine, I have anotehr simulation that uses the same logic and I have no issues. 
Now when the simulation starts the obiActor is not loaded in the script, even if i associated the code to it or passed it as a reference. 
The grasping works but badly, and I think it is because of this issue.  
the code:
```
using UnityEngine;
using Obi;
using System.Collections.Generic;

[RequireComponent(typeof(ObiActor))]
public class DistanceAnchor : MonoBehaviour
{
    public ObiActor actor;
    public ObiParticleAttachment attachment;
    public Transform anchor;
    public float anchorRadius = 0.5f;
    private ForcepsControl forcepsControl;

    private int groupIndex;
    private bool isGrasping;
    public bool IsGrasping
    {
        get { return isGrasping; }
    }
   

    void Awake()
    {
        actor = GetComponent<ObiActor>();
        forcepsControl = FindObjectOfType<ForcepsControl>();
        if (forcepsControl != null)
        {
            forcepsControl.OnRestPositionReached += CheckAndAnchorParticles;
            forcepsControl.OnReleasePositionReached += Release;
        }
    }



    void CheckAndAnchorParticles()
    {
        if (!actor.isLoaded)
        {
            Debug.LogError("Actor is not loaded");
            return;
        }

        for (int i = 0; i < actor.solverIndices.count; ++i)
        {
            int solverIndex = actor.solverIndices[i];
            float distance = Vector3.Distance(actor.GetParticlePosition(solverIndex), anchor.position);
            Debug.Log($"Distance to Anchor: {distance}, Grasping State: {isGrasping}");
            if (distance < anchorRadius && !isGrasping)
            {
                Grasp(actor, i);
            }
        }
    }



    private void Grasp(ObiActor actor, int index)
    {
        if (attachment != null)
        {
            Destroy(attachment);
        }

        attachment = actor.gameObject.AddComponent<ObiParticleAttachment>();
        attachment.target = anchor; // Attach to the anchor
        attachment.particleGroup = actor.blueprint.AppendNewParticleGroup("GraspedParticles");
        groupIndex = actor.blueprint.groups.Count - 1; // Ensure it's the last added group
        attachment.particleGroup.particleIndices = new List<int> { index };
        attachment.compliance = 0;
        attachment.attachmentType = ObiParticleAttachment.AttachmentType.Static;
        isGrasping = true;

        actor.solver.RemoveActor(actor); // Refresh the actor in the solver
        actor.solver.AddActor(actor);
    }
    private void Release()
    {
        if (attachment != null)
        {
           
            Destroy(attachment);
            actor.blueprint.RemoveParticleGroupAt(groupIndex);
            actor.solver.RemoveActor(actor); // Refresh the actor in the solver
            actor.solver.AddActor(actor);

            isGrasping = false;
        }
    }


    void OnDestroy()
    {
        if (forcepsControl != null)
        {
            forcepsControl.OnRestPositionReached -= CheckAndAnchorParticles;
            forcepsControl.OnReleasePositionReached -= Release;
        }

        // Ensure to release any grasped particles
        Release();

        // Additional cleanup if needed
        if (attachment != null)
        {
            Destroy(attachment);
            attachment = null;
        }
    }
}
```

the error: 

```
Actor is not loaded
UnityEngine.Debug:LogError (object)
DistanceAnchor:CheckAndAnchorParticles () (at Assets/Scripts/DistanceAnchor.cs:39)
ForcepsControl:UpdateThimbleRotation () (at Assets/Scripts/ForcepsControl.cs:70)
ForcepsControl:Update () (at Assets/Scripts/ForcepsControl.cs:51)

NullReferenceException: Object reference not set to an instance of an object
DistanceAnchor.CheckAndAnchorParticles () (at Assets/Scripts/DistanceAnchor.cs:43)
ForcepsControl.Update () (at Assets/Scripts/ForcepsControl.cs:48)
```

Hello,

I have a logic where I need to change the ropes material during runtime. I tried setting obiRopeExtrudedRenderer.material = new Material(copyFrom); it looks like the material is changed in the component itself but it doesn't effect the renderer. I assume this is cached on start. Is there a way to do this?

Thanks

Good morning,
I’m encountering a strange issue with grasping a closed-loop ObiRope using two tools. My goal is to grasp different points on the rope with each tool, without using constraints.
The Problem:

• If I grasp the rope with the left tool first and then with the right tool, everything works as expected. Both tools hold their grasping points correctly.
  
• However, if I grasp the rope with the right tool first and then with the left tool, the following happens:
  • The right tool keeps its constraint but the grasped particle shifts to a position far away from the intended grasping point, while still visually connected to the tip of the tool.
    
  • The rope responds to tool movements but maintains this unnatural offset for the right tool.
    
• The issue only happens when the right tool is the second to grasp, and it occurs inconsistently.
  

• Confirming the attachments are created dynamically at runtime without pre-existing constraints.
  
• Checking that particle indices are updated correctly during grasping.
  
• Ensuring the tools have unique attachment components.
  

• The left tool is holding the rope correctly.
  
• The right tool exhibits the described offset issue when grasping second.
  

Helloo, this occurred quite a while back for me and I've been able to work around it but I thought I might as well see if it can be fixed!

as you can see (though they are quite small) the handles and particle sphere gizmos that appear while in the rope blueprint path editor were at some point shrunk by me... and I'm not sure how to unshrink them as the regular 3D gizmo size slider doesn't seem to affect them. 

Thanks!

Attached Files

Thumbnail(s)
       

Hey, I would like to, in my VR app, make a barrier belt, like in cinemas at the box office or airports to cordon off aisles.







This is my script that I made along the lines of a similar script I found in examples (grapling hook) (I cannot post it in the message because of error)
https://pastebin.com/sC54e9fh





I noticed three main problems:


1.  A visual bug, as if the UV scale increases indefinitely. I have no idea what this could be. (video in attachments)

































2. Particles are not forming where the Rope length has been increased. You can see better in the screenshot what I mean.











3. When I move an object quickly in the editor, the Obi Particle Attachment doesn't seem to keep up. Does this problem only occur in the editor? Is there any way to improve it? (video in attachments)











4. When I select the ‘Roll-Out Rope’ object on the hierarchy then I get a spam on the console:

I am experiencing the exact same issue as the one in the following post. What has been done about this issue?
https://obi.virtualmethodstudio.com/foru...-4391.html

I also noticed one thing. When using multiple Skinned Cloths for one Obi Solver, if I use the same blueprint for all of them, the problem does not occur. So in your sample scene there is no problem. The problem occurs when you use different blueprints.

Hi,

In my game, you can jump on and swing from ropes. When your rope grab collider hits a particle on the rope, I move that particle to a specific position and then create an attachment (triggered when the rope grab collider hits any particle on the rope):

Hello,

I recently upgraded from V6 to V7.0.3. I have a world where there can be a lot of ropes around but if player is not engaging with them they are mostly static and standing there. Even though they are not doing anything visibly they were consuming a lot of resources and costing me lots of FPS. In v6 I had a system, if a rope is players out of range I just removed the ropes solver from the ObiFixedSolver list and it was being perfectly rendered, stayed in the world but just didn't do any calculations until player gets close to the rope. This approach saved me a lot of FPS.

Now after 7.0.3 upgrade since ObiFixedSolver is no more, I don't have any way to do this. I can manually disable ropes Obi Solver but now it is completely removed from the world and no longer rendered if I do that. Do I have any way to turn the simulation off for a specific rope while keeping it rendered in the world?

Thanks in advance.

Hello!

I have a Rope with two static attachments on it's endings. 
I need to periodically show this rope in different places of the scene, between different objects in space. 
I use only one rope, simply turning it and it's attachments off and on when needed (by gameobject.setActive). The problem is that if you turn it on, pause for half a second, for example, and then move the attachments to the desired positions, then everything is ok, rope moves there it should be (with wild stretching, but ok). 

But if you turn it on and immediately give the attachments new positions, then the rope don't moves from its place.

What is the best way to move the attachments (these are ordinary empty Transforms) so that the rope immediately moves to the desired place and stays there until the next turn off?