harnessfatality
@harnessfatality
New Member
Joined: Feb 15, 2024
Topics: 5 / Replies: 12
Reply
RE: Maintain Limit Controllers while assigning Wire Parameters

Hey Domos, Lol right you are, I’m tripping. I’m testing right now and turned out I’ve made an amateur mistake using that “getSubAnim” command

4 years ago
Forum
Reply
RE: Maintain Limit Controllers while assigning Wire Parameters

Okay, so far, I think I’m having issues because Limit Controllers aren’t using world coordinates, they’re using local. Which is annoying, I hope I’m w…

4 years ago
Forum
Topic
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

The problem isn’t speed (like you said) and I apologize for not paying attention, I should’ve read the code but I haven’t studied MaxScript’s syntax y…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

Oh wait POLYTOOLS3D. I didn’t know you used a for loop to set the values of attributes? This is actually faster than Maya’s setAttr… Okay, now I’m con…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

My project was pretty simple in other DCC softwares (Maya and C4D). I’m trying to set values of an attribute in realtime without having to use C++, th…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

PolyTools3D: HarnessFatality: So maybe there’s something wrong behind the scenes that I’m not aware of gc() is a killer. Don’t use it at a…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

Ahh, POLYTOOLS3D. Thanks a bunch for this example code. These are the results I got. time:125ms heap:174892L time:47ms heap:136L So maybe there’s so…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

Hey, so here’s a majority of the algorithm, this algorithm is basically receiving data from a UDP socket/server on a separate thread, and then it send…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

Hey Denis, I will show the rest of the code very soon. Thanks for the help so far, I see little improvements. I’m also convinced I’m doing something w…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

Hey Serejah, yes thanks for calling that out. That’s exactly how the code is but I accidentally left it out. I’ll edit the post

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

Here’s what the code looks like: def on_command_received(self, message): mxs.disableRefMsgs mxs.execute(“””try(undo off– (with redraw of…

4 years ago
Forum
Reply
RE: MAXScript | EXCEPTION_STACK_OVERFLOW The thread used up it's stack

Hey Denis, thanks for replying. I’ve tested “mxs.disablerefmsgs” and it didn’t seem to help out. Though I don’t know what it’s doing under the hood. A…

4 years ago
Forum
Page 1 / 2