Girder.LinkActive not working with Girder 4 alpha

[Rob H]

Not sure whether to report this here or elsewhere, but it seems to be a NetRemote issue.

Girder.LinkActive (actually, in my case, Girder.-1000.LinkActive) persistently remains at 0 even though it's connected to a copy of Girder 4. I also noticed that Girder.-1000.FeedbackLinkActive wasn't present at all, but presumably that doesn't get created until LinkActive is 1?

[danward79]

Hi Rob / Ben

I also noted this the other day, forgot to mention it thou.

In my case it is instance -1001

[Ben S]

I'll take a look guys, this should definitely not be the case. This is only with Girder 4, right?

Regarding FeedbackLinkActive - should this always be on if LinkActive is on for Girder 4? There is no feedback connection, as Girder 4 only uses one socket.

[avid]

Regarding FeedbackLinkActive - should this always be on if LinkActive is on for Girder 4? There is no feedback connection, as Girder 4 only uses one socket.
I would think that for G4, FeedbackLinkActive and LinkActive should just return the same value.

Brian

[Rob H]

That seems fair to me, as long as it's present.

[Ben S]

This is all set, guys. Sorry about that.

Have you guys noticed NetRemote crashing after some time using Girder 4? Mike thinks there is a memory leak with NR when using G4, but I don't see my memory growing at all.

[danward79]

Ben,

Which version? PPC or Win32?

[Rob H]

No, I've not noticed anything like that so far